High-Performance Process

Manager Control Theory

HP09
R688
08/2019
 Notices and Trademarks
Copyright 2019 by Honeywell International Sárl.
Release 688 August, 2019
While this information is presented in good faith and believed to be accurate, Honeywell disclaims
the implied warranties of merchantability and fitness for a particular purpose and makes no
express warranties except as may be stated in its written agreement with and for its customers.
In no event is Honeywell liable to anyone for any indirect, special, or consequential damages. The
information and specifications in this document are subject to change without notice.
Honeywell is a registered trademark of Honeywell International Inc.
Other brand or product names are trademarks of their respective owners.

Honeywell Process Solutions

1860 W. Rose Garden Lane
Phoenix, AZ 85027 USA
1-800 822-7673

ii HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 About This Document
This document describes how to use the High-Performance Process Manager (HPM).

ATTENTION
With TPN R684, Enhanced Universal Control Network (EUCN) is introduced.
In EUCN, the traditional coaxial cable system is no longer utilized and is
replaced with a Fault Tolerant Ethernet (FTE) based communication network.
Throughout the document, unless specifically mentioned, the terms HPM,
NIM, and UCN are interchangeably used with the terms EHPM, ENIM, and
EUCN respectively.

ATTENTION
With TPN R686, the Enhanced Network Bridge (ENB) is introduced. The
ENB is a variant of the NIM that allows communication between the LCN and
both UCN and EUCN networks. It can communicate over coaxial-based UCN
and FTE-based EUCN communication networks and provides a gateway
function between the UCN and the EUCN. The ENB also facilitates on-
process migration from HPM to EHPM (assuming you have redundant
HPMs).

ATTENTION
Beginning with TPN R686, Fieldbus support is withdrawn.

Release Information
Document Name Document Release Publication
ID Number Date

High-Performance Process Manager Control HP09 R688 08/2019

Theory - HP09

Document Category

Configuration

R688 HPM High-Performance Process Manager Control Theory iii

08/2019 Honeywell
References

References
The following list identifies all documents that may be sources of reference for material discussed
in this publication.

Document Title Doc ID

PM Family Parameter Reference Dictionary XPM09

iv HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 Support and Other Contacts

Support and Other Contacts

For support, contact your local Honeywell Process Solutions Customer Contact Center
(CCC). To find your local CCC visit the website, https://www.honeywellprocess.com/en-
US/contact-us/customer-support-contacts/Pages/default.aspx.

R688 HPM High-Performance Process Manager Control Theory v

08/2019 Honeywell
vi HPM High-Performance Process Manager Control Theory R688
Honeywell 08/2019
 Symbol Definitions

Symbol Definitions
The following table lists those symbols used in this document to denote certain conditions.

Symbol Definition

ATTENTION: Identifies information that requires special

consideration.

TIP: Identifies advice or hints for the user, often in terms of

performing a task.

REFERENCE -EXTERNAL: Identifies an additional source of

information outside of the bookset.

REFERENCE - INTERNAL: Identifies an additional source of

information within the bookset.

CAUTION Indicates a situation which, if not avoided, may result in equipment

or work (data) on the system being damaged or lost, or may result in
the inability to properly operate the process.

CAUTION: Indicates a potentially hazardous situation which, if not

avoided, may result in minor or moderate injury. It may also be used
to alert against unsafe practices.
CAUTION symbol on the equipment refers the user to the product
manual for additional information. The symbol appears next to
required information in the manual.

WARNING: Indicates a potentially hazardous situation which, if not

avoided, could result in serious injury or death.
WARNING symbol on the equipment refers the user to the product
manual for additional information. The symbol appears next to
required information in the manual.

WARNING, Risk of electrical shock: Potential shock hazard where

HAZARDOUS LIVE voltages greater than 30 Vrms, 42.4 Vpeak, or
60 VDC may be accessible.

R688 HPM High-Performance Process Manager Control Theory vii

08/2019 Honeywell
Symbol Definitions

Symbol Definition

ESD HAZARD: Danger of an electro-static discharge to which

equipment may be sensitive. Observe precautions for handling
electrostatic sensitive devices

Protective Earth (PE) terminal:. Provided for connection of the

protective earth (green or green/yellow) supply system conductor.

Functional earth terminal: Used for non-safety purposes such as

noise immunity improvement. NOTE: This connection shall be
bonded to Protective Earth at the source of supply in accordance
with national local electrical code requirements.

Earth Ground. Functional earth connection. NOTE: This

connection shall be bonded to Protective Earth at the source of
supply in accordance with national and local electrical code
requirements.

Chassis Ground: Identifies a connection to the chassis or frame of

the equipment shall be bonded to Protective Earth at the source of
supply in accordance with national and local electrical code
requirements.

viii HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 Contents

1. HPM CONTROL HARDWARE THEORY OF OPERATION ..........27

1.1 Introduction .................................................................................................. 27
1.2 HPM Module .................................................................................................. 29
1.3 I/O Subsystem .............................................................................................. 29

2. CONTROL PROCESSING THEORY OF OPERATION ................33

2.1 Control Functions ........................................................................................ 33

3. I/O POINTS....................................................................................39
3.1 I/O Points Background................................................................................. 39

4. HIGH AND LOW LEVEL ANALOG INPUT POINT .......................41

4.1 AI Points Functional Overview ................................................................... 41
4.2 Analog-to-Digital Conversion ..................................................................... 43
4.3 PV Characterization ..................................................................................... 49
4.4 PV range checking and filtering ................................................................. 49
4.5 PV source selection ..................................................................................... 50
4.6 Alarming ........................................................................................................ 51

5. SMART TRANSMITTER INTERFACE POINT ..............................53

5.1 STI Point Functional Overview ................................................................... 53
5.2 Parameter comparisons .............................................................................. 57
5.3 PV Characterization ..................................................................................... 60
5.4 PV Range Checking and Filtering ............................................................... 63
5.5 PV Source Selection .................................................................................... 65
5.6 Alarming ........................................................................................................ 65
5.7 Smart Transmitter Communication Modes................................................ 66
R688 HPM High-Performance Process Manager Control Theory ix
08/2019 Honeywell
1 HPM Control Hardware Theory of Operation
1.1 Introduction

5.8 Database Considerations .............................................................................66

5.9 Point States ...................................................................................................68
5.10 STI IOP Commands.......................................................................................69

6. ANALOG OUTPUT POINT ........................................................... 71

6.1 AO Point Functional Overview ....................................................................71
6.2 Direct/Reverse Output ..................................................................................73
6.3 Calibration Compensation ...........................................................................74
6.4 Disable Output Alarming when Using Open-Line Detection ....................75
6.5 Pre-determine the mode of the point when error occurs in IOL/IOP
communication .............................................................................................75

7. DIGITAL INPUT POINTS .............................................................. 77

7.1 DI Points Functional Overview ....................................................................77
7.2 Status Digital Input Point .............................................................................80
7.3 Latched Digital Input Point ..........................................................................85
7.4 Accumulation Digital Input Point ................................................................85
7.5 Sequence of Events Digital Input Point ......................................................87

8. DIGITAL OUTPUT POINT ............................................................ 93

8.1 DO Point Functional Overview ....................................................................93
8.2 Pulse Width Modulated DO Point ................................................................94
8.3 Status DO Point.............................................................................................96

9. PULSE INPUT POINT .................................................................. 99

9.1 Pulse Input Point Functional Overview ......................................................99
9.2 PVCALC .......................................................................................................101

10. SERIAL INTERFACE POINT...................................................... 103

x HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 1 HPM Control Hardware Theory of Operation
1.1 Introduction

10.1 Serial Interface Point Functional Overview ............................................. 103

10.2 Serial Input Point Operation ...................................................................... 104
10.3 Serial Input Point Configuration ............................................................... 105

11. SERIAL DEVICE INTERFACE ....................................................107

11.1 Serial Device Interface Functional Overview........................................... 107
11.2 Manual/Auto Station Interface .................................................................. 108
11.3 Toledo Weigh Scale Interface ................................................................... 114

12. ALARMING THEORY OF OPERATION .....................................117

12.1 Alarming Function ...................................................................................... 117
12.2 Contact Cutout Function ........................................................................... 118
12.3 Process Alarm Rebroadcast ..................................................................... 121
12.4 Red Tagging ................................................................................................ 123
12.5 Write Lockout ............................................................................................. 123

13. DIGITAL COMPOSITE POINT ....................................................125

13.1 Functional Overview .................................................................................. 125
13.2 Point States ................................................................................................. 128
13.3 Mode Attributes .......................................................................................... 131
13.4 Interlocks .................................................................................................... 131
13.5 Digital Inputs ............................................................................................... 135
13.6 Current Input State (PV)............................................................................. 139
13.7 Alarming ...................................................................................................... 141
13.8 Change-of-State Events ............................................................................. 143
13.9 Commanded State (OP) ............................................................................. 143
13.10 Digital Outputs ............................................................................................ 147
13.11 Read Back Check ....................................................................................... 152
13.12 Initialization Manual ................................................................................... 153
R688 HPM High-Performance Process Manager Control Theory xi
08/2019 Honeywell
1 HPM Control Hardware Theory of Operation
1.1 Introduction

13.13 Local Manual Indication .............................................................................156

13.14 Maintenance Statistics ...............................................................................156

14. LOGIC POINTS .......................................................................... 159

14.1 Functional Overview ...................................................................................159
14.2 Configuring a Logic Point ..........................................................................160
14.3 Logic Block Algorithms .............................................................................166

15. PROCESS MODULE DATA POINT ........................................... 187

15.1 Functional Overview ...................................................................................187
15.2 Sequence Programs Overview ..................................................................189
15.3 Unit Partitioning ..........................................................................................191
15.4 Writing sequence programs ......................................................................193
15.5 Sequence Program Structure ....................................................................194
15.6 Sequence Execution ...................................................................................199
15.7 Process Module Operating Status ............................................................200
15.8 Sequence Execution State .........................................................................203
15.9 Sequence Overrides ...................................................................................210
15.10 Sequence Alarms ........................................................................................211
15.11 Sequence Messages ...................................................................................211
15.12 Restart Option .............................................................................................213
15.13 Parameters ..................................................................................................213

16. REGULATORY PV POINT ......................................................... 215

16.1 Regulatory PV Point Background .............................................................215
16.2 PV Input Connections ................................................................................217
16.3 PV Algorithm Calculation ...........................................................................217
16.4 PV Range Check and Filtering...................................................................218
16.5 PV Value Status...........................................................................................219
xii HPM High-Performance Process Manager Control Theory R688
Honeywell 08/2019
 1 HPM Control Hardware Theory of Operation
1.1 Introduction

16.6 PV Source Selection .................................................................................. 220

16.7 PV Alarm Detection .................................................................................... 221
16.8 Deviation High alarm.................................................................................. 222

17. DATA ACQUISITION PV ALGORITHM ......................................223

17.1 Functional Overview .................................................................................. 223
17.2 Equations .................................................................................................... 223

18. FLOW COMPENSATION PV ALGORITHM................................225

18.1 Functional Overview .................................................................................. 225
18.2 Options and Special Features ................................................................... 226
18.3 Equations .................................................................................................... 227

19. MIDDLE OF THREE PV ALGORITHM........................................233

19.1 Functional Overview .................................................................................. 233
19.2 Options and Special Features ................................................................... 235
19.3 Equations .................................................................................................... 235

20. HIGH LOW AVERAGE PV ALGORITHM ...................................237

20.1 Functional Overview .................................................................................. 237
20.2 Options and Special Features ................................................................... 239
20.3 Equations .................................................................................................... 240

21. SUMMER PV ALGORITHM ........................................................243

21.1 Functional Overview .................................................................................. 243
21.2 Options and Special Features ................................................................... 244
21.3 Equations .................................................................................................... 245

22. VARIABLE DEAD TIME PV ALGORITHM .................................247

R688 HPM High-Performance Process Manager Control Theory xiii

08/2019 Honeywell
1 HPM Control Hardware Theory of Operation
1.1 Introduction

22.1 Functional Overview ...................................................................................247

22.2 Options and Special Features ...................................................................248
22.3 Equations .....................................................................................................252

23. TOTALIZER PV ALGORITHM.................................................... 255

23.1 Functional Overview ...................................................................................255
23.2 Options and Special Features ...................................................................258
23.3 Equations .....................................................................................................268

24. GENERAL LINEARIZATION PV ALGORITHM.......................... 271

24.1 Functional Overview ...................................................................................271
24.2 Options and Special Features ...................................................................271
24.3 Equations .....................................................................................................274

25. CALCULATOR PV ALGORITHM ............................................... 277

25.1 Functional Overview ...................................................................................277
25.2 Options and Special Features ...................................................................278
25.3 Equations .....................................................................................................279

26. REGULATORY CONTROL POINTS .......................................... 283

26.1 Regulatory Control Point Background .....................................................283
26.2 Regulatory Control Point Functional Overview .......................................283
26.3 Control Input Connections ........................................................................295
26.4 PV Source Selection ...................................................................................296
26.5 PV Alarm Detection.....................................................................................297
26.6 External Mode Switching ...........................................................................298
26.7 Initialization Logic.......................................................................................301
26.8 Target Value Processing ............................................................................306
26.9 PV Tracking .................................................................................................315

xiv HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 1 HPM Control Hardware Theory of Operation
1.1 Introduction

26.10 Control Algorithm Calculation .................................................................. 316

26.11 Control Output Processing ....................................................................... 318
26.12 Override Control ......................................................................................... 330

27. PID CONTROL ALGORITHM .....................................................337

27.1 Functional Overview .................................................................................. 337
27.2 Options and Special Features ................................................................... 339
27.3 Equations .................................................................................................... 349
27.4 Initialization ................................................................................................. 354
27.5 Override Feedback Processing ................................................................ 354
27.6 Control Output Connection ....................................................................... 356

28. PID W/FEEDFORWARD CONTROL ALGORITHM ....................357

28.1 Functional Overview .................................................................................. 357
28.2 Options and Special Features ................................................................... 360
28.3 Equations .................................................................................................... 362
28.4 Initialization ................................................................................................. 364
28.5 Override Feedback Processing ................................................................ 366

29. PID W/EXTERNAL RESET-FEEDBACK CONTROL ALGORITHM

.....................................................................................................369
29.1 Functional Overview .................................................................................. 369
29.2 Options and Special Features ................................................................... 372
29.3 Hand/Auto Stations .................................................................................... 375
29.4 Equations .................................................................................................... 378
29.5 Initialization ................................................................................................. 379
29.6 Override Feedback Processing ................................................................ 380

30. PID POSITION PROPORTIONAL CONTROLLER .....................381

R688 HPM High-Performance Process Manager Control Theory xv

08/2019 Honeywell
1 HPM Control Hardware Theory of Operation
1.1 Introduction

30.1 Functional Overview ...................................................................................381

30.2 Options and Special Features ...................................................................382
30.3 Equations .....................................................................................................385

31. POSITION PROPORTIONAL CONTROL ALGORITHM ............ 387

31.1 Functional Overview ...................................................................................387
31.2 Options and Special Features ...................................................................389
31.3 Equations .....................................................................................................392
31.4 Initialization .................................................................................................395

32. RATIO CONTROL ALGORITHM ................................................ 397

32.1 Functional Overview ...................................................................................397
32.2 Options and Special Features ...................................................................400
32.3 Equations .....................................................................................................402
32.4 Initialization .................................................................................................404
32.5 Override Feedback Processing .................................................................405

33. RAMP AND SOAK CONTROL ALGORITHM ............................ 407

33.1 Functional Overview ...................................................................................407
33.2 Equations .....................................................................................................418

34. AUTO MANUAL CONTROL ALGORITHM ................................ 419

34.1 Functional Overview ...................................................................................419
34.2 Options and Special Features ...................................................................421
34.3 Equations .....................................................................................................423

FOR EQUATION A ............................................................................. 423

34.4 Initialization .................................................................................................425
34.5 Override Feedback Processing .................................................................425

xvi HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 1 HPM Control Hardware Theory of Operation
1.1 Introduction

35. INCREMENTAL SUMMER ..........................................................427

35.1 Functional Overview .................................................................................. 427
35.2 Options and Special Features ................................................................... 428
35.3 Equations .................................................................................................... 430
35.4 Initialization ................................................................................................. 430
35.5 Override Feedback Processing ................................................................ 431

36. SWITCH CONTROL ALGORITHM .............................................433

36.1 Functional Overview .................................................................................. 433
36.2 Options and Special Features ................................................................... 435
36.3 Equations .................................................................................................... 438
36.4 Initialization ................................................................................................. 439
36.5 Override Feedback Processing ................................................................ 439

37. OVERRIDE SELECTOR CONTROL ALGORITHM ....................441

37.1 Functional Overview .................................................................................. 441
37.2 Options and Special Features ................................................................... 444
37.3 Equations .................................................................................................... 445
37.4 Initialization ................................................................................................. 446
37.5 Override Feedback Processing ................................................................ 447

38. MULTIPLY DIVIDE CONTROL ALGORITHM .............................449

38.1 Functional Overview .................................................................................. 449
38.2 Options and Special Features ................................................................... 450
38.3 Equations .................................................................................................... 450
38.4 Initialization ................................................................................................. 451
38.5 Override Feedback Processing ................................................................ 455

39. REGULATORY CONTROL SUMMER ALGORITHM..................457

R688 HPM High-Performance Process Manager Control Theory xvii
08/2019 Honeywell
1 HPM Control Hardware Theory of Operation
1.1 Introduction

39.1 Functional Overview ...................................................................................457

39.2 Options and Special Features ...................................................................458
39.3 Equations .....................................................................................................459
39.4 Initialization .................................................................................................460
39.5 Override Feedback Processing .................................................................460

40. OUTPUT SWITCH SELECT ALGORITHM................................. 463

40.1 Functional Overview ...................................................................................463
40.2 Options and Special Features ...................................................................468
40.3 Equations .....................................................................................................470
40.4 Initialization .................................................................................................472

41. BOX DATA POINTS ................................................................... 473

41.1 Box Data Point Background ......................................................................473

42. BOX FLAG DATA POINT ........................................................... 475

42.1 Functional Overview ...................................................................................475

43. BOX NUMERIC DATA POINT .................................................... 477

43.1 Functional Overview ...................................................................................477

44. BOX TIMER DATA POINT ......................................................... 481

44.1 Functional Overview ...................................................................................481

45. BOX TIME DATA POINT ............................................................ 483

45.1 Functional Overview ...................................................................................483

46. BOX STRING DATA POINT ....................................................... 485

46.1 Functional Overview ...................................................................................485

xviii HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 1 HPM Control Hardware Theory of Operation
1.1 Introduction

47. ARRAY POINTS ..........................................................................487

47.1 Array Background ...................................................................................... 487
47.2 Node Specific Configuration Requirements ............................................ 489
47.3 Array Parameter Names............................................................................. 489
47.4 Array Point Use with HPM Box Global Variables .................................... 490
47.5 Serial Interface to Array Points ................................................................. 494
47.6 Status and Error Checking ........................................................................ 501
47.7 Read-Back Check for Device Control/Digital Composite Points ........... 501
47.8 CL Notes ...................................................................................................... 502

48. DEVICE CONTROL POINTS ......................................................503

48.1 Functional Overview .................................................................................. 503
48.2 Input Connections ...................................................................................... 505
48.3 Output Connections ................................................................................... 516
48.4 Alarms ......................................................................................................... 522
48.5 Maintenance Statistics............................................................................... 523

49. HPM CONTROL PERFORMANCE .............................................525

49.1 Background ................................................................................................ 525
49.2 Control Slot Types ..................................................................................... 525
49.3 Scan Frequency .......................................................................................... 526
49.4 Determining Processing and Memory Capacity ..................................... 531
49.5 Overrun Handling ....................................................................................... 538
49.6 Performance Monitoring ............................................................................ 543
49.7 UCN Device Resource Utilization Display ............................................... 543

50. DATABASE CONSIDERATIONS ...............................................545

50.1 Background ................................................................................................ 545

R688 HPM High-Performance Process Manager Control Theory xix

08/2019 Honeywell
1 HPM Control Hardware Theory of Operation
1.1 Introduction

51. POINT EXECUTION STATE ....................................................... 549

51.1 Background .................................................................................................549
51.2 Run-Idle-Run Transition .............................................................................549
51.3 Warm/Cold Restart......................................................................................550

52. PEER-TO-PEER COMMUNICATION ......................................... 553

52.1 Background .................................................................................................553
52.2 Implementation ...........................................................................................553
52.3 Restrictions .................................................................................................555

53. HARDWARE REFERENCES ..................................................... 559

53.1 Hardware Reference Addressing ..............................................................559

54. REDUNDANCY ........................................................................... 563

54.1 Background .................................................................................................563
54.2 IOP Module Switchover ..............................................................................563
54.3 HPM Redundancy Parameters ...................................................................563

55. POINT RESERVATION .............................................................. 565

55.1 Background .................................................................................................565
55.2 Establishing Point Reservation .................................................................565

56. STATUS MESSAGES ................................................................ 567

56.1 Availability ...................................................................................................567
56.2 Configuration ..............................................................................................567
56.3 Operator Interaction ...................................................................................567
56.4 CL Interaction ..............................................................................................567

57. MODE AND MODE ATTRIBUTE SELECTION LIST ................. 569

xx HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 1 HPM Control Hardware Theory of Operation
1.1 Introduction

57.1 Background ................................................................................................ 569

57.2 Configuration .............................................................................................. 569

Tables
Table 4-1 HL and LL analog input point sensor types ................................................... 44
Table 4-2 Max Allowable Lead Resistance and Max Allowable Intrinsic Safety barrier
Resistance for RTD types ...................................................................................... 48
Table 5-1 STI sensor types and PV characterization .................................................... 60
Table 5-2 State Parameters of STI-IOP and the transmitter ......................................... 68
Table 5-3 STI-IOP command parameters ..................................................................... 69
Table 6-1 Event sequence ............................................................................................. 75
Table 13-1 Digital Composite Point Normal States ..................................................... 128
Table 13-2 Digital Composite Point Momentary States ............................................... 130
Table 13-3 Digital Composite Point PV Sources ......................................................... 140
Table 14-1 Entires for LOGMIX parameters ................................................................ 160
Table 15-1 Normal Sequence and Abnormal Condition Handler Component Definitions
.............................................................................................................................. 198
Table 15-2 Process Module Operating States ............................................................ 200
Table 15-3 Sequence Execution Mode ....................................................................... 202
Table 15-4 Sequence Execution States ...................................................................... 204
Table 16-1 PV Value Status Definitions ...................................................................... 219
Table 18-1 Flow Compensation Forms ....................................................................... 226
Table 18-2 Flow Compensation PV Algorithm Equations ........................................... 230
Table 22-1 Variable Dead-Time PV Algorithm Equations ........................................... 252
Table 25-1 Supported Operators and Functions ......................................................... 280
Table 26-1 Regulatory Control Point Operating Modes .............................................. 286
Table 26-2 Regulatory Control Point Mode Attributes ................................................. 288
Table 26-3 Regulatory Control Point Remote Cascade Options ................................. 291
Table 26-4 Regulatory Control Point Bad PV/Mode Shed .......................................... 294
Table 26-5 Regulatory Control Point PV Source Selection Configuration .................. 296
Table 26-6 Regulatory Control Point Bad PV Alarm Detection ................................... 297
Table 26-7 Regulatory Control Point External Mode Switching .................................. 300
Table 26-8 PID-Based Regulatory Control Algorithm Setpoint Access ....................... 307
Table 26-9 Non-PID-Based Regulatory Control Algorithm Setpoint Access ............... 309
Table 26-10 INITVAL Calculation with RATIO or BIAS Clamped ............................... 314
Table 26-11 Regulatory Control Point HMI Accessible Output Parameters................ 319
Table 26-12 Regulatory Control Override Control Status and Feedback Parameters 332
Table 27-1 Pid Control Algorithm Gain Options .......................................................... 342
Table 27-2 Pid Control Algorithm - Equation A............................................................ 352
Table 27-3 Pid Control Algorithm - Equation B............................................................ 352
Table 27-4 Pid Control Algorithm - Equation C ........................................................... 353

R688 HPM High-Performance Process Manager Control Theory xxi

08/2019 Honeywell
1 HPM Control Hardware Theory of Operation
1.1 Introduction

Table 27-5 Pid Control Algorithm - Equation D ............................................................353

Table 29-1 Hand/Auto Station Functions .....................................................................375
Table 29-2 Hand/Auto Station I/O Signals ...................................................................375
Table 30-1 PIDPOSPR Safety Shutdown SAFOPCMD Parameter Value ..................383
Table 30-2 PIDPOSPR Bad PV/Mode Shed ................................................................384
Table 30-3 PIDPOSPR Raise/Lower Equation Decision .............................................386
Table 30-4 PIDPSOPR raise/lower pulse width equation (RAISETIM) .......................386
Table 31-1 Analog Output Related Parameters ...........................................................391
Table 31-2 POSPROP Raise/Lower Equation Decision ..............................................393
Table 31-3 POSPROP Raise/Lower Pulse Width Equation ........................................394
Table 32-1 Ratio Control Algorithm Equations .............................................................403
Table 33-1 Mark Timer Parameters .............................................................................413
Table 36-1 SELXINP Parameter Status .......................................................................436
Table 38-1 Multiply/Divide Equations (CV) ..................................................................451
Table 38-2 Multiply/Divide Initialization Equations (INITVAL) ......................................453
Table 38-3 Multiply/Divide Override Feedback Equations (ORFB) .............................455
Table 47-1 Maximum Si/Array Points...........................................................................489
Table 47-2 Array Parameter Names ............................................................................489
Table 47-3 HPM Box Global Variables ........................................................................490
Table 48-1 Primary and Secondary Logic Gate Algorithms .........................................510
Table 48-2 SVHITP and SVHHTP Colors ....................................................................514
Table 48-3 SVP Bar Graph Color Chart .......................................................................515
Table 49-1 Scheduled frequency of SCANRATE parameters .....................................527
Table 49-2 Fast slots parameters ................................................................................528
Table 49-3 Memory unit capacity .................................................................................534
Table 49-4 Memory unit constraints .............................................................................535
Table 49-5 HPM Link Unit Calculation Sheet ...............................................................540
Table 52-1 Peer-to-peer implementation summary .....................................................554

xxii HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 1 HPM Control Hardware Theory of Operation
1.1 Introduction

Figures
Figure 2-1 Primary Operator Interface for control loop .................................................. 34
Figure 2-2 Primary Operator Interface for Mass Flow ................................................... 35
Figure 2-3 Primary Operator Interface for Motor ........................................................... 36
Figure 2-4 Type of Stand alone points .......................................................................... 37
Figure 4-1 Analog Input Point, Functional Diagram ...................................................... 42
Figure 4-2 PVCALC Calculation .................................................................................... 46
Figure 5-1Smart transmitter input point functional diagram .......................................... 55
Figure 5-2 STI Point Detail Display .............................................................................. 59
Figure 5-3 Linear Conversion STI IOP .......................................................................... 61
Figure 5-4 Conversion Equations .................................................................................. 62
Figure 6-1Analog Output Point Functional Diagram ...................................................... 72
Figure 6-2 Output Characterization for an Analog Output Point................................... 74
Figure 7-1Digital Input Point Functional Diagram .......................................................... 78
Figure 7-2 DI Input States............................................................................................. 79
Figure 8-1 Digital Output Point Functional Diagram ..................................................... 93
Figure 8-2 PWM Type Digital Output Point Waveforms ............................................... 94
Figure 8-3 Calculation of pulse-on-time and reverse acting outputs ............................. 95
Figure 8-4 Status Type Digital Output Point Waveforms............................................... 97
Figure 9-1 Pulse Input Point Functional Diagram ....................................................... 100
Figure 10-1 Serial Interface Point Hardware Block Diagram...................................... 103
Figure 11-1 Serial Device Interface Block Diagram ................................................... 107
Figure 11-2 Manual/Auto Station Implementation ...................................................... 110
Figure 13-1 Digital Composite Point Inputs Functional Diagram ............................... 126
Figure 13-2 Digital Composite Point Outputs Functional Diagram ............................. 127
Figure 13-3 Digital Composite Point Display .............................................................. 129
Figure 14-1 Logic Point............................................................................................... 159
Figure 14-2 AND Logic Point Algorithm ...................................................................... 167
Figure 15-1Process Module Data Point Functional Diagram ...................................... 188
Figure 15-2 Sequence Program and Unit Partitioning................................................ 192
Figure 15-3 Sequence Program Structure.................................................................. 196
Figure 15-4 Process Module Operating States Relational Diagram ........................... 201
Figure 15-5 Sequence Execution State Transitions .................................................... 203
Figure 16-1 Regulatory PV Point Functional Diagram ................................................ 216
Figure 17-1 Data Acquisition PV Algorithm Functional Diagram ................................. 223
Figure 18-1 Flow Compensation PV Algorithms ......................................................... 225
Figure 19-1 Middle of Three PV Algorithm Functional Diagram .................................. 234
Figure 20-1 High, Low, Average PV Algorithm Functional Diagram ........................... 238
Figure 21-1 Summer PV Algorithm Functional Diagram ............................................. 243
Figure 22-1 Variable Dead Time PV Algorithm Functional Diagram ........................... 247
Figure 22-2 Variable Dead-Time Functional Diagram ................................................. 249
Figure 23-1 Totalizer PV Algorithm Functional Diagram ............................................. 255

R688 HPM High-Performance Process Manager Control Theory xxiii

08/2019 Honeywell
1 HPM Control Hardware Theory of Operation
1.1 Introduction

Figure 23-2 Using a Totalizer to Fill a Tank .................................................................257

Figure 24-1 General Linearization PV Algorithm Functional Diagram ........................271
Figure 24-2 General Linearization Operation Example...............................................273
Figure 25-1 Calculator PV Algorithm Functional Diagram ..........................................277
Figure 26-1 Regulatory Control Point Functional Diagram ..........................................283
Figure 26-2Regulatory Control Point Mode Structure ..................................................287
Figure 26-3 Override Control Strategy Example ..........................................................334
Figure 27-1 PID Control Algorithm Functional Diagram..............................................338
Figure 27-2 Override Feedback Processing Diagram..................................................354
Figure 28-1 PIDFF Control Algorithm Functional Diagram .........................................357
Figure 28-2 PIDFF Control Algorithm in Feed Heater Example .................................359
Figure 29-1 PIDERFB Control Algorithm Functional Diagram ....................................371
Figure 29-2 PIDERFB Control Algorithm Example Application ..................................372
Figure 29-3 Hand/Auto Station Control Configuration and Wiring Diagram ................377
Figure 29-4 Hand/Auto Station Logic Point Configuration and Wiring Diagram ..........378
Figure 30-1 PID Position Proportional Control Algorithm Functional Diagram ...........381
Figure 31-1 POSPROP Example Control Strategy .....................................................387
Figure 31-2 POSPROP Control Algorithm Functional Diagram ..................................389
Figure 32-1 RATIOCTL Algorithm Functional Diagram ...............................................397
Figure 32-2 Ratio Control Example Application ..........................................................399
Figure 32-3 Override Feedback Processing ................................................................405
Figure 33-1 Ramp and Soak Control Algorithm Functional Diagram ..........................408
Figure 33-2 Wait Time Between Phases ....................................................................412
Figure 33-3 Ramping Waits for the Process ...............................................................412
Figure 33-4 Ramp/Soak Mark Timers ..........................................................................413
Figure 33-5 Using a Logic Slot to Achieve Additional Rampsoak Segments ..............416
Figure 34-1 Auto Manual Control Algorithm Functional Diagram ...............................419
Figure 34-2 AUTOMAN Serving as Ultimate Secondary in a Fan-Out Configuration 420
Figure 34-3 AUTOMAN Override Feedback Processing ............................................425
Figure 35-1 Incremental Summer Control Algorithm Functional Diagram ..................427
Figure 35-2 Incremental Summer Input and Output Connections ..............................427
Figure 36-1 Switch Control Algorithm Functional Diagram .........................................433
Figure 36-2 Switch Control Algorithm Examples ........................................................434
Figure 37-1 Override Selector Control Algorithm Functional Diagram ........................442
Figure 37-2 Override Control Strategy Example .........................................................443
Figure 38-1 Multiply/Divide Control Algorithm Functional Diagram ............................449
Figure 39-1 Regulatory Control Summer Functional Diagram ....................................457
Figure 40-1O P SELECT Control Algorithm Functional Description ............................463
Figure 40-2 Switching Example ...................................................................................467
Figure 42-1 Box Flag Data Point Functional Diagram ................................................476
Figure 43-1 Box Numeric Data Point Functional Diagram ...........................................478
Figure 44-1 Box Timer Data Point Functional Diagram ..............................................481
Figure 47-1 Array Point Access to Box Global Variables............................................487
xxiv HPM High-Performance Process Manager Control Theory R688
Honeywell 08/2019
 1 HPM Control Hardware Theory of Operation
1.1 Introduction

Figure 47-2 Serial Interface to an Array Point ............................................................ 488

Figure 47-3 String Array with Starting Index Set to 301 ............................................. 492
Figure 47-4 Signal Path Between SI Subsystems and Array Point ............................ 495
Figure 48-1 Device Control Point Functional Diagram ............................................... 504
Figure 48-2 Logic Gates and Destinations ................................................................. 506
Figure 48-3 Primary and Secondary Logic Input Gate ............................................... 508
Figure 48-4 Secondary Input Gate ............................................................................. 510
Figure 48-5 Primary and Secondary Logic Gates ...................................................... 510
Figure 48-6 Primary Logic Gate Destinations.............................................................. 511
Figure 48-7 Secondary Logic Gate Destinations ........................................................ 512
Figure 48-8 Detail Display of Logic Configuration ...................................................... 513
Figure 48-9 Secondary Variable Representation on the Point Detail Display ............ 514
Figure 48-10 Interlocks and Permissives Functional Diagram .................................... 518
Figure 48-11 Output Indicators on the Point Detail Display ........................................ 519
Figure 48-12 Logic Output Connections ..................................................................... 520
Figure 49-1 Display for Peer to Peer UCN overruns and soft failures ........................ 542

R688 HPM High-Performance Process Manager Control Theory xxv

08/2019 Honeywell
1 HPM Control Hardware Theory of Operation
1.1 Introduction

xxvi HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 1. HPM Control Hardware Theory of Operation
1.1 Introduction
The High-Performance Process Manager (HPM) is designed to provide flexible and
powerful process scanning and control capabilities. To do this, it uses a powerful
multiprocessor architecture with separate microprocessors dedicated to perform specific
tasks. As depicted in the following high level diagram, the HPM consists of two primary
components:
• High-Performance Process Manager Module (HPMM).
• I/O Subsystem.

R688 HPM High-Performance Process Manager Control Theory 27

08/2019 Honeywell
1 HPM Control Hardware Theory of Operation
1.1 Introduction

28 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 1 HPM Control Hardware Theory of Operation
1.2 HPM Module

1.2 HPM Module

HPPM elements
The High-Performance Process Manager Module (HPMM), as depicted in the following
detailed diagram, consists of three basic elements:
• Communication Processor and Modem.
• I/O Link Interface Processor.
• Control Processor.
Redundancy can be optionally provided and would be depicted here as a fourth basic
element of the HPMM.
Communication processor
The Communication Processor is optimized to provide High-Performance network
communications, handling such functions as network data access and peer-to-peer
communications.
Control processor
The Control Processor is the HPM resource dedicated to executing regulatory, logic, and
sequence functions, including a powerful user programming facility. Because
communication and I/O processing are performed by separate dedicated hardware, the
full power of the control processor can be applied to control strategy implementation.
I/O link interface processor
The I/O Link Interface Processor is the interface to the I/O Subsystem.

1.3 I/O Subsystem

I/O subsystem elements
The I/O Subsystem, as depicted in the following detailed diagram, consists of two basic
elements:
• redundant I/O Link.
• I/O Processors.

R688 HPM High-Performance Process Manager Control Theory 29

08/2019 Honeywell
1 HPM Control Hardware Theory of Operation
1.3 I/O Subsystem

30 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 1 HPM Control Hardware Theory of Operation
1.3 I/O Subsystem

Scanning field I/O

The I/O Processors (IOPs), in conjunction with Field Termination Assemblies (FTAs),
perform input and output scanning, and processing on all field I/O. A redundant I/O Link
is standard for added security.
I/O processing
The I/O Processors handle all field I/O for both data acquisition and control functions.
They provide such functions as engineering unit conversion and alarm limit checking
independent of the HPMM. All control operations are performed within the HPMM. All
I/O processing (for example, data acquisition) is performed separately from control
processing functions so that I/O scan rates are completely independent of I/O quantity,
controller loading, processing, and alarming. Partitioning of processing requirements
allows more efficient use of control processor capability and future integration of
additional I/O Processor types.
IOP types
Multiple types of I/O processors (IOPs) are available for the HPM, including:

Type IOP

Analog Input 16 Point, High Level—Analog Input

8 Point, Low Level—Analog Input

Analog Output 8 Point, Analog Output

16 Point, Analog Output

Digital Input 32 Point, Digital Input

32 Point, Sequence of Events—Digital Input

Digital Output 16 Point, Digital Output

32 Point, Digital Output

R688 HPM High-Performance Process Manager Control Theory 31

08/2019 Honeywell
1 HPM Control Hardware Theory of Operation
1.3 I/O Subsystem

Type IOP

Special Purpose Fieldbus (4 segments, 10 devices each)

16 Point, Smart Transmitter Interface

32 Point, Low Level—Multiplexer

8 Point, Pulse Input

32 Point, Serial Interface

16 Point, Serial Device Interface

ATTENTION
Up to 40 of the I/O processors in the preceding table can be selected in any
mix. Optionally, redundant Analog Output and High Level—Analog Input
processors (up to 40 primary and 40 redundant IOPs) are supported.

Control application implementation

You, as process engineer, have complete flexibility of choice, within the maximum HPM
design limits, in the assignment of point types and control strategies. The interactive tools
provided by both the Universal Station, GUS/Native Window, and TPS Builder are used
to implement these selections.

REFERENCE – INTERNAL
For more information concerning the assignment of point types and control
strategies:

When using… Refer to…

Universal Station or GUS/Native Engineer’s
Window tools Reference Manual

GUS/Native Window Native Window User’s Guide

TPS Builder tool TPS Builder Implementation Guide

32 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 2. Control Processing Theory of Operation
2.1 Control Functions
Background
The HPM provides a variety of control tools that can be customized to address a wide
range of process automation needs. Functions from I/O scanning, through regulatory and
logic control to more advanced control can be easily implemented through the HPM. The
HPM toolbox includes a sophisticated regulatory control package, fully integrated
interlock logic functions, and an advanced process engineer-oriented Control Language
(CL/HPM). CL/HPM is an enhanced version of the Control Language implemented by
Honeywell in the Multifunction Controller, Process Manager, and Application Module.
This language facility includes the sequence structures needed to handle batch or hybrid
applications as well as the computational capability needed for some continuous control
tasks. Key to the power of this control capability is that each of the functions shares data
freely within the HPM and can share data from other devices on the Universal Control
Network.
HPMM point types
The following point types reside in the HPMM:

• Regulatory PV • Array

• Regulatory Control • Process Module

• Digital Composite • Device Control

• Logic • Box Flag, Numeric, and Timer

Implementing control applications

Separate functional elements of the HPM are used to implement various parts of typical
control loops and control strategies. Each of these functional elements can be assigned a
user-defined point name to allow for location-independent reference to the data
associated with that function. For example, points are assigned by the user for analog
input and analog output slots. The I/O Processor data (engineering-unit range for inputs,
characterization option for outputs, and so on.) is configured as part of the point-build
process for these points. A separate point would be configured for each regulatory
control (RegCtl) slot that would be linked to the assigned analog I/O points through
input/output connections.
Point form
The HPM provides a configurable parameter called PNTFORM (Point Form) that allows
the user to define which points are to be used as the primary operator interface for point

R688 HPM High-Performance Process Manager Control Theory 33

08/2019 Honeywell
2 Control Processing Theory of Operation
2.1 Control Functions

data. The PNTFORM parameter provides the user with two choices for point form: "Full"
and "Component." Points that are configured as having "Full" point form include alarm-
related parameters and sometimes, some other miscellaneous parameters. This
information is needed when the point is to be used as the primary operator interface to
the point's data.

ATTENTION
The maximum number of points per Network Interface Module (NIM) is 8000.
Both full and component points should be counted when checking against
this limit. Note that for the DI and DO portions of a digital composite point the
inputs and outputs to and from the digital composite point are not counted as
part of the point total if they are implemented using both:
• the hardware reference source.
• destination addresses entered on the configuration form for the digital
composite point.

Database security is provided to prevent an operator from starting an

CAUTION IOP that has an invalid database. After initial configuration, each IOP
must be set valid. You cannot checkpoint unless the IOP database is
marked valid. Restoring the database from a valid checkpoint also sets
the IOP database valid. An IOP cannot be switched from Idle to Run
unless its database is valid.

Simple single loop control example

In the following figure, a single-loop PID controller has the PV of a Smart Transmitter
Interface point (FT100) connected to the PV of a RegCtl point (FIC100) that has been
configured for a PID algorithm. The output (OP) of the RegCtl point is applied to an
analog output (AO ) point (FY100). In this example:
• FIC100 is the primary operator interface and is configured as a "Full" point.
• FT100 and FY100 are parts (components) of FIC100, and could be configured as
"Component" points.

Figure 2-1 Primary Operator Interface for control loop

34 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 2 Control Processing Theory of Operation
2.1 Control Functions

PRIMARY OPERATOR INTERFACE

FOR THIS CONTROL LOOP

FIC100
PNTFORM = FT100 PV OP FY100 PNTFORM =
REGCTL
Component STI AO Component
PID ALGO

PNTFORM =
Full

SMART FIELD
TRANS- DEVICE
MITTER

Mass flow example

The following figure shows a single-loop PID controller controlling mass flow. Mass
flow is computed by the flow compensation PV algorithm in regulatory PV (RegPV)
point (FX101). FX101 receives three PVs representing the uncompensated flow, absolute
pressure, and absolute temperature from AI points FT101, PT101, and TT101. FX101
provides the PV as mass flow to a RegCtl point (FIC101) that has been configured for a
PID algorithm. FIC101 provides an output to an AO point (FY101).
In this example:
• FIC101 is the primary operator interface and would be configured as a "Full" point.
• FX101 is part of FIC101 and would be configured as a "Component" point.
• FT101, PT101, and TT101 could be configured as "Full" or "Component " points.
• FY101 must be configured as a "Component" point.

ATTENTION
"Full" would be selected for any of these points that require separate alarm
reporting, such as alarming for uncompensated flow, line pressure, or fluid
temperature.

Figure 2-2 Primary Operator Interface for Mass Flow

R688 HPM High-Performance Process Manager Control Theory 35

08/2019 Honeywell
2 Control Processing Theory of Operation
2.1 Control Functions

PRIMARY OPERATOR INTERFACE

FOR THIS CONTROL LOOP

FX101 FIC101
PNTFORM = REGPV PV REGCTL PNTFORM =
Component MASSFLOW ALGO PID ALGO Full

OP
PNTFORM =
Full or Component

PNTFORM =
FT101 PT101 TT101 FY101 Component
AI AI AI AO

FIELD FIELD FIELD FIELD

DEVICE DEVICE DEVICE DEVICE

Motor control example

The following figure shows a single-output, single-input digital composite point
(MTR100) that interfaces a motor control circuit through a digital output (DO) point
MTR100OP, and digital input (DI) point MTR100FB.
In this example:
• MTR100 is the primary operator interface and would be configured as a "Full" point.
• MTR100OP and MTR100FB are parts of TR100 and would be configured as
"Component" points.

Figure 2-3 Primary Operator Interface for Motor

36 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 2 Control Processing Theory of Operation
2.1 Control Functions

PRIMARY OPERATOR INTERFACE

MTR100

MTR100OP
OP
DO
(See Note)
DO

PNTFORM = TO /FROM
Full MOTOR CONTROL
CIRCUIT

MTR100FB
DI PV
DI

PNTFORM =
Component
DIGITAL COMPOSITE
POINT

NOTE: Full-point form cannot be assigned to DO (digital output) points; they

are always component points. Stand-alone digital output points
require using a digital composite point that has 0 (zero) inputs and 1 output.

Stand-alone points
The following figure shows three types of stand-alone points. FT102 and CT105 are
points that could be used for data acquisition; in this case these points would be
configured as full points. For the stand-alone digital output (DO) point SW103, a digital
composite (DigComp) point would be used and would be configured as having 0 (zero)
inputs and 1 output.

Figure 2-4 Type of Stand alone points

R688 HPM High-Performance Process Manager Control Theory 37

08/2019 Honeywell
2 Control Processing Theory of Operation
2.1 Control Functions

FIELD FT102
DEVICE AI PV

PNTFORM = Full

FIELD CT105
DEVICE DI PV

PNTFORM = Full

FIELD OP SW103
DEVICE DO

PNTFORM = Component

Associated HMI displays

With Release 510 and later software, an Associated Display can be configured for each
HPM point at build time by entering the name of a custom built schematic in the
ASSOCDSP parameter. At operating time, the operator can call up that associated
custom schematic from a point Detail Display or Group Display.

38 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 3. I/O Points
3.1 I/O Points Background
Purpose
The analog and digital data points in the I/O Processors (IOPs) perform input and output
processing on all field I/O. These functions are performed independently of the control
functions. The partitioning of processing requirements allows more efficient use of
control processor capability and future integration of additional IOP types.
I/O Point Types
The following I/O points are available:
• High and Low Level Analog Input Point.
• Smart Transmitter Interface Point.
• Analog Output Point.
• Digital Input Points.
• Digital Output Point.
• Pulse Input Point.
• Serial Interface Point.
• Serial Device Interface.

TIP
To support on-line field maintenance activities, Standby Manual units are
recommended for the Process Manager AO and DO I/O Processors.

ATTENTION
The Serial Device Interface (SDI) IOP is configured as a Smart Transmitter
Interface (STI) IOP.

R688 HPM High-Performance Process Manager Control Theory 39

08/2019 Honeywell
3 I/O Points
3.1 I/O Points Background

40 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 4. High and Low Level Analog Input Point
4.1 AI Points Functional Overview
Family
The High and Low Level Analog Input Points are members of the I/O Point family.
Purpose
The analog input point converts an analog PV signal received from a field sensor to
engineering units for use by other data points in the HPM, and by the rest of the
TotalPlant Solution (TPS) system.
Description
High level points are located in the High Level Analog Input (HLAI) IOP. One type of
low level point is located in the Low Level Analog Input (LLAI) IOP. This type is
generally used for control points. The other type is located in either the Low Level
Multiplexer (LLMUX) or the Remote Hardened Multiplexer (RHMUX) IOP. This type is
generally used for data acquisition points. The type of analog input point needed is based
on the type of field sensor that is providing the input to the point and the characterization
options selected by the user as listed in Table 2-1.
Operation
To accomplish this function, the analog input point (shown in the following figure)
performs:
• Analog-to-Digital Conversion.
• PV Characterization.
• PV range checking and filtering.
• PV source selection.
• Alarming.

R688 HPM High-Performance Process Manager Control Theory 41

08/2019 Honeywell
4 High and Low Level Analog Input Point
4.1 AI Points Functional Overview

Figure 4-1 Analog Input Point, Functional Diagram

PVRAW

P
V
15V DegreesC
SENSRTYP
P4 2 V DegreesF
C PVTEMP
05V H DegreesK
0-100 MV A DegreesR
PVRAW
Thermcpl R
A
Rtd Normal
C
Slidewire TCRNGOPT
T Extended
E
Therm
R
PVCHAR Rtd Direct
I
Linear Z INPTDIR
Reverse
Sqrroot A
T
I OTD (Open Thermocouple
PVEULO
O Detection)
PVEUHI N

PVCALC
(in Eu)
PVCLAMP Noclamp
PVEXEUHI Range Clamp
PVEXEULO Checking
& PV PVEXHIFL
TF PVEXLOFL
Filtering

PVAUTO
PNTFORM
Component
PVMan or PVSub Full
(from Operator or Program)
PVAUTO
PV
PVSOURCE

Man/Sub Auto Auto

PVEUHI PVP (PV in %)
Man/Sub NORMALIZATION
PVEULO LASTPV

PVEXEUHI RANGE PVEXHIFL

PVEXEULO CHECKING PVEXLOFL

PV

Enable ALENBST
Inhibit
Disable
EU
Half
A
One HIGHAL
Two L
PVALDB Three A
R
Four
Five M

PVHTP D PVHIFL
PVHPR E •
• •
• T •
PV ALARM • PV ALARM
• E •
TRIP POINTS • FLAGS
• C
AND PRIORITIES
PVROCPTP T PVROCNFL
PVROCPPR I PVROCPFL
O
N

PTINAL

42 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 4 High and Low Level Analog Input Point
4.2 Analog-to-Digital Conversion

4.2 Analog-to-Digital Conversion

Engineering units conversion
The engineering unit conversions that are performed in the HLAI, LLAI and LLMUX
points are listed in the following chart, and described in the following topics.

High Level AI Point Low Level AI Point Low Level Mux Point1

Linear Linear Linear

Square Root Square Root RTD2

Thermal Slidewire Thermal Thermal

1) In general, LLMUX points apply to (include) points built against the LLMUX IOP as well as the
RHMUX IOP. The RHMUX does not have a unique point type.
2) RTDs are not supported by RHMUX IOP.

Linear Conversion
The PVRAW value is converted to a floating-point number. The output value of the
linear conversion is PVCALC, which is calculated based on the raw input span (for
slidewire and 0-100 mV sensor types only), and the engineering unit span. The state of
the input direction parameter (INPTDIR) is taken into consideration during the
calculation of PVCALC as described in the following table.

For slidewire and 0-100 mV sensor types, when INPTDIR is Direct

For 0-5V, 0.4-2V, and 1-5V, sensor types, when INPTDIR is Direct

For slidewire and 0-100 mV sensor types, when INPTDIR is Reverse:

R688 HPM High-Performance Process Manager Control Theory 43

08/2019 Honeywell
4 High and Low Level Analog Input Point
4.2 Analog-to-Digital Conversion

For 0-5V, 0.4-2V, and 1-5V, sensor types, when INPTDIR is Reverse:

Sensor types and characterization options

The following table defines the HL and LL analog input point sensor types and PV
characterization options.
Table 4-1 HL and LL analog input point sensor types

Sensor Type AI Processor PVCHAR Options PVRAW1 PVCAL BAD PV

(SENSRTYP) Type C Detection2

0 to 5 V HL & LL Linear % EU Range Check

on PVCLAC
HL & LL Square Root

HL Thermocouple

HL RTD

0.4 to 2 V HL Linear % EU Range Check

on PVCLAC
HL Square Root

HL Thermocouple % EU HLAI checks

for open input
HL RTD

1 to 5 V HL & LL Linear % EU Range Check

on PVCLAC
HL & LL Square Root

HL Thermocouple % EU HLAI checks

for open input
HL RTD

Slidewire HL Linear Ratio EU3 Bad slidewire

source, range
check on
PVCALC

0 to 100 mV LL Linear millivolts EU3 Range check

on PVCLAC
LLMUX

44 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 4 High and Low Level Analog Input Point
4.2 Analog-to-Digital Conversion

Sensor Type AI Processor PVCHAR Options PVRAW1 PVCAL BAD PV

(SENSRTYP) Type C Detection2

RHMUX

Thermocouple LL Thermocouple µvolts EU Open

thermocouple,
LLMUX and range
check on
RHMUX PVCLAC

RTD LL RTD milli EU Range check

on PVCALC

1 PVRAW is the voltage signal at the HPM Field Termination Assembly as a percentage of
the voltage range for the sensor type. The exceptions are as follows:
− For a thermocouple sensor type, PVRAW is in microvolts after reference junction
compensation. If an open thermocouple is detected, PVRAW is set to NaN.
− For an RTD sensor type, PVRAW is in milliohms after lead-wire compensation. If
an open RTD is detected, PVRAW is set to NaN.
− An external power source is used to excite the slidewire. The power source and the
slidewire are connected to separate analog input points. One power source input
can be used with several slidewire inputs.
− For a Slidewire type, PVRAW is the slidewire ratio (Vin/Vsrc) where: Vin is the FTA
voltage input for this data point (slot); Vsrc is the FTA voltage source at the
slidewire source slot specified by parameter; SLWSRCID. If Vsrc is zero (fails the
under-range check), PVRAW is set to "NaN."
− For a 0-100 millivolt sensor type, PVRAW is the FTA voltage input for the slot.

2 If the diagnostics determine that the A/D converter has failed, PVRAW of the slot is set to
NaN.

3 The normal operating range for PVRAW is configured by the user (for a thermocouple 0%
= PVRAWLO, 100% = PVRAWHI; for a slidewire, 0 = PVRAWLO, 1 = PVRAWHI).

R688 HPM High-Performance Process Manager Control Theory 45

08/2019 Honeywell
4 High and Low Level Analog Input Point
4.2 Analog-to-Digital Conversion

Square-Root Conversion
The square-root calculation is applied to the PVRAW input such that 100% of span = 1.0.
The square-rooted value is then converted to engineering units based on the configured
PV engineering-unit range values. (For example, square root of 100% = 100%; square
root of 50% = 70.71%.) The output value of the square-root conversion is PVCALC,
which is calculated based on the state of the input direction parameter (INPTDIR) as
defined in the following table.
Figure 4-2 PVCALC Calculation

If PVRAW ≥ 0.0 and INPTDIR is Direct

If PVRAW < 0.0 and INPTDIR is Direct

If PVRAW ≥ 0.0 and INPTDIR is Reverse

If PVRAW < 0.0 and INPTDIR is Reverse

46 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 4 High and Low Level Analog Input Point
4.2 Analog-to-Digital Conversion

Thermal conversion when using Thermocouples

Thermal linearization is performed on thermocouple input types, and is selectable by
parameter PVCHAR. The following thermocouples are supported by the analog input
point:

• Btherm • Jtherm • Rtherm • Stherm

• Etherm • Ktherm • Rptherm • Ttherm

ATTENTION
The range of the thermocouple type used with the LLAI or LLMUX points can
be increased by selecting Extended as the entry for the TCRNGOPT
parameter. Refer to the PM Family PRD for the normal and extended ranges.

The LLAI and LLMUX points calculate the reference junction compensation from the
measured reference junction output level. This value is stored and then later converted
back to microvolts, with respect to 0 degrees C, for each thermocouple that is to be
compensated. The cold-junction reference compensation (PVREFJN) parameter is
expressed in microvolts for the specified thermocouple and is added to the microvolt
value for PVRAW.

ATTENTION
In general, LLMUX points apply to (include) points built against the LLMUX
IOP as well as the RHMUX IOP. The RHMUX does not have a unique point
type.

Thermal conversion when using RTDs

Thermal linearization is performed on RTD input types, and is selectable by parameter
PVCHAR. The following 3-wire RTDs are supported by the analog input point:

• PtDinRTD • PtJisRTD • NicklRTD • CopprRTD

TIP
For an RTD, the LLAI and LLMUX points calculate the lead-wire
compensation and then subtract the value from PVRAW.

R688 HPM High-Performance Process Manager Control Theory 47

08/2019 Honeywell
4 High and Low Level Analog Input Point
4.2 Analog-to-Digital Conversion

The maximum allowable lead-wire resistance and intrinsic safety barrier resistance for
the RTDs are listed in the following table.

ATTENTION
RTD is not supported by RHMUX IOP.
Proper compensation for lead-wire resistance depends on the resistance
being equal in each leg of the RTD. This includes resistance due to lead-wire
resistance and intrinsic safety barriers. No provision is made to compensate
for lead-wire resistance mismatch or intrinsic-safety-barrier resistance
mismatch. Both the lead resistance and the intrinsic-safety-barrier resistance
are allowed simultaneously when connected to an RTD in a Division 1 area.

Table 4-2 Max Allowable Lead Resistance and Max Allowable Intrinsic
Safety barrier Resistance for RTD types

RTD Max. Allowable Lead Max. Allowable Intrinsic

Type Resistance Safety Barrier
Resistance

Loop Leg Loop Leg

PtDinRTD 20 ohm 10 ohm 18 ohm 18 ohm

100 ohm DIN Characterization

PtJisRTD 20 ohm 10 ohm 18 ohm 18 ohm

100 ohm JIS Characterization

NicklRTD 20 ohm 10 ohm 18 ohm 18 ohm

120 Edison Type Characterization

CopprRTD 20 ohm 10 ohm 0.0 ohm 0.0 ohm

10 ohm SEER Standard Characterization

48 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 4 High and Low Level Analog Input Point
4.3 PV Characterization

4.3 PV Characterization
PV input signal processing
The PV signal received from the field is characterized based on the entries that were
made for the SENSRTYP, PVCHAR, PVTEMP, INPTDIR, and TCRNGOPT parameters
as shown in the figure illustrated in AI Functional Overview, Operation.
The input PV signal is first converted to a raw PV signal (PVRAW) whose units can be
%, ratio, millivolts, microvolts, or milliohms depending on the entry made for the
SENSRTYP parameter.
The PVRAW signal is then converted to the engineering units.

4.4 PV range checking and filtering

PV range checking ensures that the PVCALC output of PV characterization is within the
limits defined by parameters PVEXEULO and PVEXEUHI.

If... then...

either of the limits is violated and the output of the PVAUTO is set to NaN
clamping has not been specified

either of the limits is violated and the output of the PVAUTO is clamped to
clamping has been specified PVEXEUHI or PVEXEULO, except when
PVRAW (and consequently, PVCALC) is
NaN in which case, PVAUTO will be NaN

the range-checked and filtered value is the final output called PVAUTO is forced
less than the value as was specified by to PVEULO
configuring the LOCUTOFF parameter

First-order filtering is performed on PVCALC, as was specified through parameter TF

(filter lag time).

R688 HPM High-Performance Process Manager Control Theory 49

08/2019 Honeywell
4 High and Low Level Analog Input Point
4.5 PV source selection

4.5 PV source selection

The PVSOURCE parameter allows you to select the source of the PV for this data point.
As shown in Functional Overview, Operation the PV can:
• be provided by the Range Checking and Filtering circuit (when PVSOURCE is
Auto).
• be the manually entered PV (when PVSOURCE is Man).
• come from a sequence program (when PVSOURCE is Sub).
In addition, the PV source option parameter (PVSRCOPT) determines whether it is
permissible to change the PV source to a source other than Auto. PVSRCOPT has two
states: OnlyAuto and All. The All state allows the PV to be manually entered for this data
point.

50 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 4 High and Low Level Analog Input Point
4.6 Alarming

4.6 Alarming
The analog input data point compares the PV to threshold values and records the alarms
in the database of the data point. Alarms are then reported by the High-Performance
Process Manager Module (HPMM). The parameters that are associated with alarming in
the analog input point are:

• $OLDEVDS • PVEXHIFL • PVLLTP

• ALENBAT • PVEXLOFL • PVLOFL
• BADPVFL • PVHHFL • PVLOPR
• BADPVPR • PVHHPR • PVLOTP
• CONTCUT • PVHHTP • PVROCNFL
• EIPPCODE • PVHIFL • PVROCNPR
• H IGHAL • PVHIPR • PVROCNTP
• H IGHALPR • PVHITP • PVROCPFL
• PTINAL • PVLLFL • PVROCPPR
• PVALDB • PVLLPR • PVROCPTP
• PVALDBEU

REFERENCE - INTERNAL
Refer to the PM Family Parameter Reference Dictionary for the definitions of
these parameters.

R688 HPM High-Performance Process Manager Control Theory 51

08/2019 Honeywell
4 High and Low Level Analog Input Point
4.6 Alarming

52 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 5. Smart Transmitter Interface Point
5.1 STI Point Functional Overview
Family
The Smart Transmitter Interface (STI) point is a member of the I/O Point family.
Purpose
The Smart Transmitter Interface (STI) point provides an interface to Honeywell's
advanced series of Smartline 3000 Smart Transmitters.
Description
The STI points are located on the STI IOPs. Each STI IOP has a maximum of 16 inputs,
and it can communicate bidirectionally with up to 16 Smartline transmitters, regardless of
the mix of transmitter types (pressure, temperature, or flow) using Honeywell’s digitally
enhanced (DE) protocol.
An STIMV IOP allows up to four multi-PV transmitters or a mix of multi-PV and single
PV transmitter inputs that total no more than 16. A multi-PV transmitter is configured as
if it were in n contiguous slots where n = the number of PVs expected. The STITAG
parameter value for each contiguous slot must be identical. Refer to the PM/APM
Smartline Transmitter Integration Manual for complete details.
Communication
The STI IOP and the Smartline Transmitters use bidirectional digital communication to
allow you to configure, view, and modify the transmitter database from the Universal
Station or GUS station. This digital protocol allows a more precise PV value to be
transferred, thereby permitting more accurate control of the process. In addition, the
transmitter can also send a secondary variable such as the transmitter temperature, cold
junction temperature, or totalized value, depending on the transmitter type.

R688 HPM High-Performance Process Manager Control Theory 53

08/2019 Honeywell
5 Smart Transmitter Interface Point
5.1 STI Point Functional Overview

Transmitter database
The transmitter database is configured at the Universal Station or GUS, and down-line
loaded to the transmitter and the transmitter database can be up-line loaded to the STI
IOP as required, when the STI point is in the inactive state. During normal operation
(when the STI point is in the active state), each time that the transmitter broadcasts the
PV value to the STI IOP, it also sends the one byte of its database (depending on the
selected DECONF mode) to the STI IOP. This allows the STI IOP to compare the stored
database to the newly received database to check for database mismatches. If a mismatch
is detected, the PV is set to NaN and the status is set to DBCHANGE. You can easily
correct the mismatch by down-line loading the database stored in the STI IOP.
Operation
A functional diagram of the STI IOP point is shown in the following figure. The STI
point performs the following functions:
• PV Characterization.
• PV Range Checking and Filtering.
• Alarming.

54 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 5 Smart Transmitter Interface Point
5.1 STI Point Functional Overview

Figure 5-1Smart transmitter input point functional diagram

P
V
SMARTLINE TRANSMITTER
Spt_Gp
Spt_Ap Linear C Analog
PV H PV
(from Sfm PVCHAR Linear A PV-DB DECONF
process) (output form) R
SQrroot PV-SV
SENSRTYP A
Stp-Dp Linear C PV-SV-DB
Stt T
PIUOTDCF
B Therm E
R CJACT
PVCHAR E Therm I URL
(probe type) Z
LRL
A
T URV
I LRV
NiNiMoT c
O DAMPING
N

PVRAW % STI IOP

PVEUHI PV Engineering Unit Direct
PVEULO Conversion & PV Reverse INPT DIR
PVCHA R Input Direction
PVCALC
(in Eu)

Range PVCL AMP Noclamp

PVEXEUH I Clamp
PVEXEUL O Checking
TF & PV PVEXHIF L
Filtering PVEXLOFL

PVAUTO
PNTFORM
PVMan or PVSub Component
Full
(from Operator or Program)
PV (in Eu)
PVSOU RCE
Man/Sub Auto Auto
Man/Sub NOR MALIZATION PVP (PV in % )
LAST PV

PVEXEUH I RANGE PVEXHIF L

PVEXEULO CHECKING PVEXLOL

PV (in Eu)

Enab le
ALARM PROCESSING ALEN BST
Inhi bit

Half Di sable
A
One
L
Two HIGHAL
PVALDB A
Three
R
Four M
Five
PVHITP PVHIFL
D
PVHIPR E •
• T •
• E •
• C •
• T •
PVROCNTP I PVROCNFL
BADPVPR O
PRIMMOD N

PTINAL

R688 HPM High-Performance Process Manager Control Theory 55

08/2019 Honeywell
5 Smart Transmitter Interface Point
5.1 STI Point Functional Overview

Transmitters supported
The STI point can support the following Smartline Transmitter types:
• ST3000 Smart Pressure Transmitter for differential, gauge, and absolute pressure
measurements.
• STT3000 Smart Temperature Transmitter for temperature, millivolts, and ohms
measurements.
• MagneW 3000 Smart Magnetic Flow Transmitter for flow measurements.
• SCM3000 Smart Flow Transmitter (Coriolis method).
• Drexelbrook SLT Level Transmitter.
• MV 3000 Multivariable Pressure Transmitter.
• SGC 3000 Gas Chromatograph.
Transmitter parameters
All key transmitter parameters can be accessed from the Universal Station including:
• Upper and Lower Range Values.
• Damping.
• PV type.
• DE (Digital Enhanced communications) configuration variables.
• Status of the Transmitter.
• Transmitter's serial number and software revision number.
• Transmitter's scratchpad.
You access these variables through the point's Detail Display or custom-built schematics.
In addition to the tag name assigned to the process point associated with the transmitter,
the transmitter is also assigned a tag name and the access mechanism follows the
TDC3000 parameter access mechanism. This allows all the LCN capabilities applicable
to a data point to be also applicable to the Smartline Transmitters.
The STI IOP maintains a copy of the transmitter's database. When a transmitter failure
occurs, the database can be down-loaded to the transmitter. This database save/restore
feature can significantly reduce the downtime of a control loop by reducing the time in
getting a replacement transmitter in operation. The transmitter database can also be saved
to a History Module or removable media if a checkpoint request is initiated. This allows
for centralized control of the transmitter database, which significantly minimizes the
effort required to establish the transmitter database during startup or normal operation.
The STI IOP also allows the user to access the detailed status of a transmitter. The status
is displayed at a Universal Station or GUS together with the scratchpad information that
has been entered, including any maintenance notes.
56 HPM High-Performance Process Manager Control Theory R688
Honeywell 08/2019
 5 Smart Transmitter Interface Point
5.2 Parameter comparisons

Calibration of the transmitter can also be accomplished from the Universal Station or
GUS. This function allows on-line adjustment of the transmitter's working ranges so that
the reference points for a measurement are accurate.
In addition a Smart Field Communicator (SFC), which is a hand-held device, can also be
physically connected to the appropriate FTA in the HPM cabinet to communicate with
Smartline Transmitters without disrupting the process, as required (refer to the
appropriate Operating Guide for Smart Field Communicators).

5.2 Parameter comparisons

Relationship between the STI IOP and the transmitter database
To configure the STI IOP point to operate with the appropriate Smartline Transmitter, it
is necessary to know the parameter relationships between the STI IOP and the transmitter
database. The following table lists and describes these relationships.

Smart Transmitter STI IOP Description

Database Parameter Parameter

Upper Range Value URV Define the operating range of the transmitter. These
Lower Range Value LRV values correspond to the values for PVEUHI and
PVEULO, respectively.

Upper Range Limit URL These parameters are the respective built-in maximum
Lower Range Limit LRL and minimum limits of the transmitter and they cannot
be changed. These parameters are read-only
parameters at the Universal Station or GUS. URL must
be configured to match the URL value of the transmitter.

PV Damping DAMPING PV damping at the transmitter. Refer to PV Range

Checking and Filtering in the Smart Transmitter
Interface Point section.

Tag Identifier STITAG Transmitter identifier. This parameter is a read-only

parameter at the Universal Station or GUS.

Software Version STISWVER This parameter is a read-only parameter at the

Universal Station or GUS.

Serial Number SERIALNO Serial number (PROM) of the transmitter. This

parameter is a read-only parameter at the Universal
Station or GUS.

R688 HPM High-Performance Process Manager Control Theory 57

08/2019 Honeywell
5 Smart Transmitter Interface Point
5.2 Parameter comparisons

Smart Transmitter STI IOP Description

Database Parameter Parameter

Secondary Variable SECVAR • For a pressure transmitter, the secondary variable is

the meter-body temperature of the transmitter.
• For a temperature transmitter, the secondary variable
is the cold-junction temperature.
• For a flowmeter, the secondary variable is the
totalized value.
This parameter is a read-only parameter at the
Universal Station or GUS.

Linear/Square Root PVCHAR Refer to PV Characterization.

Characterization

Communication DECONF Refer to Smart Transmitter Communication Modes.

Mode

Cold Junction CJTACT Applicable to STT 3000 only.

Compensation Active

REFERENCE - INTERNAL
For more information on
• STI IOP, refer to the appropriate Smartline transmitter publication and to
the PM/APM Smartline Transmitter Intergration Manual.
• STI IOP parameters, refer to the PM Family Parameter Reference
Dictionary.

58 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 5 Smart Transmitter Interface Point
5.2 Parameter comparisons

STI point detail display

A detail display of a typical STI point is shown in the following figure. It also shows the
location of the transmitter database parameters.
Figure 5-2 STI Point Detail Display

DD MMM YY 08 :3 9:2 1 1

FIRST PAGE

10 0% - PVAUTO 13 .96 03 ALAR M LIMITS POINT DATA

7 5% - PVSOURC E AUTO PVHH TP PTEXECST ACTIVE

PVCAL C 13 .96 03 PVHITP ALEN BST ENABLE
5 0% - LASTPV 13 .96 03 PVLOTP OVERVAL 100
PVLL TP PNTFORM FUL L
2 5% - PVROCPTP PVRAW 13,96 03
PVROCN TP
0% -

PRIMMOD -- -- - --
SP 0.0 CONTCUT OFF RAN GE LIMITS PV COEFFIC IENTS

PV 14 .0 PT TYPE ANINNIM PVEXEUH I 1 02.9 TF 0 .0 000 0

LC N N ODE 32 PVEUH I 1 00.0
OP% PROC NET 02 PVEUL O 0.0
UC N N OD E 03 PVEXEUL O -2.9
DEV TYPE HPM UR L 12 00
MOD NU M 00 3 UR V 15 0.0
MOD TYPE STIM LR V 0.0
SLOT NUM 00 01 LR L -200.0
STI_EU DEG_C

DD MMM YY 08 :3 9:2 1 1

CONFIG PAGE
__ ____ ___ ____ ____ ___ __CONFIGUR ATION D ATA_ ___ ____ ____ ___ ____

COMMAND
PVFOR MA T D1 LOCU TOFF ------ PVLL PR NOACTION
NONE PVSRC OPT ALL PVCH AR JTHERM PVLOPR NOACTION
PVCL AMP NOCL AMP SENSR TYP STT PVROCPPR NOACTION
DN LOADDB PVALD B ONE PIUOTDC F ON PVROCN PR N OAC TION
PVALD BEU 1.000 00 BADPVPR LOW
UPL OAD DB ASSOCDSP PVHH PR NOACTION
IN PTD IR DIRECT PVHIPR HIGH
SET_LR V
Commands __ ____ ___ ____ ____ ___ __SMART TR ANSMITTER D ATA_ ___ ____ ___ __ __
SET_UR V

COR_ LRV STITAG TAPP PVRAW 13 .92 25 SECVAR 22 .90 77

SENSR TYP STT UR L 12 00.00 DAMPING 0.700 00
COR_ URV PVCH AR JTHERM UR V 0.000 00 SERIALNO 54 0893 05
CJTACT ON LR V 0.000 00 STISWVER 1.0
COR_ INPT PIUOTDC F ON LR L -199 .9 97 STATE UPD ATE
DEC ON F PV_SV_ DB STI_EU DEG_C COMMAND NONE
**MORE* *
TRANSMITTER SCR ATCH PAD : TAPP 25 62
TRANSMITTER STATUS : STATU S OKAY
ENTER
DATABASE DISCREPAN CY: 1 OF 1

Transmitter Parameters 16 114

R688 HPM High-Performance Process Manager Control Theory 59

08/2019 Honeywell
5 Smart Transmitter Interface Point
5.3 PV Characterization

5.3 PV Characterization
PV input signal processing
The PV signal (PVRAW) received from the transmitter has been characterized by the
transmitter in terms of linear or square-root characterization and damping. For the STT
3000, PVRAW is further characterized based on the entries that the user makes for the
SENSRTYP, PVCHAR, and INPTDIR parameters as shown in the Smart transmitter
input point functional diagram in the Operation section of STI Point Functional
Overview. The following table lists the PV characterization options available for the
various transmitter (sensor) types.
Sensor types and characterization options
The following table defines the STI sensor types and PV characterization options.
Table 5-1 STI sensor types and PV characterization

Sensor Type PVCHAR PVRAW1,3 PVCA PV Detection2

(SENSRTYP) Options LC

Spt_Dp Linear % in H2O EU Range check on PVCALC

(Differential
Pressure) Square Root % in H2O EU Range check on PVCALC

Spt_Gp Linear % in H2O EU Range check on PVCALC

(Gauge Pressure)

Spt_Ap Linear % in H2O EU Range check on PVCALC

(Absolute Pressure)

Stt Linear % in H2O EU Range check on PVCALC

(Temperature)4
Thermocouple % in ºC EU Open thermocouple
detection and range check
on PVCALC

RTD % in ºC EU Range check on PVCALC

RTD Ohms % in Ohms EU Range check on PVCALC

Sfm Linear % m3/Hr EU Range check on PVCALC

(Flow)

60 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 5 Smart Transmitter Interface Point
5.3 PV Characterization

Sensor Type PVCHAR PVRAW1,3 PVCA PV Detection2

(SENSRTYP) Options LC
1) PVRAW is a percentage of the configured range for the sensor type. For Multivariable
transmitters, PVRAW Engineering Units are different for each PV slot.
2) If the transmitter gross status indicates Output mode or Bad, PVRAW of the STI point
is set to NaN, and PVSTS is set to Bad.
3) The normal operating range for PVRAW (0% = PVRAWLO, 100% = PVRAWHI) is
configured by the user.
4) For the supported temperature ranges, refer to the definition of the
PVCHAR parameter in the PM Family
Parameter Reference Dictionary.

Linear Conversion
If the entry for PVCHAR is Linear, the PVRAW input from the FTA is calculated as a
proportion of the input span in percent, as determined from upper and lower range values
URV and LRV. This proportion is then used in generating an identical proportion of the
output span, as determined from PVEULO and PVEUHI shown in the following figure.
The URV and LRV values are the 100% and 0% values that correspond to the PVEUHI
and PVEULO values, respectively.

Figure 5-3 Linear Conversion STI IOP

Input to URV PVEUHI

Linear Conversion 100% Output from
Linear
Conversion

[from
(PV Value
FTA) * 100% = PVRAW ] [f(PVRAW) = PVCALC ]

0%
LRV PVEULO

R688 HPM High-Performance Process Manager Control Theory 61

08/2019 Honeywell
5 Smart Transmitter Interface Point
5.3 PV Characterization

Square-Root Conversion
If square root is selected, this function is performed by the smart transmitter in its
computation of PVRAW. The value for PVCALC is then determined in the same manner
as linear conversion. These conversion equations are provided below.
Figure 5-4 Conversion Equations

For INPTDIR = Direct:

If INPTDIR = Reverse:

Thermal conversion when using Thermocouples

Thermal linearization is available for the inputs of the Stt (temperature) transmitter.
Thermal linearization is selectable by parameter PVCHAR. The following thermocouples
are supported for an STI point:

• Btherm • Etherm • Jtherm • Ktherm

• NiNiMoTC • Ntherm • RhRad • Rtherm

• Stherm • Ttherm • W5W26TC • W3W25TC

The STI point calculates the reference junction compensation from the measured
reference junction output level. This value is stored and then later converted back to
millivolts, with respect to 0 degrees C, for each thermocouple that is to be compensated.
The external cold-junction reference compensation (CJTACT) parameter is expressed in
millivolts for the specified thermocouple and is added to the millivolt value for PVRAW.

62 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 5 Smart Transmitter Interface Point
5.4 PV Range Checking and Filtering

Thermal conversion when using RTDs

Thermal linearization is available for the inputs of the Stt (temperature) transmitter.
Thermal linearization is selectable by parameter PVCHAR. For an RTD, the STI point
calculates the lead-wire compensation and then subtracts the value from PVRAW. The
following 3-wire RTDs are supported by the STI point:

• Pt200RTD • Pt500RTD • Cu10RTD • Cu25RTD

• PtDinRTD • PtJisRTD • NicklRTD

(Pt100D) (Pt100J) (Ni500)

5.4 PV Range Checking and Filtering

PV range checking
PV range checking ensures that the PVCALC output of PV characterization is within the
limits defined by parameters PVEXEULO and PVEXEUHI.

If... then...

either of the limits is violated and the output of the range check is set to
clamping has not been specified BadPV

either of the limits is violated and the output of the range check is clamped
clamping has been specified

If the range-checked and filtered value is the final output called PVAUTO is forced
less than the value specified by the user- to PVEULO
configured LOCUTOFF parameter

PV filtering
PV filtering can be implemented at the STI IOP, or at the Smartline Transmitter. At the
STI IOP, first-order filtering is performed on PVCALC, as specified by the user through
parameter TF (filter lag time). At a transmitter, filtering is performed on the PV
depending on the value entered for the DAMPING parameter using the SFC.

R688 HPM High-Performance Process Manager Control Theory 63

08/2019 Honeywell
5 Smart Transmitter Interface Point
5.4 PV Range Checking and Filtering

You should decide the type of filtering required based on the following guidelines:
• The DAMPING parameter allows for better control accuracy because more PV
samples are used in calculating the filtered PV value at the transmitter.
• TF can be changed on-process from the Universal Station. To change the DAMPING
value requires the point to be made inactive and requires the database to be down-line
loaded to the transmitter after the change has been made.

TIP
For better control accuracy, the use of the DAMPING value is preferred over
the TF value. The transmitter accepts only certain DAMPING values from the
STI IOP, and the value received must first be converted to one of the
predefined DAMPING values that reside in the transmitter. This conversion is
accomplished automatically by the STI IOP by finding the DAMPING value
that is nearest to the desired DAMPING value.

DAMPING values differ between the Smartline Transmitters. The valid DAMPING
values for each transmitter type are contained in the following listing (values listed are
the first-order filter time constants in seconds).

Pressure (Spt) Temperature (Stt) Flow (Sfm)

0.0 0.0 0.0

0.16 0.3 0.5

0.32 0.7 1.0

0.48 1.5 2.0

1.00 3.1 3.0

2.0 6.3 4.0

4.0 12.7 5.0

8.0 25.5 10.0

16.0 51.1 50.0

32.0 102.3 100.0

64 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 5 Smart Transmitter Interface Point
5.5 PV Source Selection

5.5 PV Source Selection

The PVSOURCE parameter allows the user to select the source of the PV for this data
point. As shown in STI Functional Overview, Operation, PV can be provided by the:
• Range Checking and Filtering circuit (when PVSOURCE is Auto)
• Manually entered PV (when PVSOURCE is Man or Sub)
In addition, the PV source option parameter (PVSRCOPT) determines whether it is
permissible to change the PV source to a source other than Auto. PVSRCOPT has two
states: OnlyAuto and All. The All state allows the PV to be manually entered for this data
point.

5.6 Alarming
Function
The STI point compares the PV to threshold values and records the alarms in the
database of the data point. The alarms are then reported by the High-Performance
Process Manager Module (HPMM).
Associated parameters
The parameters that are associated with alarming in the STI point are as follows:

• ALENBST • PVHHFL • PVLOFL

• BADPVFl • PVHHPR • PVLOPR
• BADPVPR • PVHHTP • PVLOTP
• PRIMMOD • PVHIFL • PVROCNFL
• PTINAL • PVHIPR • PVROCNPR
• PVALDB • PVHITP • PVROCNTP
• PVALDBEU • PVLLFL • PVROCPFL
• PVEXHIFL • PVLLPR • PVROCPPR
• PVEXLOFL • PVLLTP • PVROCPTP

REFERENCE - INTERNAL
Refer to the PM Family Parameter Reference Dictionary for the definitions of
these parameters.

R688 HPM High-Performance Process Manager Control Theory 65

08/2019 Honeywell
5 Smart Transmitter Interface Point
5.7 Smart Transmitter Communication Modes

5.7 Smart Transmitter Communication Modes

All communications between the STI IOP and the Smartline transmitters are in bit-serial
form using the Honeywell DE (digital enhanced) protocol. The communication mode for
the transmitter is selectable through the DECONF (DE configuration mode) parameter,
whose possible entries are as follows:

DECONF Entry Definition

Analog Not supported

Pv Transmitter communicates only the PV (4-byte format)

Pv_Sv Transmitter communicates the PV and the Secondary Variable

(SV) (4-byte format)

Pv_Db see NOTE Transmitter communicates the PV and the database (6-byte
format)

Pv_Sv_Db Transmitter communicates the PV, SV, and the database (6-byte
se NOTE format)

NOTE: The use of these two modes is recommended because they offer database
mismatch detection and on-process mismatch recovery.

5.8 Database Considerations

Normal database operation
During normal operation, the STI point database and the corresponding transmitter
database contain the same information. If under special conditions, the databases are not
the same, a status message appears on the STI point's Detail Display to indicate a
database mismatch. Three possible ways that a database mismatch can occur between
the STI IOP database and the transmitter database are as follows:
• Smart Field Communicator (SFC) is used to change PV-related values in the
transmitter.
• A write operation from the Universal Station to the STI IOP (during a checkpoint
restore or point building).
• The same transmitter has been reinstalled after bench calibration, or after the
transmitter electronic module has been replaced and the LRV/URV values have been
modified.

66 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 5 Smart Transmitter Interface Point
5.8 Database Considerations

Database mismatch detection

The following parameters of the STI IOP database and the transmitter database are
compared when the STI IOP checks for database mismatches:

• CJTACT • DAMPING • DE_CONF

• FREQ60/50 • PIUOTDEN • PVCHAR

• SENSRTYP • STITAG • URL

• URV • LRV

If a database mismatch is detected, the first four parameter mismatches are displayed in
the S1 status field of the STI point's Detail Display at the Universal Station or GUS.
These mismatched parameters are preceded by the message "DATA BASE
DISCREPANCY."
Correcting a database mismatch
You can correct the mismatch by one of the following methods:
• Download the STI IOP database to the transmitter by issuing a DnLoadDb command
through the COMMAND parameter when the point is in an Inactive state. If the
loading is successful, the point STATE changes to OK when the point is made active.
• Upload the transmitter database to the STI IOP by issuing an UpLoadDb command
through the COMMAND parameter when the point is in an Inactive state. If the
loading is successful, the point STATE changes to OK when the point is made active.
• Correct the mismatched parameter using the SFC. If the parameter or parameters are
updated by the SFC to the same value as in the STI IOP database, the state changes
from Mismatch to OK when the next database transfer from the transmitter occurs.
If a mismatch occurred because the Smart Field Communicator (SFC) was used to
change a parameter in the transmitter database, the data in the transmitter database may
be correct. In this case, the STI IOP does not know which value to use and issues an
"SFC MODIFIED XMTR DATABASE" message, which appears on the Detail Display.
The user should wait until the next database transfer occurs from the transmitter before
taking action. At that time, the specific change is displayed.
A database mismatch can also occur because the transmitter was miswired during
installation. This can be fixed by correcting the transmitter wiring.
For the MagneW3000, the URL value displayed on the SFC is a factor of 10 higher than
the actual value displayed at the Universal Station. The value displayed at the SFC is the
scaled limit while the value displayed at the Universal Station represents raw data. Also,
the STI IOP does not respond to changes made in the MagneW3000 database parameters

R688 HPM High-Performance Process Manager Control Theory 67

08/2019 Honeywell
5 Smart Transmitter Interface Point
5.9 Point States

for up to 3 minutes when the database changes are made using the Local Setting Card.
This card is an option that is available with the MagneW3000.

5.9 Point States

The STATE parameter indicates the current status of the STI IOP and the transmitter.
The various states are listed in the following table.
Table 5-2 State Parameters of STI-IOP and the transmitter

States Description

OK Normal state; indicates that the STI point and the transmitter are
OK. Transmitter is updating the PV value at the STI point. STATE
remains OK when the point is made inactive.

DBChange Indicates that a database mismatch between the STI point and the
transmitter has been detected. Transmitter is not updating the PV
value at the STI point. STATE remains DBChange when the point
is made inactive.

Loading Indicates that database loading between the STI point and the
transmitter is occurring.

Loadcomp Indicates that the database transfer between the STI point and the
transmitter has been successfully completed.

Loadfail Indicates that the parameter transfer between the STI point and the
transmitter has not been successfully completed.

Calib Indicates that certain parameters are being calibrated at the

transmitter by the STI point.

Calcomp Indicates that the calibration has been successfully completed.

Calfail Indicates that the calibration has not been successfully completed.

68 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 5 Smart Transmitter Interface Point
5.10 STI IOP Commands

5.10 STI IOP Commands

The COMMAND parameter allows the engineer to load configuration parameters in the
smart transmitter and to calibrate the transmitter. (The point must first be placed in the
Inactive state through the PTEXECST parameter.) The enumerations of the COMMAND
parameter are as follows:
Table 5-3 STI-IOP command parameters

COMMAND Description
Selection

DnLoadDB Load the STI IOP database into the transmitter (down-line load)

UpLoadDb Loads the transmitter database into the STI IOP (up-line load)

Set_LRV Set the Lower Range Value

Set_URV Set the Upper Range Value

Cor_LRV Corrects the Lower Range Value

Cor_URV Corrects the Upper Range Value

Cor_Inpt Correct the zero point

RstCor Sets all input calibration parameters to their factory default values

Null A command has not been issued by the STI IOP

The result of issuing a command to an STI IOP point is reflected in the STATE
parameter for the point.

R688 HPM High-Performance Process Manager Control Theory 69

08/2019 Honeywell
5 Smart Transmitter Interface Point
5.10 STI IOP Commands

70 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 6. Analog Output Point
6.1 AO Point Functional Overview
Family
The Analog Output Point is a member of the I/O Point family.
Purpose
The analog output point converts the output value (OP) to a 4-20 mA output signal for
operating final control elements such as valves and actuators in the field. The OP
parameter value can be controlled from an HPM regulatory point, an AM regulatory
point, the operator, or a user program, depending on the selected mode and the entries for
the RCASOPT and PNTFORM parameters.
Operation
To convert the OP value to a 4-20 mA signal, the analog output point performs
• Direct/reverse Output Function.
• Nonlinear Output Characterization.
An option allows redundant Analog Output points. The following is a functional diagram
of the analog output point.

R688 HPM High-Performance Process Manager Control Theory 71

08/2019 Honeywell
6 Analog Output Point
6.1 AO Point Functional Overview

Figure 6-1Analog Output Point Functional Diagram

Output (from AM Regulatory Point)

Value RCASOPT

None

Oper Cas
Output
Value (from Operator)
MODATTR MODE
None

Man
Output
(from Program) Prog Full
Value

Componnt
Output
(from PM Regulatory Point) PNTFORM
Value

OPTDIR OP
Direct DIRECT/
REVERSE
Reverse CALCULATION

OPCHAR
On Off

OPIN0 OPOUT0
OPIN1 OPOUT1
OPIN2 OUTPUT OPOUT2
OPIN3 CHARACTERIZATION OPOUT3
OPIN4 OPOUT4
OPIN5 OPOUT5

NOTE: All parameters are shown

CALIBRATION
in the defaulted entry
COMPENSATION
positions.
OPFINAL
(To FTA) 15 014

72 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 6 Analog Output Point
6.2 Direct/Reverse Output

6.2 Direct/Reverse Output

Parameter OPTDIR allows the user to specify whether the output of the data point is
direct acting (where 4 mA = 0%, and 20 mA = 100%) or reverse acting (where 4 mA =
100%, and 20 mA = 0%). The default mode is direct acting.
Output Indication
OUTIND parameter defines how the output of an analog data point is to be displayed at
the Universal Station. The output display is determined by the selection of the value
range, which can be:
• Direct = A 4 mA output from this data point is displayed as 0% at the Universal
Station. A 20 mA output is displayed as 100%.
• Reverse = A 20 mA output from this data point is displayed as 0%. A 4 mA output is
displayed as 100%.
Nonlinear Output Characterization
Output characterization allows the user to specify an output transfer function, using
configurable X-Y coordinates that provide five linear segments. The length of each
segment is variable according to the coordinates that can be entered as applicable
constants for OPOUT1-4 and OPIN1-4 parameters, which are real numbers.
As shown in the following figure, the end points of the curve are fixed at coordinates
OPOUT0,OPIN0 (at -6.9%) and OPOUT5,OPIN5 (at 106.9%). These coordinates are
fixed at these values to ensure that neither the characterization function nor its inverse
can provide output values which are outside the -6.9% to 106.9% range.

R688 HPM High-Performance Process Manager Control Theory 73

08/2019 Honeywell
6 Analog Output Point
6.3 Calibration Compensation

Figure 6-2 Output Characterization for an Analog Output Point

OPOUT5
(106.9%)

OPOUT4

OPOUT3

OPOUT2

OPOUT1

OPOUT0
(-6.9%)
OPIN0 OPIN1 OPIN2 OPIN3 OPIN4 OPIN5
(-6.9%) (106.9%)

Depending on the output value, the analog output point interpolates linearly between the
two nearest values. The interpolated value becomes the output value OPFINAL.
Output characterization is an optional function that can be implemented by setting
parameter OPCHAR to On.

6.3 Calibration Compensation

The final stage of output processing in the analog output point is calibration
compensation. This is accomplished in the data point using internal offset and scale
constants. The output value OPFINAL is then routed to the field through the appropriate
FTA.

ATTENTION
Slot or module level soft failures can prevent a point (or points) from
outputting to the field. The regulatory control point will initiate a "Bad Output"
alarm (If configured) when any connection is broken. If all configured point
connections to the field are broken, the regulatory control point driving that
analog output slot goes into initialization.

74 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 6 Analog Output Point
6.4 Disable Output Alarming when Using Open-Line Detection

6.4 Disable Output Alarming when Using Open-Line

Detection
With R640, $OLDEVDSdisables the alarms associated with an open AO output line.
This function allows you to disable the OUTPUTFL soft failure alarms generated by the
AO IOPs when transmitters or positioners are physically disconnected for normal
maintenance.

6.5 Pre-determine the mode of the point when error

occurs in IOL/IOP communication
With R680, $BADOCMD parameter is added to the regulatory control points. This
parameter allows you to pre-determine the mode of the point to either
• hold at its current value,
or
• switch to the MANual mode when there is a communication error.
Depending on the values configured, the initialization request is set, the upstream points
are initialized, and the control is frozen.
The sequence of events in a point and the four enumeration values are described in the
following table:
Table 6-1 Event sequence

If the Enumeration Then this is the sequence of events for the point…
value is this …
During an IOP communication After an IOP communication
error error

SHEDMAN Initialization request is set. Initialization request is reset.

Mode sheds to MANual. Mode remains in MANual.

15_SEC Initialization request is set. If If the error ceases before 15

error exists even after 15 seconds, the initialization
seconds, then mode sheds to request is reset and the point
MANual. continues to work as earlier.
Otherwise, the initialization
request is reset and the mode
remains in MANual.

R688 HPM High-Performance Process Manager Control Theory 75

08/2019 Honeywell
6 Analog Output Point
6.5 Pre-determine the mode of the point when error occurs in IOL/IOP communication

If the Enumeration Then this is the sequence of events for the point…
value is this …
During an IOP communication After an IOP communication
error error

60_SEC Initialization request is set. If If the error ceases before 60

error exists even after 60 seconds then the initialization
seconds, then mode sheds to request is reset and the point
MANual. continues to work as earlier.
Otherwise, the initialization
request is reset and the mode
remains in MANual.

NO_SHED Initialization request is set. Initialization request is reset.

The point continues to work as
earlier.

76 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 7. Digital Input Points
7.1 DI Points Functional Overview
Family
The digital input point is a member of the I/O family of points.
Purpose
A digital input point converts a digital PVRAW signal received from the field to a PV
that can be used by other data points in the HPM and the system. A functional diagram of
the digital input point is shown in the following figure.

R688 HPM High-Performance Process Manager Control Theory 77

08/2019 Honeywell
7 Digital Input Points
7.1 DI Points Functional Overview

Figure 7-1Digital Input Point Functional Diagram

PVRAW NOTE: All parameters are shown in

(from field) the defaulted entry positions.
Direct
INPUT
Reverse DIRECTION
INPTDIR

DITYPE
Accum

Status PV
OVERVAL
Latched
None STARTFL
1.5 Sec
Start STOPFL
Command Stop UP/ RESETFL
Reset DOWN
ACCUMULATION
PVAUTO OLDAV

PVman PV AVTVFL
(from Operator) SOURCE Countdown OVERFLOW
PVsubstituted Resetval
(from Program)
Only AVTV
All Auto
AV
PVSRCOPT
PV
DITYPE = Status DITYPE = Latched or Status
PV PV
EVTOPT
ALMOPT
None
EIPSOE
None ChngOfSt SOE EIP

Offnorml
(EIPPCODE)
DLYTIME
(TIME STAMP)
(N/A for latched inputs)
ALENBST
EIPPCODE & TIME STAMP
Enable Inhibit
(N/A for latched inputs)
Disable
PV

Printer Printer
JnlPrint JnlPrint
Emergncy Emergncy BADPVPR
OFFNRMPR ALARM
Low DETECTION Low
High High
Journal Journal
NoAction NoAction
PVNORMFL

PVNORMAL OFFNRMFL

16 11 6
HIGHAL HIGHALPR

78 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 7 Digital Input Points
7.1 DI Points Functional Overview

Current state
The current state of the PV input is represented on the Universal Station Group and
Detail Displays as two boxes, as shown in the following figure. The boxes are lighted or
extinguished depending on the current state of PVRAW and the input direction as
configured through the INPTDIR parameter, as shown in the chart in the following
figure. The current PV state is also available to be used as an input to logic slots, and
other HPM control functions.
Figure 7-2 DI Input States

STATE 1
BOX
(Upper)
STATETXT (1)

STATE 0
BOX
(Lower)
STATETXT (0)

PVRAW INPTDIR = INPTDIR =

State Direct Reverse

PV = ON. PV = OFF.
State 1 Box is State 0 Box is
ON lighted. lighted.
State 0 Box is State 1 Box is
extinguished. extinguished.

PV = OFF. PV = ON.
State 0 Box is State 1 Box is
OFF lighted. lighted.
State 1 Box is State 0 Box is
extinguished. extinguished.

R688 HPM High-Performance Process Manager Control Theory 79

08/2019 Honeywell
7 Digital Input Points
7.2 Status Digital Input Point

Bad PV flag
Control strategies can test for a bad Digital Input PV. Parameter BADPVFL is set ON
when PV source:
• has been switched to Substituted, and the point is inactive or the module status is
Idle.
• is AUTO and the PV is not being updated, because either the point is inactive, the
module is idle, there is a slot soft failure, or the FTA is missing.
Digital input point types
The digital input point is a single-input point that can be configured as:
• Status Digital Input Point.
• Latched Digital Input Point.
• Accumulation Digital Input Point.

7.2 Status Digital Input Point

Description
For this digital input type, the PVAUTO value represents the state of the raw input signal
after the direct/reverse conversion is performed. The status digital-input point can be
configured for PV source selection, detection of off-normal alarms, and for reporting any
PV state changes to the system. The status digital input point is selected by entering
Status for the DITYPE parameter.
PV source selection
The PV source parameter (PVSOURCE) option determines the source of the PV for a
status input point. The source can be the PV input from the field (PVauto), the PV state
entered by the operator (PVman), or it can be supplied by a user program (PVsub).
PVSOURCE has no effect on the latched and accumulation options of the digital input
point. If PVSOURCE is PVauto, PV tracks PVRAW.
Off-normal alarming
Enabling, Disabling, and Inhibiting Off-Normal Alarms
The ALENBST parameter allows the operator to enable (permit), disable, or inhibit the
off-normal alarm. Disabling the alarm still allows the alarm to be listed on the Group and
Detail displays. Inhibiting the alarm prevents the current PV state from being compared
to the configured normal state.

80 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 7 Digital Input Points
7.2 Status Digital Input Point

Off-Normal Alarming & PV Change Reporting

Off-normal alarming can be selected for the digital input point through the ALMOPT
parameter. An off-normal alarm is generated when the input PV state is different than the
configured normal (desired) state for the point as specified by the PVNORMAL
parameter. The priority of the off-normal alarm is determined through the OFFNRMPR
parameter (ALPRIOR may also be used to maintain compatibility with schematics and
CL programs designed for pre-R500 software).
Additionally, all PV state changes can be historized as determined by HM volume
configuration.

Change Of State Reporting

Digital Input Status points (and Sequence of Events points) can be configured for Change
Of State (COS) alarm reporting through the ALMOPT parameter. The alarm is generated
when the input changes state in either direction. Alarm priority is determined through the
OFFNRMPR/ALPRIOR parameters as before.
COS alarms are removed from the Alarm Summary display following acknowledgement.
The Point does not remain in alarm so there is no Return-to-Normal. Point Detail or
Group displays will never show a point in COS alarm.
Older digital input IOPs may need to have a new firmware chip for COS reporting.
Check the IOP's detail display. For COS reporting the Digital Input IOP firmware
revision must be 5.0 or later.
Note that when a point with COS reporting is changed from Inactive to Active, a COS
alarm is generated if the PV = 1. There is no COS alarm if the PV = 0. The same
alarming occurs if the point is active and the IOP is put into Run mode.

Digital Input Alarm Delay

With R660, parameter $DLYOPT allows you to select one of the following four alarm-
delay options:
• PMOFFDLY – Existing alarm-delay option with delay time specified by DLYTIME
parameter (IOP based).
• NMOFFDLY – NIM based alarm off-delay option.
• NMONDLY – NIM based alarm on-delay option.
• None – Alarms are not delayed.
The alarm delay option can be disabled in one of the following ways:
• Setting the DLYTIME parameter to 0, or
• Setting the $DLYOPT option to None.
Note that you can switch between the options and retain the delay time.

R688 HPM High-Performance Process Manager Control Theory 81

08/2019 Honeywell
7 Digital Input Points
7.2 Status Digital Input Point

Note1: If a point is in alarm delay, and the CONTCUT parameter for the point is enabled,
the delay timer is terminated. When CONTCUT is disabled, the subsequent alarms
follow the configured delay.
Note 2: If a point's return-to-normal condition is delayed because of the OFF delay and
CONTCUT is made TRUE and then FALSE, the return-to-normal condition is reported
immediately. If a point's alarm is delayed because of the ON delay and CONTCUT is
made TRUE and then FALSE, the alarm is reported only after the configured delay
period.
PM OFF delay—When off-normal alarming has been configured and $DLYOPT is
configured as PMOFFDLY, any off-normal event is detected and reported to the system.
Further off-normal alarms for the same data point are not reported until the time delay (0
to 60 seconds) specified by the DLYTIME parameter expires. When the time delay
expires, the time-delay function is disabled and the off-normal alarm for the data point
can again be reported.
For Change of State alarms, when a PV state change occurs, a COS alarm is produced
and the delay timer is started. When DLYTIME expires, two situations are possible:
• the PV is in the same state and future state changes are immediately alarmed.
• the PV is in the opposite state (it may have changed many times during the
DLYTIME period) so a second COS alarm is produced and the timer starts again.
NIM ON delay— With R660, when the alarm delay option $DLYOPT is configured as
NIMONDLY and an off-normal alarm is detected, the event is not reported to the system
until the time delay (0 to 9999 seconds) specified by the DLYTIME parameter has
expired. When the time delay expires, if the point is still in alarm, the time-delay function
is disabled and the off-normal alarm for the data point is reported. After the time delay
expires, no action is taken if the point ceases to be in the alarm condition.
NIM OFF delay— With R660, when the alarm delay option $DLYOPT is configured as
NIMOFFDLY, and when the point returns to the normal state from the alarm state, the
return-to-normal is not reported to the system until the delay time (0 to 9999 seconds)
specified by DLYTIME parameter has expired. When the time delay expires and the
point continues to be in the normal condition, the return-to-normal condition is reported.
After the time delay expires, no action is taken when the point ceases to be in the return
to normal condition.
Note that the DLYTIME parameter is resident in both the NIM and the IOP, and they are
synchronized. With R660, view-only parameter $PMDLYTM is provided to monitor the
value of IOP DLYTIME value. This parameter shows 0 when $DLYOPT is set to
NMOFFDLY, NMONDLY or NONE. When $DLYOPT is set to PMOFFDLY, the
parameter shows the value specified for DLYTIME.
NIM OFF delay— With R681, the OFF delay feature is provided for BADPV and
BADCTL alarms using the new $DLBADAL parameter. This parameter allows you to

82 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 7 Digital Input Points
7.2 Status Digital Input Point

delay the return to normal condition (RTN) for a time as specified by the DLYTIME
parameter.
During delay period, if any of the BADPV or BADCTL alarm returns to normal, the
timer is restarted from its initial configured value. When the timer expires and the point
is not in alarm, the return to normal is reported. The RTN event is reported with the time
stamp when the timer expires and not the actual RTN time.
While in delay, the following instances can cause the RTN to get reported before expiry
of the timer:
• Change in $DLBADAL parameter value, and change in DLYTIME.
• Change in priority of the BADPV and BADCTL alarms.
Note: The OFF delay feature does not delay reporting of alarms; it delays only the return
to normal (RTN).
Alarm delay reset— The Alarm delay can be reset by any of the following events:
• When $DLYOPT is set to NMONDLY, if the input chatters during the alarm delay
period, the delay time is reset and restarted whenever the point goes into the alarm
state.
• When $DLYOPT is set to NMOFFDLY, if the input chatters during the alarm delay
period, the delay time is reset and restarted whenever the point goes to the return- to-
normal state.

R688 HPM High-Performance Process Manager Control Theory 83

08/2019 Honeywell
7 Digital Input Points
7.2 Status Digital Input Point

Scenarios
• When the delay timer is running, if the NIM/xPM/IOP switches over to its redundant
partner during an existing alarm condition, which is being delayed, the delayed
alarm is reported immediately.
• If there is a change in the value of DLYTIME when the $DLYOPT is NMONDLY
or NMOFFDLY and the delay timer is running the alarm will be reported
immediately and the new value is in effect from the next cycle.
• If there is a change in the value of DLYTIME when the $DLYOPT is PMOFFDLY
and the delay timer is running the new value is not applied until the delay time for
that cycle is completed.
• If there is a change in the value of $DLYOPT from PMOFFDLY to NMOFFDLY or
NMONDLY or NONE, the new value is not applied until the delay time for that
cycle is completed.
• If there is a change in the value of $DLYOPT from NMOFFDLY or NMONDLY or
NONE to PMOFFDLY or NMONDLY or NMOFFDLY or NONE, the new value is
taken into effect immediately.
• Whenever there is a configuration change that affects the alarm (like priority change,
ALENBST change, AUXUNIT change, or contact cutout change) and if the delay
timer is running, the timer will be terminated, and the delayed alarm will be reported
immediately.
Note that when the value of $DLYOPT is set to PMOFFDLY, if the input chatters during
the alarm delay time, the delay time is not restarted.
Note: Change of state alarms are momentary state change alarms and do not have Return
to Normal events. Therefore, they must not be configured for NMOFFDLY. In addition,
if there is an alarm-related configuration change when the Change of State alarm is
subjected to delay, the delayed alarm may not be reported.

Event Reporting
The EVTOPT parameter for the status input allows the user to optionally specify the tag
name (EIPPCODE) of a data point in the system that is to be notified when the PV
changes state, and/or specify that a time stamp be added to the reported PV state change.
For a status input point, EVTOPT has the four possible entries: None, EIP, SOE, and
EIPSOE. EIP specifies that the user supply the tag name of the data point in the system
that is to receive the PV state change, while SOE specifies that a time stamp is added to
the PV state change to establish a sequence of events.

Change of State Reporting can initiate Event Initiated Processing if the point is
configured for both COS and EIP. Note that digital input points that have COS (or Off

84 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 7 Digital Input Points
7.3 Latched Digital Input Point

Normal alarming) and EVTOPT EIP configured will have EIP triggered twice. EIP
processing associated with COS reporting is not recoverable for NIM/HPM failovers.
Full EIP recovery is available for DISOE points.

7.3 Latched Digital Input Point

Description
To capture the occurrence of momentary digital inputs, such as from pushbuttons,
requires you to configure the digital input point as a latched digital input point.
Configuring the point as a latched point is accomplished by entering Latched for the
DITYPE parameter.
When configured as a latched input point, an input pulse that is on for a minimum of 40
milliseconds is latched true for 1.5 seconds. This ensures that any control function that
needs to monitor this event will execute at least once during the time that the signal is
latched on.
The current state of the latched PV input is represented on the Universal Station Group
and Detail displays as two boxes, as shown DI Functional Overview. The boxes are
lighted or extinguished depending on the current state of PVRAW and the input direction
as configured through the INPTDIR parameter. The current PV state is also available to
be used as an input to logic slots, and other HPM control functions.
Event reporting
The EVTOPT parameter for the latched input allows the user to optionally specify the tag
name (EIPPCODE) of a data point in the system that is to be notified when the PV
changes state. For a latched input point, EVTOPT has two possible entries: None and
EIP.

7.4 Accumulation Digital Input Point

Description
The accumulation type digital input point counts the transitions of the digital input pulses
received from the field. The digital input point is configured for accumulation by
entering Accum for the DITYPE parameter.
Up/Down accumulation
The accumulation type digital-input point can be incremented or decremented depending
on the entry made for the COUNTDWN parameter. If the entry for this parameter is Off,
the point is to be incremented by the field transitions; if the entry is On, the point is
decremented. The accumulated or decremented value is the value of parameter AV.

R688 HPM High-Performance Process Manager Control Theory 85

08/2019 Honeywell
7 Digital Input Points
7.4 Accumulation Digital Input Point

Accumulator commands
The operator has the capability of issuing start, stop, and reset commands to the
accumulator for starting, stopping, and resetting the accumulation. For resetting the
accumulator, the operator can specify the value to which the accumulator is reset by
using the RESETVAL parameter to enter the value. When the accumulator is reset, the
old accumulated value is displayed using the OLDAV parameter.
Target value
The operator can specify the accumulator target value through the AVTV parameter.
When the accumulated value (PVAUTO) reaches the target value (PVTV), parameter
AVTVFL is set to On. AVTVFL is set to Off when the accumulator is reset.
Overflow
If the accumulated value AV overflows the accumulator (AV > 32767), the OVERFLOW
parameter is set to On. In addition, it is set to 0 when the accumulator is configured for
counting up (incrementing); it is set to 32767 if it is configured for counting down
(decrementing).

86 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 7 Digital Input Points
7.5 Sequence of Events Digital Input Point

7.5 Sequence of Events Digital Input Point

Description
Sequence of Events (SOE) points are used to report the order of occurrence of physical
events. The SOE digital input IOPs can use the same type FTAs as digital input cards,
but the best overall performance is obtained when using the high resolution 24 VDC
Digital Input FTAs.
SOE events are recorded in a journal with a timestamp so that you can determine, for
example, which event started an upset and the progression of events thereafter. The
record includes the point ID, point descriptor, state text unit, and time of occurrence to
one ms resolution. Refer to the Engineer’s Reference Manual for a discussion of SOE
Journal size requirements. For SOE Journal and Process Unit Journal Configuration
requirements refer to the Network Configuration Forms Instruction manual.
SOE points can also be configured for Change of State Reporting (an alarm is generated
when the input changes state in either direction).
Each sequence of events IOP card provides 32 status and/or latched type inputs.

R688 HPM High-Performance Process Manager Control Theory 87

08/2019 Honeywell
7 Digital Input Points
7.5 Sequence of Events Digital Input Point

Figure 7-3 SOE digital input point functional diagram

PVRA W NOTE: A ll parameters are shown in

(from field) the defa ulted entry positions.
Direct
INPUT
Reverse
INPTDIR DIRECTION

DITYPE

Status
Latched

1.5 Sec

PVAUTO
PVma n PV
(from Operator) SOURCE
PVsubstituted
(from Pro gram)
Only
All Auto
PVSRCOPT
PV
DITYPE = Status DITYPE = La tched or Status PVCHGDLY
PV PV

ALMOPT

Non e Chn gOfSt

Offn orml EVTOPT

EIPSOE Non e
DLYTIME SOE EIP
(EIPPCODE)

ALENBST D
(TIME STAMP) e
Enable Inhibit (N/A for latched inputs) l
a
Disable y
EIPPCODE & TIME STAMP
(N/A for latched inputs)
Printe r Printe r
PV
Jn lP rint Jn lP rint

Emergncy Emergn cy BADP VPR

OFFNRMPR ALARM
Low DETECTION Low

High High
Jo urnal Jo urnal
NoA ctio n NoA ctio n
PVNORMFL
PVNORMAL OFFNRMFL

HIGHAL HIGHALPR

88 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 7 Digital Input Points
7.5 Sequence of Events Digital Input Point

Timestamping
Timestamps are based on the "wall clock" time entered in the LCN. Time is broadcast
over the UCN every six seconds by the NIM with the lowest UCN address. To do this,
the time synch parameter (TIMESYNC) must be enabled during NIM configuration and
the NIM must contain an EPNI card. If there is a redundant NIM, its TIMESYNC
parameter should also have been enabled in case the primary NIM fails.
The HPMM receives time sync messages from the NIM and broadcasts time synch
messages on its own I/O Link every two seconds to the Sequence of Events IOPs. The
IOP time stamps an input state change with a code that is converted to, and reported as,
wall clock time by the HPMMs. Each IOP can store up to 20 seconds of state changes
(for all 32 points) before older events are overwritten.
If an HPMM fails, or if event collection by the HPMM is stopped or delayed, or if the
buffer in the IOP becomes full, the IOP rejects newer events (that is, it saves the older
events).
If the DISOE IOP hardware detects loss of one or more physical events, then an SOE
Lost event packet is passed in the System Status Journal (not the SOE Journal). This
packet contains the time at which lost events were detected, and should be used in
conjunction with the SOE journal to correlate the SOE events. SOE lost events are
usually caused by a chattering input.
Specifications and reporting
Resolution
The operator sees one millisecond resolution as reported in the SOE Journal. Event time
is reported in hours, minutes, seconds, and milliseconds. The entries are further sorted at
a sub-millisecond level that affects the order of entry but does not appear in the journal.

Reporting
Typical SOE Journal entries appear as follows:
Date (MM/DD/YY)
10:50:21:848 SE150501 ON
10:50:21:849 SE150501 OFF
10:50:21:850 SE150502 ON
10:50:21:851 SE150502 OFF
Minimum physical event separation
The following table shows the guaranteed Minimum Physical Event Separation (MPES)
values using various Field Termination Assemblies for two digital state change events
occurring between two points. In one case the events are on the same IOP. In the other

R688 HPM High-Performance Process Manager Control Theory 89

08/2019 Honeywell
7 Digital Input Points
7.5 Sequence of Events Digital Input Point

case, assume that the events are in different HPMMs on two separate UCNs, logical or
physical, or in case of NIM failover. Assume that both points are using the same type of
FTA. These specifications implicitly include DISOE IOP and/or HPMM failovers, are
valid for stable system operating conditions, and represents the guaranteed worst-case
conditions.

Digital Input FTA Type and Model # MPES

2 Turn-On Events 2 Events (On/Off)

in Same IOP on Different UCNs

High Resolution 24Vdc (MU/C-TDID12/52) 3.0ms 6.5ms

Galvanic 24Vd (MU/C-GDID12/13/82/83) 6.6ms 7.4ms

Low Cost 24Vdc (MU/C-TDID72) 10.6ms 10.6ms

120Vac (MU/C-TDIA12/52) 44.1ms 44.1ms

240Vac (MU/C-TDIA22/62) 44.1ms 44.1ms

Configuration
Digital input SOE IOP points are configured by selecting the DIGITAL INPUT target
from the NIM Point Build Menu. The configuration considerations are similar to those
described for the conventional digital input point, with the following additions.

PNTMODTY
For Point Module Type, select DISOE.

DITYPE
Choose STATUS as the Digital Input Type. Note that the SOE IOP can be used as a
conventional digital input point if you choose Latched.

90 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 7 Digital Input Points
7.5 Sequence of Events Digital Input Point

DEBOUNCE
The contact debounce time parameter specifies the time interval used to debounce an
input from mechanical contacts of a field input source. It is defined as the length of time
following an input state change during which the input must remain unchanged in the
new state to declare it a valid event. DEBOUNCE has a range of - 50 milliseconds in one
millisecond increments. The default value of 10 ms should suffice for most contacts. If
not, choose a value slightly longer than the manufacturer's specified contact bounce
time.
The following figures illustrate debounce operation.

A B C

• This waveform represents the field input.

• Tick marks across the waveform indicate the 200 microsecond scan intervals of the
DISOE IOP hardware.
• Assume that the input state changes at point A.
• At point B, the state change is detected, the current time and old state are recorded
and the debounce timer is started.

A B C D E F

• If the input—
− remains at a steady state until the debounce timer expires, then an event is
generated with a timestamp corresponding to the time of detection (point B).
− changes before the debounce timer expires (point c), then the change of state
event detected at B is discarded, the timer is restarted and runs for the full
debounce time.
• If a new input detected at D remains in a steady state until the debounce timer
expires (point F), then an event is generated with a timestamp corresponding to the
original time of detection (point D).
R688 HPM High-Performance Process Manager Control Theory 91
08/2019 Honeywell
7 Digital Input Points
7.5 Sequence of Events Digital Input Point

• If the input has returned to the old state (dotted line at E) when the debounce timer
runs out (point F), no event is generated.

PVCHGDLY
The PV change delay parameter specifies the time of separation in seconds for reporting
two consecutive PV change events from the same input source. It is intended to prevent
repeated rapid reporting of PV change events (that is, chattering). It can be configured
over a 0–60 second range in one second increments. It applies to points configured as
EIP, EIPSOE, or SOE only. Ideally, PVCHGDLY AND DLYTIME should have the
same value.
When a PV state change is detected, the change is reported and the PV change delay
timer is started.
If the PV state
• does not change before the delay timer runs out, no further action is taken.
• changes only once before the delay timer runs out, this second event is noticed and
timestamped with the actual time of detection, but it is not reported until the delay
timer expires.
• changes more than once before the PV change delay timer runs out, only the last
state change is noticed and timestamped but not yet reported. When the delay timer
expires, if the PV state is—
− different from the state that started the timer, this event is reported.
− is the same as the original PV state that started the timer, no event is reported.

92 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 8. Digital Output Point
8.1 DO Point Functional Overview
Family
The digital output point is a member of the I/O Point family.
Purpose
The digital output point provides a digital output to the field based on the origin of the
input and the configured parameters.
Description
A functional diagram of the digital output point is shown in the following figure. The
digital output point does not have any modes.
Figure 8-1 Digital Output Point Functional Diagram

OP (from PID Algorithm)

PWM
DOTYPE
Status
OUTDIR
Direct
Reverse

ONPULSE ON-PULSE PULSEWIDTH

PERIOD
GENERATOR MODULATOR

OFFPULSE OFF-PULSE
From GENERATOR
Digital Composite
Point or
Logic Block
SO

SO

(TO FTA) (TO FTA) (TO FTA)

DO point types
There are two types of digital output points:
• Pulse Width Modulated DO Point.

R688 HPM High-Performance Process Manager Control Theory 93

08/2019 Honeywell
8 Digital Output Point
8.2 Pulse Width Modulated DO Point

• Status DO Point.
Selection of the output type is accomplished through the DOTYPE parameter shown in
the figure illustrated in DO Point Functional Overview, Description. Actual output action
can be status, latched or momentary, depending on the configuration of the digital
composite point. The default for untagged component DO points is Status.

8.2 Pulse Width Modulated DO Point

PWM DO point use
The Pulse Width Modulated (PWM) type is used in combination with RegCtl algorithms
to provide true proportional control.
PWM DO point input
The pulse width modulated output type can receive its input from an HPM regulatory
point (that has been configured for a PID type algorithm) through a user-specified output
connection. The length of the pulse is derived from the OP parameter provided by the
regulatory point. Because OP is in percent, the percent value becomes the percent on-
time for the pulse whose period (1 to 120 seconds) is specified by the PERIOD
parameter, as shown in the timing diagram in the following figure.
Figure 8-2 PWM Type Digital Output Point Waveforms

Start of Period Start of Period

OP
(On-Time in %)

OPTDIR = Direct OUTPUT

Period (1 to 120 Seconds)

OUTPUT
OPTDIR = Reverse

PWM DO point output

The output direction of the output signal can be configured to be direct or reverse acting
by using the OPTDIR parameter, as shown in the timing diagram in the figure illustrated
in Pulse Width Modulated DO Point, PWM DO point input.
Calculating PWM DO point pulse on-time
94 HPM High-Performance Process Manager Control Theory R688
Honeywell 08/2019
 8 Digital Output Point
8.2 Pulse Width Modulated DO Point

The pulse on-time for direct and reverse acting outputs is calculated as defined in the
following table.
Figure 8-3 Calculation of pulse-on-time and reverse acting outputs

For direct action:

OP% * PERIOD
Pulse On-Time =
100

For reverse action:

100% - OP% * PERIOD

Pulse On-Time =
100

ATTENTION
If the value of OP is less than 0%, it is clamped to 0%; an OP with a value
greater than 100% is clamped to 100%.

Initialization Request Flag

Parameter INITREQ is set ON when a PWM type output is configured.

ATTENTION
Digital Composite points or Position Proportional control algorithms are
automatically forced to initialize when outputting to a Digital Output point
whose INITREQ is ON.

R688 HPM High-Performance Process Manager Control Theory 95

08/2019 Honeywell
8 Digital Output Point
8.3 Status DO Point

8.3 Status DO Point

Status DO point use
The status type output is the normal configuration for digital outputs that are linked to
digital composite points.
Status DO point input
The status output type can be controlled from a digital composite-point output, a logic
slot output, or a RegCtl point (that has been configured for the PosProp algorithm) as
determined by the output connection.
Status DO point output functions
Output latch function
The output latch function is obtained by linking digital composite-point output
connections to the SO parameter.

Pulsed output function

Pulsed operation (pulse-on or pulse-off) can be obtained by linking the output
connections to the ONPULSE and OFFPULSE parameters, respectively.
The ONPULSE parameter sets SO to On for the specified duration, as shown in the
following figure.

96 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 8 Digital Output Point
8.3 Status DO Point

Figure 8-4 Status Type Digital Output Point Waveforms

ONPULSE
(0 TO 60 Seconds)

OUTPUT
SO

OUTPUT
SO

OFFPULSE
(0 TO 60 Seconds)

At the end of the pulse time, SO is set to Off. If ONPULSE is specified as 0.0, SO is
immediately set to Off. This also applies to the OFFPULSE, except that the OFFPULSE
sets SO to Off.
If SO is received from a logic slot, the SO output of the digital output point tracks the SO
output provided by the logic slot.
Initialization Request Flag
When ON, this parameter indicates control strategies in the HPM cannot manipulate the
output. Parameter INITREQ is set ON when a Status Output type is configured and:
• the point is inactive.
• the module is idle.
• there is a soft failure such that the point is not working.

ATTENTION
Digital Composite points or Position Proportional control algorithms are
automatically forced to initialize when outputting to a Digital Output point
whose INITREQ is ON.

R688 HPM High-Performance Process Manager Control Theory 97

08/2019 Honeywell
8 Digital Output Point
8.3 Status DO Point

98 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 9. Pulse Input Point
9.1 Pulse Input Point Functional Overview
Family
The pulse input point is a member of the I/O Point family.
Purpose
The Pulse Input IOP accepts variable frequencies from a variety of devices such as
turbine meters, vortex type flow meters and positive displacement meters and converts
input pulses to flow rate in engineering units.
Description
The Pulse Input IOP accepts variable frequencies from a variety of devices such as
turbine meters, vortex type flow meters and positive displacement meters and converts
input pulses to flow rate in engineering units. Each Pulse IOP module contains eight
input points. The input frequency supported is up to 20 kHz per channel. Alarming and
filtering are provided by the IOP. Pulse Input points are configured under the Analog
Input point selection on the NIM Process Point Building Menu. The following figure
illustrates a functional drawing of the Pulse IOP.

R688 HPM High-Performance Process Manager Control Theory 99

08/2019 Honeywell
9 Pulse Input Point
9.1 Pulse Input Point Functional Overview

Figure 9-1 Pulse Input Point Functional Diagram

P AV
V $ACC SR C

3 2-BIT
PVRAW C
ACCUMUL ATION PV
H
A
R
A
Second s C C1
T
TIMEBASE Minu te s C2
E
Hou rs R
I
Z
A
T
I
PVEULO
O
PVEUHI N

PVCALC
(in Eu )
PVCLAMP Nocl amp
PVEXEU HI Ran ge Cl amp
PVEXEU LO Che cki ng
PVEXHIFL
TF & PV
PVEXLOFL
Filteri ng

PVAUTO
PNTFORM
Com ponn t
PVMan or PVSu b Full
(from Operator or Progra m)
PVAUTO
PV
PVSOU RCE
Man/Sub Auto Auto
PVEUHI PVP (PV in % )
Man/Sub NORMALIZATION
PVEULO LASTPV

PVEXEU HI RANGE PVEXHIFL

PVEXEU LO CHECKING PVEXLOFL

PV

Enab le ALENBST
Inhi bit
Di sable
Hal f
One A
Two L
PVALDB Three A HIGHAL
Four R
Five M

PVHITP D PVHIFL
PVHIPR E
• •
• T •
PV AL ARM • PV AL ARM
• E •
TRIP POIN TS • •
• C FLAGS
AND PRIOR ITIES
PVROCPTP T PVROCNFL
PVROCPPR I PVROCPFL
O
N

PTINAL

100 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 9 Pulse Input Point
9.2 PVCALC

Operation
For each point, the IOP is able to calculate flow rate in engineering units based on user
selected scaling factors. The Pulse IOP module always provides two related functions
simultaneously:

• Totalizing • Frequency counting

Totalizing
Totalizing means the IOP maintains a 32-bit accumulation (AV) for each channel
(updated every 20 ms). The least significant bits are provided by the hardware
accumulator. The 32-bit entity continually rolls (that is, there is no start, stop, or reset).
The Pulse IOP only sets the parameter AV to zero when the point is inactive, the IOP is
in Idle, or an error is detected. In the case of an error, status parameter AVSTS is set to
BAD.
Frequency counting
Frequency counting is expressed by parameter PVRAW.
Delta_AV
PVRAW = = Pulses Per Second
Elapsed Time Seconds
The frequency of the input pulse train must be greater than 0.4 Hz for the calculated PV
for that point to be correct. The AV is correct under all circumstances.

9.2 PVCALC
Calculating PVCALC
PVCALC is PVRAW after scaling (for example, barrels per minute):

R688 HPM High-Performance Process Manager Control Theory 101

08/2019 Honeywell
9 Pulse Input Point
9.2 PVCALC

C1
PVCALC = • TIMESBASE • PVRAW
C2
• C1 is an engineering units scale factor and is dimensionless, for example, barrels per
gallon).
• TIMEBASE is a time scale factor (seconds, minutes, or hours).
• C2 is a meter factor in pulses per engineering unit (for example, pulses per gallon).

TIP
If the instrument vendor supplies the factor K in engineering units per pulse
(for example, gallons per pulse), then C2 must represent the reciprocal of the
factor K; that is, C2 = 1/K.

Rate Value
The rate value is treated similar to an analog input PV and is supported by high/low
alarms, Rate of Change (ROC) alarming, filtering, and so on, on a half second processing
interval (every four seconds for ROC only).
The Pulse IOP calculates the unsigned integer AVDELTHS every half second.
AVDELTHS is the change in AV from the last half second and is intended for display
purposes. The parameter’s value is normally constant, but the operator will observe a
change if the pulse input rate varies.
Pulse Period
The pulse period (1/PV) can be determined with CL.

102 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 10. Serial Interface Point
10.1 Serial Interface Point Functional Overview
Family
The serial interface point is a member of the I/O point family.
Purpose
The Serial Interface IOP provides bi-directional interfaces to various programmable logic
controllers (PLC) and other Honeywell-approved serial devices that are compatible with
one of several interfaces.
Description
The following block diagram illustrates the Serial Interface IOP and associated hardware.
Figure 10-1 Serial Interface Point Hardware Block Diagram

APM

FTA To Field
1 Device

SI Power
IOP Panel

FTA To Field
2 Device

Each active SI slot must have a corresponding Array point. Data collected through the SI
slot is available as local data for use by Digital Composite points, Device Control points,
CL programs, and so on.

R688 HPM High-Performance Process Manager Control Theory 103

08/2019 Honeywell
10 Serial Interface Point
10.2 Serial Input Point Operation

10.2 Serial Input Point Operation

Communications
Communications to the field device is by EIA RS-232D or EIA RS-485 standards. RS-
232D communication has a limit of 15 meters (50 feet) and RS-422/485 protocol is
supported to 1.2 km (4000 feet). You can extend EIA RS-232D Communications
between an FTA and a field device with appropriate Modems.

ATTENTION
Not all EIA RS-232D or EIA RS-485 signals are supported.

Function
Each Serial Interface IOP connects to one or two FTA assemblies. There are 32 slots per
Serial I/O card. 16 slots can be configured to FTA-1 and 16 slots can be configured to
FTA-2.
Supported interfaces
Each of the 32 Serial Interface slots can support up to 512 Flags, 16 Reals, 32 Integers, or
64 ASCII characters of contiguous data to/from a field device. Plug-in modules adapt the
FTAs for different communications protocols and applications. Qualified applications
include:
• Modbus Interface—
− Modicon Modbus-RTU protocol with extensions for real numbers and string
support).
− Modicon 984 programmable logic controller.
− Rosemount Micro-Motion Transmitter.
− Other Honeywell-approved Modbus compatible devices.
• Allen-Bradley Interface—
− Allen-Bradley PLC-2, 3, and 5 programmable logic controllers.

104 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 10 Serial Interface Point
10.3 Serial Input Point Configuration

Flags and numerics

Flags and Numerics are fully supported as I/O connections; however, the Serial Interface
is primarily intended as an input vehicle and it can efficiently import large quantities of
data.
Diagnostics
The Serial Interface IOP firmware runs diagnostic routines. It monitors and reports any
detected communications timeouts or errors between the IOP and FTAs.

10.3 Serial Input Point Configuration

Scan period
On the HPMM Node Specific Configuration display, you must choose an HPMM scan
period (SCANPER). The HPMM scan period specifies the scan period in seconds at
which the HPMM images the Serial Interface IOP database to the Array points.
The maximum number of SI and associated Array points at the three configurable scan
periods are defined in the following table.

Scan Period Maximum

Number

1 80

.5 40

.25 20

IO module numbers
During Node Specific Configuration, you must also specify the IO Module Numbers that
contain SI cards. Otherwise, no specific configuration is required for an SI slot, except
what is entered for the associated Array point. Array points are described in the Array
Points section.
Detail status displays
The communication protocol in the FTA firmware is customized by Honeywell for
specific uses. The SI IOP’s Detail Status display shows the protocol, baud rate, and parity
type configured for each FTA. If a fault exists, the configuration information is replaced
with a failure message.
Checkpointing
The SI slot data is not checkpointed, but SI configuration is contained in the HPMM
Array point checkpoint. Configuration of related Array points is saved.
R688 HPM High-Performance Process Manager Control Theory 105
08/2019 Honeywell
10 Serial Interface Point
10.3 Serial Input Point Configuration

Startup
The SI slot configuration data is automatically reloaded on every startup. When reloaded,
the SI IOP Database Valid parameter is automatically set to Valid.

106 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 11. Serial Device Interface
11.1 Serial Device Interface Functional Overview
Family
The serial device interface is a member of the I/O point family.
Purpose
The Serial Device Interface (different from the Serial Interface) uses a Serial Device
Interface (SDI) module and a Companion Field Termination Assembly (FTA) designed
to transfer serial data from and to specific external devices.
Description
Each SDI board can support two serial channels and each FTA can communicate in
ANSI/EIA-232 (RS-232) or EIA-422/485. The EIA-232 interface connects to one serial
device and the EIA-485 interface can connect to a multidrop network of up to eight
devices.
The following figure illustrates a block diagram of the serial device interface.
Figure 11-1 Serial Device Interface Block Diagram

APM
FTA To Field
1 Device
SDI (e.g., EIA-232 device)
Power
IOP Panel

FTA To Field
2 Device
(e.g., EIA-485 device)

Implementation
You can communicate directly with the SDI using CL or control algorithms. Other
implementation methods are described in the Process Manager Implementation
Guideline or the PM/UDC 6000 Integration Manual.
Control
Operators typically control an SDI device from a custom schematic. You can build your
own schematic or contract with Honeywell Engineering Services to build it.
R688 HPM High-Performance Process Manager Control Theory 107
08/2019 Honeywell
11 Serial Device Interface
11.2 Manual/Auto Station Interface

Configuration
Communications with the device mimics a Smart Transmitter analog input point. The
SDI module is configured as you would for a Smart Transmitter Interface Module
(STIM, see “Smart Transmitter Interface Point” in Section 5).
Supported serial device interface types
Currently interfaces for the following devices are supported:
• Manual/Auto Station.
• Toledo Weigh Scale, Model 8142-2089.
• Toledo Weigh Scale, Model 8142-2189.
• UDC 6000 Process Controller.

11.2 Manual/Auto Station Interface

Manual/Auto Station functional description
The Manual/Auto Station interfaces with the Process Manager through the Serial Device
Interface FTA using EIA-485 protocol at 19.2 k baud. Up to four M/A Stations can be
connected in multidrop to each of the two SDI FTAs. Each of eight slots in the SDI IOP
can be configured for use with one Manual/Auto station. Slots 1–4 correspond to logical
address for FTA one and slots 9–12 correspond to logical address 1–4 on FTA two (slot
one = M/A Station 1 on FTA1, and so on and slot–9 = M/A Station 1 on FTA2 and so
on).

REFERENCE - INTERNAL
Refer to the High-Performance Process Manager Implementation Guidelines
for additional information.

108 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 11 Serial Device Interface
11.2 Manual/Auto Station Interface

Communications
Invalid data
Both data received from the SDI IOP and data received from the Manual Auto Station are
checked for reasonableness. Very small values may be rounded to .001. Very large
(absolute) values are either rejected or stored as NaN.

Time out
A time out signal is sent from the SDI IOP to the FTAs every half second. Loss of this
signal for 10 seconds or more halts all communications with the Manual/Auto Stations
connected to that FTA.

Communication failure
When communications between the FTA and an M/A Station fails, the FTA makes two
attempts to send the last message after the time out, then the point is put in bad input soft
failure. As long as the slot remains active, there is an attempt to restore communications,
but the M/A station is marked as not communicating.

REFERENCE - INTERNAL
Refer to the Manual/Auto Station Installation and Operation Manual for
additional information on the Manual/Auto Station itself.

Implementation
The PV and OP process signals are directly connected to appropriate modules in the
HPM. Process and status signals are sent from the HPM to the M/A station and operator
changes to the Set Point at the M/A station are read into the HPM as if those changes
were at a Universal Station. The following figure illustrates a typical Manual Auto
Station implementation.

R688 HPM High-Performance Process Manager Control Theory 109

08/2019 Honeywell
11 Serial Device Interface
11.2 Manual/Auto Station Interface

Figure 11-2 Manual/Auto Station Implementation

APM

FTA

PV
HLAI

Regulatory Field
Control Signals
Point
OP
AO

FTA

FTA
M/A M/A
Station Station
Logic SDI Power
Blocks IOP Panel
M/A
Station

FTA

PM override flag
Unless the PM Override flag is set, the PM responds to SP, OP, or mode change
operations from the M/A Station's front panel. The PM Override function can inhibit
operator functions attempted from the M/A station front panel that would affect SP, OP,
or Mode.

110 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 11 Serial Device Interface
11.2 Manual/Auto Station Interface

PV related parameters sent to the Manual Auto Station

The following table shows how to interpret PV related parameters seen at the Universal
Station or GUS through the STI point and their meaning as Manual/Auto station
parameters.

Parameter As an STI Point As an M/A Station Comments

Parameter Parameter

LRV Low end of operating Low end of operating PV (in engineering units)
range for PVRAW range for PVRAW

PVEUHI PV high range in PV high range in Must be set to 100.0

engineering units engineering units

PVEULO PV low range in PV low range in Must be set to 0.0

engineering units engineering units

PVEXEUHI PV extended range high PV extended range high Must be set to 100.0
limit in engineering units limit in engineering units

PVEXEULO PV extended range low PV extended range low Must be set to 0.0
limit in engineering units limit in engineering units

Other parameters sent to the Manual Auto Station

The following table shows how to interpret the control, status, and other parameters seen
at the Universal Station or GUS through the STI point and their meaning as Manual/Auto
station parameters.

Parameter Meaning as an STI Point Parameter As an M/A Station Parameter

CJTACT Internal cold junction reference active OFF = Manual Mode

ON = Auto Mode

DAMPING Damping M/A Station Alarms:

1 = Alarm 1 true
2 = Alarm 2 true
3 = Both Alarms true

PIUOTDCF Open thermocouple detect enable ON = In Override

OFF = Not in Override

PTEXECST Point execution state Active = Point is active

Inactive = Point is inactive

PVTV PV target value Setpoint in engineering units

R688 HPM High-Performance Process Manager Control Theory 111

08/2019 Honeywell
11 Serial Device Interface
11.2 Manual/Auto Station Interface

Parameter Meaning as an STI Point Parameter As an M/A Station Parameter

STITAG Transmitter tag name M/A Station Tag Name

URL Upper range limit of PV OP in per cent

URV Upper range value of PVRAW Valve position in per cent

Parameters sent from the Manual Auto Station

The following table shows how to interpret the parameters seen at the Universal Station
or GUS through the STI point and their meaning as Manual/Auto station parameters.

Parameter Meaning as an STI Point Parameter As an M/A Station Parameter

PVRAW Raw PV input value Setpoint (in engineering units) from

M/A Station

SECVAR Value of Secondary Variable OP (in per cent) from the M/Auto
Station)

SLOTSF Slot soft failures Soft failure due to bad input

STATE Current point state FTA Information

STI_EU Smart Transmitter, engineering units: Change Requests:

• INH2O • 0 = No change request
• MM_HG • 1 = SP change request
• PSI • 2 = OP change request
• KPA • 3 = Manual Mode request
• MPA • 4 = Auto Mode request

STISWVER Smart Transmitter software revision FTA information (sent from FTA):
level • Slot 1 = M/A application
• Slot 2 = Software gen date
• Slot 3 = Software rev date

112 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 11 Serial Device Interface
11.2 Manual/Auto Station Interface

Logic points and the SDI IOP

In addition to configuring the SDI IOP as an STI point, at least one, and preferably two
logic points must be built to read data from each M/A station, perform necessary
processing and then write the processed data, control, and status signals back to the M/A
station.
The primary logic point handles the control functions and the following rules apply:
• Parameter Change Requests (STI_EU), where an SP or OP change request takes
on the enumeration value shown for approximately five seconds, after which it is
reset to 0 (H2O) indicating no change request. Manual Mode change request and
Auto Mode change requests are similar except their enumeration value is reset to 0
(H2O) as soon as the new mode is written to the M/A station (by means of CJTACT).
• OP (SECVAR), where an OP request is read from the Manual/Auto Station,
processed and written back to the M/A Station through the URL parameter.
• SP (PVRAW), where an SP request from the Manual/Auto Station is processed and
written back to the Manual/Auto Station using the PVTV parameter.
The second logic point is optional and is used to write back information such as Valve
Position, Alarm state, and the Override flag using the parameters shown in the tables.

REFERENCE - INTERNAL
Refer to the High-PerformanceProcess Manager Implementations Guidelines
for detailed information about implementing the above rules.

Operating Considerations
To modify any Regulatory Control Point parameter from the M/A station, the external
Mode Switching Enable parameter ESWENBST must be set to ENABLE.
The Regulatory Control Point’s Mode attribute parameter (MODATTR) must be set to
PROG so that OP can be modified by a Logic point.
Only a one second scan period is supported for the M/Auto Station Logic points.
The PV High, PV Low, and PV Extended Range parameters must be configured with the
values shown in Table 2-6 in order to transfer an SP change request to the Regulatory
Control point’s set point parameter SPP.

R688 HPM High-Performance Process Manager Control Theory 113

08/2019 Honeywell
11 Serial Device Interface
11.3 Toledo Weigh Scale Interface

11.3 Toledo Weigh Scale Interface

Toledo Weigh Scale interface functional description
Toledo Weigh Station models T8142-2089 and T8142-2189 interface with the Advanced
Process Manager through the Serial Device Interface IOP using RS-232-D protocol at
9600 Baud. One Toledo Weigh Station can be connected to each of the two SDI FTAs.
Slots one and nine in the SDI IOP can be configured as to communicate with the Toledo
Weigh Station. The SDI IOP is implemented as a Smart Transmitter Interface Module
(STIM).
Communications
Invalid data
Invalid data—The following parameters are checked for reasonableness: DAMPING,
PVTV, URL, LRV, and DECONF.

Invalid data
When communications between an FTA and a Toledo Weigh Station fails, the FTA
makes two additional attempts to send the last message, then the Toledo Weigh Station is
marked as not communicating and PVRAW (the weight) is set to NaN.
To recover from most communication failures, switch the point execution status
PTEXECST to inactive and back to active.

Invalid data
Weight (PVRAW) and Flow Rate (SECVAR) are updated every 250 ms or faster.

REFERENCE - EXTERNAL
Refer to your Toledo Weigh Scale manual for more information.

114 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 11 Serial Device Interface
11.3 Toledo Weigh Scale Interface

Parameters sent from the Toledo Weigh Station

The following table explains the parameters used to communicate with the Toledo Weigh
Scale using an SDI interface configured as an STI module.

Parameter Meaning as an STI Point Parameter Meaning as a Weigh Scale Parameter

PVRAW Raw PV input value Weight (W)

SECVAR Value of Secondary Variable Flow Rate (R)

STI_EU Smart Transmitter, type of engineering Feed Status:

units used: • Feed is Off (x)
• 0 = In_H2O • Feed is On (F)
• 1 = MMHg • Feed is in alarm (A)
• 2 = PSI

STISWVER Smart Transmitter software revision FTA information (sent from FTA):
level • Slot 1 = Application
• Slot 2 = Software gen. date
• Slot 3 = Software rev. date

Parameters sent to the Toledo Weigh Station

The following table explains the parameters used to communicate with the Toledo Weigh
Scale using an SDI interface configured as an STI module.

Parameter Meaning as an STI Point Parameter Meaning as a Weigh Scale Parameter

CJTACT Internal cold junction reference active Feed Control:

• On = Start Feeding/Feeding
• Off = Not Feeding

DAMPING Damping Weight Filter (F)(See NOTE 1):

PIUOTDCF Open thermocouple detect enable Mode:

• On = Ascending Mode (A)
• Off = Descending Mode (D)

PVTV PV target value Weight Setpoint* (S)

URL Upper range limit of PV Alarm Setpoint* (A)

R688 HPM High-Performance Process Manager Control Theory 115

08/2019 Honeywell
11 Serial Device Interface
11.3 Toledo Weigh Scale Interface

Parameter Meaning as an STI Point Parameter Meaning as a Weigh Scale Parameter

LRV Low end of operating range for Decimal Point Position (D)
PVRAW • 1 = 1.0
• 2 = 0.1
• 3 = .01
• 4 = 0.001
• 5 = 0.0001

DECONF Digitally Enhanced Configuration Mode Parity Selection(See NOTE 2):

• 0 = No Parity
• 1 = Odd Parity
• 2 = Even Parity
• 3 = No Parity
• 4 = No change

LRL Lower Range Limit Weight recorded when feed status

switched from On to Off

NOTE 1: Values are modified to 6 digits or less by moving the decimal point per LRV.
NOTE 2: Odd parity should not be used. Even parity is preferred.

116 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 12. Alarming Theory of Operation
12.1 Alarming Function
Background
Common alarming functions that can be configured for HPM points. The alarm
parameters available depend on the point type. Refer to the individual point description
for details. Alarm detection and reporting for a point can be configured only if the full
point form is specified.
Priorities
For each point, a separate alarm priority can be specified for each alarm (for example, PV
high alarm can be low priority but PV high high alarm can be emergency). Alarm priority
configuration information is maintained by the NIM.
The following alarm priorities are supported for HPM points:

• Emergency • Journal • Printer

• High • JnlPrint • NoAction

• Low

The Journal (JnlPrint ) option causes alarms to be journaled only. This

CAUTION selection causes alarms to be journaled in the HM and printed. If the
Printer option is selected, alarms:
• are printed but not journaled.
• could be lost if the printer is not working.

Alarm enable status

Alarm enable status is applicable to full point forms and allows the user to enable,
disable, and inhibit alarms. This function is accomplished through the ALENBST
parameter. The alarm enable status function is resident in the NIM.

R688 HPM High-Performance Process Manager Control Theory 117

08/2019 Honeywell
12 Alarming Theory of Operation
12.2 Contact Cutout Function

12.2 Contact Cutout Function

Operation
The contact cutout function prevents a proliferation of alarms from being reported to the
operator. This function can be used to cut out alarms on a point when they are generated
because of alarm conditions that have been detected at other points. Contact cutout is
provided for all the point types in the HPM and is implemented through the CONTCUT
parameter. Another point or CL program must write to the CONTCUT parameter in
order to change the Contact Cutout state.
Exemption to contact cutout
With R681, the Selective Cutout feature allows the alarms of a point to pass through,
though the secondary point is in the cutout state. The NIM, flag, numeric, regulatory
control, regulatory PV, digital input, analog input, digital composite, and device control
points can be configured with the new parameters to enable selective cutout. The alarm
parameters are named $DHSELCT, $DLSELCT, $HHSELCT, $HISELCT and so on.
Selective Cutout operates in conjunction with the contact cutout feature.
When the parameter is set to ALLOW, the respective alarm passes through, even though
the point is in the cutout state. When the parameter is set to CUTOUT, the particular
alarm is blocked if the point is in the cutout state.
Alarm reporting
When the contact cutout state is applied, alarms at the point are cut out. New alarms are
not reported on the alarm summary display at the HMI (for example, Universal Station,
GUS) nor are they journaled on the system (for example, History Module, Real Time
Journal). This is the same way inhibited alarms are handled except Cutout alarms
continue to be reported to the AM or CM60 for event initiated processing (EIP). A
Contact Cutout True message is journaled for points that are in alarm when cutout. For
points that are not in alarm when cut out, no message is journaled.
On event recovery (for example, node failover), the system journals a Contact Cutout
True message for points that are currently in alarm and cut out.
Removing contact cutout
When contact cutout is removed, points that were in alarm are checked and if the alarm
condition still exists, the system generates a new alarm with a current timestamp. If the
alarm condition does not exist when contact cutout is removed, a Contact Cutout False
message is journaled for points that were in alarm.
UCN contact cutout implementation
Contact Cutout is implemented by using a logic point or a CL program to write a
Boolean variable from a primary control point into an alarmable UCN secondary point's

118 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 12 Alarming Theory of Operation
12.2 Contact Cutout Function

CONTCUT parameter. A TRUE (ON) in this parameter will cut out alarming by the
secondary point. The secondary point will not resume alarming until a logic point or CL
program writes a FALSE (OFF) into the secondary's CONTCUT parameter.
Typical implementation of Contact Cutout uses a primary point's PTINAL parameter
(point-in-alarm indicator) to control a secondary point's CONTCUT status. This is a
convenient method for providing Contact Cutout for all primary alarms, and we
recommend it as the safest and most secure implementation. However, any other valid
primary point alarm parameter, such as PVHIFL, PVHHFL, PVLOFL, PVROCNFL or
any other valid primary point Boolean parameter can be used. When distributing a
primary point's alarm status to the CONTCUT parameter of several points, use only one
input connection to make the best use of peer-to-peer resources.
When implementing a Contact Cutout connection using a logic point, the Logic Bad
Input handling Option parameter, LIBADOPT, must be set to OFF in case the primary
point fails or is deleted while in alarm. This implementation ensures that the secondary
point's CONTCUT parameter will be set to OFF in the event of a point failure. In
addition, if the primary and secondary points are in different UCN nodes, the logic point
should be located in the same node as the secondary point in case the node containing the
primary point is idled or fails.
For the same reason, we recommend that CL programs be located in the same node as the
secondary point. CL programs should include error trapping code to handle the different
failure cases previously described.
In general, Contact Cutout should be implemented using primary point alarming flags as
previously described, because these alarm parameters automatically clear (to the OFF
state) when the primary points are made INACTIVE or the node containing the primary
point is idled. Note that when connecting CONTCUT to other parameters, such as box
flags or digital composite PV flags, these parameters do not provide similar protection.
Because CONTCUT cannot be changed by the operator, it is possible to end up with a
secondary point temporarily or permanently disabled from alarming!
Primary module points
Primary Module (PRIMMOD) Points are used to collect alarms and events from points
that are related for some purpose. All UCN points with alarming capability have a
PRIMMOD parameter with which to identify a common PRIMMOD point. All points
with a matching Primmod point are considered to be in the same alarm group.
The value for the Primmod parameter can be any point in the same NIM. The value is
assigned during point build, but can later be stored by a CL program or from schematics.
If a Primmod point name is changed when alarms exist, the alarms are reissued for the
new Primmod name.
Up to 10 Primmod points can be grouped into one annunciator group in the Area data
base and Primmod points can be assigned to turn on the configurable button alarm
indicators.
R688 HPM High-Performance Process Manager Control Theory 119
08/2019 Honeywell
12 Alarming Theory of Operation
12.2 Contact Cutout Function

Auxilliary units
Alarmable NIM points in Release 520 and later software have an Auxiliary Unit
($AUXUNIT) parameter. If this parameter is set to null (- -), alarms and messages on that
point go to the primary unit. If a valid Unit ID is specified, alarms and messages from
that point go to the Auxiliary Unit.
$AUXUNIT can be configured at build time or, with the proper keylevel, it can be
initially assigned or changed by schematics, CL programs, the DEB alter parameters
function, or from the configuration page of the Point Detail display. The keylevel
necessary to change $AUXUNIT is configurable in the System Wide Values section of
the Network Configuration File.
Alarms from a point where $AUXUNIT has been configured are only accepted by
Universal or GUS stations having an Area Database in which both the Primary Unit and
the Auxiliary Unit are configured.
If an $AUXUNIT assignment is changed and there are outstanding alarms on the old
unit, alarms are deleted from the old unit and added to the new unit.

ATTENTION
It is not recommended to change AUXUNIT of a point, when the Alarm
DELAY is active. In this situation, the user has to inactivate the point before
modifying AUXUNIT.

120 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 12 Alarming Theory of Operation
12.3 Process Alarm Rebroadcast

12.3 Process Alarm Rebroadcast

With R660, acknowledged and unacknowledged process alarms (event-type 21) are
rebroadcast if they have not returned to normal (RTN) within the re-alarming interval
specified by the $REALARM parameter. The re-alarm feature is applicable for all types of
process alarms that can have an RTN event.
Re-alarming is consistent across all stations in the console in that area. Rebroadcast
alarms are also sent to the History Module with a new timestamp, and reported to the RTJ
and Process Alarm Journal where they appear as an alarm.
On the alarm displays, a rebroadcast alarm behaves like a new alarm but has a yellow time
stamp.
Rebroadcast alarms appear on the GUS Alarm Summary, and on the following GUS/US
native-window displays:
• Area Alarm Summary.
• Unit Alarm Summary.
• Alarm Annunciator.
• Point Detail.
The re-alarm feature is implemented using the $REALARM parameter that has a range of
0 through 9999 minutes. The value specified for this parameter determines the amount of
minutes that will elapse before the specified point is re-alarmed. Zero is the default value
for the $REALARM parameter. A zero value also inactivates the re-alarm feature.
The user-configured re-alarm interval is the same value for all process alarms associated
with the point.

R688 HPM High-Performance Process Manager Control Theory 121

08/2019 Honeywell
12 Alarming Theory of Operation
12.3 Process Alarm Rebroadcast

Point types that use the $REALARM parameter

The following HPM point types contain the $REALARM parameter:
• Analog Input.
• Box Flag (Only the first 1024 are alarmable).
• Box Numeric (Only the first 2047 are alarmable).
• Digital Input.
• Digital Composite.
• Device Control.
• Logic Slot.
• Regulatory PV.
• Regulatory Control.
Modify $REALARM
The following scenarios describe the change in the alarm handling because of the change
in the re-alarming interval while the point is in alarm.

ATTENTION
To prevent unusual or inconsistent re-alarming behavior, do not modify
$REALARM while the point is in alarm.

Scenario 1: Re-alarm interval is modified.

If the re-alarm interval is changed (a non-zero value changed to a different non-zero
value) while the point is in alarm, the change is not detected for the current alarm. The
change in the interval is detected only for the new alarms subsequently raised for that
point. In addition, each alarm for that point is updated with the new interval. Therefore,
all alarms of the point are synchronized.
Scenario 2: Re-alarm is cancelled.
If the re-alarm interval is changed (a non-zero value changed to zero) while the point is in
alarm, the change is immediately detected and the rebroadcast of the alarms does not
occur.
Scenario 3: Re-alarm is initiated.
If the re-alarm interval is changed (zero value changed to non-zero) while the point is in
alarm, the change is not detected for the current alarm. The change in the interval is
detected only for the new alarms subsequently raised for that point. However, the alarms
existing prior to the modification are not rebroadcast.

122 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 12 Alarming Theory of Operation
12.4 Red Tagging

Multiple alarms on the same point

Multiple alarms on the same point are rebroadcast at the same time. The first alarm
occurred for that point determines the schedule for all the subsequent alarms. Therefore,
all re-alarms for a point appear together in the alarm displays and journals.

12.4 Red Tagging

Purpose of Red Tagging
A point can be "red tagged" to indicate that it requires maintenance. This is accomplished
by setting the REDTAG parameter to On. Typically, the operator sets the output of the
point to a desired safe value before putting on the red tag. Once red tagged, the mode,
mode attribute, external mode switching state, and output cannot be changed.
Function of Red Tagging
The Red Tag function prevents changes to the output on a point that has the REDTAG
parameter set to ON, but it may still be possible to change the output connected to the
field. For example, even if a Digital Composite point has REDTAG set to ON, a
program/Logic Block can still change the state of the Digital Output.
Before red tagging a point
The mode and the mode attribute of the point must be changed to Man and Oper,
respectively, and the external mode switching state, if configured, must be Disabled
before the point can be red tagged. To red tag a digital composite point, the output of the
point must not be configured for the momentary state.
When a point is red tagged
The point can not be reconfigured or deleted if the red tag is On. Red tagging is
supported for only the analog output, RegCtl (only if it is outputting to an AO or a PWM
DO Processor), and digital composite point types. A point must be configured for the full
point form in order to be red tagged.

12.5 Write Lockout

Purpose of the Write Lockout
HPM Write Lockout is a feature that protects the HPM database. It can be enabled or
disabled from a Detail Display accessible through the HPM's Node Status display.
Engineering key level is required to make changes.
The lockout state can only be changed when the HPM is in Run or RunSoftfail state.
Function of the Write Lockout
When HPM Write Lockout is ON, most writes to the HPM are locked out. All parameter
reads are allowed and cable swaps, HPMM swaps, and IOP swaps are permitted. Peer-
R688 HPM High-Performance Process Manager Control Theory 123
08/2019 Honeywell
12 Alarming Theory of Operation
12.5 Write Lockout

to-peer writes are locked out but peer-to-peer reads from the same or other nodes are
permitted.

124 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 13. Digital Composite Point
13.1 Functional Overview
Purpose
The Digital Composite Point allows manipulation of sets of digital outputs and interprets
corresponding feedback of digital inputs. It provides a structured approach to handling
interlock functions and includes indication to the operator of existence of interlock
condition.
Description
The digital composite point is a multi-input/multi-output point that provides an interface
to discrete devices such as motors, pumps, solenoid valves, and motor-operated valves.
This point provides built-in structures for handling interlocks, and supports display of the
interlock conditions in group, detail, and graphic displays. In addition, the digital
composite point can be used with logic slots and other digital points to implement
complex interlock schemes.
Features
Features of the digital composite point include:
• Input and output states of the data point are totally independent of each other and can
be configured as required by the user's application.
• The inputs and outputs of the point can be linked to I/O points or to Boolean flags
within the HPM.
• Supports devices with two or three commandable states (motor-operated valves,
reversing motors, and so on).
• Specific states can be defined as being momentary.
• Provides structured approach to handling interlock functions and includes indication
to the operator of existence of interlock condition.
Functional diagrams
The input portion of a digital composite point can be configured only if the user has
entered 1 or 2 for the number-of-digital-inputs parameter (NODINPTS). A functional
diagram of the input portion of the digital composite point is shown in the following
figure.

R688 HPM High-Performance Process Manager Control Theory 117

08/2019 Honeywell
13 Digital Composite Point
13.1 Functional Overview

Figure 13-1 Digital Composite Point Inputs Functional Diagram

D1 CURRENT
INPUT1
INPUT STATE
INPUT2 D2 GENERATOR

PVAUTO

Current Output State

Track
Auto
PV (from Operator)
Man PVSOURCE

PV (from Program)
Sub

All OnlyAuto

PVSRCOPT

PV

BAD PV BADPVFL
ALARMING

BADPVPR

Current Output State

COMMAND
DISAGREE CMDDISFL
FBTIME > 0
ALARMING
CMDDISPR

COMMAND
CMDFALTM > 0 CMDFALFL
FAIL ALARM

PVNORMAL
< > None OFF-NORMAL OFFNRMFL
ALARMING
OFFNRMPR

UNCOMMANDED
UNCMDFL
CHANGE ALARM
1611 7

126 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 13 Digital Composite Point
13.1 Functional Overview

A functional diagram of the output portion of a digital composite point is shown in the
following figure.
Figure 13-2 Digital Composite Point Outputs Functional Diagram

Operator
Commanded State Off
(OP) from Operator Off

On On
Commanded State NMODATTR OROPT BYPASS
(OP) from Program
Program

Commanded
STATE 2 State STATE 1

STATE 0
Permissive
Interlocks ON ON ON
(P1, P0, & P2 are OFF OFF OFF
controlled by P2 P0 P1
Logic Blocks)

STATE 2 STATE 0 STATE 1

ON OFF
STATE 2
Override
Interlocks I2
(I2, I1, & I0 are
controlled by ON
OFF
Logic Blocks) STATE 1
I1

ON
OFF
STATE 0
I0

OFF
Safety ON
Interlock
STATE 0 SI0

Output Connections
(Up to 3 Outputs)
PULSEWTH OUTPUT STxOPy
STCHGOPT STATE
STxOPy
SEALOPT GENERATOR
MOMSTATE (OPFINAL) STxOPy
x = 0, 1, 2
y = 1, 2, 3

R688 HPM High-Performance Process Manager Control Theory 127

08/2019 Honeywell
13 Digital Composite Point
13.2 Point States

13.2 Point States

Introduction
The Digital Composite point supports three point states:

• Normal states • Momentary states • Moving/Bad states

Normal states
A digital composite point can have two or three normal states that allow the data point to
interface with devices that have two or three operational states. The normal states of a
digital composite point are presented in the following table.

Table 13-1 Digital Composite Point Normal States

State Description

0 Inactive State (a.k.a. Middle State).

This is considered a safe state. If for any reason a valid output cannot be
determined, the OP is forced to this state. Refer to: Initialization Manual for
more information.

1 First Active State.

2 Second Active State.

Applicable only when the entry for the NOSTATES parameter is 3, signifying
that the data point has three states.

These states can best be described by showing how the digital composite data point is
depicted in a group display, as shown in the following figure. On the display, each state
is represented by a separate box. The state 0 box is the middle box, the state 1 box is the
upper box, and state 2 box is the lower box. (The state 2 box does not appear if the point
has been configured for two states where parameter NOSTATES = 2). The state
descriptor for each box is an 8-character descriptor and appears at the top of the box. In
the following figure, the descriptors are FORWARD (for state 1), STOP (for state 0), and
REVERSE (for state 2), which are specified by parameters STATETXT(0)-
STATETXT(2).

128 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 13 Digital Composite Point
13.2 Point States

The lower portion of each box is split, with the left box being the indicator for the input
PV state, and the right box being the commanded-output state indicator. The condition of
the PV input that causes the left box to light is determined by parameters D2D1_00 -
D2D1_11. The condition that causes the right box to light is determined by OP being
commanded to that state.
Figure 13-3 Digital Composite Point Display

State 1 Descriptor
STATETXT (1)
FORWARD
State 1 Box

PVState 1 Indicator
OP State 1 Indicator (Commanded State)
PVFL (1)

State 0 Descriptor
STOP STATETXT (0)
State 0 Box

PVState 0 Indicator
OP State 0 Indicator (Commanded State)
PVFL (0)

State 2 Descriptor
REVERSE STATETXT (2)
State 2 Box

PV State 2 Indicator OP State 2 Indicator (Commanded State)

PVFL (2)
Double Bar in Output
State indicator shows
that this state cannot
be commanded

As an example, assume that the digital composite point shown in the previous figure is
connected through digital output points and digital input points to a motor control circuit
and that the current state of the digital composite point is state 0 (STOP).
In state 0, the PV indicator of the STOP box is lit, indicating that the motor is stopped
because the proper PV input has been received from the field. All other indicators in the
display are in the extinguished condition.

R688 HPM High-Performance Process Manager Control Theory 129

08/2019 Honeywell
13 Digital Composite Point
13.2 Point States

When the operator touches the FORWARD box to place the motor in the forward
running direction, the digital composite point output goes to State 1. Outputs from the
digital composite point are provided as determined by the ST1_OPn parameter (where
n=1.3). When the proper PV inputs are received from the field, the FORWARD box is
lighted. This indicates to the operator that the motor is running. Also, the current state of
the PV can be read by a logic slot or by a user program by accessing parameter PVFL(n)
where n is 0, 1, or 2. If the PV is in State 0, PVFL(0) is on; otherwise, PVFL(0) is off.
PVFL(1) and PV(FL2) operate in the same manner for States 1 and 2, respectively.
Similarly, when the operator presses the STOP box, the operator is notified that the
motor is stopped by the lighted PV indicator in the STOP box. The operator can then
select the REVERSE box to start the motor running in the reverse direction.
Momentary states
The states of a digital composite point can be configured as being momentary by using
the MOMSTATE parameter. The commanded states can be configured as momentary
where the state acts like a doorbell (state remains active as long as a switch is pressed).
The momentary states (MOMSTATE) parameter specifies which of the states are
momentary as presented in the following table.
Table 13-2 Digital Composite Point Momentary States

Entry Description

Mom_1 State 1 is momentary.

• When released from this state, it jumps back to State 0.

Mom_0 State 0 is momentary.

• When released from this state, it jumps back to State 1.
• Mom_0 can be selected only if the NOSTATES parameter = 2.

Mom_2 State 2 is momentary.

• When released from this state, it jumps back to State 0.
• Mom_2 can be selected only if NOSTATES parameter = 3.

Mom_1_2 States 1 and 2 are momentary.

• When released from any one of these states, it jumps back to
State 0.
• Mom_1_2 can be selected only if NOSTATES parameter = 3.

A state cannot be set to momentary if the MOMSTATE parameter = NONE.

MOMSTATE is mutually exclusive with the Seal-In option or State Change option
(STCHGOPT).

130 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 13 Digital Composite Point
13.3 Mode Attributes

Moving/Bad states
The digital composite point has two standard states that represent conditions when the
current state of the device is "bad" (indeterminate) or the current state is "moving" (from
one state to another). The bad state can result when the PV input signals from the process
are in an inconsistent state (for example, for a valve, the limit switches indicating open
and closed are both simultaneously on). The moving state is encountered when the device
is in transition from one state to another (for example, a slow moving valve is changing
from the open state to the closed state). The moving/bad state descriptor is located below
the State 2 box on the display. In the example described above, the descriptor assigned
for the BADPVTXT parameter would be the word FAULTY and the descriptor assigned
for the MOVPVTXT parameter would be the word MOVING. These descriptors are
configured once for each HPM box data point and then are used for all digital composite
points in the same HPM.
If the standard "bad/moving" default text is not desired, you can select the PV Text
Option during point configuration, and enter two eight-character strings of your choice.
While the words "bad/moving" are defined on a PM/HPM box basis, your entries
override them on a per point basis. Up to 15 unique bad/moving text descriptors can be
defined on a UCN network basis.

13.3 Mode Attributes

The digital composite point supports only the manual (MAN) mode with mode attributes
(specified by parameter NMODATTR) of Operator and Program. If the mode attribute is
Operator, only the operator can provide the commanded output state, as shown in the
Digital composite point outputs functional diagram illustrated in. On the other hand, if
the mode attribute is Program, only user programs (continuous or discontinuous) can
provide the commanded output state. The operator mode attribute flag (OPRATRFL) is
also provided for potential use by the interlocking logic.
The MODEPERM parameter is provided to optionally prevent the operator (as opposed
to the supervisor or engineer) from changing the mode attribute.
Parameter PRGATRFL indicates when the point is in Program mode attribute and
parameter NRMATRFL indicates when the point is in the configured Normal mode
attribute.

13.4 Interlocks
Types of interlocks
Two kinds of interlocks, permissives and overrides, are provided in the output portion of
a digital composite point. The states of the interlocks are typically controlled by output
connections from logic slots that can write to the P0-P2 permissive interlock parameters,
and I0-I2 override interlock parameters. In addition, a safety override interlock (SI0) that
cannot be bypassed is provided.
R688 HPM High-Performance Process Manager Control Theory 131
08/2019 Honeywell
13 Digital Composite Point
13.4 Interlocks

Permissive Interlocks
The permissive interlock parameters P0-P2 (illustrated in the Digital composite point
outputs functional diagram) are controlled by logic slot outputs, and the permissive
interlocks determine whether the operator and user programs are allowed to change the
output of a digital composite point to a specific state. A permissive interlock is provided
for each of the three states. The permissive interlocks themselves never cause the output
to change.
For the commanded output to be changed to the desired state, the corresponding
permissive interlock parameter must be set to ON. As an example, if a logic-slot output
has set parameter P1 to OFF, the commanded output of the digital composite point
cannot be set to State 1. The permissive interlock parameters P0, P1, and P2 are all
defaulted to ON, thereby allowing permission for all the states. They must be
individually set to OFF by the logic slots to prevent access to the corresponding
commanded output state.
Override Interlocks
The override interlock parameters I0-I2 (illustrated in the Digital composite point outputs
functional diagram in the) are also controlled by the logic slot outputs and can force the
commanded output to a specific state regardless of the condition of the permissive
interlocks. The operator and user programs cannot change the output state when any
override interlock is in the ON condition. An override interlock is provided for each of
the three output states.
When parameter I0 is set to ON by a logic slot output, the commanded output state is
forced to State 0 (regardless of the condition of parameters I1 and I2). When I0 is OFF
and I1 is ON, the commanded output is forced to State 1 (regardless of parameter I2).
Finally, when I0 and I1 are OFF and I2 is ON, the commanded output is forced to
State 2.
Override interlock parameters I0-I2 are all defaulted to OFF, disabling all the override
interlocks. They must be set to ON to force the output to go to any specific state. If the
override interlock forces the output to go to a momentary state, it stays in that state as
long as the interlock remains ON and then switches back to the original state when the
override interlock is reset to Off.
When all the override interlocks are OFF, the last value of the commanded output is
maintained (except for momentary state) until changed by the operator, a user program,
or another override interlock. The interlock logic restores the output value to the output
devices (Digital Output IOPs) whenever the interlock value changes, even if the state
asserted by the interlock is already in effect.
The Override Alarm Option (OVRDALOP) allows an Optional alarm to be generated
when an override occurs. You have the following configuration choices for the Override
Alarm Option:

132 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 13 Digital Composite Point
13.4 Interlocks

a) no alarm.
b) return to normal when the override is cleared (auto return).
c) Operator confirmation required after interlock is cleared (the operator must confirm
the alarm before it is possible to command a new state).
The occurrence of a new override takes precedence over any previously active override
(including the Safety Override Interlock, SIO) if that condition has returned to inactive.
Therefore, to the operator, a lower priority confirmation appears to overwrite a higher
priority override if that higher priority override has reset. This is sometimes called an
auto-confirm of the previous override.
If a higher priority override has been reset, the descriptions and confirm prompt (if
Cnfm_Rqd was configured) remain visible until the operator confirms the override from
the Detail Display. The confirm prompt and alarm are then reset. If any other override
occurs after a previous condition has reset, regardless of the previous priority, the new
description and confirm prompt appear. This also applies to the Real Time Journal
Display. If the confirmation required option was not selected for a particular class of
overrides, the description will still override the previous one and the previous confirm
prompt goes away, if the previous override condition has reset.

ATTENTION
When upgrading from an R400 APM to an R500 HPM, note the differences
described herein and make sure your strategy continues to operate a
intended.

In R410 and R500 systems, a lower priority interlock (such as I1) can become active if a
higher priority interlock (such as I0) is no longer true, but has not yet been confirmed. In
R400 systems, Confirmation has to be done before the lower priority interlock is
activated.
When the Digital Composite point is built, you can specify the tag name of the Logic
point that is driving the interlocks as parameter LOGICSRC. The contents of this
parameter then appear on the Group Display when the Digital Composite point is
selected. After identifying the Logic point, an operator can call up the Detail Display for
that point to find out about the interlocks.
You can predefine an eight character alarm descriptor for each override interlock, I0-I2.
When the override interlock is activated, that string is displayed on the detail display. CL
programs can write into these descriptors (InDESC) before asserting the interlock. The
detail display text then explains why the program forced the interlock (for example, TOO
HOT in the Override Alarm Descriptor, OVRDDESC).

R688 HPM High-Performance Process Manager Control Theory 133

08/2019 Honeywell
13 Digital Composite Point
13.4 Interlocks

Configurable Interlock Bypass

The operator can have the ability to bypass the permissive and override interlocks for a
digital composite point. To do so, the override parameter OROPT must be set to ON. The
operator can then set (or reset) the parameter BYPASS. Note that while BYPASS is ON,
the point execution state parameter can’t be changed. When the BYPASS parameter is
reset, existing override interlocks (if any) take effect immediately. The group display
shows whether interlocks are being bypassed. The organizational summary display lists
all the points for which BYPASS = ON.
Safety Interlocks for State 0 (SI0)
The safety override interlock parameter SI0 behaves like the I0 interlock, but it cannot be
bypassed even when BYPASS is configured and turned on (illustrated in the Digital
composite point outputs functional diagram).
If a device has tripped as a result of a state 0 interlock, an interlock-trip alarm
(SI0ALOPT) can result (if configured). The interlock-trip alarm has three options: None
(no alarming), Auto Return or Alarm with Confirm Required. The alarms are described
as follows:
Auto Return— if a state 0 interlock causes the OP state to change, an interlock-trip alarm
is generated and then automatically terminated when the interlock, that caused the alarm
returns to OFF.
Alarm with Confirm Required— if a state 0 interlock causes the OP state to change, an
interlock-trip alarm is generated. The interlock that caused the alarm must return to OFF
and the operator must reset the trip-confirm required flag OVRDCONF.
The trip-confirm required flag can also be reset by REDTAG, BYPASS, or
LOCALMAN, but the motor cannot be restarted by the operator, interlock, or other
system functions until the interlock trip alarm is terminated.
If SIO resets, a lower priority interlock can be asserted and confirm automatically as
described in Override Interlocks.
You can predefine an 8-character alarm descriptor for SIO. When the safety override
interlock is activated, that string is displayed on the detail display. CL programs can
write into these descriptors (InDESC) before asserting the interlock. The detail display
text then explains why the program forced the interlock (for example, TOO HOT in the
Override Alarm Descriptor, SIODESC). SIOALPR sets the interlock-trip alarm priority.
Trip Descriptor—When a device trips because of an interlock, the cause of the trip is
available as an 8-character descriptor from the parameter OVRDDESC.

134 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 13 Digital Composite Point
13.5 Digital Inputs

13.5 Digital Inputs

Background
When configuring digital inputs of the digital composite data point, you can specify the
input connections, PV states, PV source and options, alarming, and change-of-state
events.
Input connections
The inputs to a digital composite point are specified through digital input-source
parameters DISRC(1)-DISRC(2). Inputs to the digital composite point are designated as
Input 1 and Input 2, and they can be obtained from any of the following sources:

• Digital Input Point—PV • HPM Box PV Flags

• Digital Output Point—SO • Process Module Slot Flags

• Logic Slot Output • Array Point Flags

• Logic Slot Flags • Device Control Slot Flags

ATTENTION
Please note that:
• these sources must be in the same HPM box as the digital composite
point that is being configured.
• the status of Input 1 is represented by parameter D1; Input 2 is
represented by parameter D2.
• Input 2 can be configured only when the entry for the number-of-digital-
inputs parameter (NODINPTS) is 2.

Digital Input Point—PV

To assign the PV of a digital input point to the PV input of a digital composite point in
the same HPM box, you can enter the following information for the respective DISRC(n)
input connection parameter:
Tagname.PVFL or
!DImmSss.PVFL
where:
• Tagname is the 8- or 16-character name of the point that will provide the PV.
• PVFL signifies the PV of the respective digital input point.
• !DI signifies a digital input point. This is the start of the hardware reference address.
• mm is the Digital Input IOP Card number from 1-40 within the same HPM.
R688 HPM High-Performance Process Manager Control Theory 135
08/2019 Honeywell
13 Digital Composite Point
13.5 Digital Inputs

• the letter “S” is a constant.

• ss is the slot number in the same Digital Input IOP Card in the range from 1-32.

136 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 13 Digital Composite Point
13.5 Digital Inputs

Logic Slot Output

To assign the logic slot output to the PV input of a digital composite point, the user can
enter the following information for the respective DISRC(n) input connection parameter:
Tagname.SO(nn)
where:
• Tagname is the 8- or 16-character name assigned to the logic slot that is providing
the output.
• SO signifies the output of the logic block.
• nn is the logic block number in the range from 1–24.
Logic Slot Flags
To assign a logic slot flag to the input of a digital composite point, the user can enter the
following information for the respective DISRC(n) input connection parameter:
Tagname.FL(nn)
where:
• Tagname is the 8- or 16-character name assigned to the logic slot that is providing
the flag.
• FL signifies the logic-slot flag.
• nn is the flag number in the range from 1–12.
HPM Box PV Flags
To assign a HPM box PV flag to the input of a the digital composite point, the user can
enter the following information for the respective DISRC(n) input connection parameter:
Tagname.PVFL or
!BOX.FL(nnnn) where:
• Tagname is the 8- or 16-character name assigned to the box PV flag.
• PVFL signifies the PV flag.
• !BOX specifies the HPM box.
• FL(nnnn) is the flag number that has a range from 1 to 16384.
Device Control Slot Flags
To assign the digital composite-point input to a Device Control slot flag, the user can
enter the following information for the respective DISRC(n) input connection parameter:
Tagname.FL(nn)
where:

R688 HPM High-Performance Process Manager Control Theory 137

08/2019 Honeywell
13 Digital Composite Point
13.5 Digital Inputs

• Tagname is the 8- or 16-character name assigned to the data point through the
NAME parameter.
• FL signifies a flag.
• nn is the flag number to which the input of the digital composite is sent. The flag
number has a range of 7-12: flag numbers 1-6 have dedicated uses and cannot be used
as destinations by a Device Control point.
Array Point Flags
To assign the digital composite-point input to an Array Point flag, the user can enter the
following information for the respective DISRC(n) input connection parameter:
Tagname.FL(nn)
where:
• Tagname is the 8- or 16-character name assigned to the data point through the
NAME parameter.
• FL signifies a flag.
• nn is the flag number to which the input of the digital composite is sent. The flag
number has a range of 1-NFLAG, where NFLAG is the array point parameter that
defines the number of flags in the Array point.

138 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 13 Digital Composite Point
13.6 Current Input State (PV)

Process Module Slot Flags

To assign a Process Module slot flag to the input of a digital composite point, enter the
following information for the respective DISRC(n) input connection parameter:
Tagname.FL(nn)
where:
• Tagname is the 8- or 16-character name assigned to the Process Module flag.
• FL(nn) signifies the flag.

13.6 Current Input State (PV)

Background
The flexibility of the digital composite point allows the user to assign the states of the PV
for each possible combination of digital inputs, so that the states correspond to the
different applications in which this point type can be used. The PV parameter represents
the current state of the interfaced device and is derived from inputs D1 and D2 that can
be feedback signals from the process. Separate parameters are used to configure a single-
input point and a dual-input point.

TIP
The inputs to a digital composite point are usually the PVs from digital input
points. The digital input points should be configured as component points that
force the input direction to be direct (as opposed to reverse).

Direct/Reverse action
The actual direct/reverse action can be configured by assigning the appropriate PV state
to the input as described in the following paragraphs.
Single input points
For a single-input point, there is only one input parameter (D1). D1 has two possible PV
states (PVstate0 and PVstate1) that can be assigned to either of the following input
conditions:
• D1 = 1 (D1 is ON; parameter D1_1)
• D1 = 0 (D1 is OFF; parameter D1_0)
You assign either PVstate0 or PVstate1 to parameter D_1; the system automatically
assigns the other PV state to parameter D1_0.

R688 HPM High-Performance Process Manager Control Theory 139

08/2019 Honeywell
13 Digital Composite Point
13.6 Current Input State (PV)

Dual input points

For a dual-input point, there are two input parameters (D2 and D1) that together have
four possible combinations of input values as follows:
• D2D1 = 00 (D2 is OFF, D1 is OFF; parameter D2D1_00)
• D2D1 = 01 (D2 is OFF, D1 is ON; parameter D2D1_01)
• D2D1 = 10 (D2 is ON, D1 is OFF; parameter D2D1_10)
• D2D1 = 11 (D1 is ON, D2 is ON; parameter D2D1_11)
To these four combinations of input values, you can assign any four of the following five
PV states:

• Pvstate1 • Pvstate0 • Pvstate2

• MovPV • BadPV

PVstates1, 0, and 2 cause the PV indicator to be lighted in the respective state box on the
group display when the assigned D2D1 input conditions are satisfied. The MovPV and
BadPV states cause the respective MOVPVTXT or BADPVTXT descriptor to appear
below the state boxes on the group display.
PV source
The PV source parameter (PVSOURCE) determines the source of the current PV state
for the digital input portion of the digital composite data point. The possible sources of
the current PV state are presented in the following table.
Table 13-3 Digital Composite Point PV Sources

Source Description

Man Manual—Current PV state is provided by the operator.

Auto Automatic—Current PV state is derived from Input 1 (D1) and Input 2

(D2).

Track Current PV state is the commanded output state.

Sub Substituted—Current PV state is provided by a user program.

PV Source Option
During configuration, the user can specify the PV sources that can be used for this data
point. Parameter PVSRCOPT allows the user to select the PV source as being only
AUTO, or to select all the PV sources in the above listing as allowable sources of the PV.

140 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 13 Digital Composite Point
13.7 Alarming

Note that the organizational summary display lists all the points for which PVSOURCE =
TRACK.

13.7 Alarming
Background
The digital composite point can be configured to detect and report command disagree,
command fault, uncommanded change, or off-normal alarms. You have the option of
specifying no alarming for the data point. Digital composite points also generate a bad
PV alarm when any input is coming from a digital input point that has a bad PV flag
(BADPVFL) status of ON.

ATTENTION
Please note that:
• Digital Composite point alarm options can be configured only if the digital
composite point is configured to have inputs, or inputs and outputs.
• The BADPVPR parameter determines priority of the bad PV alarm.

Command disagree
During the command disagree timeout interval, determined by the feedback-time
parameter, FBTIME, it is possible, in some instances, that the state defined as BADPV
could occur in the PV inputs, but not reflect an actual failure of the inputs or associated
hardware. To lessen operator confusion, these "state" BADPVs should be ignored.
Therefore, only BADPVs resulting from detected input errors are declared by the point
during the timeout interval. If a "state" BADPV occurs, the previous PV remains
displayed.
When the commanded-output state is changed and the actual input PVstate does not
change accordingly within a predefined feedback time, a command disagree alarm is
generated.
The feedback time (1 to 1000 seconds) is specified by the FBTIME parameter and the
timer starts whenever the OP value changes. A command disagree alarm is also
generated if OP changes are caused by the interlocks.
This alarm condition returns to normal when the input PV state and the commanded-
output state are the same. If the commanded state is momentary, no alarm is generated.
For example, a motor may have two PV states (RUN and STOP), but there may be three
commanded output states (RUN, STOP, and JOG) where JOG is defined as a momentary
state. Command-disagree alarming is performed for only the RUN and STOP
commanded output states.

R688 HPM High-Performance Process Manager Control Theory 141

08/2019 Honeywell
13 Digital Composite Point
13.7 Alarming

Command fail
The command fail alarm is similar to the command disagree alarm, but instead of waiting
for the actual state to equal the commanded state, a check is made to verify that the PV
changed from its original value to any other value within a configurable time interval.
For slow devices, absence of this alarm provides feedback that the device responded to
the command, even if it has not yet moved to its final position. The command fail alarm
is enabled by entering an integer greater than zero for the command failure timeout
parameter, CMDFALTM.
Uncommanded change
If a change does not occur in the commanded output state but the input PV state changes
(and the PV is not bad), an uncommanded-change alarm is generated. This alarm
condition returns to normal when the input PV state and the commanded state are the
same. If the point state has been configured as being momentary, this type of alarm is not
applicable. Alarm priority for the command disagree alarm, the command fail alarm, and
the uncommanded change alarm is determined by the Command Disagree Priority
(CMDDISPR) parameter.
Off-Normal
Detection of off-normal alarms is inhibited by selecting an FBTIME greater than zero.
The normal state of the PV input is defined by the user through the PVNORMAL
parameter.
When the PV input state is different than the state specified by the PVNORMAL
parameter, the off-normal alarm is generated. The alarm condition returns to normal
when the PV input state and the specified PV normal state are the same. When command
disagree is configured, the off-normal alarm is inhibited if PVNORMAL = ON. This is to
avoid two alarms at the same time and help isolate failures. You can set the priority of
the off-normal alarm with the OFFNRMPR parameter.

142 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 13 Digital Composite Point
13.8 Change-of-State Events

13.8 Change-of-State Events

Any transitions in the PV input state can be used for triggering event-initiated processing
of points in the Application Module (AM). It is configured by entering EIP for the event-
report-option parameter EVTOPT. The user must enter the tag name of the AM or CM
point using the EIPPCODE parameter.

13.9 Commanded State (OP)

Functional description
The command to go to a specific state results in outputs to the process that drives the
actual state of the device to the commanded state. The commanded state is represented by
the OP parameter in the digital composite point; the commanded state can be State 1
(ST1), State 0 (ST0), or State 2 (ST2). The OP parameter is available for configuration
only if the number of digital output connections (NODOPTS) is configured to be greater
than 0.
Up to nine Boolean parameters of the form STx_OPy (where x = 0, 1, or 2 for the state
number and y = 1, 2, or 3 for the output number) allow the user to specify the state values
that are to be stored by the output connections. For each of the three commanded states
per output connection, you must define the value (On or Off) of the state.
CL programs or Logic points can test the parameter INITREQ to see if they are allowed
to command a certain state. If INITREQ(i) = ON, then CL programs or Logic points
cannot change the output to STATE(i) (i = 0, 1, or 2).
Status Output
The Status Output command parameter allows Logic points or CL programs (HPM or
AM) to manipulate outputs (subject to interlocks and the mode attribute). Logic or CL
programs can set SOCMD(i) to ON to command State(i) where I = 0, 1, or 2. The same
rules apply as storing the corresponding state to the OP parameter, that is, the mode
attribute must be PROGRAM, the corresponding permissive must be available, no
override can be active, and so on. The actual output (OP) is switched to the requested
state only by an OFF to ON change of the corresponding SOCMD(i) flag. There is no
priority scheme; the last one changing from OFF to ON controls the output.

R688 HPM High-Performance Process Manager Control Theory 143

08/2019 Honeywell
13 Digital Composite Point
13.9 Commanded State (OP)

OP can be commanded to state 1 or state 0 using the OPCMD parameter. When OPCMD
is ON, OP is set to state 1. When OPCMD is OFF, OP is set to State 0. OPCMD can be
used when three states are defined, but will only command OP to state 1 or state 0.
Overrides take precedence over OPCMD; however, when the override is cleared, the OP
will be commanded to the state determined by OPCMD. OPCMD should not be used in
conjunction with SOCMD since OPCMD will always override the state set by SOCMD.
Like SOCMD, OPCMD only affects OP when the mode attribute is PROGRAM.

ATTENTION
Do not configure two different logic outputs to drive OPCMD and SOCMD of
the same Digital Composite Point.

Seal-In circuit
The seal-in circuit is a configurable option (SEALOPT). It is used to unlatch the digital
output contacts on detection of the PV, not following the output command as happens on
a device drop out (for example, a stopped motor).
This condition is determined to be true any time the PV is not in state1 or state 2 and
either of the following is present:
• a command disagree alarm.
• an uncommanded state change alarm.
If the seal-in option is enabled, when the above condition is detected, the output
destinations are set to the state corresponding to OP of state 0, but OP is not altered. The
actual state commanded to the output destinations can be observed on the lower part of
the group display as OPFINAL. OPFINAL is displayed in reverse video if it is different
from OP. OPFINAL is set equal to OP on the next store to OP, thus clearing the seal
condition. However, if OPCMD is used, it must be set OFF, then ON to clear the seal
condition.

ATTENTION
The seal-in option is mutually exclusive with MOMSTATE.

ATTENTION
Setting the permissive interlock parameter for any state to OFF when that
state is already commanded, does not take effect. For example, if state 1 is
already commanded, then if you set the permissive interlock parameter P1 to
OFF, it does not take effect until state 1 is reset.
While configuring Device Control point with the seal-in option enabled, you
must review the OP and OPFINAL values to check if there is any

144 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 13 Digital Composite Point
13.9 Commanded State (OP)

uncommanded change and make necessary changes if required, before

setting the OP value to state 1.

R688 HPM High-Performance Process Manager Control Theory 145

08/2019 Honeywell
13 Digital Composite Point
13.9 Commanded State (OP)

State Change Option

A configurable option (STCHGOPT) allows break before make on output changes. You
must configure state 0 as the break, or off, or inactive state. The number of states must
equal 3.
When an output change from state 1 to state 2 or from state 2 to state 1 is commanded:
• OP changes to state 0 first.
• if the command disagree time out alarm is configured and a corresponding PV state
is applicable, the alarm is held off until a successful feedback has been reached (that
is, PV = state 0).
• the digital composite point waits for a predefined pause time (PAUSETIM).
• OP is then changed to the requested value.

TIP
If the break before make option is enabled, commanding a motor to change
direction from forward to reverse causes the motor to stop before reversing.

ATTENTION
Please note that:
• the CL state change statement waits until feedback for the second OP
change is successfully received.
• the state change option is mutually exclusive with MOMSTATE.

146 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 13 Digital Composite Point
13.10 Digital Outputs

13.10 Digital Outputs

Introduction
You can specify the latched or pulsed output type for the digital composite point through
the configurable output connections.
Latched Output
Configuring the digital composite point for a latched output is accomplished by
specifying any parameter other than ONPULSE or OFFPULSE.
Pulsed Output
Configuring the digital composite point for a pulsed output is accomplished through the
output connections by specifying the ONPULSE or OFFPULSE parameters as the
destination points for the outputs. The width of the pulse is configured at the digital
composite data point through the PULSEWTH parameter; it allows the user to specify a
pulse width from 0 to 60 seconds as a real number. The selected pulse width applies to all
of the output connections.
Output Connections
The destinations of the outputs (and the output types) from a digital composite point are
specified by the user through the DODSTN(1)-DODSTN(3) parameters. The categories
of destinations that can be specified are as follows:
• Digital Output Point—Pulsed Output.
• !DO signifies a digital output point. This is the start of the hardware-reference form
of addressing the digital output.
• mm is the IOP card number from 1-40 of the Digital Output IOP Card within the
same HPM.
• letter ‘S’ is a constant.
• ss is the slot number in the range from 1-16 on the same Digital Output IOP Card.
• Logic Slot Flags.
• HPM Box PV Flags.
• Process Module Slot Flags.
• Device Control Slot Flags.
• Array Point Flags.
These destinations must be in the same HPM box as the digital composite point that is
being configured.

R688 HPM High-Performance Process Manager Control Theory 147

08/2019 Honeywell
13 Digital Composite Point
13.10 Digital Outputs

Digital Output Point—Latched Output

To assign the digital composite-point output to the latched output of a digital output
point, the user can enter either of the following output connections for the respective
DODSTN(n) output connection parameter:
Tagname.SO
or
!DOmmSss.SO
where:
• Tagname is the 8- or 16-character name assigned to the data point through the
NAME parameter.
• SO signifies the status output of the digital output point.
• !DO signifies a digital output point. This is the start of the hardware-reference form
of addressing the digital output.
• mm is the IOP card number from 1-40 of the Digital Output IOP Card within the
same HPM.
• the letter ‘S’ is a constant.
• ss is the slot number in the range from 1-16 on the same Digital Output IOP Card.
Digital Output Point—Pulsed Output
Pulsed outputs can be either of two types: normally off pulsed-on, and normally on
pulsed-off. To assign the digital composite-point output to the pulsed output of a digital
output point, the user can enter the following information for the respective DODSTN(n)
output connection parameter:

148 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 13 Digital Composite Point
13.10 Digital Outputs

For a normally off pulsed-on output:

Tagname.ONPULSE
or
!DOmmSss.ONPULSE
where:
• Tag Name is the 8- or 16-character name assigned to the data point through the
NAME parameter.
• OFFPULSE signifies the pulsed output of the digital output point.
• !DO signifies a digital output point. This is the start of the hardware-reference form
of addressing the digital output.
• mm is the IOP card number from 1-40 of the Digital Output IOP Card within the
same HPM.
• the letter ‘S’ is a constant.
• ss is the slot number in the range from 1-16 on the same Digital Output IOP Card.

For a normally on pulsed-off output:

Tagname.OFFPULSE
or
!DOmmSss.OFFPULSE
where:
• Tagname is the 8- or 16-character name assigned to the data point through the
NAME parameter.
• OFFPULSE signifies the pulsed output of the digital output point.
• !DO signifies a digital output point. This is the start of the hardware-reference form
of addressing the digital output.
• mm is the IOP card number from 1-40 of the Digital Output IOP Card within the
same HPM.
• letter ‘S’ is a constant.
• ss is the slot number in the range from 1-16 on the same Digital Output IOP Card.
Logic Slot Flags
To assign the digital composite-point output to a logic-slot flag, the user can enter the
following information for the respective DODSTN(n) output connection parameter:
Tagname.FL(nn)
where:
R688 HPM High-Performance Process Manager Control Theory 149
08/2019 Honeywell
13 Digital Composite Point
13.10 Digital Outputs

• Tagname is the 8- or 16-character name assigned to the data point through the
NAME parameter.
• FL signifies a logic-slot flag.
• nn is the flag number to which the output of the digital composite is sent. The flag
number has a range of 7–12: flag numbers 1–6 have dedicated uses and cannot be
used as destinations by a digital composite point.
HPM Box PV Flags
To assign the digital composite-point output to an HPM box PV flag in the same HPM
box, the user can enter the following information for the respective DODSTN(n) output
connection parameter:
Tagname.PVFL or !BOX.FL(nnnn)
where:
• Tagname is the 8- or 16-character name assigned to the data point through the
NAME parameter.
• PVFL signifies the PV flag.
• !BOX specifies the same HPM box in which the digital composite point resides.
• nnnn is the flag number. Box flags from 1 to 16,384 are available.

150 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 13 Digital Composite Point
13.10 Digital Outputs

Device Control Slot Flags

To assign the digital composite-point output to a Device Control slot flag, the user can
enter the following information for the respective DODSTN(n) output connection
parameter:
Tagname.FL(nn)
where:
• Tagname is the 8- or 16-character name assigned to the data point through the
NAME parameter.
• FL signifies a flag.
• nn is the flag number to which the output of the digital composite is sent. The flag
number has a range of 7–12: flag numbers 1–6 have dedicated uses and cannot be
used as destinations by a Device Control point.
Array Point Flags
To assign the digital composite-point output to an Array Point flag, the user can enter the
following information for the respective DODSTN(n) output connection parameter:
Tagname.FL(nn)
where:
• Tagname is the 8- or 16-character name assigned to the data point through the
NAME parameter.
• FL signifies a flag.
• nn is the flag number to which the output of the digital composite is sent. The flag
number has a range of 1-NFLAG, where NFLAG is the array point parameter that
defines the number of flags in the Array point.

R688 HPM High-Performance Process Manager Control Theory 151

08/2019 Honeywell
13 Digital Composite Point
13.11 Read Back Check

13.11 Read Back Check

Digital Composite and Device Control points can have digital output connections through
an SI/Array point to a field device. The field device or its interface may interrupt or
change the output and not provide any indication of the change.
If flag data is mapped back from the SI/Array point, a digital output read-back check
determines the actual value of the output. After a new output state is stored to the digital
output connections, the read-back check is delayed for a time period equal to the
feedback-time parameter time (FBTIME) or 4 seconds, whichever is greater. This delay
allows the SI/Array output enough time to reach even a slow responding field device
before causing a Command Disagree alarm (see

152 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 Digital Composite Point” in Section 1 and “Alarming” in Section 13.7).
If a discrepancy then exists between OPFINAL and OP, the operator is advised. If
OPFINAL does not agree with any of the defined states, its state is displayed as NONE.

13.12 Initialization Manual

Initialization
A digital composite point that has at least one output connected to a discrete point (DO,
Flag, or SI Array) is placed into the initialization manual condition (INITMAN is On)
when the:
• associated DO point has failed or been powered off (digital composite point cannot
communicate with the DO point), the DO point is in an idle condition, or in standby
manual, for the FTA is missing.
• associated DO point has its initialization request (INITREQ) flag set. The flag may
be set because the point is inactive, the point is not configured as a status output type,
or one of the output diagnostics has failed.
• digital composite point is inactive.
• HPMM is in an idle condition.
Operator notification
INIT is displayed for the particular digital composite point to inform the user that one of
the above conditions has occurred. When the condition is corrected, INITMAN is set to
Off.

R688 HPM High-Performance Process Manager Control Theory 153

08/2019 Honeywell
13 Digital Composite Point
13.12 Initialization Manual

Initialization Option
With R630, parameter $INITOPT allows the user to configure a digital composite point
so that the digital composite point holds the output value (OP) at its last value when the
point recovers from the initialization manual condition.
The $INITOPT parameter has two values; NORMAL and HOLDOP. If NORMAL is
selected as the entry for the $INITOPT parameter, the digital composite point operates as
currently described in the Initialization section.
If HOLDOP is selected, the output value is held at its last value (previous state) as long
as the initialization condition persists. When the digital composite recovers from the
initialization manual condition, the output is not sent to the output point unless an
override interlock or safety interlock is active. If the active interlock (I0, I1, I2, or SIO)
is not bypassed, the digital-composite point output value is set to the value of the active
interlock.

CAUTION
If HOLDOP has been selected as the entry for the $INITOPT parameter, it is
possible that the state of the output field device does not match the state of
the OPFINAL parameter after recovery from initialization has been
completed. There may be a mismatch between the digital-composite output
value and the output device state that requires operator intervention to
correct this mismatch. Therefore, there may be uncertainty in the validity of
the field device state after recovering from initialization.
For recommendations about the implementation and use of the $INITOPT
parameter, refer to the description of the $INITOPT parameter in the PM
Family Parameter Reference Dictionary.

154 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 13 Digital Composite Point
13.12 Initialization Manual

Operation
When INITMAN transitions from On to Off, the digital composite point provides an
output value OP as follows:

If $INITOPT is configured as then the OP value sent to the field

Normal... device...
override interlocks are active and not corresponds to the highest priority override
bypassed interlock
feedback is configured tracks the PV state if the PV state is valid
(that is, not bad or moving).
if the input is bad and there are no the OP value is back-initialized from the
output connections to output connections
ONPULSE/OFFPULSE
if the input is bad and output is set to State0
connections to
ONPULSE/OFFPULSE exist
none of the above conditions exist is set to State0

If $INITOPT is configured as then the OP value...

HoldOp...
HOLD is configured for the $INITOPT is held at the last output value
parameter
override interlocks are active and not corresponds to the highest priority override
bypassed interlock

feedback is configured and the value causes an uncommanded change alarm to

of the PV does not match the value of be generated
the OP

If the tracked PV is not valid a BADPV alarm is generated

R688 HPM High-Performance Process Manager Control Theory 155

08/2019 Honeywell
13 Digital Composite Point
13.13 Local Manual Indication

13.13 Local Manual Indication

Field devices that are interfaced by a digital composite point often have a local
HAND/OFF/AUTO (often called HAND/OFF/REMOTE) switch. Unless this switch is in
AUTO position, the control system (HPM) may not have any control over that device.
The users can optionally feedback the switch position into the HPM to obtain some
display indication for the operator. This indication is provided by the word LOCALMAN
appearing at the bottom of the digital composite point on a group display. Further, when
in local manual, any changes to the output by the operator, and user programs, are
prohibited. The override interlocks are still active when the local manual condition is on.
When the local manual condition is on, both OP and OPFINAL follow the PV value (the
actual state of the device).
To support HAND/OFF/AUTO switches, a Boolean flag called LOCALMAN is
provided. The ON state indicates that the switch is not in AUTO position. The user can
hard-wire the AUTO position of the HAND/OFF/AUTO switch through a digital input
point. The state of the digital input state is then stored to the LOCALMAN flag from
logic slot outputs or sequence programs.

13.14 Maintenance Statistics

Types of maintenance statistics provided
The Maintenance Statistics page of the Digital Composite Point Detail Display provides
statistical information about the point. For example:
• accumulated number of transitions to each state.
• date/time of most recent statistics reset.
• accumulated time in each state.
• date/time of most recent change to each state.
• accumulated number of safety interlock overrides.
Enabling maintenance statistics
Statistics are enabled by entries in the Maintenance Statistics section during point
configuration. You can enter the maximum number of hours that you want to allow in
each state and maximum number of transitions that you want to allow into each state.
Even if either maximum is reached, the Digital Composite point does not provide an
alarm, but a CL program can be written to monitor the statistics and take action.
Reset and Redtag
The above statistics are accumulated since the most recent reset. A program can reset the
statistics with the RESETFL parameter anytime or they can be reset from the
Maintenance Statistics page as explained below.

156 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 13 Digital Composite Point
13.14 Maintenance Statistics

The Maintenance Statistics display contains a REDTAG target. The REDTAG and
RESET targets work as follows:
If you select the REDTAG target (and ENTER), the point’s REDTAG parameter is set to
ON and a RESET target appears. Selecting the RESET target (and ENTER), resets the
points maintenance statistic values. If you select REDTAG (and ENTER, the REDTAG
condition clears and the RESET target disappears.

R688 HPM High-Performance Process Manager Control Theory 157

08/2019 Honeywell
 14. Logic Points
14.1 Functional Overview
Description
The logic point provides a configurable mix of logic capability that, together with a
digital composite point, provides the basis for integrated logic functions. The logic point
is also fully integrated with the regulatory functions in the HPM. A logic point consists
of logic blocks, flags, numerics, user-defined generic descriptors, input connections, and
output connections as shown in the following figure.
Figure 14-1 Logic Point

GENERIC DESCRIPTORS

PARMDESC (1) DESCTEXT (1)

: :
PARMDESC (12) DESCTEXT (12)

LOGIC INPUT LOGIC BLOCKS LOGIC OUTPUT

CONNECTIONS CONNECTIONS

SO (1)
LISRC (1) L (1) LOGALG (1) LOSRC (1) LODSTN (1)
:
: : LOENBL (1) :
:
: :
:
SO (24) LOSRC (12) LODSTN (12)
LISRC (12) L (12) LOGALG (24)

LOENBL (12)

NUMERICS FLAGS

NN (1) . . NN (8) = User FL (1) = Always OFF.

Set FL (2) = Always ON.
FL (3) = Point Activation.
FL (4) = PMM Startup.
FL (5) = At Least One Bad LI.
FL (6) = Watchdog Reset Flag.
FL (7) .. FL (12) = User Set.

R688 HPM High-Performance Process Manager Control Theory 159

08/2019 Honeywell
14 Logic Points
14.2 Configuring a Logic Point

Connections
The logic point can have up to 12 input connections, 24 logic blocks, and 12 output
connections. The actual number of these is specified through the entry made for
LOGMIX parameter as shown in the following table.
Table 14-1 Entires for LOGMIX parameters

Input Logic Output LOGMIX

Connections Blocks Connections Param. Entry

12 24 4 12_24_4

12 16 8 12_16_8

12 8 12 12_8_12

14.2 Configuring a Logic Point

Input connections
Inputs to the logic point are assigned by the user during configuration by using logic
input connections. The user can specify up to 12 inputs that are assigned to logic-point
inputs L(1) to L(12), as shown in the figure in Logic Points, Functional Overview,
Description. The logic input connections can be specified using the
"Tagname.Parameter" format, or the hardware reference address format by using the
LISRC parameter.
The inputs to the logic point can be obtained from any of the following sources:
• Any Boolean, integer, enumeration, self-defining enumeration, or real parameter
within this HPMM or in another UCN node. Note that the integer, enumeration, or
self-defining enumeration parameters are automatically converted to real values.
• Any parameter from the IOPs in this HPM. Note that each IOP resident parameter
counts as one of a maximum of four prefetches across the I/O Link (per logic block).
The exception is for the following parameters which are scanned—
− PVFL and BADPVFL of a DI point.
− SO and INITREQ of a DO point.
− PV, PVSTS, BADPVFL, PVHHFL, PVHIFL, PVLLFL, PVLOFL,
PVROCNFL, PVROCPFL of an AI point.

160 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 14 Logic Points
14.2 Configuring a Logic Point

Effect of communication and configuration errors

Because the logic point can be used for implementing safety interlocks, special handling
is provided for inputs, especially Boolean inputs that cannot be obtained because of
communication or configuration errors.
For example, an input obtained from a failed DI Processor can result in a communication
error. Alternatively, an input can be coming from a digital composite point in another
HPM (or APM OR PM) and the point mix in that HPM can be changed such that the
specified point no longer exists. This results in a configuration error. In order for the
logic to be able to continue in spite of a configuration error, the following special
features are provided:
• Bad Boolean Inputs—If a Boolean input is not successfully fetched, its value is
defaulted based on the logic input bad handling option parameter (LIBADOPT) as
follows—
− LIBADOPT = On
The On state is substituted for the unsuccessful input.
− LIBADOPT = Off
The Off state is substituted for the unsuccessful input.
− LIBADOPT = Hold
The previous value (the last successfully fetched value) is substituted for the
unsuccessful input. On startup, the previous value is defaulted to the Off state. If
required, the startup condition can be monitored by checking the startup flag.
• Bad Real Inputs—If a real input cannot be successfully fetched, its value is
defaulted to NaN. If required, special action can be taken in the logic by checking it
with the "check for bad" logic algorithm.
• Input Bad Flag—When an error is encountered in fetching the value of any input,
flag FL(5) is set to On. Note that flag FL(5) is not set to On if a real input is
successfully fetched but has a value of NaN.
• Processing Order—The logic points defined for each HPM are processed in
descending order. Within each logic point, the inputs are calculated first, then the
gates are processed, then the outputs are processed, each in ascending order.

R688 HPM High-Performance Process Manager Control Theory 161

08/2019 Honeywell
14 Logic Points
14.2 Configuring a Logic Point

Flags
Twelve flags, FL(1) to FL(12), are provided for each logic point. The states of flags
FL(1) to FL(6) are controlled by the HPM and cannot be changed by the user. Flags
FL(7) to FL(12) are assigned by the user for controlling the path of the logic in the
respective logic point. The flags are described in the following table.

TIP
You can not change Flags FL(1) to FL(5), but the states of these flags can be
used as inputs to the logic points and can also be read by user programs.

Flag Description

FL(1) Always Off (see “Output connections” in Section 14.2 when used for
logic output enable).

FL(2) Always On.

FL(3) On only if this logic point is processing for the first time after
becoming active.

FL(4) On only if this point is processing for the first time after the HPMM
box state has transitioned from Idle to Run, or the HPMM has gone
into the Run state following a power-up.

FL(5) On if at least one of the logic input connections was unsuccessful in

fetching the specified source parameter.

FL(6) Used by the watchdog timer logic algorithm. It is set to On by the

function or device being monitored to indicate that it is alive. The
watchdog timer algorithm always sets this flag to Off. Flag FL(6)
cannot be changed from the Universal Station.

FL(7)-FL(12) Can be changed as determined by the user. They can be changed

from the Universal Station, other logic points, or user programs.

Numerics
Eight numerics, NN(1) to NN(8), are provided with each logic point. The numerics can
be used as reference values for the comparison logic algorithms, or they can be used as
source parameters for the output connections when writing predefined analog constants
to other points. The values of the numerics can be changed from the Universal Station, by
other logic points, or by user programs. A bad numeric input typically has the value NaN.

162 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 14 Logic Points
14.2 Configuring a Logic Point

Logic blocks
The logic operations are performed by the logic blocks. Up to 24 logic blocks may be
configured by the user for each logic point. The actual number of logic blocks configured
is determined by the logic mix described in Logic Points, Connections. Each logic block
consists of:
• Up to 4 inputs (specified by S1, S2, S3, S4).
• One logic algorithm (specified by LOGALG).
• One Boolean output (specified by SO).
The parameters associated with a logic block are always qualified with an array index
corresponding to the number of that logic block. For example, LOGALG(4) represents
the algorithm configured in the logic block number 4, whose output is SO(4), and the
inputs may be S1(4), S2(4), and so on.
On the first time through configuration, the outputs of all logic blocks are set to OFF;
however, on a subsequent restart (for example: IDLE to RUN transition of the HPMM
state, or INACTIVE to ACTIVE transition of the point execution state), all the outputs
are held at their previous values.
The logic points defined for each HPM are processed in descending order. Within each
logic point, the inputs are calculated first, then the gates are processed, then the outputs
are processed, each in ascending order.
Output connections
Logic output connections are used to write the values of local parameters of a respective
logic point to the configured destinations. Up to 12 output connections can be configured
for each logic point. The actual number of output connections is determined by the
LOGMIX parameter described in Logic Points, Connections. The destinations are
specified by parameter LODSTN by using the "Tagname.Parameter" format or the
hardware reference address format.
The logic output connection can write the selected local parameters of a logic point to
any of the following destinations:
Any Boolean, integer, enumeration, self-defining enumeration, or real parameter in this
HPMM, or another UCN node
Any Boolean, integer, enumeration, self-defining enumeration, or real parameter in the
IOPs in this HPM. A maximum of 8 such connections can be configured for each point.
The remaining 4 output connections can be used to write to boolean or real parameters
that reside in this HPMM or in another UCN node.
The user must specify the local parameter within the logic point and the destination to
which it is to be written. The local parameter to be written is specified as the logic output
source (LOSRC(n), where n = 1 to 12). The source parameter for the output connection
can be selected from any of the flags (specified as FL1, FL2, and so on), numerics
R688 HPM High-Performance Process Manager Control Theory 163
08/2019 Honeywell
14 Logic Points
14.2 Configuring a Logic Point

(specified as N1, N2, and so on), external inputs (specified as L1, L2, and so on), or the
output of any of the logic blocks (specified as SO1, SO2, and so on.).
Associated with each output connection is a logic output enable flag, LOENBL(n). The
parameter pointed to by LOENBL(n) must be ON for the corresponding output
connection to write to the specified destination. If store-only-on-a-change is required, the
appropriate condition to store can be determined by the CHDETECT logic algorithm and
then used to manipulate the enable signal; or if the FL1 parameter is specified for the
output enable and the output data type is Boolean, then output occurs on change only.
The logic output enable flag can be obtained from any of the flags (specified as FL1,
FL2, and so on), external inputs (specified as L1, L2, and so on.), or the output of any of
the logic blocks (specified as SO1, SO2, and so on.).
Generic descriptors
Up to 12 user-defined generic descriptors are provided with each logic point for
identifying parameters of the logic point with custom names that are to be shown on
Universal Station displays. Generic descriptors can be assigned to any of the following
logic-point parameters:
• Flags (FL1, FL2, and so on).
• Numerics (N1, N2, and so on).
• External inputs (L1, L2, and so on).
• Outputs of any of the logic blocks (SO1, SO2, and so on).
Typically, the generic descriptors identify critical interlock signals, operator-adjusted
parameters, and so on.
The actual number of descriptors used is determined by the NODESC parameter for this
logic point. For each descriptor, the parameter to which it is attached is defined by
PRMDESC(n) parameter, and the corresponding 8-character descriptor is defined by
GENDESC(n).

164 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 14 Logic Points
14.2 Configuring a Logic Point

Configurable alarms
Four custom alarms can be configured for each logic point. The alarm source can be any
of the logic inputs (L1–L12), logic flags (FL1–FL12), logic gate outputs (SO1–SO24), or
None.
When the alarm source is None, a CL program can force an alarm by writing ON to the
alarm flag (C1FL–C4FL) and clear the alarm by writing OFF to the alarm flag.
Each of the four custom alarms permits an 8-character descriptor that appears on page
one of the Detail Display, the Alarm Summery Display, and the Real Time Journal, when
that alarm is active.
The alarm priority choices are:

• No Action • Journal • Low • High

• Emergency • Journal Print • Printer

Parameters

REFERENCE - INTERNAL
For a complete list of the parameters associated with the Logic Point
algorithms, refer to the PM Family Parameter Reference Dictionary.

R688 HPM High-Performance Process Manager Control Theory 165

08/2019 Honeywell
14 Logic Points
14.3 Logic Block Algorithms

14.3 Logic Block Algorithms

Logic functions
Logic blocks perform logic functions. A logic block can have one-to-four inputs and
produce a single Boolean output, depending on the selected algorithm. The algorithm can
require real or Boolean inputs. The real inputs can be obtained from any of the numerics
(specified as NN1, NN2, and so on) or the external inputs (specified as L1, L2, and so
on). The Boolean inputs can be any of the flags (specified as FL1, FL2, and so on),
external inputs (specified as L1, L2, and so on), or the output of any of the logic blocks
(specified as SO1, SO2, and so on).
When one of the external inputs (L(1), L(2), .. L(12)) is used as an input to an algorithm,
the value fetched can be real or Boolean. If the algorithm requires a real input and the
fetched value is Boolean, it is treated as NaN. If the algorithm requires a Boolean input
and the fetched value is real, it is treated as OFF. In either case, the bad input flag, FL(5),
is not affected.
Supported Logic Block algorithms
The following logic block algorithms are supported.

Null AND gate OR gate NOT gate

NAND gate NOR Gate XOR Gate Qualified OR gate

with 2 Inputs ON

Discrepancy 3 Two Out of Three Switch Qualified OR gate

Voting with 3 Inputs ON

Compare Equal with Compare Not Equal Compare Greater Compare Greater
Deadband with Deadband Than with Deadband Than or Equal to with
Deadband

Compare Less Than Compare Less Than Check for Bad Fixed-Size Pulse
with Deadband or Equal to with
Deadband

Pulse with Maximum Pulse with Minmum Delay On Delay

Time Limit Time Limit

Off Delay Watchdog Timer Flip-Flop Change Detect

Null
This logic algorithm provides an output (SO) that is always set to OFF.

166 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 14 Logic Points
14.3 Logic Block Algorithms

AND Gate
This algorithm provides a 3-input AND gate, with each input (S1, S2, and S3) having the
capability of being optionally inverted, as required. The output SO is determined as
follows.
Figure 14-2 AND Logic Point Algorithm

S1

S2 AND SO

S3

ATTENTION
In the following truth table, REV indicates if the input is reverse acting
(inverted).

S1 S1REV S2 S2REV S3 S3REV SO

OFF ON OFF ON OFF ON OFF

OFF ON OFF ON ON OFF OFF

OFF ON ON OFF OFF ON OFF

OFF ON ON OFF ON OFF OFF

ON OFF OFF ON OFF ON OFF

ON OFF OFF ON ON OFF OFF

ON OFF ON OFF OFF ON OFF

ON OFF ON OFF ON OFF ON

OR Gate
This logic algorithm provides a 3-input OR gate, with each input (S1, S2, and S3) having
the capability of being optionally inverted, as required. The output SO is determined as
follows.

R688 HPM High-Performance Process Manager Control Theory 167

08/2019 Honeywell
14 Logic Points
14.3 Logic Block Algorithms

S1

S2 OR SO

S3

ATTENTION
In the following truth table, REV indicates if the input is reverse acting
(inverted).

S1 S1REV S2 S2REV S3 S3REV SO

OFF ON OFF ON OFF ON OFF

OFF ON OFF ON ON OFF ON

OFF ON ON OFF OFF ON ON

OFF ON ON OFF ON OFF ON

ON OFF OFF ON OFF ON ON

ON OFF OFF ON ON OFF ON

ON OFF ON OFF OFF ON ON

ON OFF ON OFF ON OFF ON

168 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 14 Logic Points
14.3 Logic Block Algorithms

NOT Gate
This algorithm provides the Boolean inversion (NOT) function. The output SO is the
inversion of the input S1 as follows.

S1 NOT SO

If S1 is... then SO is...

OFF ON

ON OFF

NAND Gate
This algorithm provides a 3-input NAND gate, with each input (S1, S2, and S3) having
the capability of being optionally inverted. The output SO is determined as follows.

S1

S2 NAND SO

S3

ATTENTION
In the following truth table, REV indicates if the input is reverse acting
(inverted).

R688 HPM High-Performance Process Manager Control Theory 169

08/2019 Honeywell
14 Logic Points
14.3 Logic Block Algorithms

S1 S1REV S2 S2REV S3 S3REV SO

OFF ON OFF ON OFF ON ON

OFF ON OFF ON ON OFF ON

OFF ON ON OFF OFF ON ON

OFF ON ON OFF ON OFF ON

ON OFF OFF ON OFF ON ON

ON OFF OFF ON ON OFF ON

ON OFF ON OFF OFF ON ON

ON OFF ON OFF ON OFF OFF

NOR Gate
This logic algorithm provides a 3-input NOR gate, with each input (S1, S2, and S3)
having the capability of being optionally inverted. The output SO is determined as
follows.

S1

S2 NOR SO

S3

ATTENTION
In the following truth table, REV indicates if the input is reverse acting
(inverted).

170 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 14 Logic Points
14.3 Logic Block Algorithms

S1 S1REV S2 S2REV S3 S3REV SO

OFF ON OFF ON OFF ON ON

OFF ON OFF ON ON OFF OFF

OFF ON ON OFF OFF ON OFF

OFF ON ON OFF ON OFF OFF

ON OFF OFF ON OFF ON OFF

ON OFF OFF ON ON OFF OFF

ON OFF ON OFF OFF ON OFF

ON OFF ON OFF ON OFF OFF

XOR Gate
This algorithm provides a 2-input exclusive-OR gate. The output SO is determined as
follows.

S1

XOR SO

S2

S1 S2 SO

OFF OFF OFF

OFF ON ON

ON OFF ON

ON ON OFF

R688 HPM High-Performance Process Manager Control Theory 171

08/2019 Honeywell
14 Logic Points
14.3 Logic Block Algorithms

Qualified OR Gate with 2 Inputs ON

This algorithm provides a 4-input qualified-OR function that requires at least two inputs
to be ON before output SO is set to ON. The output is determined as follows.

S1

S2
QOR2 SO
S3

S4

If... then... else...

any two or more inputs (S1, S2, S3, S4) are ON SO = ON SO = OFF

172 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 14 Logic Points
14.3 Logic Block Algorithms

Qualified OR Gate with 3 Inputs ON

This algorithm provides a 4-input qualified-OR function that requires at least three inputs
to be ON before output SO is set to ON. The output is determined as follows.

S1

S2
QOR3 SO
S3

S4

If... then... else...

any three or more inputs (S1, S2, S3, S4) are ON SO = ON SO = OFF

Discrepancy 3
The Discrepancy 3 algorithm has three inputs and an output. The output SO is set True if
the three inputs do not agree for longer than the delay time (DLYTIME). The delay time
is configurable and has a range of 1 to 8000 seconds. If the configured delay time is less
than or equal to one sample time of this logic point, it is assumed to be equal to one
sample time.
The output is determined as follows.

DLYTIME

S1

S2 DISCREP3 SO

S3

If... or... or... after... then... else...

S1 <> S2 S2 <> S3 S3 <> S1 T >= DLYTIME SO = ON SO = OFF

R688 HPM High-Performance Process Manager Control Theory 173

08/2019 Honeywell
14 Logic Points
14.3 Logic Block Algorithms

The Discrepancy block is used to monitor inputs S1 - S3 for inactivity or failure. The
output (SO) goes true if any input disagrees with either of the other two inputs for longer
than the preset delay time.
Two Out of Three Voting
A two out of three voting function can be implemented with the QOR2 and DISCREP3
logic blocks as follows. One input to the QOR2 block is connected to a source that is
always off such as the output (LO) of logic flag 1.

S1 DLYTIME

S2 S1
QOR2 SO
S3 S2 DISCREP3 SO

S4 S3

FL1 (Off)

If... or... or... then... else...

S1 and S2 S2 and S3 S3 and S1 SO = ON SO = OFF

Switch
This algorithm provides a 2-input switch. Output SO is determined as follows.

If... then... else...

S3 = ON SO = S1 SO = S2

174 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 14 Logic Points
14.3 Logic Block Algorithms

Compare Equal with Deadband

This algorithm compares two real inputs (R1 and R2) for being "almost equal" or within
a specified deadband. Output SO is determined as follows.

R1

R2
EQ SO

DEADBAND

If... then... else...

ABS(R1 - R2) <= DEADBAND SO = ON SO = OFF

ATTENTION
If R1 and/or R2 inputs are "NaN", then SO is not changed.

Compare Not Equal with Deadband

This algorithm compares two real inputs for NOT being "almost equal," or being outside
of a prespecified deadband. Output SO is determined as follows:

R1

R2
NE SO

DEADBAND

If... then... else...

ABS(R1 - R2) > DEADBAND SO = ON SO = OFF

R688 HPM High-Performance Process Manager Control Theory 175

08/2019 Honeywell
14 Logic Points
14.3 Logic Block Algorithms

ATTENTION
If R1 and/or R2 inputs are "NaN", then SO is not changed.

Compare Greater Than with Deadband

This algorithm compares a real input (R1) for being greater than another real input (R2)
with a predefined deadband. Output SO is determined as follows.

R1

R2
GT SO

DEADBAND

If... then... else... then... else...

R1 > R2 SO = ON R1 <= (R2 - DEADBAND) SO = OFF SO = OFF

ATTENTION
If R1 and/or R2 inputs are "NaN", then SO is not changed.

Compare Greater Than or Equal with Deadband

This algorithm compares a real input (R1) for being greater than or equal to another real
input (R2) with a specified deadband. Output SO is determined as follows.

R1

R2
GE SO

DEADBAND

176 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 14 Logic Points
14.3 Logic Block Algorithms

If... then... else... then... else...

R1 >= R2 SO = ON R1 < (R2 - DEADBAND) SO = OFF SO is not changed

ATTENTION
If R1 and/or R2 inputs are "NaN", then SO is not changed.

Compare Less Than with Deadband

This algorithm compares a real input (R1) for being less than another real input (R2) with
a predefined deadband. Output SO is determined as follows.

R1

R2
LT SO

DEADBAND

If... then... else... then... else...

R1 < R2 SO = ON R1 >= (R2 - DEADBAND) SO = OFF SO is not changed

ATTENTION
If R1 and/or R2 inputs are "NaN", then SO is not changed.

R688 HPM High-Performance Process Manager Control Theory 177

08/2019 Honeywell
14 Logic Points
14.3 Logic Block Algorithms

Compare Less Than or Equal with Deadband

This logic algorithm compares a real input (R1) for being less than or equal to another
real input (R2) with a predefined deadband. Output SO is determined as follows.

R1

R2
LE SO

DEADBAND

If... then... else... then... else...

R1 <= R2 SO = ON R1 > (R2 + DEADBAND) SO = OFF SO is not changed

ATTENTION
If R1 and/or R2 inputs are "NaN", then SO is not changed.

Check for Bad

This logic algorithm checks a real input (R1) for being bad (equal to NaN). Output SO is
determined as follows.

R1 CHECKBAD SO

If... then... else...

R1 is NaN SO = ON SO = OFF

178 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 14 Logic Points
14.3 Logic Block Algorithms

Fixed-Size Pulse
This logic algorithm provides a fixed-size output pulse at the SO output each time the S1
input transitions from the OFF state to the ON state. The output pulse width (in seconds)
is specified by the DLYTIME parameter. If the delay time is less than or equal to one
sample time (of the logic point), it is assumed to be equal to one sample time. Another
output pulse cannot be generated until the generation of the preceding pulse has been
completed.

DLYTIME

S1 PULSE SO

S1

DLYTIME DLYTIME

SO

R688 HPM High-Performance Process Manager Control Theory 179

08/2019 Honeywell
14 Logic Points
14.3 Logic Block Algorithms

Pulse with Maximum Time Limit

This logic algorithm provides a pulse at the SO output each time the S1 input transitions
from the OFF to the ON state. If the input stays ON longer than a predefined time, the
output pulse is terminated. The maximum output pulse width (in seconds) is specified by
the DLYTIME parameter. If the specified output pulse width is less than or equal to one
sample time (of the logic point), it is assumed to be equal to one sample time.

DLYTIME

S1 MAXPULSE SO

S1

DLYTIME DLYTIME

SO

180 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 14 Logic Points
14.3 Logic Block Algorithms

Pulse with Minimum Time Limit

This algorithm generates a pulse at the SO output each time the S1 input transitions from
the OFF to the ON state. If the S1 input stays ON for an interval that is less than the
specified time, the output pulse is extended until the timed interval is over. The minimum
output pulse width (in seconds) is specified by the DLYTIME parameter. If the specified
output pulse width is less than, or equal to, one sample time (of the logic point), it is
assumed to be equal to one sample time.

DLYTIME

S1 MINPULSE SO

S1

DLYTIME DLYTIME

SO

R688 HPM High-Performance Process Manager Control Theory 181

08/2019 Honeywell
14 Logic Points
14.3 Logic Block Algorithms

Delay
This logic algorithm delays the input signal at the S1 input by one sample time. The SO
output always follows the input after one sample time delay.

S1 DELAY SO

182 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 14 Logic Points
14.3 Logic Block Algorithms

On Delay
This logic algorithm delays the input signal supplied at the S1 input when the input signal
is going from the OFF to the ON state. (There is no delay provided when the input
changes from the ON to the OFF state.) When the input state changes from OFF to ON,
an internal timer starts counting down the delay time specified by the DLYTIME
parameter (in seconds). When it times out, the S1 input is monitored again, and if it is
still ON, the SO output is set to ON. When the input state transitions to OFF, the SO
output is set to OFF immediately, and the timer is shut off (if it is running). If the
specified delay time is less than or equal to one sample time (of the logic point), it is
assumed to be equal to one sample time.

DLYTIME

S1 ONDLY SO

S1

DLYTIME DLYTIME

SO

R688 HPM High-Performance Process Manager Control Theory 183

08/2019 Honeywell
14 Logic Points
14.3 Logic Block Algorithms

Off Delay
This logic algorithm delays the input signal supplied at the S1 input when the input signal
is going from the ON to the OFF state. (There is no delay provided when the input
changes from the OFF to the ON state.) When the input state changes from ON to OFF,
an internal timer starts counting down the delay time specified by the DLYTIME
parameter (in seconds). When it times out, the S1 input is monitored again, and if it is
still OFF, the SO output is set to OFF. When the input state transitions to ON, the SO
output is set to ON immediately, and the timer is shut off (if it is running). If the
specified delay is less than or equal to one sample time (of the logic point), it is assumed
to be equal to one sample time.

DLYTIME

S1 OFFDLY SO

S1

DLYTIME DLYTIME

SO

184 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 14 Logic Points
14.3 Logic Block Algorithms

Watchdog Timer
This logic algorithm provides a "time out" capability to monitor other system functions
or remote devices. The function or device monitored must set the watchdog reset flag
FL(6) (of this logic point) to ON within a time interval specified (in seconds) by the
DLYTIME parameter, otherwise it is assumed to have failed, and the SO output of the
algorithm is set to ON. If the specified delay time is less than or equal to one sample time
(of the logic point), it is assumed to be equal to one sample time. When the watchdog
timer algorithm runs and if the FL(6) flag is ON, the internal timer is set equal to
DLYTIME, and FL(6) and the output SO are both set to OFF. However, if FL(6) is OFF,
the internal timer is decremented, and if it becomes zero, the SO output is set to ON.
Because this algorithm always uses the FL(6) flag of the logic point as the reset input,
only one Watchdog Timer algorithm should be configured for each logic point.
Flip-Flop
This algorithm provides the flip-flop function. The SO output is determined by the states
of inputs S1 and S2 as follows.

S1

S2 FLIPFLOP SO

S3

S1 S2 SO
OFF OFF Not changed
ON OFF OFF
OFF ON ON
ON ON S3 input

R688 HPM High-Performance Process Manager Control Theory 185

08/2019 Honeywell
14 Logic Points
14.3 Logic Block Algorithms

Change Detect
This algorithm is used to detect changes in up-to-three inputs. The output SO is
determined as follows.

S1

S2 CHDETECT SO

S3

SO = (S1 < > S1_last_time)

OR
(S2 < > S2_last_time)
OR
(S3 < > S3_last_time)

186 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 15. Process Module Data Point
15.1 Functional Overview
Purpose
Control strategies frequently need the flexibility of user programs for continuous, batch,
or hybrid applications. A Process Module Data Point is the resource for execution of
user-created programs written in Honeywell's Control Language (CL/HPM). CL/HPM is
a member of Honeywell's family of advanced process-engineer oriented languages and is
a powerful tool for advanced continuous control, sequential control, and computations.
CL programs are self-documenting, which is an important feature when future
modifications of control strategies are anticipated.
Description
The Process Module Data Point, as shown in the following figure, is the interface
between the system and a CL/HPM (sequence) program that resides in the Process
Module Data Point.

R688 HPM High-Performance Process Manager Control Theory 187

08/2019 Honeywell
15 Process Module Data Point
15.1 Functional Overview

Figure 15-1Process Module Data Point Functional Diagram

PROCESS MODULE DATA POINT

PROCMOD
OVERPHAS SEQUENCE
OVERSTEP
CONTROL
OVERSTAT
ACP INTERFACE
BATCHID

LOCAL VARIABLES
SEQMODE CL/HPM
SEQUENCE • 127 Flags
SEQNAME
PROGRAM • 80 Numerics
PHASE STATUS
• 16 Strings
STEP • Normal • 4 Time s
INTERFACE Sequence
STATMENT
PHASETIM • Subroutines

• Abnormal
Condition
Handlers
ALPRIOR
ALARM
PHASEAL
INTERFACE
SEQERR

HPM BOX DATABASE

16 118

188 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 15 Process Module Data Point
15.2 Sequence Programs Overview

Use
The Process Module Data Point is the mechanism through which:
• an operator, a CL/AM block, a user-written CM program, or another sequence
program can start and stop a sequence program and monitor the current status of a
sequence program.
• sequence alarms (sequence errors, failures, and phase alarms) are reported to the
system; an alarm priority can be assigned to sequence alarms.
• a sequence program can send information to an Advanced Control Point (ACP) in a
Computing Module when implementing high-level control strategies.
Capacity
Total statement capacity depends on configuration. The maximum number of CL/HPM
statements = 3(22000 - n) where n is the number of Memory Units used by data points
(see “Determining Processing and Memory Capacity” in Section 49.4).
Using the Universal Station or the Universal Work Station, individual programs can be
easily modified and reloaded without affecting the execution of regulatory control, logic
blocks, and other user programs.

15.2 Sequence Programs Overview

To accomplish the desired sequence control, the sequence program can:
• Monitor current process values such as temperatures, pressures, and flows and
current states of devices such as valves and motors, by—
− accessing values from the local HPM database, and from any other node such as
HPM, APM, PM, LM, or SM that is on the same UCN.
− reading the values of almost all parameters in the HPM database except for
character-string descriptors such as PTDESC (Point Descriptor), and
input/output connections.
• Control the process by using accessed values to calculate new values and write
them to the appropriate parameters, where the sequence program—
− writes values into the local HPM database and into any other node such as
HPM, APM, PM, LM or SM that is on the same UCN.
− writes values to all parameters in the HPM database except for calculated
variables such as alarm flags and general configuration parameters such as
PVALGID (PV Algorithm Identifier).
• Use the variables that reside in the local Process Module Data Point, including—
− 127 local flag variables.
− 80 local numeric variables.
R688 HPM High-Performance Process Manager Control Theory 189
08/2019 Honeywell
15 Process Module Data Point
15.2 Sequence Programs Overview

− eight 8-character string variables Point (can alternatively use four 32-character
or two 64-character strings).
− 4 time variables.
• Use the variables (flag, numeric, string, time, timer) that reside in another Process
Module Data Point.
• Use HPM Box resident variables (flag, numeric, string, time, timer) within the
same HPM, noting that—
− CL programs cannot access HPM Box variables with an index of greater than
4,095.
− Array points can be used to refer to those variables.
• Start another sequence program or force an abnormal condition in another
Process Module Data Point as required.
• Issue predefined or computed messages to the operator to inform you of current
process conditions and to provide instructions. (the operator can also override various
portions of the sequence, as required).

ATTENTION
With R530, the compile time of a loaded CL/HPM sequence program is
provided. Time and Date stamp information is shown on the Detail Display of
the UCN ProcMod point. To access this page, select the target CONFIG
PARAMS from the first page of the ProcMod Point Detail Display.

190 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 15 Process Module Data Point
15.3 Unit Partitioning

15.3 Unit Partitioning

Background
The user's process is usually partitioned into process units where the operators have the
responsibility to control one or more process units. To support this type of partitioning,
the HPM Process Module Data Points (sequence programs) can be partitioned on a
process unit basis as shown in the following figure. This is accomplished by using the
following three elements:
• The set of CL/HPM sequence programs that control individual process unit.
• The set of process monitoring and control elements that are used by the sequence
program to control the operation of the process unit.
• Operating displays show various portions of the sequence programs. One example is
the Module Summary Display, which shows the current status of the process modules
on a process unit basis. Other displays are the Module Group and Module Detail
displays which allows the operator to start and stop the sequence programs.

R688 HPM High-Performance Process Manager Control Theory 191

08/2019 Honeywell
15 Process Module Data Point
15.3 Unit Partitioning

Figure 15-2 Sequence Program and Unit Partitioning

High Performance
Process Manager Module

(HPMM)

Process Module Data Points

1 2 3 4 5 • • • (Sequence
• Slots) • • • • • • • • 25

Unit 1 Unit 2 Unit 3 Unit 4 Unit 5

Process Equipment 16 119

Consistent partition practices

Wherever possible, process unit partitioning should be consistent with the inherent
boundaries in the system, such as:
• beginning and end points of major separable segments of a process.
• physical separations or classifications of process equipment components.

192 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 15 Process Module Data Point
15.4 Writing sequence programs

15.4 Writing sequence programs

Background
Sequence programs are written in CL/HPM and compiled at a Universal Station or
through TPS Builder. At compilation time, each sequence program is bound to a specific
Process Module Data Point (that is, a specific sequence slot) and is written to a separate
object file. These files can be directly downline loaded through the NIM to the process
module slots in the designated HPM.

ATTENTION
To prepare CL/HPM programs, refer to the Control Language High-
Performance Process Manager Reference Manual To compile a CL/HPM
program (binding it to a process module point) and load it into the HPM:
• using the Universal Station, refer to Control Language High-
Performance Process Manager Data Entry.
• using the TPS Builder, refer to the TPS Builder Configuration Tool Guide.

Sequence library
The Sequence Library contains the names of the sequence programs. The Sequence
Library is divided into three sections, with each section having a maximum of 1000
entries. (The section is defined by the LIBRYNUM parameter.) A section of the library
can be viewed by reconstituting the point, using $NxxLiby where xx is the UCN number
on which the NIM resides and y is the section number of the library.
Library entries can be made automatically by the CL Compiler, or they can be entered
manually by the user. If the manual entry method is to be used, the user should first enter
the names on the NIM Library Configuration Form, AP88-540. The LIBRYTXT
parameter defines the allowable character set for the library entries.
Library 1 is reserved for sequence names; Libraries 2 and 3 are reserved for all other
names. If the CL Compiler completely fills up Libraries 2 and 3, the compiler will begin
entering the overflow information into Library 1, beginning with index number 1,000 and
working down towards index number 2.
The sequence library resides in the NIM, and it is applicable to all the HPMs (or APMs,
or PMs) on the same UCN.

R688 HPM High-Performance Process Manager Control Theory 193

08/2019 Honeywell
15 Process Module Data Point
15.5 Sequence Program Structure

Local variables
Each Process Module Data Point contains 127 local flags, 80 local numerics, 4 local time
variables, and 16 local 8-character strings. The strings can alternatively be allocated as
8 16-character, 4 32-character, or 2 64-character strings. Flags are designated FL(1) to
FL(127) and the numerics are designated NN(1) to NN(80). Times are designated
TIME(1) to TIME(4) and Strings are designated STRn(mm) where n is the string length
(8, 16, 32, 64) and mm is the specific string number. For example, STR8(15) for 8-
character strings, STR16(7) for 16-character strings, and so on.
The primary purpose of the flags and numerics is to provide storage for recipe data and
intermediate results. Time variables are used to record date/time information, and strings
contain text strings that name or describe things. These local variables can be accessed by
the sequence executing in the same process module in which they reside, or they can be
accessed by any other sequence in the same HPM. The flags and numerics can also be
accessed by all system functions, such as CL programs in the AM, Universal Station
displays, and so on. They can be accessed as local variables by CL/HPM by using the AT
clause. Refer to the Control Language High-Performance Process Manager Reference
Manual
These local variables are accessed by the various system elements using the
"Tagname.Parameter" convention where the Tagname is the name of the process module
in which they reside, and the "Parameter" is the parameter name such as FL(15), NN(25),
STR8(15), or Time(4). To store (write) into the local flags and numerics, the keylock
position must equal or exceed the minimum access level specified in parameter
SPLOCK.
Process module flags and numerics are set to the default values of OFF and NaN
respectively, when the process module data point is deleted or when the HPM database is
initialized to default values. Time and string variables are initialized to spaces and 0
seconds, respectively. The HPM database is set to default values on initial loading of the
HPM Box data point and when the SCANRATE parameter or point mix changes in
subsequent loads of the HPM Box data point. Process Module data point local flags and
numerics are left unchanged during downloading of sequence programs or the process
module data point itself to allow a record or history to exist between programs.
Flag, Numeric, String, Times, and Timer variables that reside in the HPM box are a
different set of variables from the local flags, numerics, strings, and times. These
variables are available to the sequence programs in this HPM and to the other sequence
programs in the HPMs (or APM, or PMs) on the same UCN and, with some minor
restrictions, to other system functions. They are described in Section 9 of this manual.

15.5 Sequence Program Structure

Parts of a sequence program
As illustrated in the following figure, each sequence program consists of program header
194 HPM High-Performance Process Manager Control Theory R688
Honeywell 08/2019
 15 Process Module Data Point
15.5 Sequence Program Structure

and two main sections:

• data declaration section.
• execution section.

R688 HPM High-Performance Process Manager Control Theory 195

08/2019 Honeywell
15 Process Module Data Point
15.5 Sequence Program Structure

Figure 15-3 Sequence Program Structure

196 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 15 Process Module Data Point
15.5 Sequence Program Structure

Data declaration
The data declaration section requires you to provide optional CL/HPM statements that
relate user-defined names to HPM flags, numerics, strings, and times that declare the
numeric constants, and that name the data points used in the program.
Execution declaration
The execution section consists of one-to-three parts:
• Normal Sequence (refer to Error! Reference source not found.) which—
− is the main program that provides control when conditions in the process are
normal (for example, the process is proceeding within acceptable limits and
does not require special control actions) is divided into "Phases," "Steps," and
"Statements" (as shown in Figure 15-3).
• Subroutines, which—
− simplify the program structure and are used for executing repetitive functions,
thereby reducing the programming effort and memory requirements.
− can be called by the normal sequence, other subroutines, or abnormal condition
handlers.
− permit two levels of nesting for both normal and abnormal sequences (a runtime
error is generated if the nesting level is violated).
− are specific to one sequence program (that is, subroutines defined outside of the
program and maintained in subroutine libraries are not supported in the High-
Performance Process Manager).
• Abnormal-Condition Handlers (see Error! Reference source not found.), which—
− provide corrective action when abnormal conditions are encountered.
− detect abnormal conditions when the SEQEXEC value is Run, Pause, Fail,
Error, or End.
− suspends the normal sequence when an abnormal condition is detected and
begins execution of the appropriate abnormal-condition handler.
− are identified in the sequence program by the HANDLER statement, preceded
by the name for the type of handler, and followed by the user-given handler
name (for example, HOLD HANDLER cooldown).
− consist of steps and statements. Hold and Shutdown abnormal-condition
handlers and an Emergency Shutdown handler.
− have priority over each other and over the normal sequences.
− can be enabled or disabled anywhere within a Phase by using the ENB
statement, which causes a suspend condition, but the new conditions to be
monitored take effect immediately.
R688 HPM High-Performance Process Manager Control Theory 197
08/2019 Honeywell
15 Process Module Data Point
15.5 Sequence Program Structure

− can also be enabled or disabled by the phase header in the phase statement.

ATTENTION
The abnormal condition handlers and the normal sequence order of
execution priority is as follows:
• Emergency Shutdown (Highest Priority).
• Shutdown.
• Hold.
• Normal Sequence (Lowest Priority).
The priority of a Restart Section is the same as the abnormal-condition
handler that contains the Restart Section.

Table 15-1 Normal Sequence and Abnormal Condition Handler Component

Definitions

Item Definition

Normal Sequence

Phase A sequence program consists of a grouping of phases. A phase executes a

major process function or marks a major process milestone, such as a charging
phase or heat-up phase. Phase boundaries are key points of synchronization in
the control program. A phase is identified in the sequence program by the
PHASE statement, and consists of optional steps and statements.

Step A step executes a minor process function such as opening a valve with
associated checks and verification, or checking a temperature. At least one step
is executed each time the sequence is executed. A step is visible at a Universal
Station as a process milestone. It is identified in the sequence program by a
STEP statement, and consists of an ordered set of CL/HPM statements. The
step size is limited to a maximum of 255 statements.

Statement One CL/HPM instruction. A statement performs an elementary action, such as

commanding a valve to open, do arithmetic operations, fetch variables, and so
on.

Abnormal-Condition Handlers

Hold Executed on an abnormal condition that requires a partial shutdown and can be
terminated by a restart section that is identified by the RESTART statement,
followed by the handler's END statement

198 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 15 Process Module Data Point
15.6 Sequence Execution

Item Definition

Shutdown Executed on an abnormal condition that requires a systematic shutdown can be

terminated by a restart section that is identified by the RESTART statement,
followed by the handler's END statement

Emergency Executed on an abnormal condition that requires a complete, sudden shutdown

Shutdown and can be terminated by only the handler's END statement

15.6 Sequence Execution

Normal execution
Execution of the normal sequence can be initiated by:
• an operator from the Process Module Detail Display.
• another sequence, executing in another process module by using the INITIATE
statement. Generally, this other sequence is a master or supervisory sequence; that is,
a sequence program that initiates, monitors, and controls other sequences.
• a CL Block in an AM which changes the PROCMOD parameter value in the HPM
to Strt (Start).
• a user-written program in a CM which changes the PROCMOD parameter value in
the HPM to Strt (Start).

TIP
To manipulate the PROCMOD parameter successfully:
• its value must be Off and the value of SEQEXEC must be Loaded.
• the keylock position must equal or exceed the minimum access level
specified in parameter CTLLOCK.
The value of PROCMOD can be changed to START from any keylock
position regardless of the access level specified in CTLLOCK.

Execution of abnormal handlers

Enabled abnormal-condition handlers can be initiated by:
• a request from an operator.
• Predefined process condition detected by the sequence program at every preemption
point, such as before executing a step.
• activation by a statement in the sequence (for example, INITIATE HOLD).
• an INITIATE statement from another sequence.

R688 HPM High-Performance Process Manager Control Theory 199

08/2019 Honeywell
15 Process Module Data Point
15.7 Process Module Operating Status

• a CL block in an AM.
• a user-written program in a CM.

15.7 Process Module Operating Status

The process module operational state represents the operational condition of a process
module. The module state is represented through the PROCMOD parameter and the
allowable states are listed and described in the following table. A state diagram is
provided in the following figure.

Table 15-2 Process Module Operating States

State Description

Off Process module slot is not being processed. A sequence program

can be assigned to a process module but it cannot be executed.
The sequence execution mode is not applicable to this module
state.

Norm (Normal) The normal sequence program is running in the process module
slot.

Hold Process module is executing the hold abnormal-condition handler.

Hold sequence may be initiated by one of the items listed in
Execution of abnormal handlers.

Shdn Process module is executing the Shutdown abnormal-condition

(Shutdown) handler. Shutdown sequence can be initiated by one of the items
listed in Execution of abnormal handlers. Shutdown has priority
over Hold.

Emsd Process module is executing the Emergency Shutdown abnormal-

(Emergency condition handler. Emergency Shutdown sequence can be initiated
Shutdown) by one of the items listed in Execution of abnormal handlers.

ATTENTION
Parameter PROCMOD also contains the Strt (Start) and Stop states,
which are transitional states that can be controlled by one of the items
listed in Execution of abnormal handlers.

200 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 15 Process Module Data Point
15.7 Process Module Operating Status

Figure 15-4 Process Module Operating States Relational Diagram

From Normal or Abnormal

OFF Condition Handler

STOP

START

Return
NORMAL

HOLD

EMERGENCY
SHUTDOWN
SHUTDOWN

Hold,
Shutdown,
Restart
Restart
Section
Section

R688 HPM High-Performance Process Manager Control Theory 201

08/2019 Honeywell
15 Process Module Data Point
15.7 Process Module Operating Status

Sequence execution mode

The sequence execution mode defines the manner in which the sequence program is
executed. The sequence execution mode is established through the SEQMODE
parameter, and the allowable modes are listed and described in the following table.

Table 15-3 Sequence Execution Mode

Execution Description
Mode

Auto Normal mode of operation. Sequence runs from beginning to end

(Automatic) without operator intervention.

SemiAuto Sequence stops at all PAUSE statements in the sequence.

(Semi- Sequence can be restarted by the operator.
Automatic)

SnglStep Normally used for debugging. Sequence is executed one step at a

(Single-Step) time. Sequence can be restarted by the operator.

202 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 15 Process Module Data Point
15.8 Sequence Execution State

15.8 Sequence Execution State

The sequence execution state represents the current state of the sequence program. These
states are defined through parameter SEQEXEC and are listed and described in the
following table. The following figure shows the possible state transitions of the sequence.
Figure 15-5 Sequence Execution State Transitions

NO T LOADED

LOADING

LOADED

RUN

END PAUSE FAIL ERROR

R688 HPM High-Performance Process Manager Control Theory 203

08/2019 Honeywell
15 Process Module Data Point
15.8 Sequence Execution State

Table 15-4 Sequence Execution States

Execution State Description

NL (Not Loaded) Initial state in which sequence has not been assigned to a process module.
This state is automatically entered from the DLL state when loading has
been aborted.

DLL (Down- Transient state during which the loading of the sequence into the process
Line Loading) module slot is in progress.

Loaded Sequence program has been loaded into the process module slot. This state
is automatically entered from the DLL state when loading has been
completed.

Run Sequence program is running.

Pause Execution of the sequence is suspended because of the execution of a

PAUSE statement, or the completion of a step when in the single-step
mode. Sequence execution can be resumed by the operator.

Fail Sequence execution is suspended because of the detection of one of the

failure conditions listed below. A system message that describes the failure
condition is generated. Sequence execution can be resumed by the
operator.

Failure Code Definition

165 Sequence has been stopped by the operator

166 Attempt to start an abnormal-condition handler that has

not been enabled and no lower-priority abnormal-
condition- handler is enabled. Possibly using INITIATE
Suggestions:
• use INITIATE with a When Error clause.

167 Not used

168 Not used

169 An attempt was made to start a sequence that was not

loaded into the process module slot.

204 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 15 Process Module Data Point
15.8 Sequence Execution State

Execution State Description

170 Communication error detected in READ/WRITE

statement.
Possible cause:
• a READ/WRITE statement without a When Error Path
fails a bad read. (a post store reports its own failure
code.)
Suggestions:
• determine validity of the attempted fetch or store.
• check actual presence of point.

171 Communication error detected during an I/O Link access.

This error is generated for all post-store problems.
Possible cause:
• IO Link poststore failed.
• DI scan PV status is bad.
Suggestions:
• check I/O Link for reasons for bad post-store, or bad
PV in DI scan.

172 Range error has been detected.

Possible cause:
• box timer set point value greater than 32000.
• illegal stores to Digital Composite parameters.

173 Store failure because of "rights" error. For example, an

attempt was made to write to a parameter when the point
was not in the proper mode.
Possible cause:
• other points reject stores.
• attempt to write to box timer set-point or time base
when state is in RUN.
• attempt to start timer when PV is greater than SP.
• attempt to INITIATE a lower priority handler while in a
higher priority handler.
Suggestion:
• check state of point not accepting the store.

174 An interlock error condition has been detected.

R688 HPM High-Performance Process Manager Control Theory 205

08/2019 Honeywell
15 Process Module Data Point
15.8 Sequence Execution State

Execution State Description

175—255 Reserved for future use.

Error Sequence execution is suspended because of the detection of one of the

error conditions listed below. A system message that describes the error
condition is generated. Sequence execution can be resumed by the operator

Failure Code Definition

101 Not used

102 Array index error.

Possible cause:
• violated array index bound check.
Suggestions:
• check array bounds defined in the LOCAL.
• statement or in the subroutine header.

103 Illegal generated code.

Possible cause:
• could not find variable operator code in the reference
list.
• invalid statement header.
• unsupported built-in function call.
Suggestions:
• contact Honeywell Technical Assistance Center.

104 Illegal generated code referencing a parameter or

variable.
Possible cause:
• bad box timer parameter code.
• local numeric/flag index out of range.
• invalid time base.
Suggestions:
• contact Honeywell Technical Assistance Center.

206 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 15 Process Module Data Point
15.8 Sequence Execution State

Execution State Description

105 Interpreter stack overflow.

Possible cause:
• Not enough stack depth.
Suggestions:
• contact Honeywell Technical Assistance Center.

106 GO TO destination error.

Possible cause:
• invalid destination.
Suggestions:
• contact Honeywell Technical Assistance Center.

107 Key-level error.

Possible cause:
• tried store to read only parameter.
• tried store with access level invalid.
• system error.
Suggestions:
• contact Honeywell Technical Assistance Center.

108 Configuration mismatch error.

Possible cause:
• may be system error.
Suggestions:
• contact Honeywell Technical Assistance Center.

109 I/O Link prefetch overflow.

Possible cause:
• exceeded 12 I/O Link prefetches per step.
Suggestions:
• insert a new STEP in the code if several IOL references
are made within this step.

R688 HPM High-Performance Process Manager Control Theory 207

08/2019 Honeywell
15 Process Module Data Point
15.8 Sequence Execution State

Execution State Description

110 Subroutine nesting level error.

Possible cause:
• nesting of subroutine calls is more than two levels
deep.
Suggestions:
• reduce nesting level of subroutine call to no more than
two (a subroutine called from a normal or abnormal
program can call only one more level of subroutine).

111 Illegal value error.

Possible cause:
• illegal value detected when doing READ/WRITE or
SET.
Suggestions:
• contact Honeywell Technical Assistance Center.

112 FAIL statement was executed by the sequence.

Suggestions:
• restart.
• make necessary changes, then resume execution at
the next sequence statement.

113 I/O Link prefetch buffers full.

Possible cause:
• IOL prefetch buffers full (tried to fetch IOL parameters 8
times in a row, with preemption each time was
unsuccessful.)
Suggestions
• redistribute I/O Link fetches to another programming
cycle.
• insert WAITS to slow collection down.
• break into additional STEPS.

208 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 15 Process Module Data Point
15.8 Sequence Execution State

Execution State Description

114 I/O Link poststore buffers full.

Possible cause:
• IOL poststore buffers full (tried to fetch UCN
parameters 8 times in a row, with preemption each time
was unsuccessful.)
Suggestions
• redistribute I/O Link fetches to another programming
cycle.
• insert WAITS to slow collection down.
• break into additional STEPS.

115 UCN Link prefetch buffers full.

Possible cause:
• I/O prefetch buffers full (tried to fetch UCN parameters
16 times in a row, with preemption each time was
unsuccessful.)
Suggestions:
• redistribute I/O Link fetches to another programming
cycle.
• insert WAITS to slow collection down.
• break into additional STEPS.

116 UCN Link poststore buffers full.

Possible cause:
• I/O poststore buffers full (tried to fetch UCN parameters
16 times in a row, with preemption each time was
unsuccessful.)
Suggestions:
• redistribute I/O Link fetches to another programming
cycle.
• insert WAITS to slow collection down.
• break into additional STEPS.

117—164 Reserved

R688 HPM High-Performance Process Manager Control Theory 209

08/2019 Honeywell
15 Process Module Data Point
15.9 Sequence Overrides

Execution State Description

End Sequence execution has been completed as indicated by the execution of

an END statement. This state is entered at the completion of a normal
sequence or an abnormal condition handler (Hold, Shutdown, or Emergency
Shutdown) sequence.

15.9 Sequence Overrides

Operator displays
The process module operator displays allow you to perform phase, step, and statement
overrides when the sequence execution state is Fail, Error, or Pause.
Illegal access
Attempts to access the override function from anywhere other than a Universal or GUS
Station results in an error code of 107 (key-level error).
Restrictions
The overrides are not restricted by the value in CNTLOCK if the sequence execution
state is Fail or Error.
Types of overrides
• Phase Override, which:
− allows the user to skip execution of one phase after another, in forward or
reverse order.
− works only in the sequence for which it is invoked; it is implemented through
the OVERPHAS parameter.
• Step Override, which:
− allows the user to skip execution of one step after another, in forward or reverse
order.
− works only in the phase for which it is invoked; it is implemented through the
OVERSTEP parameter.
Statement Override, which:
• allows user at a Universal Station to skip execution of one statement after another, in
forward or reverse order.
• works only in the step for which it is invoked; it is implemented through the
OVERSTAT parameter.

210 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 15 Process Module Data Point
15.10 Sequence Alarms

15.10 Sequence Alarms

Generation
Sequence alarms are generated when:
• process-module operational state is changed to Hold (HOLD), Shutdown (SHDN),
or Emergency Shutdown (EMSD) as indicated by a change in the PROCMOD
parameter. The PROCMOD parameter—
− can be changed by entry into an abnormal condition handler or externally by
operator, AM, and so on.
− has a key level of Operator and can be written to from the LCN (by an operator,
a CL/AM program, and so on), or by a CL/HPM program.
• sequence execution state is changed to Fail, Error, or End as indicated by a change in
the SEQEXEC parameter. The SEQEXEC parameter—
− has a key level of View only.
− cannot be changed from the LCN or by a CL/HPM program.
• phase timer has elapsed as determined by the PHASETIM parameter
Priorities
The priority of the sequence alarm can be configured for each process module through
the SEQPR parameter. The entry for this parameter may be:

• Emergency • High

• Low • JnlPrint

• Printer • Journal

• NoAction

15.11 Sequence Messages

Status messages
Sequence-status messages are issued when:
• Process Module operational state is changed.
• Sequence-execution mode is changed.
• Sequence-execution state is changed.
• Sequence begins a new phase.
• A sequence message is issued.

R688 HPM High-Performance Process Manager Control Theory 211

08/2019 Honeywell
15 Process Module Data Point
15.11 Sequence Messages

Operator messages
Two types of programmed operator messages can be generated by a sequence program:
• Message with feedback—A SEND statement with the confirmation option (WAIT)
causes the sequence to be suspended until the message has been confirmed by the
user at the Universal Station.
• Message without feedback—This message is a 1-way communication from the
sequence to a destination, such as the Universal or GUS station.
These messages can be displayed at the Universal or GUS Station and/or logged on the
printer, depending on how the user codes the message statement.

TIP
It is good practice to confirm any outstanding messages after a sequence
failure before rerunning the sequence and before loading a new sequence.

212 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 15 Process Module Data Point
15.12 Restart Option

15.12 Restart Option

Function
The restart option determines how the sequence program is started following a warm
restart. A Warm restart is considered as being a transition from Idle to Run, or a short
power interruption that does not change the HPM database. The restart options are
include:
• Restart
• Off
Restart option
When the sequence-execution state is Run, the sequence program is started from the very
beginning; otherwise, the process module operational state is changed to Off and the
sequence-execution state is changed to Loaded (or Not Loaded if a sequence has not been
loaded). If an abnormal handler is executing when the warm start occurs, execution
begins from the beginning of the normal sequence and not from the abnormal handler. A
sequence-state change event is issued to report the transition from Hold, Shutdown, or
Emergency Shutdown to Normal.
Off
The process module operational state is changed to Off and the sequence-execution state
is changed to Loaded (or Not Loaded if a sequence has not been loaded).

15.13 Parameters
REFERENCE - INTERNAL
For a complete list of the parameters associated with the Process Module
Data Point, refer to the PM Family Parameter Reference Dictionary.

R688 HPM High-Performance Process Manager Control Theory 213

08/2019 Honeywell
15 Process Module Data Point
15.13 Parameters

214 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 16. Regulatory PV Point
16.1 Regulatory PV Point Background
Features
While standard I/O functions such as engineering unit conversion and alarming are
handled directly by the I/O Processors, Regulatory PV (RegPV) points provide an easy-
to-use configurable approach for implementing PV calculations and compensation
functions. PV processing provides a menu of selectable algorithms such as mass flow,
totalization, and variable dead-time compensation.
Algorithms
The Regulatory PV Point (RegPV) supports the following algorithms:
• Data Acquisition (DataAcq) PV Algorithm, (see Section 17)
• Flow Compensation (FlowComp) PV Algorithm, (see Section 18)
• Middle of Three (Mid0f3) PV Algorithm, (see Section 1)
• High Low Average (HiLoAvg) PV Algorithm, (see Section 1)
• Summer PV Algorithm, (see Section 21)
• Variable Dead Time with Lead Lag (VDTLDLag) PV Algorithm, (see Section 0)
• Totalizer (Totalizr) PV Algorithm, (see Section 0)
• General Linearization (GenLin) PV Algorithm, (see Section 1)
• Calculator (Calcultr) PV Algorithm, (see Section 0)

R688 HPM High-Performance Process Manager Control Theory 215

08/2019 Honeywell
16 Regulatory PV Point
16.1 Regulatory PV Point Background

Functional diagram
Figure 16-1 Regulatory PV Point Functional Diagram

PV (from data point

specified by
input connection)

PV INPUT
NOPINPTS PROCESSING

PV USER-SUPPLIED
PVALGID :
ALGORITHM VALUES FOR THE
CALCULATION :
PVINIT CONFIGURED
ALGORITHM
PVCALC
(in EU)

PVCLAMP Noclamp
PVEXEUHI PV FILTERING Clamp
PVEXEULO AND
RANGE CHECK PVEXHIFL
TF PVEXLOFL

PVAUTO

PNTFORM
Componnt
PVMan or PVSub Full
(from Operator or Program)
PVAUTO
PV

PVSOURCE

Man/Sub Auto Auto

PVEUHI PVP (PV in %)
Man/Sub NORMALIZATION
PVEULO LASTPV

PVEXEUHI RANGE PVEXHIFL

CHECKING
PVEXEULO PVEXLOFL

PV

EU
Half
A HIGHAL
One L
Two A
PVALDB R
Three
Four M
Five
D
PVHHTP E PVHHFL
T
PVHHPR E PVHIFL
: C :
PV ALARM : T : PV ALARM
TRIP POINTS : I : FLAGS
AND PRIORITIES : O :
PVROCPTP N PVROCNFL
PVROCPPR PVROCPFL

PTINAL

216 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 16 Regulatory PV Point
16.2 PV Input Connections

16.2 PV Input Connections

Purpose
PV input connections are used to specify the source(s) for the inputs to PV algorithms. A
maximum of six PV input connections can be configured for an algorithm, as required by
the individual PV algorithm. You may implement the input connections by using the
"Tagname.Parameter" format.
Using the Tagname.Parameter format
When using the "Tagname.Parameter" format, the user must enter the tag name of the
data point and the name of the parameter within that data point. The source parameter
must contain a real number, integer, or Boolean quantity. The values provided by the
input connection parameters are assigned to destination parameters within the RegPV
point by the PIDSTN parameter. The destination parameters for these sources default to
one for each input to the configured PV algorithm.
Relationship to algorithms
One input connection must be configured for each algorithm input, otherwise the point
cannot be made active.

16.3 PV Algorithm Calculation

The configured PV algorithm accepts the values received through the PV input
connections and produces the calculated PV value (PVCALC) plus its value status
(PVAUTOST).

R688 HPM High-Performance Process Manager Control Theory 217

08/2019 Honeywell
16 Regulatory PV Point
16.4 PV Range Check and Filtering

16.4 PV Range Check and Filtering

PV range
The PV range is configured in PVEULO and PVEUHI in a range from 0% to 100.0% of
the engineering-units range. This is usually the normal operating range for the PV but it
can extend into a configurable extended range, as defined by PVEXEULO and
PVEXEUHI. The extended range is forced to be equal to or greater than the range
defined by PVEULO and PVEUHI. PVCALC is generally constrained within
PVEXEULO and PVEXEUHI, but the checks and constraints depend on the PV source.
If PVSOURCE is:
• Auto, and if—
− PVAUTOST contains Bad, PVSTS is Bad and no PV-range checks are made.
− PVAUTO is outside the extended range and PV clamping (PVCLAMP) is not
configured, the PV becomes a bad value and PVSTS is Bad; however, if PV
clamping is configured, the PV becomes equal to the value of the violated range
and PVSTS becomes Uncertn. In either case, the appropriate PV-range violation
flag is set (PVEXLOFL or PVEXHIFL).
• Man—Any value from the Universal Station that is outside the extended range is not
accepted. PVSTS is already uncertain because the source is Man.
• contains Sub—If a program stores a PV value outside the extended range, the
appropriate PVEXLOFL or PVEXHIFL flag is set. PVSTS is already uncertain
because the source is Sub.
Output clamping
If clamping of the output is specified by the PVCLAMP parameter, PV filtering is
performed before the range check. If the value entered for PV filtering through the TF
parameter is other than the default value of 0.0, a single-lag filter is applied to the
PVCALC value to remove noise. If a filter value is not specified, PVAUTO contains the
same value as PVCALC.
Last good PV value
Data-point parameter LASTPV always holds the last good value of the PV.

218 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 16 Regulatory PV Point
16.5 PV Value Status

16.5 PV Value Status

The value in the PV value-status parameter, PVSTS, is determined as defined in the
following table.
Table 16-1 PV Value Status Definitions

PV Value Status Definition

Normal PVSOURCE = Auto, PVAUTOST = Normal, and the PV value is within

the range defined by PVEULO and PVEUHI

Uncertn One of the following is indicated:

• PVSOURCE = Man or Sub and the PV value does not equal NaN
(that is, is a valid, real number).
• PVSOURCE = Auto, and PVAUTOST = Uncertn. Note that
PVAUTOST contains Uncertn if at least one of the required algorithm
inputs is Uncertn and none of the required algorithm inputs is Bad.
• PVSOURCE = Auto and the value in PVAUTO is outside the
engineering-units range and is clamped.

Bad The PV value is NaN, resulting from one of the following conditions:
• PVSOURCE = Auto and PVAUTO = NaN.
• PVSOURCE = Auto, the value in PVAUTO is out-of-range, and has
not been clamped.
• PVSOURCE = Sub or Man and the PV is stored as NaN.

R688 HPM High-Performance Process Manager Control Theory 219

08/2019 Honeywell
16 Regulatory PV Point
16.6 PV Source Selection

16.6 PV Source Selection

Source
As illustrated in the Regulatory PV Point functional diagram figure, the source of the PV
may be:
• PV processing.
• an operator input.
• a user-written program.
It is specified by the PVSOURCE parameter, whose value can be changed by an
operator, a supervisor, an engineer, or a user-written program. The PVSOURCE
parameter is configurable only if Full has been entered for the PNTFORM parameter.
Valid PV source values
PVSOURCE can have one of the values:
• Auto—PV is received from PV processing through the PV filtering function. The
value is in PVAUTO and its status is contained in PVAUTOST. During normal
operation, the PV source is Auto, and the PV and its value status (PVSTS) become
equal to PVAUTO and PVAUTOST, respectively, before PV range checks are made.
When the PV source is changed from Auto to Man or Sub, the PV remains at the last
value until it is changed by the operator (Man) or a program (Sub), so it doesn't
"bump." In Man or Sub, the status in PVSTS is Uncertn. When the PV source is
changed from Man or Sub to Auto, the PV immediately goes to the PVAUTO value.
This might cause a bump in the value unless it is changed gradually to the value in
PVAUTO before changing the source.
• Man—The PV is entered by an operator, supervisor, or engineer at a Universal
Station.
• Sub—The PV is entered by a user-written program. A program can store a bad value
in PV, and if it does, PVSTS goes Bad.

TIP
You can prevent PV source changes by configuring OnlyAuto in PVSRCOPT.
This fixes the source as Auto and the parameter PVSOURCE is removed
from the point. Configuring All in PVSRCOPT allows normal PV source
selection.

220 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 16 Regulatory PV Point
16.7 PV Alarm Detection

16.7 PV Alarm Detection

Implementation
The PV alarming function can be implemented only when Full has been entered for the
PNTFORM parameter.
Alarms detected
The following types of alarms are detected during PV alarm processing:
• PV High/Low.
• PV High-High/Low-Low.
• PV Rate-of-Change Positive/Negative.
• PV Significant Change.
• BadPV.
• Deviation High (Note: Deviation High Alarm is applicable only to MidOf3 and
HiLoAvg algorithm types).
Effect on alarm processing
PV source selection has no effect on alarm processing.

R688 HPM High-Performance Process Manager Control Theory 221

08/2019 Honeywell
16 Regulatory PV Point
16.8 Deviation High alarm

16.8 Deviation High alarm

Applicability
With TPN R683 the deviation high alarm has been introduced for HPM Regulatory PV
points using Midof3 and HiLoAvg algorithms. Selective cutout, re-alarm and alarm delay
options are applicable for the deviation high alarm.
Configuration
The deviation high alarm for Midof3 and HiLoAvg is disabled by default. The trip point
for deviation high alarm can be entered in the DEVHITP parameter. If the absolute
difference between any two inputs exceeds the set deviation trip point value a deviation
high alarm is generated. Inputs which are active and whose status is ‘Normal’ or
‘Uncertain’ are considered for deviation alarming. Deviation high alarm can be enabled
and priority can be set by using the DEVHIPR parameter.Thereby, the alarm can be
viewed on the Alarm Summary or Event History. The DEVHIFL parameter is used as a
flag to detect the generated alarm.
The deviation alarm is generated even if any of the inputs are force-selected.The alarm
returns to normal when the deviation is less than the configured trip point minus a
deadband equal to 10% of the trip point value.

222 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 17. Data Acquisition PV Algorithm
17.1 Functional Overview
Family
The Data Acquisition (DATAACQ) algorithm is a member of the Regulatory PV
algorithms.
Description
This algorithm normally accepts the input and places it, unchanged, in PVCALC (see the
following figure. All of the other PV algorithms alter the input(s) in some way.
Figure 17-1 Data Acquisition PV Algorithm Functional Diagram

Measured
Process
or (Data
Value from P1 DATAC PVCAL
Parameter)
Another
Data

Inputs and outputs

The input to this algorithm and its output are in engineering units.
Use
The most common use of this algorithm is to provide a PV that has been through PV
Input Processing, PV Algorithm Processing, PV Filtering, and PV Source Selection (see
the previous figure). The value in PVCALC is filtered, and becomes PV, if the PV source
is Auto.
The input can be a measured process-variable, or the calculated PV or calculated output
of another data point.

17.2 Equations
Background
This algorithm has one equation form.

R688 HPM High-Performance Process Manager Control Theory 223

08/2019 Honeywell
17 Data Acquisition PV Algorithm
17.2 Equations

Equation legend
In the Data Acquisition equation:
• P1 contains the first input value.
• PVCALC contains the value that becomes the PV when PVSOURCE = Auto.
Equations
The operation is simply the replacement of the data point's calculated PV (PVCALC)
with the value of the input:
PVCALC = P1

224 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 18. Flow Compensation PV Algorithm
18.1 Functional Overview
Family
The Flow Compensation ( FLOWCOMP) algorithm is a member of the Regulatory PV
algorithms.
Description
This algorithm compensates a flow measurement for variations in temperature, absolute
pressure, specific gravity, or molecular weight. The measured flow can be that of a gas, a
vapor, or a liquid. An extended equation is provided for industrial steam-flow
compensation, which includes factors that compensate for steam quality and
compressibility.
Figure 18-1 Flow Compensation PV Algorithms

Flow Input
P
G
COMPTERM (Data Point
T FLOWCOMP PVCALC
Inputs Parameter)
Q
X

Simplified Equation

PVCALC = F * COMPTERM

Where F is uncompensated flow and

COMPTERM has five forms

A: Liquids
B: Gasses, Vapors
C: Gasses, Vapors (Specific Gravity)
D: Volumetric Flow of Gasses and Vapors
E: Steam

Use
The uncompensated-flow input is typically a square-rooted, differential pressure
measurement. Other direct-flow measurements can also be used. The square root should

R688 HPM High-Performance Process Manager Control Theory 225

08/2019 Honeywell
18 Flow Compensation PV Algorithm
18.2 Options and Special Features

be extracted before the input to the data point, and the input value must be in engineering
units. For process-connected inputs, the square root can be extracted in the IOP;
conversion to EUs also takes place in the IOP.
The compensation is calculated from temperature, pressure, specific gravity, molecular
weight, steam quality, or steam compressibility. Choice of inputs depends on the type of
the equation selected. All of these inputs are obtained through PV input-connections.

18.2 Options and Special Features

Forms of flow compensation
The parameter PVEQN specifies one of five different equations for this algorithm. Each
of these equations represents a different form of flow compensation by calculating the
compensation term (COMPTERM) differently (see “Equations” in Section 18 for the
actual equations).
Table 18-1 Flow Compensation Forms

Equation Form of Flow Compensation

A Primarily used for mass-flow or volumetric-flow compensation for liquids. Actual

(measured or calculated) specific gravity is used as a compensation input.

B Primarily used for mass-flow compensation of gas or vapor flows. Actual absolute
temperature and pressure are used as compensation inputs.

C Used for mass-flow compensation of gas or vapor flows. Actual specific gravity
(measured or calculated), absolute temperature, and pressure are used as
compensation inputs.

D Principally used for volumetric-flow compensation for gas or vapor flows. Actual
temperature, pressure, and molecular weight are used as compensation inputs.
The molecular weight can be calculated by the Calculator algorithm, or a user
written program in the AM or Computing Module (CM50/CM60).

E Used for mass-flow compensation of steam flows in industrial applications. Actual

temperature, pressure, specific gravity, steam compressibility, and steam quality
are used as compensation inputs. This equation can also be used for "custody
transfer" of gases or liquids.

Restart or point activation

On a cold or warm restart, or when this data point is activated, PVCALC is recalculated
the next time the FLOWCOMP data point is processed.

226 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 18 Flow Compensation PV Algorithm
18.3 Equations

Error handling
If the status of any of the input values is bad, PVCALC contains NaN and the
PVAUTOST becomes Bad. If there are no bad inputs but the status of one or more of the
inputs is "uncertain," the PVAUTOST becomes Uncertn.
Zero pressure reference
Parameter P0 compensates for ambient atmospheric pressure. Most pressure sensors
measure pressure relative to the atmospheric pressure. If the pressure measurement is
actually absolute, P0 must be set to a value of zero. The usual zero reference is a value
for sea level. If the pressure sensor is at a significantly different elevation than sea level,
P0 should be set to a more appropriate value. For example, Denver, Colorado has an
average atmospheric pressure of about 12.2 psia. Standard sea-level atmospheric pressure
is 14.696 psia. P0 contains the absolute value of ambient atmospheric pressure.
Units of measure
The absolute value of either U.S. Customary Units or SI (metric) units can be used. All
inputs and parameters must be in engineering units of one system or the other. The
typical value for P0 (see “Equations” in Section 18 for definition of this parameter) in
U.S. Customary Units is 14.696 psia and in SI units it is 101.325 kPa. The typical T0
value is 459.69°F in U.S. Customary Units and 273.15°C in SI units.
Compensation term value
Typically, the COMPTERM value is near 1. It should never be zero or negative. The
COMPLO and COMPHI limits are used to prevent unrealistic values of COMPTERM
caused by incorrect inputs. Should the calculated value of COMPTERM go beyond one
of these limits, the value is held (clamped) at that limit. You should estimate the range of
COMPTERM by considering the most extreme input-conditions you expect. Also, you
should set the PV range for this data point, by considering the largest compensated-flow
value expected.
Custody transfer
Equation E can be used for "custody transfer" of gases or liquids. To do so, set parameter
RX equal to one and specify the input connection to X to come from RX in this data
point.

18.3 Equations
Background
You configure PVEQN for data point that uses the Flow Compensation algorithm to
specify one of five equations. The equations select the compensation term. The basic
equation is:

R688 HPM High-Performance Process Manager Control Theory 227

08/2019 Honeywell
18 Flow Compensation PV Algorithm
18.3 Equations

PVCALC = C * * F * COMPTERM

Equation legend
For the basic equation:
• PVCALC =The output of this algorithm. It is selected as the PV for this data point
when the PVSOURCE is Auto.
• C =Scale factor. The default value is 1.0.
• C1, C2 =Constants for correcting for assumed design conditions. Default value for
each is 1.0.
• F =The uncompensated flow input. A square-rooted, differential pressure input.
• COMPTERM =The compensation term. This term differs in each of the five flow-
compensation equations, A through E. Its value lies between the COMPLO and
COMPHI limits, which are specified by the process engineer. If either limit parameter
contains NaN, the corresponding limit check is not made.

228 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 18 Flow Compensation PV Algorithm
18.3 Equations

For the COMPTERM equations (A through E):

• the following (in engineering units) are received through input connections—
− G = Measured or calculated specific gravity or molecular weight.
− P = Measured actual gage pressure.
− T = Measured actual temperature.
− X = Measured actual steam compressibility.
− Q = Measured actual steam-quality factor.
• the following parameters are specified by the process engineer—
− RG = Design specific gravity or reference molecular weight, in the same
engineering units as G (Default value = 1.0).
− RP = Design pressure, converted to an absolute value (Default value = 1.0).
− RQ = Design steam quality factor, in the same units as Q (Default value =1.0)
− RT = Design temperature, converted to an absolute value (Default value = 1.0).
− P0 = Factor to convert gauge pressure to an absolute value. Typically 14.696
psia or 101.325 kPa. Enter the absolute value of the number. Default value = 0.
If the measured pressure is already an absolute value, enter 0.
− T0 = Factor to convert Celsius and Fahrenheit temperatures to an absolute value.
Typically 459.69°F or 273.15°C (use the absolute value of the number when
entering a value in T0). Default value = 0. If the measured temperature is
already an absolute value, enter 0.
− RX = Reference steam compressibility, in the same engineering units as X.
Default value = 1.0.

R688 HPM High-Performance Process Manager Control Theory 229

08/2019 Honeywell
18 Flow Compensation PV Algorithm
18.3 Equations

Equations

ATTENTION
These equations are performed using absolute values for pressure and
temperature. You must convert temperatures and pressures to absolute
values in order to use this algorithm.

Five forms of COMPTERM may be calculated using Equations A through E. Each are
defined in the following table.
The COMPTERM computation depends on the value of the PVCHAR parameter. If
PVCHAR = SqrRoot, then COMPTERM is as shown. If PVCHAR = Linear, then
COMPTERM is determined without the square root function.
Table 18-2 Flow Compensation PV Algorithm Equations

Equation Definition

A
(Liquids)

B
(Gases & Vapors)

C
(Gases & Vapors w/specific
Gravity)

D
(Volume Flow of Gases &
Vapors)

E
Steam

230 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 18 Flow Compensation PV Algorithm
18.3 Equations

Compensating for assumed design conditions

Equation A can be used for either mass or volumetric compensation of liquid flows. The
use depends on whether the measurement of uncompensated flow is a mass measurement
or a volumetric measurement, and on the desired uncompensated-flow units. Here are
three ways to use Equation A:
• Converting an uncompensated mass-flow to compensated mass-flow—
− C1 and C2 are configured as 1.0.
• Converting an uncompensated, standard volumetric-flow to compensated mass-
flow—
− C1 is configured to equal the design density, referenced to standard conditions.
− C2 is configured as 1.0.
• Converting uncompensated, standard volumetric-flow to compensated, standard
volumetric-flow.

ATTENTION
When using Equation A to Convert uncompensated, standard volumetric-flow
to compensated, standard volumetric-flow, if the variations in standard
density caused by fluid-composition changes are significant, C2 is
manipulated as:
• If the measured value of specific gravity at flow conditions is available,
the actual specific gravity, referred to standard conditions, is calculated
from that measurement by another data point and input to C2 through a
general input connection.
• If actual specific gravity is measured by a lab, a numeric data-point could
be used to hold the value and input to C1 through a general input
connection.
For the latter case, another data point uses the lab value to calculate specific
gravity at flow conditions and the result is input G.

R688 HPM High-Performance Process Manager Control Theory 231

08/2019 Honeywell
18 Flow Compensation PV Algorithm
18.3 Equations

232 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 19. Middle of Three PV Algorithm
19.1 Functional Overview
Family
The Middle of Three PV algorithm is a member of the Regulatory PV algorithms.
Description
This algorithm provides a calculated PV (PVCALC) that is normally the middle value of
three values from the PV input connections. PVAUTOST is Bad, only if all three inputs
to this algorithm are bad. If at least one input is valid (normal or uncertain), the algorithm
provides a valid value in PVCALC.
When configured with only two inputs, this algorithm serves as a high/low selector or
input averaging block. These functions are selected by choosing the corresponding
control equation (A, B or C as shown below).
If only one valid input value is available, it is selected. If only two valid input values are
available, the selected value can be the highest or the lowest, or the average of the two, as
specified when you select the equation to be used by this algorithm.

R688 HPM High-Performance Process Manager Control Theory 233

08/2019 Honeywell
19 Middle of Three PV Algorithm
19.1 Functional Overview

Figure 19-1 Middle of Three PV Algorithm Functional Diagram

P1
PVCALC
P2 MIDOF3 (Data Point
Parameter)
SELINP
P3

Normal Operation: PVCALC = Middle value for three input values.

WIth only two valid inputs:

Equation A: PVCALC = Highest of the two inputs

Equation B: PVCALC = Lowest of the two inputs

Equation C: PVCALC = Average of the two inputs

WIth only one valid input: PVCALC = Value of the input

SELINP = The selected input, Select P1 through Select P3, except with only
two valid inputs and Equation C, SELINP contains None.

With TPN R683 a deviation high alarm has been introduced for MidOf3 algorithms.
When the absolute difference between any two inputs exceeds the set deviation trip point
value a deviation high alarm is generated.
Use
This algorithm is used to provide a reasonably secure PVCALC when inputs are
available from three redundant inputs, one or more of which may occasionally fail or
provide erratic values. The Low Selector, High Selector, Average PV algorithm provides
a somewhat similar function with up-to-six input connections.

234 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 19 Middle of Three PV Algorithm
19.2 Options and Special Features

19.2 Options and Special Features

Normal Operation with three valid inputs
Normal operation occurs if there are no inputs with a bad-value status. Inputs are treated
as valid if their value status is either normal or uncertain.
If no two inputs have equal values:
• PVCALC = the middle value of the three inputs, P1, P2 and P3.
• SELINP = the selected input, SelectP1 through SelectP3.
If there are two inputs with equal values or if all three input values are equal:
• PVCALC = the value for which there is at least one other equal.
• SELINP = the lowest-number input with and equal value, SelectP1 through
SelectP3.
Error handling
PVAUTOST becomes Uncertn only when the selected input is uncertain, or for equation
C, when one of the inputs used for averaging is uncertain.
The PVAUTO status is bad and PVCALC becomes NaN when the status of all three
inputs is bad.

19.3 Equations
Background
If three valid inputs are present, the equations have no meaning and the algorithm
functions normally, as described in Normal Operation with three valid inputs. The
equations specify what the algorithm is to do if one or more inputs have a bad-value
status.

R688 HPM High-Performance Process Manager Control Theory 235

08/2019 Honeywell
19 Middle of Three PV Algorithm
19.3 Equations

Equation legend
The following legend applies to all Middle of Three PV algorithms:

PVCALC = The output of this algorithm. It is selected as the PV for the data
point when the PVSOURCE is Auto.

P1, P2, and P3 The input values. The default value is NaN.

SELINP = The selected input, SelectP1 through SelectP3. If no input is

selected or if PVCALC contains an average value, SELINP contains
None.

Equations
The equations function as follows:

Input Status Equation Function

One (1) Bad A • PVCALC = Highest of the two input values

• SELINP = The selected input, SelectP1 through SelectP3

B • PVCALC = Lowest of the two input values

• SELINP = The selected input, SelectP1 through SelectP3

C • PVCALC = The average of the two input values

• SELINP = None

Two (2) Bad A, B, C • PVCALC = the value of the valid input

• SELINP = The selected input, SelectP1 through SelectP3

Three (3) Bad A, B, C • PVCALC = NaN

• SELINP = None

236 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 20. High Low Average PV Algorithm
20.1 Functional Overview
Family
The High Selector, Low Selector, Average (HILOAVG) PV algorithm is a member of the
Regulatory PV algorithms.
Description
This algorithm does one of the following:
• Selects the input with the highest value.
• Selects the input with the lowest value.
• Calculates the average value of all valid inputs.
As illustrated in the following figure, the HILOAVG PV algorithm can accept up-to-six
inputs. Valid inputs are those with a status that is "Normal" or "Uncertain." When the
input selection functions are used, the number of the input that is selected is contained in
a accessible parameter (SELINP).

R688 HPM High-Performance Process Manager Control Theory 237

08/2019 Honeywell
20 High Low Average PV Algorithm
20.1 Functional Overview

Figure 20-1 High, Low, Average PV Algorithm Functional Diagram

Example: P1
P2 EQUATION A PVCALC
Temperature P3 HILOAVG (Data Point
Inputs from P4 (HI) Parameters)
Six Points in P5
SELINP
a Boiler P6

Which is the
hottest s pot
PVCALC = Highest of the Input Values
in the boiler?

P1
P2 PVCALC
EQUATION B (Data Point
P3
HILOAVG Parameters)
P4
(LO)
P5 SELINP
P6

PVCALC = Lowest of the Input Values

P1
P2
P3 EQUATION C (Data Point
P4 HILOAVG PVCALC Parameters)
P5 (Avg.)
P6

PVCALC = Average of All Valid Input Values

PVCALC = P1 . . . . . + PN,
N

Where N = the number of configured inputs

238 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 20 High Low Average PV Algorithm
20.2 Options and Special Features

With TPN R683 a deviation high alarm has been introduced for HiLoAvg algorithms.
When the absolute difference between any two inputs exceeds the set deviation trip point
value a deviation high alarm is generated.
Use
One example of the use of this algorithm is shown at the top of the preceding figure. In
this example, the high value-selector version of the algorithm is used to detect hot spots
in a boiler or a reactor.
Either the high value-selector version or the low value-selector version can be used to
detect production bottlenecks. For example, this algorithm might be used to notify the
process operator that production is currently constrained by the speed of a gas
compressor. One of the selector options might also be used to select the "safest" PV for
control.
One use of the averaging option is in balancing furnace passes. In this application, the
algorithm calculates the average of the outlet temperatures of the passes.

20.2 Options and Special Features

Forced selection
The data point can be configured to allow the Universal Station operator, a user-written
program, or a general-input connection to force selection of one of the inputs. If the
FRCPERM parameter is configured as:
• On, the forced-selection function is enabled and an operator or a user-written
program can force the selection.
• Off, the forced-selection function is disabled.
The FSELIN parameter specifies the input to be selected, when selection is forced
(SelectP1 through SelectP6).
Error handling
Except when forced selection is in effect (Forced Selection), inputs with a bad status are
ignored and they do not make the PVAUTOST is Bad. For example, if the algorithm is
configured as a 4-input high-selector and one of the inputs goes bad, the algorithm
functions as a 3-input high-selector.
If the number of valid inputs (PVSTS is Normal or Uncertn) is less than the minimum
number specified in parameter NMIN, PVCALC becomes NaN and the PVAUTOST is
bad.

R688 HPM High-Performance Process Manager Control Theory 239

08/2019 Honeywell
20 High Low Average PV Algorithm
20.3 Equations

PVAUTOST is changed to Uncertn under any of the following conditions:

• An input selection is forced and the status of that input is not bad (is normal or
uncertain).
• Forced selection is not in effect, at least as many inputs as specified by NMIN are
normal or uncertain, and the status of the selected one (Equation A or B) is uncertain.
• Equation C (averaging) is chosen, at least as many inputs as specified by NMIN are
not bad (normal or uncertain), and the status of any of them is uncertain.
PVCALC becomes NaN and PVAUTOST becomes Bad under either of the following
conditions:
• The selection of an input is forced and the status of that input is bad.
• Forced selection is not in effect, and there are fewer inputs with a status other than
bad than are specified by NMIN.
Restart or point activation
On a cold or warm restart, or when this data point is activated, PVCALC is simply
recalculated the next time this data point is processed.

20.3 Equations
Background
The High. Low, Average PV algorithm includes three equations options:
• Equation A, which selects the highest input value.
• Equation B, which selects the lowest input value.
• Equation C, which calculates the average of all valid inputs.

240 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 20 High Low Average PV Algorithm
20.3 Equations

Equations
Equation A—High Selector:
• If FRCPERM and FORCE are both On, then
− PVCALC = the value of the input indicated by FSELIN
− SELINP = FSELIN
• If either FRCPERM or FORCE is Off, then
− PVCALC = the highest valid input
− SELINP = the selected input, SelectP1 through SelectP8
Equation B—Low Selector:
• If FRCPERM and FORCE are both On, then
− PVCALC = the value of the input indicated by FSELIN
− SELINP = FSELIN
• If either FRCPERM or FORCE is Off, then
− PVCALC = the lowest valid input
− SELINP = the selected input, SelectP1 through SelectP8
Equation C—Average:
• If FRCPERM and FORCE are both On, then
− PVCALC = the value of the input indicated by FSELIN
− SELINP = FSELIN
• If either FRCPERM or FORCE is Off, then
− PVCALC = (Sum of the valid inputs)/N
− SELINP = None

R688 HPM High-Performance Process Manager Control Theory 241

08/2019 Honeywell
20 High Low Average PV Algorithm
20.3 Equations

242 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 21. Summer PV Algorithm
21.1 Functional Overview
Family
The Summer PV algorithm is a member of the Regulatory PV algorithms.
Description
This algorithm calculates a PV (PVCALC) that is the sum of up-to-six input values. The
input values can be scaled, the combined inputs can be scaled and a bias value can be
added to the result.
Figure 21-1 Summer PV Algorithm Functional Diagram

P1
P2
P3 (Data Point
P4 SUMMER PVCALC
Parameters)
P5
P6

EQUATION B, simplified:

PVCALC = P1 + P2 + . . . + P6

Use
A typical use is the calculation of the rate at which a component of a raw product is
entering a process unit, which is found by summing the proportion of the component in
each of several input streams and multiplying by the stream flow rates. This algorithm
can also be used to calculate a net heat loss by finding the difference between the heat
inputs and heat outputs (the difference can be obtained by using a negative scale factor,
for example, –1.0).
Other possible uses are mass-balance, heat-balance, and inventory calculations.
This equation can be used to scale and bias a single variable using Equation A.

R688 HPM High-Performance Process Manager Control Theory 243

08/2019 Honeywell
21 Summer PV Algorithm
21.2 Options and Special Features

21.2 Options and Special Features

Ensuring adequate PV range
Because the input values can be either positive or negative, as can the scale factors and
bias values, the results in PVCALC can have a broad range of values. You should
evaluate the worst-case values you expect to be in use, to establish the PV range. When
you configure the data point, be sure to specify a PV range adequate to cover all expected
values.
Error handling
If there are no inputs with a bad status and the status of at least one input is uncertain,
PVAUTOST is Uncertain.
If the status of at least one input is bad, the PVAUTOST becomes Bad and PVCALC
contains NaN.
Restart or point activation
On any type of restart or when this data point is activated, PVCALC is normally
calculated.

244 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 21 Summer PV Algorithm
21.3 Equations

21.3 Equations
Background
You can select one of two equations when you configure a data point that uses the
Summer PV algorithm:
Equation legend
For both equations:
• PVCALC = The output of this algorithm. It is selected as the PV for this data point
when the PV source is AUTOmatic.
• C = The overall scale factor. Default = 1.0.
• C1 through Cn = The scale factors for P1 through Pn. Default = 1.0.
• P1 through Pn = The PV input values. Equation B is limited to six inputs. Default for
all values is NaN.
• D = The overall bias. Default = 0.
• n = The number of PV inputs used. Default = 2.
Equations
Equation Definition

A PVCALC = C * P1 + D

B PVCALC = C * ((C1 * P1) + (C2 * P2) + . . . + (Cn * Pn)) + D

R688 HPM High-Performance Process Manager Control Theory 245

08/2019 Honeywell
21 Summer PV Algorithm
21.3 Equations

246 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 22. Variable Dead Time PV Algorithm
22.1 Functional Overview
Family
The Variable Dead Time with Lead-Lag Compensation PV algorithm is a member of the
Regulatory PV algorithms.
Description
This algorithm provides a calculated PV (PVCALC) in which value changes may be
delayed from the time that the corresponding change occurred in the P1 input. Dynamic
lead-lag compensation to the PV can also be provided. Lag compensation is available in
combination with the delay or with no delay. The delay time can be fixed or can be
varied as the value of an input varies.
Figure 22-1 Variable Dead Time PV Algorithm Functional Diagram

Process Input P1

(Data Point
VDTLL PVCALC Parameters)

Variable Dead
Time Input P2

Equation A: One Lead and Two Lag Compensations

Equation B: Fixed Dead Time

Equation C: Variable Dead Time

Equation D: Variable Dead Time with Two Lag Compensations

R688 HPM High-Performance Process Manager Control Theory 247

08/2019 Honeywell
22 Variable Dead Time PV Algorithm
22.2 Options and Special Features

Use
This algorithm is used for feedforward control and in process simulations. It may be used
as the PV algorithm in a data point that uses the PID Feedforward control algorithm.
In a typical feedforward application, the PV provided by this algorithm serves as the
feedforward PV. An operator can "cut out" this feedforward component by switching the
PVSOURCE to Man.

22.2 Options and Special Features

Combinations of delay and lead-lag compensation
You select the combinations of delay, lead compensation, and lag compensation by
selecting Equation A, Equation B, Equation C, or Equation D when configuring the data
point. The equations function as follows:

Equation Definition

A A change in the input value (P1) is subjected to one lead compensation

(Lead-Lag) and two lag compensations. If you specify a time constant of zero in the
Lead Compensation time constant, TLD, Lag Compensation time
constants, TLG1, or TLG2, the corresponding lead or lag compensation
is suppressed. If you don't suppress the lead compensation, you must
use at least one lag compensation.

B A change in the input value (P1) is delayed by a user-specified time.

(Fixed Dead Time) This data point must be made inactive in order to change the dead-time
value (TD).

C A change in the input value (P1) is delayed by a time period the duration
(Variable Dead Time) of which varies as the inverse of P2-input value variations. The variable
time period is determined by P2, the C1 and C2 scale factors, and bias
values D1 and D2. The delay (or dead time) typically represents a delay
in the process that depends on some variable in the process, such as
flow, feed rate, or a conveyer-belt speed.

D A change in the input value (P1) is delayed as with Equation C and then
Variable Dead Time receives lag compensation as specified by one or two time constants
(w/Two Lags (TLG1, TLG2). This equation is useful for simulating a portion of a
process that can be represented by a dead time and one or two lags.
The cutoff feature applies as for Equation C.

248 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 22 Variable Dead Time PV Algorithm
22.2 Options and Special Features

TIP
Equations C and D have a cutoff feature that can simulate situations like a
conveyer belt stopping. If the flow or speed value, represented by the P2
input, drops below a limit that you configure in the CUTOFFLM parameter,
the value of the delayed P1 signal (DP1) goes to zero. (DP1 is not an
external parameter.) When P2 again exceeds the CUTOFFLM value, DP1
resumes as a normal, delayed output. If you don't want this feature,
configure CUTOFFLM as NaN. Note that DP1 is subject to scale factor C
and bias value D.
Equation C can be used to produce a fixed delay time that can be changed
while the data point is active.

Calculating dead-time
The delay (dead-time)) of the input values is accomplished by a process that has the
effect of shifting the values through a table in the HPM's memory. Values are shifted
from one location in the table to the next, at intervals calculated to provide the desired
delay.
Figure 22-2 Variable Dead-Time Functional Diagram

Updated each time the

point is processed.

From the process or

another data point P1
New table input at each
NRATE*TS interval

Delay Table Updated at each

NRATE*TS interval.

Interpolator DP1

Maximum of 30 locations Delayed P1 Output

New interpolated value

each time the data point
is processed (at each
TS interval)

R688 HPM High-Performance Process Manager Control Theory 249

08/2019 Honeywell
22 Variable Dead Time PV Algorithm
22.2 Options and Special Features

For an example of the delay-table operation, suppose that the P1-input value has been
constant at 5.0 units for an hour. Assume that the specified delay time, TD, is 15 minutes
and that the data point is processed every second; Time Sample (TS = 1/60) min. as
determined by the SCANRATE parameter. At this time, the output of the interpolator is
5.0 units, all of the locations in the table contain a value of 5.0 units, and P1 contains a
value of 5.0 units.
Now suppose that the input to P1 suddenly changes to 6.0 units. The interval at which
new values are shifted through the table and the number of table locations in use have
been set up so that it takes 15 minutes for the new value of 6.0 units to appear at the
output of the interpolator.
Changing dead-time parameters
Variable delay-time (dead-time) parameters C1, C2, D1, and D2 in Equations C and D
can be changed at a Universal Station while the data point is active. Note that the D1
value allows a supervisor or engineer to add a fixed delay time to the total variable delay
time.
The C1 and C2 parameters are used to specify the time scale of the P2 value. D1 can be
used to offset that scale. Note that the P2 value is inversely proportional to the variable
time delay. Where P2 represents a flow rate or speed, when the flow or speed decreases,
the time delay increases to simulate the effect of the reduced flow or speed.
Restrictions on dead-time
The minimum fixed delay-time (dead-time, Equation B) is equal to TS, the processing
interval in minutes. Delay values greater than 32,000*TS are rejected.
For Equations C and D the minimum step-change in the TD value is equal to NLOC*TS.
This is also the value of the smallest dead time (delay time). If the TDNEW value is less
than zero, it is clamped to zero. Also, if TDNEW exceeds 32,000*TS, it is clamped to
32,000*TS.
Time-Constant recommendations
We recommend that the processing rate of a data point that uses this algorithm and
Equation A or D must be at least ten times greater than the lead or lag break-point
frequencies, so, divided by lead break-point frequency) be less than or equal to 10, so,
• TLG1 should be equal to or greater than 2 * TS.
• TLG2 should be equal to or greater than 2 * TS.
• |TLD| should be equal to or greater than 10 * TS.
Both positive and negative lead times can be specified, so it is the absolute value of TLD
that must be equal to or greater than 10 * TS.

250 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 22 Variable Dead Time PV Algorithm
22.2 Options and Special Features

We recommend that the rate amplitude (lag break-point frequency divided by the lead
break-point frequency) be less than or equal to 10 so, |TLD| should be equal to or less
than 10 * TLG1.

Using Equation C or D for a fixed dead-time

You can use these variable delay-time (dead-time) equations to attain a fixed delay time
by setting the value of C1 to 0 and adjusting the value of D1 to get the desired delay
value. This permits changes of delay time from a Universal Station while the data point is
active, but the resolution may be much less than using a fixed delay time (Equation B),
where the delay can be changed only by making the point inactive and then active again.
Restart or point activation
On a cold start, a warm start, and when the data point is activated, the lead-lag dynamics
are set to the steady state, and all values in the delay table are set to the current value of
the P1 input. PVCALC is calculated as follows:
PVCALC = C * P1 + D

Error handling
For Equations C and D, if neither input has a bad-value status, but one or both has an
uncertain-value status, PVAUTOST is Uncertn. Equations A and B don't use the P2
input, so for them, PVAUTOST is Uncertn only if the P1-value status (P1STS) is
Uncertn.
For Equations C and D, if either input has a bad-value status, PVCALC becomes NaN
and the PVAUTOST is Bad. For Equations A and B, when P1STS is Bad, it causes
PVCALC to contain NaN and the PVAUTOST to be Bad.
When the input-value status is again normal or uncertain, the data point is initialized as
for a cold start in Restart or point activation and the PVAUTO-value status becomes
normal, or uncertain, as appropriate.

R688 HPM High-Performance Process Manager Control Theory 251

08/2019 Honeywell
22 Variable Dead Time PV Algorithm
22.3 Equations

22.3 Equations
Background
You can select one of four equations when you configure a data point that uses the
Variable Dead Time with Lead-Lag Compensation PV algorithm:
Equation legend
For all equations:
• PVCALC = The output of this algorithm. It is selected as the PV for this data point
when the PV source is AUTOmatic.
• C = The overall scale factor. Default value = 1.0.
• C1 = Scale factor, TDNEW denominator. Default value = 1.0.
• C2 = Scale factor for P2. Default value = 1.0.
• CUTOFFLM = Cutoff (zero-flow or zero-belt speed) limit. Default = 0.0.
• D = Overall bias. Default value = 0.
• DP1 = The delayed P1 value. Not accessible to Universal Stations nor to user-written
programs.
• D1 = Bias value for the variable delay time. Default value = 0.
• D2 = Bias for P2. Default value = 0.
• P1 = The input value to which the delay and lead-lag compensation are applied.
• P2 = The input value that changes the variable delay when Equation C or Equation D
is used.
• s = The Laplace operator (notation only, not a parameter).
• t = The present time (notation only, not a parameter),
• t-TD = The present time minus the actual dead (delay) time (notation only, not a
parameter).
• TD = The fixed time delay in minutes for Equation B. The actual variable delay time
in minutes for Equations C and D. Default = 0.
• TDNEW = The calculated new (ideal) delay time in minutes for Equations C and D.
• TLD = Lead-compensation time constant in minutes. 0 = no lead. Default = 0.
• TLG1 = Lag-compensation time constant 1 in minutes. 0 = no lag. Default = 0.
• TLG2 = Lag-compensation time constant 2 in minutes. 0 = no lag. Default = 0.
Equations
Table 22-1 Variable Dead-Time PV Algorithm Equations

252 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 22 Variable Dead Time PV Algorithm
22.3 Equations

Equation Definition

A Lead Compensation with Two Lag Compensations.

B Fixed Delay Time.

C Variable Delay Time—if CUTOFFLM does not contain NaN and if P2 is less than
CUTOFFLM, DP1 = 0; otherwise, calculate DP1 using:

D Variable Delay Time with Two Lag Compensations.

R688 HPM High-Performance Process Manager Control Theory 253

08/2019 Honeywell
22 Variable Dead Time PV Algorithm
22.3 Equations

254 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 23. Totalizer PV Algorithm
23.1 Functional Overview
Family
The Totalizer (TOTALZR) PV algorithm is a member of the Regulatory PV algorithms.
Description
This algorithm provides a time-scaled accumulation of an input value. The input value is
typically a flow measurement. Either analog or pulse input can be selected through
parameter ACCTYPE. The time-base can be seconds, minutes, or hours.
Figure 23-1 Totalizer PV Algorithm Functional Diagram

S ta rt
O per ator or u ser- S to p
Rese t Time -scale d
written p rog ram TO TAL IZR P VCA LC
TIMEB A SE accu mula ti on
Tar get Va lue

A nal og (HL AI)

Tar get-va lue
P1
flag s
A CCTYP E
P2

PV AV

P ulse IOP

The accumulation can be started, stopped, and reset by commands from a Universal
Station operator or from a user-written program. An operator or user-written program can
establish a target value for the accumulation. Status indicators are available to indicate
that the accumulation is near the target value, nearer to the target value, and is complete
(has reached or exceeded the target value).

R688 HPM High-Performance Process Manager Control Theory 255

08/2019 Honeywell
23 Totalizer PV Algorithm
23.1 Functional Overview

For situations where the flow transmitter may not be precisely calibrated near the zero-
flow value, a zero-flow cutoff feature is provided that avoids accumulating negative flow
values. When the flow is below a user-specified cutoff value, the input value is clamped
to zero.
Use
The Totalizer PV algorithm accumulates periodic measurements over time. It is
principally used to accumulate total flows, or in applications such as the measurement of
ingredients that are blended. The accumulated value can be used for control or just as
process history.
An example of TOTALIZER's use in control is determining how full a tank is, so that the
flow into the tank can be shut off before it overflows. In such an application, the P1 input
to TOTALIZR would be the PV of PID-flow controller.
Typical operation
The events in an operation that uses TOTALIZR might be as follows (see Error!
Reference source not found.)
• The target value, which represents the desired total volume, is specified to the
AVTV (displayed as the setpoint) parameter in the TOTALIZR point, by an operator
at a Universal Station or by a user-written program.
• An operator or a user-written program issues a Reset command (using the
COMMAND parameter) to the TOTALIZR point. This sets any accumulation value
equal to RESETVAL.
• A Start command is issued to the TOTALIZR point. A logic slot or user program
sets the setpoint to some value.
• When the first "slowdown" or "near-target" flag (ADEV1FL) comes on, it is read by
logic or user program and reduces the setpoint.
• When the second "slowdown" or "near-target" flag (ADEV2FL) comes on, it is read
by logic or user program and reduces the setpoint.
• When the accumulation reaches the target value (AVTV), filling is complete and the
complete flag (AVTVFL) comes on. It is read by logic or user program and sets the
setpoint = 0.

256 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 23 Totalizer PV Algorithm
23.1 Functional Overview

Figure 23-2 Using a Totalizer to Fill a Tank

Target
Value
(PVTV)

AVDEV1FL
P1 TOTALIZER AVDEV2FL CL Block(s)
AVTVFL

SP
PID OP
PV

F Flow Transmitter

Liquid

R688 HPM High-Performance Process Manager Control Theory 257

08/2019 Honeywell
23 Totalizer PV Algorithm
23.2 Options and Special Features

23.2 Options and Special Features

Time-Base
You specify the time base in seconds, minutes, or hours, in parameter TIMEBASE. This
is the time base in which the flow measurement is made. For example, liters per second.
This parameter only applies when ACCTYPE = ANALOG.
Engineering-units scaling
• Scale factor, C, can be used to convert from one set of engineering units to
another, for example, from gallons per minute to barrels per minute.
Commands and States
Commands can be issued to the data point that is using TOTALIZR from a Universal
Station or by a user-written program. These commands are written in the TOTALIZR
point's COMMAND parameter.
The commands are as follows:
• None—No action.
• Start—Start the accumulation. STATE changes to Running.
• Stop—Stop the accumulation. STATE changes to Stopped.
• Reset—Reset the accumulated value to a user-specified value. This value is
specified in parameter RESETVAL. If the accumulator is running, it continues from
the reset value.
Command Flags
In addition to the above (enumerated) commands, explicit command flags are provided to
reset, start, or stop the totalizer.
• RESETFL — Off to On transition causes the totalizer to be reset (see “Accumulated
value before reset” in Section 23.2).
• STARTFL — Off to On transition causes the STATE of totalizer to be Running.
• STOPFL — Off to On transition causes the STATE of totalizer to be changed to
Stopped.
The above flags are program-access level, so they can be written to by a Logic Point or a
user-written program.
Accumulated value before reset
The reset command sets the PVCALC parameter equal to the reset value (RESETVAL).
The value of PVCALC just prior to being reset is saved as the old accumulation value

258 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 23 Totalizer PV Algorithm
23.2 Options and Special Features

(OLDAV). This allows other system functions using the totalized value to be able to reset
the totalizer without losing any "accumulation."
Range of Values
The accumulated value has a normal range of PVEULO to PVEUHI, where PVEUHI
defines the point where the bar graph is at the 100% level, and PVEULO is the point
where the bar graph is at the 0% level.
Clamping option
This algorithm will continue to totalize past PVEUHI until it reaches the value of
PVEXEUHI. When it reaches PVEXEUHI, the following occurs:
• If NoClamp was selected, the PV is set to BadPV and displayed as NAN.
• If Clamp was selected, the PV is flagged as uncertain and clamped to PVEXEUHI.
In either case, the algorithm continues to accumulate a value in PVCALC until it is reset,
regardless of the selection of NoClamp/Clamp.
Using scientific notation
Values are accumulated as integers, but displayed as real numbers. You can enter values
using scientific notation; for example, 1,000,000 can be entered as 1E6. If the
accumulated value exceeds the limit of displayable characters, it will be displayed in
scientific notation.
Near-Zero cutoff
To prevent accumulation of negative flow values, where the flow transmitter may not be
precisely calibrated near zero flow, you can specify a cutoff value in parameter
CUTOFFLM. When the P1 value is below CUTOFFLM, it is replaced by zero. You can
eliminate this feature by specifying NaN in CUTOFFLM.
Target-Value flags
The target value can be specified by an operator or a user-written program that is stored
in AVTV. This feature can be disabled by storing NaN in AVTV.
When the accumulated value in PVCALC is equal to or greater than AVTV, the target-
value-reached flag, AVTVFL, goes to On, indicating that the accumulation is complete.
Even if the accumulator has stopped, this check is made on each processing pass.
You can specify two other trip points in AVDEV1TP and AVDEV2TP, as deviations
from AVTV. Each of them is associated with a flag:
• AVDEV1FL trips when—
PVCALC > AVTV - AVDEV1TP
• AVDEV2FL trips when—

R688 HPM High-Performance Process Manager Control Theory 259

08/2019 Honeywell
23 Totalizer PV Algorithm
23.2 Options and Special Features

PVCALC > AVTV - AVDEV2TP

When the PVAUTOST of the accumulated value is Bad, AVTVFL, AVDEV1FL, and
AVDEV2FL are all Off.
Bad-Input and warm-restart Options
You can configure equations A through F for this algorithm, but instead of specifying the
calculation, they specify combinations of the following five options:
• Use Zero—When the accumulator is running, if the input status P1STS (or P2STS
for Pulse IOP) is Bad, the input value is replaced by zero and the accumulation
continues with a PVAUTOST of Uncertn. When the input status is Normal,
PVAUTOST remains Uncertn until a reset command is received. No special action by
the operator is required.
• Use Last Good Value—When the accumulator is running, if the input status is bad,
the input value is replaced by the last good value and the accumulation continues with
PVAUTOST as Uncertn. When the input status is Normal, PVAUTOST remains
Uncertn until a Reset command is received. No special action by the operator is
required.
• Set PVAUTOST Bad and Stop—When the accumulator is running and the input
status is bad, the value in PVCALC becomes NaN, PVAUTOST goes Bad, and the
accumulator is stopped. If the PVSOURCE is Auto, a bad-PV alarm is generated.
When the input status is again Normal, PVAUTOST remains Bad until the
accumulator is started again. To restart the accumulation, the operator should estimate
its value and use the Reset command (see “Commands and States” in Section 23.2) to
establish that value, then use the Start command to restart the accumulation. The last
accumulated value before the status went bad is in LASTPV.

260 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 23 Totalizer PV Algorithm
23.2 Options and Special Features

• Continue After a Warm Restart—On a warm restart when the accumulator is

running, the accumulation continues from the last PVCALC value. The PVAUTOST
goes to uncertain (UNCERTN) and remains so until a Reset command is received.
When the Pulse Input IOP is used (ACCTYPE = PULSE), accumulation continues
with the accumulated value count (AV) obtained from the IOP. The totalizer
assumes that exactly one rollover of the IOP count has occurred, if necessary. The
PVAUTOST goes to UNCERTN and remains so until a Reset command is received.
• Set PVAUTOST Bad and Stop After a Warm Restart—On a warm restart when
the accumulator is running, the value in PVCALC becomes NaN, PVAUTOST goes
Bad, and the accumulation is stopped. The operator must intervene to restart the
accumulator.
These options are selected as follows:

Equation Bad Input Handling Warm Restart

A Use Zero Continue

B Use Last Good Value Continue
C Set Bad and Stop Continue
D Use zero Set Bad and Stop
E Use Last Good Value Set Bad and Stop
F Set Bad and Stop Set Bad and Stop

If the accumulator is stopped, the input status is ignored. If the accumulator is stopped on
a warm restart, no special action by the operator is required.
Restart or point activation
When the TOTALIZR data point is activated, the PVCALC value becomes NaN,
PVAUTOST goes Bad and the accumulator state is Stopped. If the PVSOURCE is Auto,
this causes a bad-PV alarm and the operator must re-establish normal operation.
The processing that takes place for a warm restart is described in Bad-Input and warm-
restart Options.

R688 HPM High-Performance Process Manager Control Theory 261

08/2019 Honeywell
23 Totalizer PV Algorithm
23.2 Options and Special Features

Error handling
PVAUTOST is Uncertn when
• The input status (P1STS or P2STS) is Uncertn.
• The input status is Bad and the "use zero" or "use last value" (Equation A, B, D, or
E) is configured (see “Bad-Input and warm-restart Options” in Section 23.2).
• The data point is in a warm restart and the continue option (Equations A, B, or C) is
configured (see “Bad-Input and warm-restart Options” in Section 23.2).
A Reset command is needed to return PVAUTOST status to Normal, provided the input
status is Normal.
PVCALC contains NaN and the PVAUTOST is bad when
• The input status is Bad and the "set bad and stop" (Equation C or F) is configured.
• The data point is in a warm restart and is configured for "set bad and stop"
(Equations D, E, or F) is configured.
A Reset command is needed to return PVAUTOST to Normal, provided the input status
is Normal.
PV or AV selection
Either of the parameters AV or PV is available at the input of the Regulatory PV
Totalizer algorithm. Normally AV is used, but only if all the following conditions are
true—
• Pulse IOP is running.
• Point is active.
• IOP PV is not in lo cutoff.
• IOP PV is not clamped.
• IOP PV source is AUTO.
• there are no soft failures against the IOP slot.

262 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 23 Totalizer PV Algorithm
23.2 Options and Special Features

Automatic PV reset
With TPN R684, HPM Totalizer RegPV points are provided with an option to
automatically reset and restart the accumulation of PV value at specific configured
intervals. The two point-based parameters - $AUTROPT and $AUTRTIM are used to
configure the automatic PV reset.
$AUTROPT – Automatic Reset Option
The $AUTROPT (Automatic Reset Option) parameter is an enumeration. It provides the
following options:

$AUTROPT Value Description

NONE This is the default option indicating that the automatic reset is
not configured for this point.

HOURLY PV value resets every one hour from the configured automatic
reset time.

8HOURS PV value resets every 8 hours from the configured automatic

reset time.

12HOURS PV value resets every 12 hours from the configured automatic

reset time.

DAILY PV value resets every 24 hours from the configured automatic

reset time.

WEEKLY PV value resets every 7 days from the configured automatic

reset time.

MONTHLY PV value resets every month at the specified day and time as
configured in the automatic reset time.

YEARLY PV value resets every year at the specified day and time as
configured in the automatic reset time.

R688 HPM High-Performance Process Manager Control Theory 263

08/2019 Honeywell
23 Totalizer PV Algorithm
23.2 Options and Special Features

$AUTRTIM – Automatic Reset Time

The Automatic Reset Time ($AUTRTIM) parameter is a time-based parameter. It
indicates an offset value that is within the interval determined by the reset option
parameter. With 0 00:00:00 being the lower limit for all options, the automatic reset
functionality is active at 0 00:00:00, if the $AUTROPT is set to a value other than
NONE. The various offset values are as follows:

$AUTROPT Value $AUTRTIM Value

NONE N/A

HOURLY Offset time to be set in minutes or seconds ranging from [0

00:00:00] to [0 00:59:59].

8HOURS Offset time to be set in hours ranging from [0 00:00:00] to [0

07:59:59].

12HOURS Offset time to be set in hours ranging from [0 00:00:00] to [0

11:59:59].

DAILY Offset time to be set to any hour in the day ranging from [0
00:00:00] to [0 23:59:59].

WEEKLY Offset time to be set to any day in the week ranging from [0
00:00:00] to [6 23:59:59].

MONTHLY Offset time to be set to any day in the calendar month ranging
from [0 00:00:00] to [30 23:59:59].

YEARLY Offset time to be set to any day in the calendar year ranging
from [0 00:00:00] to [365 23:59:59].

TIP
The $AUTRTIM parameter goes invisible in PED when the $AUTROPT
parameter is set to NONE (default).

264 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 23 Totalizer PV Algorithm
23.2 Options and Special Features

Configuring the Automatic Reset Option ($AUTROPT) and the

Automatic Reset Time ($AUTRTIM) parameter
The steps to configure the $AUTROPT and $AUTRTIM parameters are as follows:

Step Action

1 Build a Reg PV Process Point on the Network Interface Module.

2 Select HPM as the NODETYP.
3 Select TOTALIZR as the PVALGID and press Enter.
The $AUTROPT parameter is displayed on page 4 (NIM Reg PV Totalizer
algorithm) of the PED display.
4 Select any one of the options for the $AUTROPT parameter.
Note: Once $AUTROPT is set to a value other than NONE, $AUTRTIM is
visible.
5 Enter an Offset time for the $AUTRTIM parameter.
Note: The offset time selected must be within the time interval of the
previously selected $AUTROPT option in the format - DDD-HH:MM:SS.

TIP
• The automatic reset occurs at the UCN time. Reset time may be different
from the time on the station if there is no clock master and if the nodes
are in Local mode.
• Program reset, Command driven reset and/or Operator reset does not
have any impact on the automatic reset.

Change in Automatic Reset Option and Time

When the automatic reset function is active, if there is any change either in the option or
the reset time then the next reset time is recalculated immediately. The next reset happens
at the newly calculated time.

Automatic Reset and the UCN time change

The automatic reset function monitors the changes in the system time and recalculates the
next reset time accordingly. This accommodates the UCN time change due to daylight-
saving.

R688 HPM High-Performance Process Manager Control Theory 265

08/2019 Honeywell
23 Totalizer PV Algorithm
23.2 Options and Special Features

Changes to the accumulated value on automatic reset

When an automatic reset is configured, the accumulated value in PV is stored in OLDAV
and the PV value is set equal to RESETVAL at the time of reset. Accumulation starts
from then on until the next automatic reset or manual reset, depending on the
configuration.

Resetting the PV value on the Last day of February

To reset the PV value on the last day of February irrespective of the year being a leap
year or non-leap year, enter 59 for DDD of $AUTRTIM. The automatic reset happens on
the 29th of February in case of a leap year and on 28th of February in case of a non-leap
year.
The following table illustrates this scenario:
Parameter Configuration

$AUTROPT YEARLY

$AUTRTIM 59-00:00:00

Resetting Totalizer PV value – WEEKLY

For the WEEKLY option, the days of the week corresponding to the DDD value of
$AUTRTIM are as follows:
DDD of $AUTRTIM Value Day of the Week

0 Sunday

1 Monday

2 Tuesday

3 Wednesday

4 Thursday

5 Friday

6 Saturday

Resetting Totalizer PV value - MONTHLY

If the number of days in a month is less than the offset configured, the reset happens on
the last day of the month as per the calendar. The following table illustrates a scenario:

266 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 23 Totalizer PV Algorithm
23.2 Options and Special Features

Parameter Configuration

$AUTROPT MONTHLY

$AUTRTIM 29-06:30:20

If the month is February and the year is a non-leap year, the reset occurs on 28th of
February at 06:30:20.
Similarly, if the month is April, the reset occurs on the 30th of April.

HPM IDLE to RUN

When there is an IDLE to RUN transition for HPM, the PV value resets immediately if
the time of transition is later than the pre-calculated reset time and the next reset time is
recalculated.
The following table illustrates a scenario where HPM is in the IDLE state since 12:10:10
and transitioned to RUN at 12:45:00:

Parameter Configuration

$AUTROPT HOURLY

$AUTRTIM 0 00:20:30

The PV value resets immediately when HPM transitions from IDLE to RUN at 12:45:00.
The next reset time is calculated as 13:20:30.

TIP
For the automatic reset functionality, the behavior of totalizer points during
PTEXECST change from INACTIVE to ACTIVE is same as when HPM
changes from IDLE to RUN.

R688 HPM High-Performance Process Manager Control Theory 267

08/2019 Honeywell
23 Totalizer PV Algorithm
23.3 Equations

23.3 Equations
Background
NormalText
Equation legend
For each of the equations:
• PVCALC(i)=The output of this algorithm from the current pass. It is selected as the
PV for this data point when PVSOURCE is Auto.
• PVCALC(i-1)=The accumulated value at the end of the last processing pass for this
point.
• C=The scale factor. Can be used to convert from eng. units to different eng. units.
Default value = 1.0
• (Time-scale)=TS*60 if TIMEBASE contains Seconds.
• TS if TIMEBASE contains Minutes.
• TS/60 if TIMEBASE contains Hours.
• TS=The data-point processing interval in minutes.
• Pn=The input value. Typically a flow rate.
Equations
Configure one of the Equations A through F for a TOTALIZR data point equation
specifying the operating bad-input and warm-restart options according to Bad-Input and
warm-restart Options.
For Analog Operation:
• For all equations, when the accumulator is running, the accumulated value in
PVCALC is calculated as follows:
PVCALC(i) = PVCALC(i-1) + C * (TIME-SCALE) * Pn

268 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 23 Totalizer PV Algorithm
23.3 Equations

For Pulse Input Operation

• If pulse is selected through parameter ACCTYPE, operation is the same, except
input from the Pulse IOP is supported as follows—
− As the Totalizer PV algorithm functional diagram figure indicates, P1/P2 input
is from the Pulse IOP.
− Normally the P2 input (AV) is used as the accumulated value from the pulse
IOP. It is a 32 bit unsigned integer and used to determine volume.
− This method is more precise than if the Pulse IOP rate value is used.
− Error handling selected by Equations A through F references the P2 input status.
• The PV Totalizer algorithm contains a single user-configurable constant (C) —
PVCALC = C * DELTA_AV + PVCALC_LAST_SAMPLE
When configuring the PV Totalizer algorithm for pulse operation, select ACCTYPE =
PULSE. Then, define the pulse input sour

ce, P1SRC(1) to be the PV parameter of the PI IOP. The HPMM software uses the entity
specified for P1SRC(1) to establish the algorithm’s second input (P2) except that it uses
the parameter ID of AV.

R688 HPM High-Performance Process Manager Control Theory 269

08/2019 Honeywell
23 Totalizer PV Algorithm
23.3 Equations

270 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 24. General Linearization PV Algorithm
24.1 Functional Overview
Family
The General Linearization (GENLIN) PV algorithm is a member of the Regulatory PV
algorithms.
Description
This algorithm calculates a PV that is a function of the input. The function can be any
that can be represented by up-to-12 continuous, linear segments. You specify the base
value and slope of each segment. The input is compared with the input range of each
segment and the output is set at the intersection of the input with the appropriate
segment. See the following two figures, Figure 24-1and Figure 24-2.
Figure 24-1 General Linearization PV Algorithm Functional Diagram

(Data Point
P1 GENLIN PVCALC
Parameter)

Use
This algorithm is typically used to provide a linearized PV (in engineering units) for a
sensor with a nonlinear characteristic. This algorithm can also be used to characterize
functions of a single variable, such as heat transfer vs. flow rate, or efficiency as a
function of load. The algorithm is particularly useful when the relationship of the input to
engineering units is empirically determined.
This algorithm supplements the standard linearization functions that are provided in the
IOPs for standard temperature sensors and differential flow meters.

24.2 Options and Special Features

Restart or point activation
On a cold or warm restart, or when a data point using this algorithm is activated,
PVCALC is recalculated the next time this data point is processed.

R688 HPM High-Performance Process Manager Control Theory 271

08/2019 Honeywell
24 General Linearization PV Algorithm
24.2 Options and Special Features

Error handling
If P1STS is Uncertn, PVAUTOST status becomes Uncertn.
If P1STS is Bad or if any of the segment coordinates (INi or OUTi) contains NaN,
PVAUTOST becomes Bad.
If any of the segment coordinate values (INi or OUTi) contains NaN, a configuration
alarm is generated.
Operator parameter changes
The SEGTOT, INi, and OUTi parameters can be changed by the operator, but only if the
data point that uses the GenLin algorithm is made inactive.
Parameter value restrictions
The input coordinate value parameters must be specified in ascending order from the
smallest value to the largest.

272 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 24 General Linearization PV Algorithm
24.2 Options and Special Features

Figure 24-2 General Linearization Operation Example

OUT3 100 -

90 -

80 -
Solution D
70 -

60 -
PVCALC

50 - SEGTOT = 3
OUT2 Solution A
40 -
Solution C
30 -

OUT1 20 -
Solution B
10 -

OUT0 0 -

0 10 20 30 40 50 60 70 80 90 100

IN0 IN1 IN2 IN3

IN0 = 0.0 OUT0 = 0.0 Beginning of 1st se gment

IN1 = 30.0 OUT1 = 20.0 End of 1st segment
IN2 = 55.0 OUT2 = 45.0 End of 2nd se gment
IN3 = 85.0 OUT3 = 100.0 End of 3r d segment

Solution A (P1 = IN2):

PVCALC = OUT2 = 45.0

Solution B (P1 > IN1):

OUT1 - OUT 0 20 - 0
PVCALC = *( P1 -IN0) +OUT0 = *( 20 - 0 ) + 0 = 13.33
IN1 - IN0 30 - 0

Solution C (P1 int ersects any but 1st and last segment):

OUT(i+1) - OUTi 45 - 20
PVCALC = *( P1 - INi) + OUTi = *( 45 - 3 0) + 20 = 35.0
IN(I+1) - INI 55 - 30

Solution D (P1 int ersects the last segment) :

OUTsegtot - OUT(segtot - 1)
PVCALC = *[P1 - IN(segtot - 1)] + OUT(segtot -1)
INsegtot - IN( segtot - 1)

100 - 45
=
85 - 55 *( 70 - 5 5) + 45 = 72.5

R688 HPM High-Performance Process Manager Control Theory 273

08/2019 Honeywell
24 General Linearization PV Algorithm
24.3 Equations

Segment extensions
The first and last segments are treated as if they indefinitely extended, so if P1 is less
than IN0 or greater than INsegtot, PVCALC is computed by assuming that the slope of
the appropriate segment continues to the intersection point.

24.3 Equations
Equation legend
For each equation:
• PVCALC =The output of this algorithm. It is selected as the PV for this data point
when the PV source is AUTOmatic.
• P1 =The input value.
• IN(i) =Input value at the beginning of the intersecting segment.
• IN(i+1) =Input value at the end of the intersecting segment.
• OUT(i+1)=Output value at the end of the intersecting segment.
• segtot =A subscript indicating the user-entered value in SEGTOT.
Equations
Each time this algorithm is processed the input value P1 is compared with each segment,
starting with the first and continuing until a segment is found that intersects with the
input. When that segment is found, PVCALC is calculated as follows:
• If the P1 value is exactly equal to the input value at the beginning of any segment
(P1 = INi, for i in a range from 0 to the value in SEGTOT),

• If P1 intersects the first segment (P1 < IN1),

• If P1 intersects any segment except the first one or the last one [INi < P1 < IN(i+1)
for any i from 1 to segtot-2],

• If P1 intersects the last segment [P1 > IN(segtot-1)],

274 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 24 General Linearization PV Algorithm
24.3 Equations

R688 HPM High-Performance Process Manager Control Theory 275

08/2019 Honeywell
24 General Linearization PV Algorithm
24.3 Equations

276 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 25. Calculator PV Algorithm
25.1 Functional Overview
Family
The Calculator (CALCULTR) PV algorithm is a member of the Regulatory PV
algorithms.
Description
The calculator algorithm allows the user to write an equation to compute the PV and up
to four intermediate results. The result from evaluating the expression is stored into
PVCALC, which is then processed like any other PV algorithm.
Figure 25-1 Calculator PV Algorithm Functional Diagram

P1
P2
P3 (Data Point
P4 CALCEXP PVCALC
Parameters)
P5
P6

Accepts up to six inputs (POINT.PARAMETER).

Equation may be up to 60 characters long.
Up to 4 intermediate results
FORTRAN-like syntax rules
High Select; Low Select; Average Select and Middle of 3 Select support

With TPN R683, the CALCEXP parameter of the HPM calculator points can accept up to
60 characters. All access mechanisms of CALCEXP parameter supports the revised
length of the equation.
However, the CALCEXP parameter of the APM and PM calculator points can accept
only up to 40 characters.

ATTENTION
If the equations are configured with more than 40 characters, the CPU

R688 HPM High-Performance Process Manager Control Theory 277

08/2019 Honeywell
25 Calculator PV Algorithm
25.2 Options and Special Features

consumption increases. Honeywell recommends users to apply due

delligence in configuring the points with more than 40 characters.

Use
This algorithm can be used to perform any calculation or arithmetic function on up to six
inputs, using up to four intermediate results. Additionally is can be used as a selector
algorithm as noted above.

25.2 Options and Special Features

Configuring inputs
You may configure up-to-six inputs, using the "Tagname.Parameter" format for
PISCRC(n). The destination inputs can be assigned, using PIDSTN(n) for P1 through P6.
HI, LO, and AVG functions may have any number of inputs including constants.
Intermediate calculations
Up to four intermediate results can be calculated, for example:
C1=<expr_1>; C2=<expr_2>; C3 =<expr_3>;
C4=<expr_4>;<expr_5>
The result of expr_5 is stored in PVCALC (because it has no equate associated with it).
There is no restriction on the order in which the sub equations and the expression for
PVCALC are specified.
If C1-C4 are expressions, they are recalculated every time the algorithm is processed.
User configurable results
If it is necessary, or desirable, to key user configurable constants into the equation, C1-
C4 can be useful. C1-C4 can then be entered or modified by an operator through the
detail displays, or by logic slots, or user program.
Equation length
The equation can comprise up to 60 characters including the subequations.
Syntax
FORTRAN syntax rules apply; up-to-five levels of nesting of expressions.
Error handling
If the calculated value of PVCALC is "bad," PVAUTOST is marked Bad. If the final
value of PVCALC is a normal number, PVAUTOST is marked Uncertn if any input that
is used in the calculation is uncertain or bad; otherwise it is set equal to Normal.

278 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 25 Calculator PV Algorithm
25.3 Equations

If the HI, LO, and AVG functions have bad inputs, they are ignored in the computation;
if all inputs are bad, the result is marked bad. On MID3 function, if only one input is bad,
the result is set equal to the average of the other two.

25.3 Equations
Background
The equation is specified at the time of point building and is loaded from the DEB
without additional steps such as compilation or linking. Up-to-six inputs can be
configured and stored into the destination parameters P1, P2 . . . P6.
Guidelines
The following general guidelines apply:
• The equation can be up to 60 characters long.
• FORTRAN-like syntax rules apply.
• Up to 5 levels of nesting of expressions.
• Free format real and mixed real and integer calculations permitted.
• Up to four intermediate results.
• The result of any expression that has no "equate" associated with it is stored into
PVCALC.
• On point activation or warm restart PVCALC is initialized to the P1 input.

R688 HPM High-Performance Process Manager Control Theory 279

08/2019 Honeywell
25 Calculator PV Algorithm
25.3 Equations

Supported operators and functions

Table 25-1 Supported Operators and Functions

Type Operator/Function Symbol

Operators Divide /
Multiply *
Subtract -
Add +

Arithmetic Functions Absolute ABS

Square SQR
Square Root SQRT
Natural Logarithm LN
Base_10 Logarithm LOG
Exponent EXP
Sine SIN
Cosine COS
Tangent TAN
Arc-tangent ATAN

Special Functions High Select MAX

Low Select MIN
Average Select AVG
Middle of Three MID3

Arithmetic Assignment Equate =

Statement

Other Separator ;

280 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 25 Calculator PV Algorithm
25.3 Equations

Equations
The equation can be up to 60 characters long. It is entered into the Parameter Entry
Display in the port for the parameter CALCEXP. You can configure up to four
intermediate expressions. The result of an expression not having an "equate" associated
with it is stored in PVCALC.
Examples of use of this algorithm's equation:

R688 HPM High-Performance Process Manager Control Theory 281

08/2019 Honeywell
25 Calculator PV Algorithm
25.3 Equations

282 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 26. Regulatory Control Points
26.1 Regulatory Control Point Background
Purpose
Regulatory Control (RegCtl) points are used to perform standard control functions by
executing the algorithms that have been configured. Each control algorithm includes a
wide range of configurable options to allow implementation of complex control strategies
by a simple menu-select process. For example, initialization and windup protection are
inherently provided for all point interconnections. Also, the capability to ramp a setpoint
(by operator entry of a target value and ramp time) is configurable. Predefined and
custom displays are available to support these control strategies. These standard support
functions significantly simplify the implementation and use of sophisticated multi-loop
control strategies. Increasingly advanced control strategies become practical as a result of
the ease of HPM configuration.
Algorithms
The Regulatory Control (RegCtl) point supports the following algorithms:
• PID Control Algorithm, (see Section 1)
• PID w/Feedforward Control Algorithm, (see Section 28)
• PID w/External Reset-Feedback Control Algorithm, (see Section 29)
• PID Position Proportional Controller, (see Section 30)
• Position Proportional Control Algorithm, (see Section 31)
• Ratio Control Algorithm, (see Section 0)
• Ramp and Soak Control Algorithm, (see Section 33)
• Auto Manual Control Algorithm, (see Section 1)
• Incremental Summer, (see Section 1)
• Switch Control Algorithm, (see Section 1)
• Override Selector Control Algorithm, (see Section 37)
• Multiply Divide Control Algorithm, (see Section 1)
• Regulatory Control Summer Algorithm, (see Section 39)

26.2 Regulatory Control Point Functional Overview

Functional overview
Figure 26-1 Regulatory Control Point Functional Diagram

R688 HPM High-Performance Process Manager Control Theory 283

08/2019 Honeywell
26 Regulatory Control Points
26.2 Regulatory Control Point Functional Overview

PV (Input Value)

Input CONTROL INPUT

Parameters PROCESSING

PV SOURCE ALL OTHER

PID, PosProp. SELECTION ALGORITHMS
and Ratio Ctl
Algorithms
PV ALARM
DETECTION

EXTERNAL MODE
SWITCHING

INITIALIZATION
LOGIC

TARGET VALUE
PROCESSING OR
DEVIATION
ALARMING

PID and ALL OTHER

PosProp. PV ALGORITHMS
TRACKING

DEVIATION
ALARMING

CONTROL
ALGORITHM
CALCULATION

CONTROL OP (Output Value)

OUTPUT
PROCESSING

ALARM
DISTRIBUTION

284 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 26 Regulatory Control Points
26.2 Regulatory Control Point Functional Overview

REFERENCE - INTERNAL
Descriptions of each step in the regulatory control point functional processing
diagram are provided in the following topics.
• Control Input Processing.
• PV Source Selection.
• PV Alarm Detection.
• External Mode Switching.
• Initialization Logic.
• Target Value Processing or Deviation Alarming.
• PV Tracking.
• Deviation Alarming.
• Control Algorithm Processing.
• Control Output Processing.
• Alarm Distribution.

R688 HPM High-Performance Process Manager Control Theory 285

08/2019 Honeywell
26 Regulatory Control Points
26.2 Regulatory Control Point Functional Overview

Operating modes
Table Regulatory Control point operating modes and figure Regulatory Control point
mode structure define the operating modes and mode attributes applicable to the
Regulatory Control point (RegCtl).
Separate flags are provided to indicate if the current mode is manual (MANMODFL),
auto (AUTMODFL), cascade (CASMODFL), backup cascade (BCAMODFL), or if the
mode attribute is Oper (OPRATRFL) or program (PRGATRFL). The modes and mode
attributes can be used in conjunction with the logic slots to implement interlocks.

Table 26-1 Regulatory Control Point Operating Modes

Operating Mode Definition

Manual Provides the operator or the discontinuous program with direct

(Man) control over the output value of the data point, regardless of
any automatic control strategy.

Automatic Output value is computed by the configured RegCtl algorithm,

(Auto) and the setpoint comes from the local setpoint (LSP) location
in the RegCtl point. An operator or a discontinuous program
can change the setpoint value.

Cascade (Cas) Data point receives its setpoint value from a primary data
point.

Backup Cascade Data point receives its setpoint value from a primary data
(Bcas) point.

286 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 26 Regulatory Control Points
26.2 Regulatory Control Point Functional Overview

Figure 26-2Regulatory Control Point Mode Structure

OP (from AM)
Ddc
DdcRsp Spc

Rsp
RCASOPT

Cas
PV (from Program) Bcas Auto

Man
PV (from Operator) Sub MODE
Man
Configured Auto
PVAUTO
PV Connection (CISRC) PVSOURCE
REGULATORY MODE
CONTROL OP
OP
POINT Cas or Auto
SP
Man

MODE MODATTR

Prog
Cas Auto None
Oper
Configured
SP Connection (CISRC)

MODE
Bcas Auto

Man
Cas

RCASOPT
Spc Rsp

DdcRsp
Ddc

SP (from AM)
None
SP (from Operator)
Oper MODATTR
SP (from Program)
Prog

OP (from Operator)
OP (from Program)

R688 HPM High-Performance Process Manager Control Theory 287

08/2019 Honeywell
26 Regulatory Control Points
26.2 Regulatory Control Point Functional Overview

Normal Mode
The normal mode is the mode that is copied into the MODE parameter when the operator
presses the NORM button. Also at that time, the content of the NMODATTR parameter
is copied into the MODATTR parameter. This then becomes the mode for the data point.
The possible entries for the normal mode are None, Man, Auto, Cas, and Bcas. The
normal mode flag (NRMMODFL) indicates if the mode for the point is normal mode.

Attributes
The mode attribute, as defined in the following table, denotes who has the authority to
change certain parameters of a data point, and is established through parameter
MODATTR.
Table 26-2 Regulatory Control Point Mode Attributes

Mode Attribute Definition

Operator Operator Access Level—The Operator can supply the setpoint,
output value, mode, ratio, and bias for a data point.
Program Program Access Level—programs can supply the setpoint, output
value, mode, ratio, and bias for a data point.
None The mode does not have an attribute.

The normal mode attribute is the attribute that is copied into the MODATTR parameter
when the NORM button is pressed. The possible entries for the NMODATTR parameter
are Operator, Program, and None. The normal mode attribute flag (NRMATRFL)
indicates if the point is in the configured normal mode attribute.

ATTENTION
An access level of Ccont (Continuous Control) allows supervisory control
from an LCN module, such as the AM, to change the setpoint, output value,
and mode of a data point.

288 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 26 Regulatory Control Points
26.2 Regulatory Control Point Functional Overview

Remote cascade handling

ATTENTION
With TPN R685, you can integrate standalone EUCN nodes with the
Experion network. The integration of EUCN nodes with the Experion network
provides the capability for peer-to-peer communication between ACE/C300
controllers and EHPM controllers.

The HPM supports supervisory or DDC control for the PID algorithms from any of the
following remote devices such as:
• Computer (through the CG)
• AM
• ACE-T through TPN Server
In addition to this, the EHPM which is integrated with the Experion network also
supports supervisory or DDC control for the PID algorithms from any of the following
remote devices such as:
• ACE through FTE
• C300 through FTE
If the remote cascade connection is coming from a regulatory data point in the
AM/ACE/C300, it handles everything automatically; however, in all other cases
(including the continuous CL programs in the AM directly writing to the HPM), you
must ensure that the following conditions are handled:
• remote device must use the continuous control access-level provided by the AM and
UCNOUT/EUCNOUT for writing to the SP, OP, and MODE parameters.
• remote device must also handle mode changes for closing the cascade.
• initialization to ensure bumpless mode transfers.
• windup protection.

EUCNOUT block
EUCNOUT block is a configurable block for creating regulatory control cascade strategies
between the ACE/C300 supervisory controller and the Enhanced High-Performance Process
Manager (EHPM) controllers residing on the EUCN.
The EUCNOUT function block supports Setpoint Control (SPC), Direct Digital Control (DDC),
Remote Setpoint Control (RSP) and Direct Digital Control with Remote Setpoint (DDCRSP)
remote cascade types between the regulatory control function blocks included in an ACE/C300
supervisory controller control strategy and the regulatory control points included in an EHPM
controller.
The EUCNOUT block does not require an OPC gateway or a TPN server to communicate with the
Process Manager controller.

R688 HPM High-Performance Process Manager Control Theory 289

08/2019 Honeywell
26 Regulatory Control Points
26.2 Regulatory Control Point Functional Overview

The BASIC/FULL value of the NODFSTAT parameter does not impact the EUCNOUT block
functionality, but the HPM UCNWRTLK parameter status impacts the EUCNOUT block
functionality.

UCNOUT block
UCNOUT block is a configurable block for creating regulatory control cascade strategies
between the Experion ACE-T supervisory controller and the Process Manager controller.
The UCNOUT block requires an OPC gateway or a TPN Server to communicate with the
Process Manager controller.

REFERENCE - EXTERNAL
For more information on UCNOUT/EUCNOUT block, refer to the following
documents in the Experion bookset.
• Control Builder Components Theory
• Control Builder Components Reference

Remote cascade options

The following table defines the remote cascade options provided by the RCASOPT
parameter.
For the EHPM integrated with Experion, the RCASOPT parameter exists within the
EUCNOUT ACE/C300 and the EHPM regulatory and analog output FULL PNTFORM.
These are configured inside the ACE/C300 EUCNOUT function block to match the
corresponding EHPM parameters.

WARNING
While using the BCAS and Auto BIAS options, make sure that the
backup controller’s output is not configured as the source of SP in the
downstream controller’s input connection.

290 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 26 Regulatory Control Points
26.2 Regulatory Control Point Functional Overview

Table 26-3 Regulatory Control Point Remote Cascade Options

Option Definition
Supervisory This option is configured by setting RCASOPT to Spc. The
Control (Spc) AM/ACE/C300 control strategy writes to the setpoint of the RegCtl
point, subject to the setpoint limits, when the RegCtl point is in Cas
mode.
Direct Digital This option is configured by setting RCASOPT to Ddc. The
Control AM/ACE/C300 control strategy writes to the OP output of the RegCtl
(Ddc) point, when the RegCtl point is in Cas mode. The SP cannot be written
by the AM/ACE/C300 control strategy to the RegCtl point. If the control
algorithm is a PID type and is configured for PV tracking, the SP is set
equal to the PV when in Cas mode.
Direct Digital This option is available for only PID-type algorithms. It is configured by
Control with setting RCASOPT to DdcRsp. The AM/ACE/C300 control strategy
Remote Setpoint writes directly to the OP output of the RegCtl point when it is in Cas
(DdcRsp) mode. The AM/ACE/C300 can also write to the SP of the RegCtl point
subject to the setpoint limits. PV tracking is not performed in Cas mode.
This option is used primarily when a single PID controller in the HPM is
used to back up a higher level control strategy running in the
AM/ACE/C300. The higher level control strategy writes to the OP and
also provides the SP for the backup control strategy.
Remote Setpoint This option is available for only PID-type algorithms and is configured
(Rsp)
by setting RCASOPT to Rsp. The AM control strategy writes to the SP
through an AM general output connection, whereas the ACE/C300
control strategy writes to the SP through an ACE/C300 output
connection, subject to the setpoint limits, when the RegCtl point is in
the Auto mode and it is being initialized by its secondary (that is
INITMAN flag is ON). PV tracking is not performed in Auto mode when
INITMAN is ON, if Rsp is selected.
Note: For more information on Rsp option for the ACE/C300, refer to
the Control Builder Components Theory in the Experion bookset.

ATTENTION
The Remote Setpoint (Rsp) option is primarily used in a cascade control
strategy where a RegCtl point serves as backup to a higher level control
strategy running in the AM/ACE/C300, and the higher-level control strategy
provides the SP for the backup control strategy. In the backup strategy, the
primary PID would be configured for the Rsp option (allowing the
AM/ACE/C300 to specify the backup SP), and the secondary would be

R688 HPM High-Performance Process Manager Control Theory 291

08/2019 Honeywell
26 Regulatory Control Points
26.2 Regulatory Control Point Functional Overview

typically configured for Ddc or Spc control.

Remote cascade request

The remote cascade request flag (CASREQ) is set to Request but the actual mode is left
unchanged when the RCASOPT parameter for the RegCtl point is configured for Spc,
Ddc or DdcRsp. This happens when the operator or a discontinuous user program (for
example, a sequence program) tries to change the mode to Cas.
The actual mode is changed to Cas only:
1. When the AM/ACE/C300 control strategy explicitly writes the mode to Cas (it
should do this only after seeing a remote cascade request from the secondary).
2. If Spc is entered for the RCASOPT parameter, and the AM/ACE/C300 control
strategy writes to the setpoint.
3. If Ddc or DdcRsp is entered for the RCASOPT parameter, and the AM/ACE/C300
control strategy writes to the output value OP of the RegCtl point.

ATTENTION
After CASREQ has been set to Request, any mode change causes CASREQ
to be set to NotReq.

WARNING
Do not use EUCNOUT with the RegCtl or AO unless OUTIND parameter is
set to DIRECT or OPTDIR is set appropriately for balancing the control
strategies.
ACE/C300 control strategy writes to EHPM using EUCNOUT overrides the
UCN/HPM FULL/BASIC parameter status but does depend on HPM
UCNWRTLK parameter status.
There are multiple paths for control output to EHPM. You should coordinate
the upper level control schemes to avoid conflicts between unique interfaces
such as:
• UCN peer-to-peer
• LCN Computer Gateway
• AM and AM/CL control
• ACE-T control though TPN Server
• ACE-T/C300 control through FTE

292 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 26 Regulatory Control Points
26.2 Regulatory Control Point Functional Overview

Remote cascade shed

The remote cascade shed mechanism in the HPM allows the user to substitute the local
backup control strategy in the HPM for the AM/ACE/C300 control strategy if the
AM/ACE/C300 or NIM fails.
When a RegCtl point that is configured for Spc, Ddc, or DdcRsp control is in Cas mode
and the SP (if Spc) or the OP (if Ddc or DdcRsp) is not updated by the AM/ACE/C300
within a predefined time, the AM/ACE/C300 or the NIM is assumed to have failed. The
backup control strategy is substituted by means of changing the mode to a pre-configured
backup mode. The maximum time allowed between updates is specified by SHEDTIME
(in seconds) and the backup mode is specified by SHEDMODE. Shedding to the backup
mode can be disabled by setting SHEDTIME to 0.
When the mode is shed to the pre-configured shed mode, the remote cascade shed flag
(RCASSHED) is set to On (mainly for indication at the Universal Station). Any
subsequent mode c
hanges automatically set the RCASSHED to Off. The remote cascade request flag is also
set to On, which allows the AM/ACE/C300 to resume control at a later time without
operator intervention.
Note: SHEDTIME parameter is applicable only for xPM regulatory control points and
not for xPM analog outputs.
Note: Redundant NIM/ENIM/ENB failover or Redundant HPM controller swap-over
may cause some peer-to-peer communication loss between HPM nodes for a short
duration. This includes EHPMs and HPM/EHPM hybrid pairs (during migration). This
may result in a temporary BAD VALUE which may cause mode shedding. To address
this, consider increasing the SHEDTIME parameter to a value greater than or equal to 5
seconds (if the value is non-zero and less than 5).

Bad PV/Mode shed

ATTENTION
This function does not apply to the RampSoak, IncrSum, or RatioCtl
algorithms.

The Regulatory Control parameter BADCTLOP determines if the mode sheds to manual
on detection of a bad PV (or bad CV for algorithms that do not have a meaningful PV).
For the definition of a bad PV, refer to BADPVFL in the PM Family Parameter
Reference Dictionary.

R688 HPM High-Performance Process Manager Control Theory 293

08/2019 Honeywell
26 Regulatory Control Points
26.2 Regulatory Control Point Functional Overview

ATTENTION
In MAN mode, when a point is in BADCTL and the BADCTLOP parameter is
not NOSHED, the user can go beyond the $MOPxxLM values, up to the
extended limits (106.9, -6.9) when using the RAMP keys.

The BADCTLOP parameter is configured on a per point basis as shown in the following
table.
Table 26-4 Regulatory Control Point Bad PV/Mode Shed

BADCTLOP Output SHED To Mode Ext. Mode Comments

Selection (Mode) Attribute Switching

No Shed Held Held N/A N/A Point resumes control

after initializing on PV
recovery.

Shed Hold Held Manual Operator Disabled Point is not

automatically
Shed Low -6.9% returned to the
previous mode before
Shed High 106.9% shed to manual.
Shed Safe Safe Op Operator is not
allowed to return to
the previous mode
until the bad control
condition clears.

294 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 26 Regulatory Control Points
26.3 Control Input Connections

Safety Shutdown
This option allows you to implement safety interlocks that effectively shutdown a single
control loop. The shutdown flag is set by a user-written program. When the shutdown
flag (SHUTDOWN) is set to:
• On, the mode and the mode attribute are changed to Man and Oper, respectively, and
the OP output is set equal to a predefined safe output value (SAFEOP), and—
− the external-mode-switching enable state (ESWENBST) is disabled, if it is
currently enabled.
− as long as it is On, the MODE, MODATTR, ESWENBST, and OP parameter
values cannot be changed.
• Off, the control loop must be manually restarted, and—
− a Logic Point or CL program must be used to reset the Safety Shutdown Flag
(from ON to OFF).

ATTENTION
If the point is already red tagged when the shutdown flag is turned On, the
output value is not changed. Typically, the safe output value can be
configured as 0% (if the valve is fully closed) or 100% (if valve fully open). In
some cases it may be important to just hold the last value. This can be
achieved by setting the SAFEOP parameter to NaN.

26.3 Control Input Connections

Use
Control input connections are typically used to assign "non-initializable" inputs to the
configured control algorithm. They can be used to assign initializable inputs (see “
Initalizable inputs” in Section 0), but if initialization and windup protection are required,
a control output connection from the primary point must be used.
Number and destination
The number of control input connections (NOCINPTS) and the destination parameter
(CIDSTN) for each connection are defaulted based on the non-initializable inputs
required by the control algorithm. (Refer to the individual control algorithm
configuration form for the destination parameters within each algorithm) The control
input connection-source parameter CISRC allows the user to specify the source of the
input using the "Tagname.Parameter" format.

R688 HPM High-Performance Process Manager Control Theory 295

08/2019 Honeywell
26 Regulatory Control Points
26.4 PV Source Selection

Sources
The inputs can be obtained from any source parameter that is a real number, an integer,
or a Boolean state. (Boolean states are treated as real numbers by the algorithm. The Off
state is equal to a real number of 0.0; the on state is equal to 1.0). For all RegCtl
algorithms except PIDERFB, the point's control output connections are also considered
input connections because the RegCtl point reads the output status before writing to it. A
RegCtl point can have up to seven input and output connections that obtain non-I/O scan
parameters from I/O Processors in the same HPM.
Initalizable inputs
Generally, initializable inputs are stored with control output connections at the primary
data point, and no input connections are required; however, in some cases it may be
required to obtain initializable inputs with input connections (for example, when
initialization and windup protection are not needed). To achieve this, the number of
control inputs is allowed to be increased based on the initializable inputs of the control
algorithm.

26.4 PV Source Selection

Applicability

ATTENTION
The PV Source Selection step in the Regulatory Control processing applies
only to the Pid, PosProp, and RatioCtl algorithms.

Source
The source of the PV can be an analog input point, a PV algorithm, a Universal Station,
or a user-written program.
Specified by
The source of the PV is specified by the PVSOURCE parameter, whose value can be
changed by an operator, a supervisor, an engineer, or a user-written program.
Configuration
The PVSOURCE parameter is configurable only if the data point has been configured as
a full point. PVSOURCE can have one of the values defined in the following table.
Table 26-5 Regulatory Control Point PV Source Selection Configuration

Value Definition

296 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 26 Regulatory Control Points
26.5 PV Alarm Detection

Value Definition

Auto PV is received from an analog input point or a PV algorithm. The value

is in PVAUTO and its status is contained in PVAUTOST. During normal
operation, the PV source is Auto, and the PV and its value status
(PVSTS) become equal to PVAUTO and PVAUTOST, respectively,
before PV range checks are made. When the PV source is changed
from Auto to Man or Sub, the PV remains at the last value until it is
changed by the operator (Man) or a program (Sub), so it doesn't
"bump." In Man or Sub, the status in PVSTS is Uncertain. When the PV
source is changed from Man or Sub to Auto, the PV immediately goes
to the PVAUTO value. This might cause a bump in the value unless it is
changed gradually to the value in PVAUTO before changing the source.

Man The PV is entered by an operator, supervisor, or engineer at a Universal

Station

Sub The PV is entered by a user-written program. A program can store a

bad value in PV, and if it does, PVSTS becomes Bad.

TIP
You can prevent PV source changes by entering OnlyAuto for the
PVSRCOPT parameter. This fixes the source as AUTO and the parameter
PVSOURCE is removed from the point. Configuring All in PVSRCOPT allows
normal PV source selection.

26.5 PV Alarm Detection

Applicability

ATTENTION
The PV Source Selection step in the Regulatory Control processing applies
only to the Pid, PosProp, and RatioCtl algorithms.

Configuration
Alarms for a RegCtl point can be configured only when the point has been configured as
a full point. Alarm types supported by the RegCtl points are provided in the following
table.
Table 26-6 Regulatory Control Point Bad PV Alarm Detection

Alarm Type Algorithms

R688 HPM High-Performance Process Manager Control Theory 297

08/2019 Honeywell
26 Regulatory Control Points
26.6 External Mode Switching

Alarm Type Algorithms

PV High/Low Applicable to only the Pid, PosProp, and RatioCtl

Regulatory Control point algorithms

PV High-High/Low-Low Applicable to only the Pid, PosProp, and RatioCtl

Regulatory Control point algorithms

PV Rate-of-Change Applicable to only the Pid, PosProp, and RatioCtl

Positive/Negative algorithms Applicable to only the Pid, PosProp, and
RatioCtl Regulatory Control point algorithms

PV Significant Change Applicable to only the Pid, PosProp, and RatioCtl

Regulatory Control point algorithms

BadPV Applicable to only the Pid, PosProp, and RatioCtl

Regulatory Control point algorithms

Bad Control Applicable to all Regulatory Control point algorithms

Deviation High/Low Applicable to all Regulatory Control point algorithms

Advisory deviation Applicable to all Regulatory Control point algorithms

Bad Output Applicable to all Regulatory Control point algorithms

REFERENCE - INTERNAL
For detailed alarm information, refer to the System Control Functions.

26.6 External Mode Switching

Use and operation
External mode switching (EMS) is typically used to establish mode interlocks or, under
certain process conditions, to restrict the use of a mode that invokes a higher level of
control. External mode switching is an option and can be configured by entering Ems for
the EXTSWOPT parameter. Mode changes made through external mode switching have
no effect on the mode attribute of the data point, or on the normal mode and normal
mode attribute of the point. When a mode change is made, the last values of the normal
mode and normal mode attribute parameters stay in effect.
Flags
Each regulatory data point has three parameters that are used as flags to indicate the
mode to which the point has been switched.
ESWAUTO (RegCtl)
298 HPM High-Performance Process Manager Control Theory R688
Honeywell 08/2019
 26 Regulatory Control Points
26.6 External Mode Switching

ESWCAS (RegCtl)
ESWMAN (RegCtl)

R688 HPM High-Performance Process Manager Control Theory 299

08/2019 Honeywell
26 Regulatory Control Points
26.6 External Mode Switching

Enabling EMS
When external mode switching is enabled by the operator or the program by setting the
ESWENBST parameter to Enable, both:
• are prevented from changing the mode of the data point when the point is in the
ESWMAN, ESWAUTO or ESWCAS mode as indicated in the following table.
• may disable external mode switching at any time by entering Disable for the
ESWENBST parameter.
Table 26-7 Regulatory Control Point External Mode Switching

EXTSWOPT ESWMAN ESWAUTO ESWCAS Parameter's New Mode is...

An Operator or Program may change the mode when...

EMS X X X Last Mode Requested

EMS F F F Previous Mode1

An Operator or Program may not change the mode when...

not EMS T X X Man

not EMS F T X Auto2

not EMS F F T CAS2

1 The mode when the point was last processed.

2 If the effective new mode is invalid for the control function, the mode will not change.

300 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 26 Regulatory Control Points
26.7 Initialization Logic

26.7 Initialization Logic

Background
Initialization provides meaningful initial values in the data point parameters before
processing is started or restarted. Separate mechanisms are provided to initialize:
• PV-related parameters.
• Control-related parameters.

CAUTION
Up to four output connections are permitted from a Regulatory Control point
but the control output destinations must be all IOPs (AOs or pulse width
modulated DOs) or all Regulatory Control inputs. The outputs cannot be a
mix of IOPs and Regulatory Control inputs.

R688 HPM High-Performance Process Manager Control Theory 301

08/2019 Honeywell
26 Regulatory Control Points
26.7 Initialization Logic

PV initialization purpose
The principal purpose of PV initialization is to set up starting values the first time the
point is processed or the first time it is processed after recovering from a BadPV value
status. PV initialization is useful for only functions involved in history collection or for
dynamically varying values. Stated another way, PV initialization is required where the
new value depends on the previous value.
Events causing PV initialization
The following events cause PV initialization:
• Point's execution state is changed to Active.
• HPM undergoes a warm or cold restart.
• PVAUTOST recovers from Bad value status.
Functions of PV initialization
PV initialization consists of the following functions:
• PVCALC is calculated from the PV inputs, using the steady-state portion of the
equation.
• PVAUTO is made equal to PVCALC.
• No other PV processing is affected by PV initialization.

ATTENTION
With regards to PV initialization, please note that:
• calculations that don't involve time use the normal equation.
• if PV filtering is configured, the filter dynamics are initialized to steady
state.

Control initialization purpose

Control initialization allows normal control strategies to be re-established after they have
been interrupted without "bumps" in the output to the process, and without the need for
manual balancing of values to avoid such bumps.

302 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 26 Regulatory Control Points
26.7 Initialization Logic

Functions of control initialization

Control initialization compensates for changes that may have occurred since the normal
control strategy was last operating. For example, an operator might have taken over
control of the output to the process, so that it now has a value that is different than
normal processing would calculate. The initialization procedures automatically readjust
either the bias value in the data point(s) or an input to the data point(s) so that when
normal control is reestablished, the output to the process does not move or "bump."
For the control algorithms, the new value is back-calculated for an input that absorbs any
output change. This value and an initialization request are sent to the primary data point
that provides the input. Thus, the primary absorbs the change and it must take similar
action with its own primary, if it has one, so that the whole strategy can absorb the
change.
Control initialization paths
By configuring a control output connection from one point (primary) to an initializable
input to another point (secondary) an initialization path is created. It is along this
initialization path that a value is transferred for use by a primary to absorb external
process-upsets that may have occurred at the secondary.
Two or more active paths from a single primary to multiple secondaries are referred to as
"fan out" connections. Where there are two or more control output connections from a
primary to two or more secondaries and all of these outputs are indisposable, the primary
goes into the initialization state.
The value that is to be protected from a bump (the value to back-calculate from) is
obtained at the point's output or at the secondary's initializable input. When "fan out"
connections to more than one output are used, the Regulatory Control output is initialized
from the first disposable secondary.
At each point-processing pass, information is retrieved from all secondaries to which the
data point has control output connections. The initialization data retrieved includes
• Initialization Request.
• Initialization Value.

R688 HPM High-Performance Process Manager Control Theory 303

08/2019 Honeywell
26 Regulatory Control Points
26.7 Initialization Logic

Control initialization requests from a secondary

An initialization request from the secondary causes the control output connection on the
primary to go to an "output indisposable" state, a condition where a newly generated
output to the secondary has no effect on the secondary. A control output connection also
has "output indisposable" status if an error has been detected when the initialization
request and initialization value should have been received.
When all connections from a primary are in the "output-indisposable" state, the primary
is forced to the initialized state. This causes the primary to set its initialization request. In
turn, this may cause the control output connection of a preceding primary to assume the
"output indisposable" state and may force that primary to be initialized as well. In this
manner, the initialization state is propagated upstream to all interconnected primaries.
Control initialization state
During the initialization state, each point remains in that state until a disposable output
connection is found. For points with:
• one control output connection, the primary sets its output value to the initialization
value received from its secondary while in the initialized state.
• two or more control output connection, the primary sets its output value to the
initialization value received from its secondary on the first processing pass when a
disposable output connection is available.
When initialization is being performed for a control strategy, each data point's output is
readjusted by back-calculating an initializable input or by an internal (bias) adjustment.
When each point resumes normal calculations, the new output and the input value at its
secondary are balanced and no bump occurs.
Indisposable outputs are not the only factor for triggering initialization. It is possible to
force a back-calculation by writing to a point's output while it is in MANual mode, or a
user program or a logic slot can set the control initialization flag in a point. For these
cases, the point does not go to the initialization state but its primary may, because the
point sent an initialization request to the primary.
Special handling is provided for connections to local I/O (for example, Analog Outputs
or Digital Pulse Width Modulated Outputs). In the event that communication with the
local output module is lost, the mode automatically goes to MANual to permit the
operator to take control. When communication with the module is restored, back
initialization to the output value occurs automatically. The operator can then return the
strategy to the desired mode. This handling is triggered by loss of communications on the
I/O link, failure of the I/O processor, or an I/O processor-detected power outage.
Events causing control initialization
The need to initialize a data point is indicated by external upsets that directly affect the
point or it is indicated by an initialization request from a secondary data point.

304 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 26 Regulatory Control Points
26.7 Initialization Logic

Control initialization is caused by any of the following:

• A user program or logic slot has requested initialization (see “Control initialization
forced by a program or logic slot” in Section 26.7).
• The point is active for the first time (an inactive to active transition).
• The point is executing the first time after a warm HPM restart.
• All control output connections were indisposable and now one or more output
connections are disposable.
− A control output connection is indisposable when a secondary has made an
initialization request, or
− A communication/configuration error has been detected in retrieving an
initialization request and initialization value from a secondary.
Reasons a secondary data point requests initialization
The following are the reasons why a secondary data point sends an initialization request
to its primary data point:
• The secondary isn't in Cas mode.
• The secondary is inactive.
• The initializable input to the secondary (the destination of the primary's control
output connection) is not selected for a secondary that uses the Switch algorithm
(configured for PV tracking) or the input is being bypassed by the Override Selector
algorithm.
• The secondary is in the initialization state.
Control initialization of a point in the same HPM
For a primary and a secondary that are both in the same HPM, an enhancement is
provided. This enhancement presents the operator with an immediate indication of
initialization when a cascade strategy is opened or closed.

R688 HPM High-Performance Process Manager Control Theory 305

08/2019 Honeywell
26 Regulatory Control Points
26.8 Target Value Processing

Control initialization forced by a program or logic slot

A user-written program or a logic slot can cause a data point to initialize by setting the
data point's control initialization-request flag (CTRLINIT). The next time the point is
processed, it initializes. CTRLINIT is cleared when the processing pass is complete. An
initialization request is sent to its primary, thus propagating initialization up through the
control strategy.
Limit checking during control initialization
Limit checks apply during initialization except for output rate-of-change limits.
Indication of initialization
The HMI display will indicate a data point is initializing when that point is viewed. INIT
appears in the point-status field that is just below the mode indicator on a group display
or a detail display.

26.8 Target Value Processing

Applicability

ATTENTION
Target Value Processing applies only to the Pid, PosProp, PIDPosPr, and
RatioCtl algorithms.

Setpoint Handling
Setpoint handling takes place only if the configured control algorithm requires a setpoint.
Setpoint-handling functions are as follows:
• Setpoint (SP) limits.
• SP Target-Value processing.
• PV Tracking.
• Deviation Alarming.
• Advisory Deviation-alarm processing.
• Ratio and bias options.
• Setpoint Restrictions.
Setpoint access restrictions in PID Algorithms
The table on the next page defines the activities that may write a value into the SP for
PID-based regulatory control points. Also refer to Setpoint access restrictions in non-PID
Algorithms as required.

306 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 26 Regulatory Control Points
26.8 Target Value Processing

Table 26-8 PID-Based Regulatory Control Algorithm Setpoint Access

MODE BOX-IDLE RCASOPT PID Algorithms

or ATTRIB
POINT PVTRK = ON PVTRK = OFF
ACTIVE
or MODE ATTRB MODE ATTRB
INITMAN
OPR PRG OPR PRG

MAN No Any I I Opr Prg1

Yes Any I I Opr Prg1

Auto No Any Opr Prg1 Opr Prg1

Yes None I I Opr Prg1

SPC I I Opr Prg1

DDC I I Opr Prg1

DDCRSP I I Opr Prg1

RSP RC RC RC1 RC1

CAS No None PC PC PC PC

SPC RC RC RC RC

DDC I I PC PC

DDCRSP RC RC RC RC

RSP PC PC PC PC

Yes None I I NCH NCH

SPC I I NCH NCH

DDC I I NCH NCH

DDCRSP I I NCH NCH

RSP I I NCH NCH

BCAS No Any PC PC PC PC

R688 HPM High-Performance Process Manager Control Theory 307

08/2019 Honeywell
26 Regulatory Control Points
26.8 Target Value Processing

MODE BOX-IDLE RCASOPT PID Algorithms

or ATTRIB
POINT PVTRK = ON PVTRK = OFF
ACTIVE
or MODE ATTRB MODE ATTRB
INITMAN
OPR PRG OPR PRG
Yes Any I I NCH NCH

I — SP is being initialized, no change permitted.

Opr — Operator from group or detail display.
Prg — Discontinuous CL programs or sequence programs.
PC — HPM cascade. Mainly the output connections from another control slot in this
HPM or another HPM.
RC — Remote cascade. These include: continuous CL programs on LCN, output
connections from regulatory points in the AM, or user computers on the LCN.
NCH — Operator from group or detail display.
1 — Operator from group or detail display.

308 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 26 Regulatory Control Points
26.8 Target Value Processing

Setpoint access restrictions in non-PID Algorithms

The following table defines the activities that may write a value into the SP for non-PID-
based regulatory control points. Also refer to Setpoint access restrictions in PID
Algorithms as required.

Table 26-9 Non-PID-Based Regulatory Control Algorithm Setpoint Access

MODE BOX-IDLE RCASOPT MODE

or ATTRIB
POINT ACTIVE OPR PRG
or
INITMAN

Man No Any I I

Yes I I

AUTO No Any Opr Prg1

Yes None I I

SPC I I

DDC I I

DDCRSP —— ——

RSP —— ——

CAS No Any PC PC

SPC RC RC

DDC I I

DDCRSP —— ——

RSP —— ——

Yes None I I

SPC I I

DDC —— ——

R688 HPM High-Performance Process Manager Control Theory 309

08/2019 Honeywell
26 Regulatory Control Points
26.8 Target Value Processing

MODE BOX-IDLE RCASOPT MODE

or ATTRIB
POINT ACTIVE OPR PRG
or
INITMAN

DDCRSP —— ——

RSP —— ——

BCAS No Any PC PC

Yes Any I I

I — SP is being initialized, no change permitted.

Opr — Operator from group or detail display.
Prg — Discontinuous CL programs or sequence programs.
PC — HPM cascade. Mainly the output connections from another control slot in this HPM or
another HPM.
RC — Remote cascade. These include: continuous CL programs on LCN, output
connections from regulatory points in the AM, or user computers on the LCN.
NCH — Operator from group or detail display.
1 — Operator from group or detail display.

Setpoint limits
Setpoint limit parameters SPHILM and SPLOLM prevent setpoint values from exceeding
user-configured high and low limit values. These limits are configured in the same
engineering units as the SP and must be within the SP range plus extensions. Crossover
of setpoint limits is not allowed. The configured setpoint limits also apply to the
advisory-target value.
Setpoint limits are observed in initialization calculations. If the limits are violated by the
SP value, anti-reset windup-status propagation is invoked.

310 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 26 Regulatory Control Points
26.8 Target Value Processing

Setpoint target-values
This option allows an operator or a user-written program to "ramp" the setpoint from the
current value to a new value over a period of time. The option is configured through the
Data Entity Builder by entering TV in setpoint option parameter SPOPT.

If the SP is to be ramped by... then the mode attribute (MODATTR) must be...

an Operator Oper

a User-Written Program Prog

The standard process for entering and initiating a new SP target-value is: Once the
procedure is complete, when RAMPTIME = 0, SP reaches the new value and the status
in TVPROC changes to Off.
1. The desired new SP value in SPTV is entered.
2. The ramp time (in minutes) in RAMPTIME is entered.
3. Run is entered through TVROC.
4. The SP begins moving linearly toward the new value and the value in RAMPTIME
decreases with time.

ATTENTION
Actions 1 and 2 cause the TVPROC parameter to go to Preset if the point is
in the Auto mode, INITMAN is Off, and TVPROC is Off.
TVPROC (Action 3) can be changed to the Run state only from the Preset
state.

While TVPROC contains either Preset or Run, SP high and low limits, and the SP high
and low engineering-unit ranges can't be changed. The following applies to TVPROC if
it is in the Run state:

If... then the...

Mode is changed to Man state goes to Preset

Mode is changed to Cas state goes to Off

INITMAN is True state goes to Preset

a store SP operation is performed state is forced to Off

SPTV > SP and the SP1 is Hi or LoHi SP stops changing

R688 HPM High-Performance Process Manager Control Theory 311

08/2019 Honeywell
26 Regulatory Control Points
26.8 Target Value Processing

If... then the...

SPTV > SP and the SP1 is not Hi or LoHi SP ramping continues from the stop position2

SPTV < SP and the output1 is Lo or HiLo SP stops changing

none of the above are True SP is ramped to SPTV2

1 indicated by ARWNET parameter.

2 when SP is ramping, ARWNET is not shown of Group or Detail displays.
• SP may normally be inferred from the output windup status.
• ARWNET may be accessed from a custom display.

Tolerance Check
Release 530 and later provides a function called “SP/OP Tolerance Check.” This function
uses two new parameters, called $SPTOL and $OPTOL, that allow you to configure an
SP (setpoint) and an OP (output) tolerance value.
Manually entered values are checked against the specified tolerance. If the tolerance is
violated in either a plus or a minus direction from the current set value, the operator is
alerted with a beep from the keyboard and a warning message. Operator confirmation is
required before the value is stored.
The tolerance check is made from the Detail Display, Group Display, and in schematic
actors RS_SYS, CHG_ZONE, and USER_CZ.

ATTENTION
The SP/OP Tolerance Check applies to manually entered:
• SP and OP values for the AM, HG, and the NIM Regulatory Control
points.
• OP values for HG and NIM Analog Output points.
• OP values for HG Analog Composite points.

312 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 26 Regulatory Control Points
26.8 Target Value Processing

Deviation Alarming
Configuration
Deviation (PV-SP) high and low alarms can be configured by using the alarm trip points
provided by the DEVHITP and DEVLOTP parameters. In addition, alarm priorities can
be established for these trip points by using the DEVHIPR and DEVLOPR parameters.
Parameters DEVHIFL and DEVLOFL are used as flags to indicate that a deviation (high
or low) alarm has been detected. This alarm returns to normal when the deviation (PV-
SP) is less than or equal to the configured trip point minus a deadband equal to 10% of
the trip point value.

Advisory deviation alarming

This option allows an operator to manually change the SP to a predetermined value. The
predetermined value is usually calculated by a user-written program that stores the value
in advisory setpoint parameter ADVSP rather than storing it directly in SP. Advisory-
deviation alarming is selected by entering Asp for setpoint option parameter SPOPT.
This alarm type is available if the RegCtl point has been configured as a full point. When
this option is selected, an alarm is generated if the difference between the PV and the
value in ADVSP is greater than the trip-point value in ADVDEVTP. This alarm returns
to normal when the difference between the PV and ADVSP is less than or equal to the
value in ADVDEVTP minus a deadband equal to 10% of the trip-point value.
The following conditions must be true if advisory-deviation alarming is to function:
• SPOPT = Asp
• ADVDEVTP < > NaN
• ASPROC = Enable
• PV alarm status in PVVALST < > Bad
• Alarm-enable status in ALENBST < > Inhibit

ATTENTION
If the advisory-deviation alarm is present and the value of one of the above-
listed configuration parameters is changed, the advisory-deviation alarm is
reset.
If parameter ASPPROC = Disable, the value in ADVSP equals the value in
SP.

Bad output alarm

The Regulatory Control point's Bad Output Alarm option (when enabled) generates a
process alarm if one or more of the configured output connections to Analog Output or
R688 HPM High-Performance Process Manager Control Theory 313
08/2019 Honeywell
26 Regulatory Control Points
26.8 Target Value Processing

Digital Output points are broken. Broken means data cannot be pushed to a point. This
alarm is cleared when all connections to the AO or DO points are good, or when the Bad
Output Alarm Option is disabled.
Ratio and Bias options

ATTENTION
Ratio and Bias options apply only to the PID algorithms.
If SP target value processing or advisory deviation alarming is configured for
a RegCtl point, the ratio/bias options cannot be configured for the same data
point.

The ratio and bias options are configured by entering one of the following values in ratio
and bias option parameter RBOPT:
• FixRatBi—Fixed Ratio and Bias
• AutoRat—Auto Ratio and Bias
• AutoBi—Fixed Ratio and Auto Bias
If one of these options is configured, the SP is modified before being used by the PID
algorithm as follows (where SP_Store_Value is the setpoint before the modification):
SP_Store_Value*RATIO + BIAS
In normal operation (in Cas mode and INITMAN is Off), all three options work alike.
RATIO and BIAS can be changed by a Universal Station operator or by user-written
programs (depending on whether MODATTR contains Oper or Prog).
During initialization of this point, however, RATIO and BIAS can be changed only if
they are not being initialized, based on the value in RBOPT, as follows:
• FixRatBi—The initialization value calculated for this point's primary is—
RINITVAL = (SP - BIAS)/RATIO
• AutoRat—RATIO is initialized as—
RATIO = (SP - BIAS)/Store Value
If either RATIO or BIAS attempt to go outside one of their limits, it is clamped at the
limit, and INITVAL is calculated as defined in the following table.
Table 26-10 INITVAL Calculation with RATIO or BIAS Clamped

Ratio/Bias Calculation

RATIO INITVAL = (SP - BIAS)/RATIO

...then AutoBi is initialized as:

314 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 26 Regulatory Control Points
26.9 PV Tracking

Ratio/Bias Calculation
BIAS = SP - (Store_Value*RATIO)
BIAS INITVAL = (SP - BIAS)/RATIO

Ratio limits
You can configure high and low limits for the RATIO value that can be applied to the
setpoint for Pid Algorithms. A Universal Station user with a Supervisor key can change
these limits. An operator is not allowed to enter a value that exceeds these limits. If a
user-written program attempts to store a value outside the limits, it is clamped to the
limit. Crossover of these limits is prohibited.
You configure RATIO limit values using:
• RTHILM—Ratio high limit
• RTLOLM—Ratio low limit
Bias limits
Two user-setable Hi and Lo limits on the SP-related bias parameter are provided.
Whenever operator or program entries are outside the limits, the entries are clamped to
the closest limit. Crossover of limits is inhibited.
You can configure high and low limits for the BIAS value that can be applied to the
setpoint for PID algorithms. A Universal Station user with a Supervisor key can change
these limits. An operator is prohibited from entering a value exceeding these limits. A
user-written program is clamped to the exceeded limit. Crossover of these limits is
prohibited.
You configure BIAS limit values using:
• BSHILM—Bias high limit
• BSLOLM—Bias low limit

26.9 PV Tracking
Applicability

ATTENTION
PV Tracking applies only to the Pid algorithms.

Configuration
PV tracking is configured by entering Track for the PVTRACK parameter. During PV
tracking, SP is set equal to PV whenever the cascade is broken by an operator or a

R688 HPM High-Performance Process Manager Control Theory 315

08/2019 Honeywell
26 Regulatory Control Points
26.10 Control Algorithm Calculation

program action, or the RegCtl point is a secondary (in a local cascade strategy) and the
cascade is momentarily interrupted by a 1-shot initialization.
Occurrence
PV tracking occurs when:
• Mode is Man.
• Mode is Cas and RCASOPT is Ddc.
• INITMAN is On.
• RegCtl point is being processed for the first time after becoming active.
• RegCtl point is a secondary within a local cascade-control strategy (inside the same
HPM), and it is going through a 1-shot control initialization, which occurs when—
− the control initialization-request flag CTRLINIT is On.
− the point is being processed for the first time after the HPM state has changed to
Run.
− just recovering from a bad PV.
− this slot has only one disposable secondary that just underwent 1-shot
initialization.

ATTENTION
PV tracking (even if configured) is not done on return from a Bad PV.

26.10 Control Algorithm Calculation

Windup protection
PID algorithms are protected from windup caused by reset action. Windup status
parameters are maintained that pass the status "upstream" to the primary points along the
initialization path. Each PID algorithm checks its output windup status and takes
appropriate action to prevent reset windup. These functions are standard and require no
configuration by the user.
Windup status
The following parameters contain windup-status information:
• ARWOP—Output (OP) windup status.
• ARWNET—Windup status for SP or another initializable input.
When this point's ARWOP contains something other than Normal, integral control in the
windup direction stops. Integral action in the other direction and P and D action
continues.

316 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 26 Regulatory Control Points
26.10 Control Algorithm Calculation

For the remainder of the control subsystem, the windup status serves only as a warning,
and not as a constraint. For example if the status in ARWNET is Lo, lowering SP won't
have an immediate effect on the output of the final secondary; however, SP can be
lowered if the SP low-limit has not yet been reached.
The values in the windup-status parameters indicate whether raising or lowering the
associated parameter value will affect the output of the final secondary, as it should. The
values for parameters ARWNET and ARWOP are as follows:
• Normal—Free to move in either direction.
• Hi—Free to move only in the lower direction.
• Lo—Free to move only in the upper direction.
• HiLo—Not free to move in any direction.
With R670 and later, when OUTIND is set to Reverse, the values of the displayed output
and the related output parameters are changed. However, the value of the Output
Indication does not affect the actual or the displayed values of the ARWOP parameter.

R688 HPM High-Performance Process Manager Control Theory 317

08/2019 Honeywell
26 Regulatory Control Points
26.11 Control Output Processing

Windup status propagation

Windup status is propagated to ARWOP and ARWNET of the same point, and then from
ARWNET of the secondary point to the primary point, and so on.
Propagation from secondary to primary is instantaneous if both are in the same process
unit and the same HPM. Otherwise, it takes place on the next processing pass for each
point.

26.11 Control Output Processing

Purpose
The primary task of control output processing is to make the control algorithm
calculation available to the rest of the system (displays, printers, CL programs, other data
points, and so on). Control algorithms are produced and provided in percent or
engineering units (EUs) as needed.
Functions
Control output processing performs the following functions:
• Provides the output value in percent and EUs for displays, printing, CL programs,
and for interpoint communications.
• Processes control output connections that send the output to the secondary data point
after conversion to EUs.
• Constrains the output to the configured limits.
• Generates and propagates windup status as a result of a violation an output limit.
Accessible output parameters
The following table lists and defines the parameters which contain and provide
significant output-processing information. All are accessible for displays and printing,
and can be accessed by programs written in CL.

318 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 26 Regulatory Control Points
26.11 Control Output Processing

Table 26-11 Regulatory Control Point HMI Accessible Output Parameters

Parameter Definition

CV The result (calculated value) of calculation of the control algorithm,

can be in percent or EU depending upon the control algorithm.

OP The final control output, expressed as % of EU Range of the

output.

OPEU Final control output in Engineering Units.

CVEUHI Output EU Range corresponding to 100% value of OP.

CVEULO Output EU Range corresponding to 0% value of OP.

Initial control processing

During initial control processing, initialization data is fetched from the secondary points
indicated by each control output connection.
The output engineering-unit range in CVEULO and CVEUHI is determined, based on the
EU range of the secondary pointed to by the first active control output connection. If this
connection has a communication or configuration error, the output range is set to bad and
the point is aborted. If this happens, the CI connections and CO connections, scheduled
for execution after initial control processing are not processed.
Normal computation
The normal computation process is as follows:
1. CV is calculated by the control algorithm.
2. OP is calculated from CV, with the units based on the range defined by CVEULO
and CVEUHI. Note that the values in CVEULO and CVEUHI are determined by
the engineering-units range of the secondary point to which the first active
connection is made.
3. OP is checked for minimum output change, output rate-of-change, output high-
limit, and output low-limit. If any of the limits is exceeded, the OP value is adjusted
or clamped as applicable.
4. The windup status is set.
5. Each control output connection is processed individually. If the control output
connection is disposable, then the—
− corresponding value in the secondary point is made equal to OP, if the
destination parameter is OP, otherwise it is made equal to OPEU.

R688 HPM High-Performance Process Manager Control Theory 319

08/2019 Honeywell
26 Regulatory Control Points
26.11 Control Output Processing

− OP or OPEU value is transferred to the secondary's destination parameter,

subject to applicable limits on the destination parameter (for example, SP
limits).
In Manual Mode
When in manual mode (MAN):
1. OP is set (in percent) by an operator or by a user-written program, depending on the
attribute.
2. Each control output connection receives normal processing, as described above.
Remaining process is as defined under "Normal Computation."
From secondary data-point
When initializing because of a request from a secondary data-point:
1. If all of the control output connections are indisposable, CV is initialized to its last
value. When the first disposable control output connection becomes available, the CV
is back-calculated (% to EU conversion if the destination parameter is OP) from the
destination parameter of the secondary.
2. OP is calculated from CV, based on CVEULO and CVEUHI.
Output High and Low Limits
You can configure high- and low-limit values for the RegCtl point output using
parameters OPHILM and OPLOLM . These limits are expressed as a percentage of the
output range and the limit values can range from -6.9% to 106.9%. A Universal Station
user with a Supervisory key can change these limits. Crossover of these limits is not
permitted.
When an output limit is reached or exceeded, windup status is propagated up through
cascade strategies.
ATTENTION
Using AM/PM CL, if you attempt to configure OPHILM/OPLOLM value
beyond the current $MOPHILM/$MOPLOLM value, then this operation
clamps the OPHILM/OPLOLM value at the $MOPHILM/$MOPLOLM value.

Output Rate-of-Change Limits

You can configure a maximum rate of change in percent-per-minute for output values of
RegCtl points using the OPROCLM parameter. The effect of this limit is to reduce
excessive rates of change in the output, to the limit. The smallest limit can't be less than
0.1 percent per point-processing interval. The default value for the limit is NaN, which
eliminates the limit check.

320 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 26 Regulatory Control Points
26.11 Control Output Processing

Typically, the output rate-of-change limit is used to match the slew rate of the final
control element to the control dynamics.
Use caution when setting the value of OPROCLM. This value should be set before loop
tuning has taken place. When done this way, tuning accommodates any slow down in
response time caused by rate limiting. If OPROCLM is changed after a loop has been
tuned, it is possible for poor loop dynamics or even instability to result.
Note that when a choice is available, rate limiting should be applied to PID algorithms
(PID, PIDFF, and PIDERFB) rather than regulatory control algorithms of other types.
The PID algorithms support special processing to prevent windup of the CV during rate
limiting. Other algorithms cannot provide this special processing.
Output Minimum-Change Limit
You can configure a minimum output-change value for RegCtl points using parameter
OPMCHLM. This value is a percentage of the output-value range. If the absolute
difference between the output value at one processing pass and the next doesn't equal or
exceed the minimum change, the earlier value is maintained. A Universal Station user
with a Supervisory key can change the minimum output-change value.
The default minimum output-change value is NaN, which eliminates the minimum
change check.
This feature is used to minimize "wear and tear" on the final control device.
Output Limiting in Manual Mode
Control output connections are used to establish initializable cascade connections
between the output of the RegCtl point output and other points. Control output
connections are accomplished through parameter CODSTN. To assign the RegCtl output
to the parameter of another data point, the user can choose from one of the following two
output connection conventions (Tagname.Parameter or hardware reference address):
Tagname.Parameter
or
!MTmmSss.Parameter
Where:
1. MT is the IOP type (AO or DO).
2. mm is the IOP number in the HPM file, from 1 to 40.
3. ss is the slot number from 1 to 8 for analog outputs, and from 1 to 16 for digital
outputs.
4. Parameter is the parameter in the AO, DO point to which this output value is to be
written.

R688 HPM High-Performance Process Manager Control Theory 321

08/2019 Honeywell
26 Regulatory Control Points
26.11 Control Output Processing

Up-to-four output connections can be configured for a RegCtl point. Initialization and
wind-up protection are supported for multi-output configurations.

ATTENTION
Fieldbus does not support a control connection output when the Regulatory
Control point is configured for the PIDERFB algorithm.

The RegCtl data point can write the output value to only the following destination
parameters:
1. SP, RATIO, X1, X2, X3, and X4 parameters of another RegCtl data point in the same
HPM. When a control output connection is made to the RATIO parameter, the ratio
high and low limits on the secondary are used as its engineering unit range. Also the
secondary should be configured for a ratio bias option of auto ratio and placed in
Program Cascade mode for the initialization to work correctly.
2. X1 parameter of a RegCtl data point in another HPM or APM on the same UCN.
3. SP parameter of a RegCtl point in another HPM, APM, or PM on the same UCN.
4. OP parameter of an analog output point in the same HPM. The component form of the
output connection can be used to connect to an AO point that has been configured as a
component point. The following restrictions apply:
− The total number of control input and output connections fetching data from the
I/O Processors must not exceed seven (prefetch limit updated in R600).
− The analog output slot must be configured as a component point.
− The output destinations cannot be a mix of IOPs and RegCtl points.
5. OP parameter of a digital output point that has been configured for pulse-width
modulation in the same HPM.
− The total number of control input and output connections fetching data from the
I/O Processors must not exceed seven (prefetch limit updated in R600).
6. Any addressable parameter of any accessible slot if the configured control algorithm
is PidERFB.

ATTENTION
When a Regulatory Control point output is connected to the setpoint of a
RegCtl point in another HPM, APM, or PM on the same UCN , it counts as
one input and one output for the purpose of limiting the number of
input/output connections going across HPMs.

322 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 26 Regulatory Control Points
26.11 Control Output Processing

Option to configure OP limits in MAN mode

Beginning with TPN R686, you can additionally configure OP limits for HPM
Regulatory Control points in the MAN mode, to clamp the OP value to the AO channel.
This configuration can be achieved using the two new parameters:
Parameter Default value Range

$MOPLOLM -6.9 (R686.1-R686.4, -6.9% to OPLOLM and

R687.1-R687.3, NaN
R688.1)
NaN (R687.4 and
R688.2)
$MOPHILM 106.9 (R686.1-R686.4, OPHILM to 106.9%
R687.1-R687.3, and NaN
R688.1)

NaN (R687.4 and

R688.2)
Users with Engineer access can set manual OP limit parameters.
These new parameters are not dependent on any trip parameters as they are applicable in
MAN mode only. They will not be operational in the non-manual modes like AUTO,
CAS or PROG.

ATTENTION
The $MOPHILM and $MOPLOLM values can only be modified in MAN mode
with OPERATOR mode attribute (for example, Detail Display, Data Entity
Builder, DATACHG schematic, and ramp keys). Changes to these values are
not allowed from AM/PM CL or peer controllers.

ATTENTION
Using AM/PM CL, if you attempt to configure OPHILM/OPLOLM value
beyond the current $MOPHILM/$MOPLOLM value, then this operation
clamps the OPHILM/OPLOLM value at the $MOPHILM/$MOPLOLM value.

This functionality does not modify point behavior in any mode. The existing limits, trip
points and all associated features like control action, clamping and alarming of the
RegCtl points remain unaffected due to this new functionality.

R688 HPM High-Performance Process Manager Control Theory 323

08/2019 Honeywell
26 Regulatory Control Points
26.11 Control Output Processing

The change events for the new parameters will be logged in the operator process change
events journal as existing for the OPHILM and OPLOLM parameters.
This functionality does not modify or improve the point processing.
Shown here are a few examples to depict the behavior of RegCtl points when OP values
are moved beyond the range of the new parameters ($MOPLOLM, $MOPHILM).
OP value modification in MAN mode
The OP value cannot be moved beyond the set manual limits; however, the existing OP
limits, OPHILM and OPLOLM shall have no impact on the OP in MAN mode.
The following are few example scenarios,
OP value moved over $MOPHILM:
• OPHILM is set to 90 and $MOPHILM is set to 95.
• RegCtl point is in MAN mode.
• Operator enters a value of 92 to OP.
• RegCtl point accepts the value of 92.
• Operator enters a value of 96.
• RegCtl points throws an error retaining the previous entered value of 92, since the
value of 96 exceeds $MOPHILM.
• Change the RegCtl point mode to AUTO.
• OP value goes to the OPHILM limit causing a bump in the OP value.

OP value moved below $MOPLOLM:

• OPLOLM is set to 10 and $MOPLOLM is set to 5.
• RegCtl point is in MAN mode.
• Operator enters a value of 8 to OP.
• RegCtl point accepts the value of 8.
• Operator enters a value of 4.
• RegCtl points throws an error retaining the previous entered value of 8, since the
value of 4 is lesser than $MOPLOLM.
• Change the RegCtl point mode to AUTO.
• OP value goes to the OPLOLM limit causing a bump in the OP value.

324 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 26 Regulatory Control Points
26.11 Control Output Processing

AUTO mode and MAN mode limits are set at the same value:
• OPHILM and $MOPHILM is set to 90.
• RegCtl point is in MAN mode.
• Operator enters a value of 92 to OP.
• RegCtl points throws an error retaining a value of 90, since the value exceeds
$MOPHILM.
• Change the RegCtl point mode to AUTO.
• OP value goes to the OPHILM limit causing a bump in the OP value.

AUTO mode and MAN mode limits are left at their default values.
• OPHILM = 105.0; $MOPHILM = NaN; OPLOLM = -5.0; $MOPLOLM = NaN.
• RegCtl point is in AUTO mode.
• OP value can reach up to a maximum of 105 and gets clamped at 105
• Switch the mode to MAN.
• Operator can enter a value up to 106.9.

Note: The behavior is the same on the lower limits as well.

Manual OP limit values set over or below OP value - changes to $MOPHILM or

$MOPLOLM will not immediately cause a change to the current OP value in MAN
mode. The new limits will be checked on the next value stored for OP.
• $MOPHILM = 102; OP = 100.
• RegCtl point is in MAN mode.
• Operator tries to set $MOPHILM = 92.
• Limit value accepted and OP value stays at 100.
• $MOPLOLM = 10; OP = 12.
• Operator tries to set $MOPLOLM = 20.
• Limit value accepted and OP value stays at 12.

Note: The OP value in MAN mode is tied to $MOPHILM/$MOPLOLM and in non-

MAN mode, it is tied to OPHILM/OPLOLM respectively.

R688 HPM High-Performance Process Manager Control Theory 325

08/2019 Honeywell
26 Regulatory Control Points
26.11 Control Output Processing

OP value modification in MAN mode using ramp keys

ATTENTION
If the OP value exceeds either $MOPHILM/$MOPLOLM MAN limit while
using the ramp keys, then the value is clamped at the appropriate limit and a
value clamped error is reported.

Sudden change in OP value

A sudden change in the OP value can occur if the mode is changed from MAN to AUTO
or if the ramp keys are used after a change to either MAN limit:
• RegCtl point is in MAN mode.
• OPHILM=90, $MOPHILM = 100; OP = 100.
• Change the RegCtl point mode to AUTO.
• OP value goes to the OPHILM causing a bump in the OP value.
• RegCtl point is in MAN mode.
• Set OP = 100
• Change $MOPHILM to 90.
• $MOPHILM changes to 90 while OP value remains at 100
• Using the slow ramp key change OP to either direction.
• The OP value suddenly changes to 90.
Note: The behavior is similar in case of lower limits ($MOPLOLM).

$MOPHILM/$MOPLOLM value modification in MAN mode

$MOPHILM value moved over or below OPHILM:
• OPHILM is set to 90.
• RegCtl point is in MAN mode.
• Operator enters a value of 92 to $MOPHILM.
• RegCtl point accepts the value of 92.
• Operator enters a value of 80 to $MOPHILM.
• RegCtl points returns an error retaining a value of 92.

326 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 26 Regulatory Control Points
26.11 Control Output Processing

$MOPLOLM value moved over or below OPLOLM:

• OPLOLM is set to 20.
• RegCtl point is in MAN mode.
• Operator enters a value of 10 to $MOPLOLM.
• RegCtl point accepts the value of 10.
• Operator enters a value of 30 to $MOPLOLM.
• RegCtl point returns an error retaining a value of 10.

ATTENTION
The $MOPHILM and $MOPLOLM values can only be modified in MAN mode
with OPERATOR mode attribute (for example, Detail Display, Data Entity
Builder, DATACHG schematic, and ramp keys). Changes to these values are
not allowed from AM/PM CL or peer controllers.

AM/PM CL writes to OPHILM/OPLOLM value

Using AM/PM CL attempting to write OPHILM/OPLOLMvalue beyond current
$MOPHILM/$MOPLOLM value clamps the OPHILM/OPLOLM value at the
$MOPHILM/$MOPLOLM value.
• OPHILM is set to 80.
• $MOPHILM is set to 90.
• AM/HPM CL attempts to store 100 for OPHILM.
• OPHILM is clamped to 90.
• OPLOLM is set to 20.
• $MOPLOLM is set to 10.
• AM/HPM CL attempts to store 0 for OPLOLM.
• OPLOLM is clamped to 10.

R688 HPM High-Performance Process Manager Control Theory 327

08/2019 Honeywell
26 Regulatory Control Points
26.11 Control Output Processing

Output High/Low alarms

With R510 and later software, an Output High or Output Low alarm is set when a
Regulatory Control point's output value (OP) exceeds the configured high or low alarm
limit. The alarm is removed when the value of OP returns toward normal past a
configurable deadband.
The following parameters deal with the Output Alarms and are configurable for each
point:
1. OPHITP/OPLOTP contain the Output High/Low Alarm trip points.
2. OPHIPR/OPLOPR contain the Output High/Low Alarm priorities.
3. OPHAFL/OPLAFL contain the Output High/Low Alarm flags.
4. OPALDB contains a deadband for the Output Alarms.
The output alarms are only available for Regulatory Control points configured as full
points and are disabled if the trip points are not specified.
Tolerance Check

REFERENCE - INTERNAL
A Tolerance Check function applies (Release 530 and later) to the OP. For
details of this function, refer to Tolerance Check under Regulatory Control
Points, Target Value Processing.

Output Indication
The OUTIND parameter defines how the output of a regulatory data point is to be
displayed at the Universal Station. The output display is determined by the selection of
the value range, which can be:
• Direct = A 4 mA output from this data point is displayed as 0% at the Universal
Station. A 20 mA output is displayed as 100%.
• Reverse = A 20 mA output from this data point is displayed as 0%. A 4 mA output is
displayed as 100%.
With R670, when the value of OUTIND parameter is set to Reverse, the output
indication for the output alarm trip points (OPHITP and OPLOTP) and output limits
(OPHILM and OPLOLM) are reversed. The output indications for output alarm priorities
(OPHIPR and OPLOPR), output alarm flags (OPHAFL and OPLAFL), and output limit
exceeded flags (OPHIFL and OPLOFL) are swapped.
This option is applicable to the following regulatory-control point parameters:

328 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 26 Regulatory Control Points
26.11 Control Output Processing

Regulatory Control Point If OUTIND = Direct, the If OUTIND = Reverse, the

Parameters value of the parameter is value of the parameter is
displayed as displayed as

OPHITP (OP High Trip Output High Trip point Displayed OPHITP value
Point) value =100.0% - Output Low
Trip point value

OPLOTP (OP Low Trip Output Low Trip point Displayed OPLOTP value
Point) value =100.0% - Output High
Trip point value

OPHIPR (OP High Alarm Output High Alarm Priority Output Low Alarm Priority
Priority) value value

OPLOPR (OP Low Alarm Output Low Alarm Priority Output High Alarm Priority
Priority) value value

OPHAFL (OP High Alarm Output High Alarm Flag Output Low Alarm Flag
Flag) value value

OPLAFL (OP Low Alarm Output Low Alarm Flag Output High Alarm Flag
Flag) value value

OPHILM (OP High Limit) Output High Limit value 100% - Output Low Limit
value

OPLOLM (OP Low Limit) Output Low Limit value 100% - Output High Limit
value

OPHIFL (OP High Flag) Output High Limit Output Low Limit
Exceeded Flag value Exceeded Flag value

OPLOFL (OP Low Flag) Output Low Limit Output High Limit
Exceeded Flag value Exceeded Flag value

SAFEOP (Safe Output) Safe Output value 100.0% –Safe Output

Value

R688 HPM High-Performance Process Manager Control Theory 329

08/2019 Honeywell
26 Regulatory Control Points
26.12 Override Control

When using the OUTIND parameter, Honeywell recommends you to

CAUTION carefully design the logic of the affected parameters as described
below:
For nodes on the LCN:
Before setting the value of OUTIND to Reverse, ensure the AM/CL
programs, the schematics, and the TPS applications can accommodate
the modified behavior of these parameters.
For xPM nodes on the same UCN:
xPM CL programs, peer-to-peer connections, and connections within a
box directly interact with the actual values of the xPM parameters.
Therefore, there is a difference between the actual values used in the
UCN xPM nodes and the displayed values of the affected parameters
that are shown on the LCN nodes.

26.12 Override Control

Purpose
Override control strategies are primarily used for multivariable constraint control. In such
a strategy, control of a single process variable is based on one of two or more PVs. These
multiple PVs are referred to as "constraints." A selector algorithm selects the PV to be
used for control. When a different PV is selected, the former PV has been overridden—
the new PV has constrained the others.
Most often, with override control, the objective is to achieve the best possible control of a
PV without violating any of the constraints. The manipulated variable is driven by the
output of an Override Selector algorithm that selects the highest or the lowest of up to
four inputs. A PID that is in a cascade strategy (but is not selected) is prevented from
winding up with the help of override initialization. In the rest of this section, the term
"O/R selector" is used to mean an Override Selector control algorithm that is configured
for external initialization. Refer to the detailed description of the Override Selector
algorithm in this section.
Applications
The following are example applications for override control:
• Boiler Control, in a typical strategy—
− the constraint on the fuel flow (SP of the fuel-flow PID controller) may be that it
cannot exceed the actual air flow, multiplied by a ratio (which may be computed
by the O2 controller).

330 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 26 Regulatory Control Points
26.12 Override Control

− In this case, the fuel flow is the primary PV to be controlled and the actual air-
flow PV is the "constraint".
• Heating, in some applications—
− it may be desirable to control the temperature of the feed (the primary PV) as
well as possible, without ever letting the temperature of the hottest part of the
pot (or the heat exchanger) exceed a safe limit.
− In this case, the safe limit on the pot temperature is the "constraint".
• Oven Temperature-Control, in a typical application—
− temperatures can be measured at several places in the oven, and it may be
desirable to control all these PVs by controlling one valve.
− One PID controller can be used for each PV, and the PID controller representing
the PV that is farthest from its SP can be allowed to control the valve.
− In this case, there is no primary PV, because all the PVs have the same
importance and each PID controller represents a constraint on the others.

R688 HPM High-Performance Process Manager Control Theory 331

08/2019 Honeywell
26 Regulatory Control Points
26.12 Override Control

Status and feedback

Regulatory Control algorithm data points and Override Selector Control algorithms
contain the parameters provided to support O/R strategies.
Table 26-12 Regulatory Control Override Control Status and Feedback
Parameters

Algorithm Parameter Override Status or Definition

Regulatory PTORST • NotCon – The point is not connected to an O/R selector.
Control Strictly, it means that this point is not on an initializable path to
an O/R Selector or it is now being initialized. PTORST defaults
to this value.
• Sel – The point is a part of an O/R control strategy and is now
selected.
• NotSel – The point is part of an O/R control strategy and is not
selected by the O/R selector.
Override OROPT • When On, the feedback value is propagated to non-selected
Selector primaries of the override selector algorithm.
• When Off, the feedback value is not propagated. However,
non-selected primaries are kept from winding up by
propagating a windup status opposite of the OrSel equation (Hi-
Lo) in addition to the OrSel point windup status (ARWNET) to
the non-selected primaries. This windup status propagation
prohibits the non-selected primaries of the OrSel from winding
up in the direction opposite of the OrSel selection equation.
OROFFSET • When On, PID output is initialized to: Feedback Value + Gain *
Error.
• When Off, PID output is initialized to only the Feedback value.

ATTENTION
The status in PTORST becomes NotCon when:
• the point is returned from inactive to active status.
• it undergoes a cold start.
• it is initialized.

332 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 26 Regulatory Control Points
26.12 Override Control

Processing example

ATTENTION
There must be at least one PID controller in the O/R strategy.
The override status (Feedback Value) can be propagated to a maximum of
five primaries.
All points downstream of the O/R selector are processed at their specified
interval.

The override portion of the control strategy includes the Override Selector point and all
points "upstream" from it. In this example, the points named TAG-A, TAG-B, TAG-C,
TAG-D, and TAG-E constitute the O/R strategy.
1. All points upstream of the O/R selector are processed on normal cycles (highest slot
index to lowest). In the example, the points can be processed in TAG-D, TAG-A,
TAG-B, TAG-C order. Their PV and control algorithms are executed normally. The
next point to be processed is the O/R selector (TAG-E in the example). It selects one
input. Assume input X2 is selected.
2. The O/R selector then propagates appropriate O/R status to each one of its own
initializing primaries. It also propagates the O/R-feedback value to the non-selected,
initializing primaries. In the example, TAG-E propagates O/R status of Sel to TAG-
C because input X2 is selected, and O/R-status Notsel to TAG-B. Further, TAG-E
propagates the O/R-feedback value to the non-selected, initializing primary, TAG-B.
TAG-D does not receive the O/R status nor the feedback value because it is not an
initializing primary.
3. Each primary (provided it is in Cas mode), in turn, propagates O/R status to its own
primaries (if any). It also propagates O/R feedback upstream, if it is not selected. In
the example, TAG-B would propagate Notsel and an O/R feedback value to TAG-A.
4. The propagation upstream continues until there are no more primaries. The output of
any PID in a cascade chain, connected to a non-selected input of the O/R selector is
initialized to override-feedback value, plus gain times deviation (PV-SP) if
OROFFSET is On. If OROFFSET is Off, it is initialized to the override-feedback
value. Because TAG–A contains a PID algorithm and is not selected, it undergoes
O/R initialization.
5. The whole cycle is repeated.

R688 HPM High-Performance Process Manager Control Theory 333

08/2019 Honeywell
26 Regulatory Control Points
26.12 Override Control

Figure 26-3 Override Control Strategy Example

TAG-A TAG-B
PV PV
OP
PID PID
OP
SP SP TAG-E
X1 O/R
TAG-C LO OP
SP SELECT
OP X2
PID
X3
PV TAG-F
To
X1
Secondary
SOME or Valve
TAG-D CONTROL
PV ALGO.
PV ALGO. X2

Multiple override selectors in a strategy

When multiple override selectors are included in a control strategy, the O/R-feedback
propagation is initiated by only the most downstream O/R selector.
In the example override control strategy defined in Override Control, if TAG-F were
also an O/R selector, the O/R strategy would consist of points TAG-A, TAG-B, TAG-C,
TAG-D, TAG-E, and TAG-F. O/R propagation would be initiated by TAG-F and not
TAG-E, as before.
Initialization in an override strategy
When a cascade is broken in an override strategy, initialization propagation supersedes
override propagation.
In the example override control strategy defined in Override Control, if point TAG-B is
placed in Man mode, it doesn't propagate O/R status or an O/R-feedback value to TAG-
A. TAG-A's O/R status then is Notcon.

334 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 26 Regulatory Control Points
26.12 Override Control

Guidelines for using override control

Follow these guidelines to configure properly functioning override strategies:
• Proportional and Derivative Action on PIDs—
− PIDs in an override scheme may be configured with proportional and derivative
action on SP.
− use of these actions should be carefully considered because undesired results
may occur, such as momentary oscillation caused by "kicks" in the error.
• Boundaries—
− the entire O/R strategy must be within the same HPM.
− the number of primaries for initiating the O/R strategy must be less-than or
equal to 5.
• Fanout—
− fanout control output connections are not allowed in an O/R strategy.
− all primaries upstream from the O/R-selector point can have only one control
output connection.

R688 HPM High-Performance Process Manager Control Theory 335

08/2019 Honeywell
26 Regulatory Control Points
26.12 Override Control

336 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 27. PID Control Algorithm
27.1 Functional Overview
Family
The PID control algorithm is a member of the Regulatory Control algorithms.
Purpose
The PID algorithm is used as a controller that either directly moves a control device
(valve) in the process, or provides an input to another data point.
Description
The PID control algorithm is a regulatory control function that operates as a proportional-
integral-derivative (PID) controller. You can choose one of two forms of this algorithm:
the interactive (or real) form and the non-interactive (or ideal) form.
It operates to reduce error in the control loop to zero. Error is represented by the
difference between the process variable in percent (PVP) and the setpoint in percent
(SPP). The control-algorithm output value (CV) is also calculated as a percentage of the
configured engineering-units range for the data point that uses this algorithm.
This algorithm supports all remote cascade options. PV source selection is supported if
the point is configured "full."
Inputs and outputs
As shown in the following figure, the PID algorithm requires only one input connection.
The default for number of input connections is 1; however, it can be increased to 2,
allowing the SP to be fetched with an input connection. When the SP is fetched, the
normal operating mode of the point is usually affected.
Input sources for a secondary include another data point on the same UCN, an AM data
point, or a point properly configured in another CM with proper access level. If the
remote cascade connection is coming from a regulatory data point in the AM, it handles
everything automatically.

R688 HPM High-Performance Process Manager Control Theory 337

08/2019 Honeywell
27 PID Control Algorithm
27.1 Functional Overview

The output of this algorithm is normally "floating," because of the dynamics of the
integral and derivative terms. Internally, the output is calculated as increments of output
change, but the increments are accumulated to provide a full-value output, thus
simplifying the techniques used to achieve "bumpless" outputs when modes or tuning
constants are changed.
Figure 27-1 PID Control Algorithm Functional Diagram

Setpoint Feedforward
From Initializing Processing Signal
Primary
CAS

SPP
To
PIDFF CV OP
AUTO Secondary
PVP
Operator or
User-Written
Program Output
From PV Algo or
I/O Module Processing

PID Forms: Interactive (Real)

Noninteractive (Ideal)
Equations:
A: Full PID
B: PI on error, D on PV change only
C: I on error, PD on PV change only
D: Integral control only

Feedforward Action: Additive, Scale and Add

Multiplicative; Scale and Multiply

Use
If the HPM's PID point is:
• a primary for another data point in the same or another HPM (including APMs and
PMs), then its output is connected to the SP of the other data point (through
Tagname.Parameter).
• directly controlling a valve, then its output is connected to:
− the output of an Analog or Digital IOP through "Tagname.Parameter", or
− the hardware reference address !AOmmSss.OP or !DOmmSss.OP (where mm is
the IOP card number in the HPM, and ss is the slot number of the output on the
IOP card).
• a secondary for another data point, then it can be configured to receive an input from
another source.

338 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 27 PID Control Algorithm
27.2 Options and Special Features

ATTENTION
In all other cases (including the continuous CL programs in the AM directly
writing to the HPM), the you must take care to assure:
• the remote device must.
− use "continuous_control" access level for stores to SP, OP, and
MODE parameters.
− handle mode changes for closing the cascade.
• initialization for bumpless mode transfers.
• windup protection.

27.2 Options and Special Features

Interactive and Non-interactive PID forms
During configuration, you select from one of the following two forms:
• Interactive (Real) Form, which emulates traditional pneumatic-PID controllers.
The advantage of this form is that the poles (lags) and zeros (leads), both of which
must be real, can be easily placed. In this form—
− P, I, and D terms are calculated as the sum of P and I, multiplied by D.
− D interacts in the time domain with the P and I terms.
• Non-interactive (Ideal) Form, which is often called the digital-computer version of
the PID controller. In this form —
− P, I, and D are added in the time domain.
− D is added as a damped derivative to limit peak amplitude.
Engineering Unit ranges
The PV engineering unit range (PVEULO and PVEUHI) must be specified. The setpoint
engineering unit range (SPEULO and SPEUHI) always follows the PV range. The output
engineering unit range (CVEULO and CVEUHI) is derived from the secondary if the
number of output connections is greater than 0, otherwise it must be specified.
Control terms
You select the combinations of proportion, integral, and derivative control terms by
choosing Equation A, B, C, or D. The equations function as follows (see “Equations” in
Section 27.3):
• Equation A—
− all three terms (P, I, and D) act on the error (PV - SP).
• Equation B—
R688 HPM High-Performance Process Manager Control Theory 339
08/2019 Honeywell
27 PID Control Algorithm
27.2 Options and Special Features

− proportional (P) and integral (I) terms act on error (PV - SP).
− derivative (D) acts on PV changes.
− used to eliminate derivative spikes in control action that occur with quick changes
in the setpoint.
• Equation C—
− integral (I) term acts on error (PV - SP).
− proportion (P) and derivative (D) terms act on PV changes.
− provides the smoothest and slowest response to setpoint changes.
• Equation D—
− integral (I) control only.
Single term control
When you use equation A, B, or C, the integral or derivative terms can be eliminated by
setting their time constants to 0. Setting both T1 and T2 to 0 results in only proportional
control.
Use Equation D to achieve only integral control.
Direct and Reverse control action
When configuring a data point that uses the PID algorithm, you can select direct-control
action or reverse-control action. You can also change the control action through the detail
display if you have an engineer's key, or a user-written program can change the control
action. The control action can be changed at the Universal Station or by a program, only
while the data point is in Man mode. The attribute must be appropriate (Oper or Prog) for
the change to be accepted.
Changing the control action effectively changes the sign of the gain. With direct action,
an increase in PV increases output; with reverse action, an increase in PV decreases
output.

TIP

Control Action If the PVP... the Error... and the CV...

Direct
 Increases  Increases  Increases
Reverse
 Increases  Increases  Decreases

340 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 27 PID Control Algorithm
27.2 Options and Special Features

PV tracking
PV tracking is typically chosen when the data point is a secondary in a cascade control
strategy, because it allows the PID to resume control with no error, after the point has
been in Man mode or is initialized.
It can also be used when the data point is the ultimate primary point. In such a case, a
startup procedure could be used where the point is started in Man mode and the valve
manually adjusted to bring the PV close to the desired value, and the data point would
then be switched to Auto.
PV tracking (even if configured) is not done on return from a Bad PV.
PV tracking is configured by setting PVTRACK to Track. If configured, SP is set equal
to PV when the cascade is broken by an operator, a program action, or when this data
point is a secondary in a local cascade strategy and the cascade is momentarily
interrupted by one-shot initialization; that is, when the following conditions exist:
• the data point that uses this algorithm is in Man mode.
• the mode of this data point is Cas and RCASOPT = Ddc.
• INITMAN = On, and either the—
− mode is not Auto, or
− RCASOPT is not Rsp.

R688 HPM High-Performance Process Manager Control Theory 341

08/2019 Honeywell
27 PID Control Algorithm
27.2 Options and Special Features

• the first time the data point is processed after becoming active.
• this slot is a secondary within a local (inside the same HPM) and is going through 1-
shot control initialization.

ATTENTION
1-shot control initialization occurs when:
• the control initialization request flag (CTRLINIT) is On.
• this slot is being processed for the first time after the HPM state has
changed to RUN (OK).
• this slot has just recovered from a bad PV.
• this slot has only one disposable secondary that just underwent 1-shot
initialization.

Gain options
When configuring a data point that uses the PID algorithm, and equations A, B, or C, you
can choose any of the four gain options listed in the following table.

Table 27-1 Pid Control Algorithm Gain Options

Gain Option Description

Linear Gain The most commonly used gain option. You set the gain, K, in the chosen
equation. The default value for K is 1.

Gap Gain Used to reduce the sensitivity of the control action when the PV is in a
Modification1 narrow band (gap) around the setpoint. The size of this band is specified by
the user. K, as used in the chosen equation is derived as follows:
• if (SP - GAPLO) < PV < (SP + GAPHI), then—
K = KLIN * KGAP
• if PV is outside the gap, then—
K = KLIN
If the resulting value in K exceeds 240.0, it is clamped at 240.0.

342 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 27 PID Control Algorithm
27.2 Options and Special Features

Gain Option Description

Nonlinear Gain Provides control action proportional to the square of the error, rather than
Modification2 the error itself. The gain, K, used by the chosen equation, is derived as
follows:

External Gain Compensates for nonlinear-process gain. The gain, K, used by the chosen
Modification3 equation, is modified by an input value that can be from the process, from a
PV calculated from a process input by a PV algorithm, or from a user-
written program.
K is derived as follows:
K = KLIN * KEXT
If the resulting value in K exceeds 240.0, it is clamped at 240.0.
1 KLIN = Linear-gain parameter, in percent-per-percent. Range is 0.0 to 240.0, and the
value is tuned at a Universal Station. Default = 1.0.
KGAP = Gain-modification factor, specified by the user. Range is 0.0 to 1.0. Default = 1.0.
GAPLO = Bottom limit of the gap in the same engineering units as the PV. Can be any
value ≥ 0.0. Default = 0.
GAPHI = Upper limit of the gap in the same engineering units as the PV. Can be any value
≥ 0.0. Default = 0.
2 KLIN = Same as for gap gain.
KNL = Nonlinear-gain modifier.
NLFM = Nonlinear-gain form. 0 or 1, as specified by the user. Default = 1.
3 NLGAIN = Nonlinear gain, specified by the user. Value ranges from 0.0 to 240.0.default = 0.
PVP = PV in percent.
SPP = SP in percent.

TIP
Regarding the External Gain Modification option:
• when used to compensate for nonlinear-process gain the PID gain may
be tuned independently of the operating point of the process. For
R688 HPM High-Performance Process Manager Control Theory 343
08/2019 Honeywell
27 PID Control Algorithm
27.2 Options and Special Features

example—
− In controlling the level in a tank whose cross section is not constant,
the gain could be modified to compensate for the nonlinear rate of
level change that is caused by the changing shape of the tank.
− The General Linearization PV algorithm (subsection 7.9.8) could be
used to compute the inverse of the level-change characteristic, and
the resulting PV could be used to modify the level-control gain.
• it is possible to use this option for multiplicative-feedforward control, but
the PID with Feedforward-control algorithm is a better choice as it
provides a better operator interface and better recovery from a "bad"
feedforward input.

Windup handling
When the output of this algorithm reaches the user-specified output limits, or reaches the
setpoint limits of the data point's secondary, or when a woundup-status indication is
received from the secondary, the PID algorithm stops calculating the integral term but the
calculation of the proportional and derivative terms continues.
This is the same way that windup conditions are handled in Basic Controllers,
Multifunction Controllers, and Extended Controllers.
Output suppression
This feature suppresses output "kicks" when switching to cascade (Cas) mode.
Without this suppression feature, the first setpoint change after switching from Man or
Auto to Cas mode could cause a sudden move (kick) in the output because of the
proportional or derivative terms. This "kick" occurs when, for some reason, the primary
data point's output is not initialized, and an abrupt change in the setpoint occurs when
Cas mode resumes.

344 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 27 PID Control Algorithm
27.2 Options and Special Features

To suppress this "kick," the proportional and derivative terms are not calculated the first
time the PID data point is processed after changing to Cas mode.

TIP
This feature is especially useful when the PID point is one of two or more
secondaries of its primary data point. When this data point is changed to Cas
mode, even if the primary is not initialized, the output of this data point does
not bump the first time it is processed.

Initializing PID Output Without Affecting Dynamics

A logic slot or a user-written program in the HPM, AM, or a CM (FORTRAN or Pascal)
can store a value in the CV parameter of the PID data point, even while the algorithm is
doing its normal, incremental PID calculation. This may change the full-value output of
the data point, but it has no effect on the continuing incrementation or decrementation of
the output. It is possible, therefore, for a user-written program to initialize a PID output
without affecting the dynamics of the PID calculations, and without initializing the
output of the primary data point.

TIP
As an example of the usefulness of this feature, consider a single PID that is
controlling temperature by controlling the flow of either gas or oil. This PID's
output is connected to both flow controllers, but only one secondary is in
cascade at any time.
When a change from one fuel to the other is made:
• the user-written program initializes the output of the temperature-
controller PID by storing a new, full-value output in CV
• the cascade connection is switched from one to the other, and the
dynamic compensation of the flow of the new fuel proceeds
• the value stored in CV is the setpoint of the new secondary in percent
(SPP)
Through this technique, the full-value output of the primary has been
initialized without affecting its dynamic calculations, so the fuel switchover is
quick and smooth.

R688 HPM High-Performance Process Manager Control Theory 345

08/2019 Honeywell
27 PID Control Algorithm
27.2 Options and Special Features

Restrictions and recommendations for some values

The following are restrictions and recommendations for some of the values used with this
algorithm:

Restrictions
1 The specified engineering units range for the PV also applies to the SP

Recommendations
1 For best performance, we recommend that the integral (T1) and derivative
(T2) time constants be within the following ranges:
• T1 > 20.0 * TS

• T2 > 100.0 * TS for the interactive (real) form of the PID

• T2 > 10.0 * TS for the non-iteractive (ideal) form of the PID

2 For the interactive form of the PID, if:

• T1 > 0 but < 2.0 * TS, it is clamped to 2.0 * TS
• T2 > 0 but < 10.0 * TS, it is clamped to 0.0 * TS

Bias options
Ratio control can be achieved by modifying the setpoint input to the PID algorithm by a
RATIO of some other process point that is stored to through a control output connection,
for example, a fuel-to-air ratio in furnace control (it can also be accomplished with the
Ratio Control algorithm. When configuring a PID data point, you can select one of the
following options for modifying the setpoint through the RBOPT parameter:

• No ratio or bias • Fixed ratio and bias

• Auto ratio (fixed bias) • Auto bias (fixed ratio)

If you select one of the ratio and bias options, configured or operator-entered ratio and
bias values are used to modify the setpoint (by multiplying it by the ratio and adding the
bias value) only while the data point is in Cas mode. In Auto mode, the ratio calculation
does not occur because this option is intended to receive the process value to be modified
by the ratio, only from another data point (which can happen only in the Cas mode).

346 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 27 PID Control Algorithm
27.2 Options and Special Features

The "Auto ratio and Auto bias" options adjust the ratio or bias while the data point is in
Auto or Man modes, or is undergoing initialization, so that when it returns to Cas mode,
the new SP won't "bump" the process. With:
• Auto ratio, the operator can—
− change only bias; ratio is calculated to maintain the same setpoint when the
mode is changed to Cas.
− change the ratio in Cas mode.
• Auto bias, the operator can—
− change only ratio; bias is calculated to maintain the same setpoint when the
mode is changed to Cas.
− change the bias in Cas mode.
Modification of the setpoint by a ratio and a bias is actually handled by setpoint
processing rather than by the PID algorithm. It is applied to only PID setpoints.
These options allow this one algorithm to perform PID Ratio, PID Auto Ratio, and PID
Auto Bias functions.
The parameters used for these options are RBOPT, RATIO, BIAS, RTHILM, RTLOLM,
BSHILM, and BSLOLM.

R688 HPM High-Performance Process Manager Control Theory 347

08/2019 Honeywell
27 PID Control Algorithm
27.2 Options and Special Features

Operating modes
The PID algorithm operates in the following modes:
• Man
• Auto
• Cas
• Bcas – If RCASOPT = Spc or Ddc or DdcRsp
Remote Cascade options
All Remote Cascade Options are supported: Spc, Ddc, DdcRsp and Rsp.
Restart or Point Activation
On a warm restart, or when the data point is activated, initialization takes place.
Error Handling
If the status of the PV value goes bad, the CV value is changed to bad (NaN) and the data
point remains in the current mode. When the PV-value status returns to normal, the CV
value is initialized and the PID dynamics are returned to a steady state. An initialization
request and initialization value is sent to the primary data point.

348 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 27 PID Control Algorithm
27.3 Equations

27.3 Equations
Background
You can select one of four equations when you configure a data point that uses the PID
control algorithm. Each equation differs in the interactive and non-interactive forms of
the algorithm. The following tables provide a description of each equation and it's
Interactive (Real) and Non-interactive (Ideal) forms. The following equations are
supported:
• Equation A where – P, I, and D act on the error
• Equation B where – P and I act on the error, D acts on PV changes
• Equation C where – I acts on the error, and P and D act on PV changes
• Equation C where – Integral (I) control only is supported
Equation legend
When reviewing these equations, please note that:
• CV = output of the PID algorithm, full value in percent
• a = for the—

− Interactive form, a constant equal to is the high-frequency gain or rate

amplitude

− Non-interactive form, a constant equal to

• PVP = process variable in percent
• SPP = setpoint in percent
• S = laplace operator
• T1 = integral time constant in minutes per repeat for interactive form
• T2 = derivative time constant in minutes

REFERENCE - INTERNAL
Certain restrictions and recommendations apply to the integral and derivative
time constants, refer to Restrictions and recommendations for some values
for more information.

Tuning Conversions from Interactive to Non-Interactive PID

PID algorithms are implemented from the following transfer functions:

R688 HPM High-Performance Process Manager Control Theory 349

08/2019 Honeywell
27 PID Control Algorithm
27.3 Equations

Interactive PID
CV( s ) (T1 s + 1)(T2 s + 1)
=K
e( s ) T1 s (αT2 s + 1)
(1)

Non-Interactive PID
CV( s ) 1 s
= K ni (1 + + TD )
e( s ) TI s (αTdf s + 1)
(2)

If the rate limiters are ignored the transfer functions take on the following forms:

Interactive PID

CV( s ) (T1 s + 1)(T2 s + 1)

=K
e( s ) T1 s
(3)

Non-Interactive PID

CV( s ) 1
= K ni (1 + + TD s )
e( s ) TI s
(4)
Equation (3) can be arithmetically manipulated to obtain the form of equation (4) by
multiplying out the nominator and then converting to a sum:
CV( s ) T1T2 s 2 + (T1 + T2 ) s + 1
=K
e( s ) T1 s

CV( s ) T1T2 s 2 (T1 + T2 ) s 1

= K( + + )
e( s ) T1 s T1 s T1 s

350 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 27 PID Control Algorithm
27.3 Equations

CV( s ) T1T2 s (T1 + T2 ) 1

= K( + + )
e( s ) T1 T1 T1 s

CV( s ) T1 + T2 T1T2 s 1
=K ( +1+ )
e( s ) T1 T1 + T2 (T1 + T2 ) s

CV( s ) T2 1 T1T2
= K (1 + )(1 + + s) (5)
e( s ) T1 (T1 + T2 ) s (T1 + T2 )

Comparing the respective coefficients of equations (4) and (5) gives the Non-Interactive
PID tuning coefficients in terms of the Interactive PID tuning parameters:
T2
K ni = K (1 + ); TI = T1 + T2 ;
T1

R688 HPM High-Performance Process Manager Control Theory 351

08/2019 Honeywell
27 PID Control Algorithm
27.3 Equations

Equation A
Table 27-2 Pid Control Algorithm - Equation A

Equation A

Description:
P, I, and D act on the error

Interactive (Real) Form:

Non-interactive (Ideal) Form:

Equation B
Table 27-3 Pid Control Algorithm - Equation B

Equation B
Description:
P and I act on error, D acts on PV
Used to eliminate derivative spikes in control action that occur with quick changes in the setpoint
Interactive (Real) Form:

Non-interactive (Ideal) Form:

352 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 27 PID Control Algorithm
27.3 Equations

Equation C
Table 27-4 Pid Control Algorithm - Equation C

Equation C

Description:
I acts on error, P and D act on PV
Provides the smoothest and slowest response to setpoint changes

Interactive (Real) Form:

Non-interactive (Ideal) Form:

Equation D
Table 27-5 Pid Control Algorithm - Equation D

Equation D

Description:
Integral control, only

Interactive (Real) Form:

Non-interactive (Ideal) Form:

R688 HPM High-Performance Process Manager Control Theory 353

08/2019 Honeywell
27 PID Control Algorithm
27.4 Initialization

27.4 Initialization
When the output destination of the primary is to the secondary, initialization occurs as
follows:
• When the control initialization request flag (CTRLINIT) is on.
• When this slot is being processed for the first time after the HPM state (APMMSTS)
has changed to Run or OK.
• When this slot is just recovering from a Bad PV.
• When this slot has only one disposable secondary that just underwent 1-shot
initialization.
• When the output is indisposable (when the mode of the secondary slot is not in Cas).

27.5 Override Feedback Processing

When a PID point's secondary uses an Override Selector algorithm then the actions
described in the following table occur.
Figure 27-2 Override Feedback Processing Diagram

From
Primary
CAS
SPP PID
CV OP X1 CV
AUTO X2 Override
X3 SELECTOR
X4

INITVAL
To PTORST PTORST
Primary
ORFBSEC ORFBSEC

ORFBSEC is not an external parameter

354 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 27 PID Control Algorithm
27.5 Override Feedback Processing

Action Description
1 When override feedback is propagated, override status is returned in PTORST to the
PID point as one of the following:
• Not Connected • Selected • Not Selected

2 When the PID point is processed, if the status is returned as—

• Not Connected, then there is no action
• Not Selected and if the PID point's mode is Auto or Cas and CV is not equal to
NaN, then—
− in Direct-Control if OROFFSET = On (CV = ORFBSEC ∗* + GAIN *
ERROR) the PID point's CV is initialized as
CV = ORFBSEC + K * (PVP – SPP)

− in Reverse-Control if OROFFSET = On (CV = ORFBSEC ∗* + GAIN *

ERROR) the PID point's CV is initialized as
CV = ORFBSEC – K * (PVP – SPP)
(where K * (PVP - SPP) = offset value for Equations A, B, and C; K = 1 for
Equation D)

ATTENTION
The following important notes apply to Override Feedback processing:
• When the PID point is Not Selected and is in Cas mode an override-
feedback value is calculated as follows and sent to the primary:

− If RBOPT is not equal to NoRatBi, then ORFB =

• If RBOPT is equal to NoRatBi, then ORFB = PV.

• The not connected/not selected/selected status received from the PID's
secondary, is also sent on to the primary.
• If the offset value is in such a direction that it causes the non-selected
PID to become selected, the offset values will be set to 0.0.

* ORFBSEC is not an external parameter

R688 HPM High-Performance Process Manager Control Theory 355
08/2019 Honeywell
27 PID Control Algorithm
27.6 Control Output Connection

27.6 Control Output Connection

Control outputs can be to the following destinations:
• SP, RATIO, X1, X2, X3, and X4 parameters of another control slot in the same
HPM box†.
• When output connections are made to RATIO, the secondary mode should be Cas
and MODATTR should be PROGRAM and RBOPT should be AutoRat.
• SP of a control slot in another HPM (or APM or PM) box on the same Universal
Control Network†.
• X1 input of a control slot in another HPM (or APM) on the same Universal Control
Network.

ATTENTION
† Such a connection counts as one output and one input for the purpose of
limiting the number of UCN connections.

When output connections are not to any of the above, they can be to
• OP parameter of an analog output slot inside an AO IOP in the same HPM box∗. AO
point must be configured as a component point.
• OP parameter of a digital output slot (configured for DOTYPE = PWM ) in the same
HPM box*.
• Any addressable parameter of any accessible slot if the control algorithm is PID with
external reset feedback.

ATTENTION
Output does not go to a device on the Data Hiway (MC, EC, CB).

∗ See “Control Output Connection”, for restrictions and additional information

356 HPM High-Performance Process Manager Control Theory R688
Honeywell 08/2019
 28. PID w/Feedforward Control Algorithm
28.1 Functional Overview
Family
The PID with Feedforward control algorithm is a member of the Regulatory Control
algorithms.
Purpose
The PID with Feedforward (PIDFF) control algorithm is used as a controller that either
directly moves a control device (valve) in the process, or provides an input to another
data point. It is identical to the PID Control Algorithm, Purpose, except as defined below
herein.
Description
The PID Feedforward Control Algorithm (PIDFF) is a regulatory control function that,
like the PID Control Algorithm, Description, operates as a proportional-integral-
derivative (PID) controller except that it:
• accepts a—
− feedforward signal to be added to, or multiplied by, the algorithm's incremental
output, before the full-value output is accumulated.
− value that is representative of some condition in the process, to be combined with
the PID's incremental output before the full-value output is accumulated.
• lets you combine a feedforward signal with the PID output without using another
data point or algorithm to do it.
This algorithm supports all remote cascade options. PV source selection is supported if
the point is configured "full."

REFERENCE - INTERNAL
For operational additional operational details of the PID with Feedforward
(PIDFF) Control Algorithm, refer to PID Control Algorithm, Functional
Overview.

Inputs and Outputs

As shown in the following figure, the PIDFF algorithm requires two input connections
(from PV processing and FF inputs). The inputs can be increased to three, allowing the
SP to be fetched with an input connection.
Figure 28-1 PIDFF Control Algorithm Functional Diagram

R688 HPM High-Performance Process Manager Control Theory 357

08/2019 Honeywell
28 PID w/Feedforward Control Algorithm
28.1 Functional Overview

Setpoint Feedforward
From Initializing Processing Signal
Primary
CAS
SPP
To
PIDFF CV OP
AUTO Secondary
PVP
Operator or
User-Written
Program From PV Algo or Output
I/O Module Processing

PID Forms: Interactive (Real)

Noninteractive (Ideal)
Equations:
A: Full PID
B: PI on error, D on PV change only
C: I on error, PD on PV change only
D: Integral control only

Feedforward Action: Additive, Scale and Add

Multiplicative; Scale and Multiply

Feedforward
The feedforward signal can be obtained from an analog-input point, and it is often
subjected to dead-time compensation or lead-lag compensation before being connected to
the FF input of this algorithm. That compensation can be provided by algorithms such as
the Variable Dead-Time with Lead-Lag Compensation PV. The following figure shows
an example of such a strategy.

358 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 28 PID w/Feedforward Control Algorithm
28.1 Functional Overview

Figure 28-2 PIDFF Control Algorithm in Feed Heater Example

Inlet Feed

Dynamic Feed- Forward

PV Algo rithm:
Signal
F Variable Dead -Time
with Lead-Lag

PIDFF % Fuel Flow

Auto Controller
SPP Output
PID +, * OP
Cas Accumulation
PVP

T Fuel

Outlet Feed

In this example, if:

• Additive-feedforward action is chosen, the feedforward signal is:
− multiplied by a user-specified scale factor (KF).
− then added to the incremental output of the PID computation.
• Multiplicative feedforward action is chosen, the feedforward signal is:
− multiplied by the scale factor (KF).
− then multiplied by the full value output of the PID computation.

TIP
Additive-feedforward action, as shown in the example, would permit you to
use the scale factor that could be used to convert an engineering-units input
to a percentage.
Multiplicative feedforward action is typically used to compensate for
variations in process gain that are caused by changes in throughput.
For example if the feed rate is doubled in a heating application twice the
amount of fuel might be required, which is the equivalent to doubling the
process gain.

R688 HPM High-Performance Process Manager Control Theory 359

08/2019 Honeywell
28 PID w/Feedforward Control Algorithm
28.2 Options and Special Features

Use
The use of the PID Feedforward Control Algorithm (PIDFF) is the same as the PID
Control Algorithm, Use.

28.2 Options and Special Features

Relationships to the PID control algorithm
All of the following PID Control-algorithm options and special features apply to the PID
Feedforward Algorithm:
• Interactive and Non-interactive PID forms
• Engineering Unit ranges
• Control terms
• Single term control
• Direct and Reverse control action
• PV tracking
• Gain options
• Windup handling
• Output suppression
• Initializing PID Output Without Affecting Dynamics
• Restrictions and recommendations for some values
• Bias options
• Operating modes
UCNOUT block
UCNOUT block is a configurable block for creating regulatory control cascade strategies
between the Experion ACE-T supervisory controller and the Process Manager controller.
The UCNOUT block requires an OPC gateway or a TPN Server to communicate with the
Process Manager controller.

REFERENCE - EXTERNAL
For more information on UCNOUT/EUCNOUT block, refer to the following
documents in the Experion bookset.
• Control Builder Components Theory
• Control Builder Components Reference

360 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 28 PID w/Feedforward Control Algorithm
28.2 Options and Special Features

Remote cascade options

• Restart or Point Activation
• Error Handling
• Restart or Point Activation
• Error Handling
Add or Multiply Action
Parameter FFOPT is configured to specify whether the feedforward signal is to be added
to the incremental PID output or multiplied by it.
Bypassing Feedforward Control Action
An operator or a user-written program can bypass the feedforward action by one of the
following:
• If the feedforward signal comes from a PV algorithm, switch the PV source for the
data point that is using the PV algorithm to Man (if you do this and the PV is changed
while the PVSOURCE is Man, the feedforward signal is affected). To resume
feedforward action, switch the PVSOURCE back to Auto.
• If the feedforward signal comes from a control algorithm, switch the mode of the
data point that is using the control algorithm to Man (if you do this and the output
(OP) is changed while the source point is in manual, the feedforward signal is
affected). To resume feedforward action, switch back to Normal mode (Auto or Cas).
Feedforward Signal Value Status
If the value status for the feedforward signal goes bad, the feedforward component of the
output value is frozen at the last good value and normal PID processing continues.
When the value status of the feedforward signal returns to normal, normal feedforward
action resumes. This does not cause a bump in the output because any change from the
last good value is internally absorbed and the PID dynamics are not affected. The
floating, full-value output continues as if there was no feedforward change but the
contribution of the feedforward action continues from that time.

R688 HPM High-Performance Process Manager Control Theory 361

08/2019 Honeywell
28 PID w/Feedforward Control Algorithm
28.3 Equations

Operating Modes
The PIDFF algorithm operates in the following modes:
• Man
• Auto
• Cas
• Bcas — If RCASOPT = Spc or Ddc or DdcRsp
Remote Cascade Options
All Remote Cascade Options are supported: Spc, Ddc, DdcRsp and Rsp.

28.3 Equations
Background
The available equations in the PID with Feedforward (PIDFF) control algorithm are
identical to the those of the PID algorithm except that they include the following
functions:

• Additive action • Multiplicative action

REFERENCE - INTERNAL
Refer to the following for information concerning equations in the PID control
algorithm:
• Background.
• Equation A where – P, I, and D act on the error.
• Equation B where – P and I act on the error, D acts on PV changes.
• Equation C where – I acts on the error, and P and D act on PV changes.
• Equation C where – Integral (I) control only is supported.

362 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 28 PID w/Feedforward Control Algorithm
28.3 Equations

Equation legend
When reviewing these equations, please note that:
• CV = Full-value output in percent, PID combined with feedforward action.
• CVPID = The full value output before the multiplicative term. This is an internal
parameter and is not available to displays nor to user-written programs.
• CVPID = The full value output before the multiplicative term. This is an internal
parameter and is not available to displays nor to user-written programs.
• DELCV = The incremental output of PID computation. Default = N/A.
• BFF = Bias value for multiplicative action. Default = 0.
• FF = The feedforward input signal, from a control-input connection. Normally from
a parameter with a percentage value. Default = N/A.
• FF lgv = Last good value for the FF input (notation only, not a user-visible
parameter).
• KFF = Scale factor applied to FF. Normally the source parameter is in units of
percent. However, if it isn't, KFF can be used as an EU to percent conversion factor.
In this case, KFF is set to the following where EUHI and EULO correspond to the EU
range of the source parameter.

• n and n-1 = Notation to indicate the value this pass (n) and the preceding pass (n-1).

R688 HPM High-Performance Process Manager Control Theory 363

08/2019 Honeywell
28 PID w/Feedforward Control Algorithm
28.4 Initialization

Additive action
When additive action is used, the feedforward signal is applied to the incremental output
of the PID computation using the equation:

ATTENTION
If the status of... Then...
FFn or FFn-1 is bad

Multiplicative action
When multilicative action is used:
• the feedforward signal is applied to the output of the PID computation using the
equations:

• CV is a read only parameter for CL programs.

• the back calculation of CVPID keeps CV unchanged preventing a bump.

ATTENTION
If the status of... then...
FFn or FFn-1 is bad CV = CVPID * (KFF * FFn + BFF)

FFn is OK and FFn-1 is bad

If the result of (KFF * FFn + BFF) is less than 0.01, it is clamped at 0.01.

28.4 Initialization
Background
Initialization in the PID with Feedforward (PIDFF) control algorithm is identical to the
PID control algorithm except that it includes the following functions:

364 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 28 PID w/Feedforward Control Algorithm
28.4 Initialization

• Additive action

• Additive action
• Multiplicative action

REFERENCE - INTERNAL
Refer to the following for information concerning Initialization in the PID
control algorithm:
• Background.
• Equation A where – P, I, and D act on the error.
• Equation B where – P and I act on the error, D acts on PV changes.
• Equation C where – I acts on the error, and P and D act on PV changes.
• Equation C where – Integral (I) control only is supported.

R688 HPM High-Performance Process Manager Control Theory 365

08/2019 Honeywell
28 PID w/Feedforward Control Algorithm
28.5 Override Feedback Processing

28.5 Override Feedback Processing

Background
Override-feedback for the processing for the PIDFF control algorithm is the same as
described for the PID algorithm inOverride Feedback Processing, unless a if
multiplicative action is configured. In this case, a feedforward term is added to the output
calculations for Direct control and Reverse control.
Direct control
In Direct-Control, if OROFFSET is:
• On (CV = ORFBSEC * + GAIN * ERROR) the PIDFF point's CV is initialized
as—
CV = ORFBSEC + K * (KFF * FF + BFF) * (PVP – SPP)
• Off (CV = ORFBSEC * + GAIN * ERROR) the PIDFF point's CV is initialized
as—
CV = ORFBSEC + K * (KFF * FF + BFF)

ATTENTION
ORFBSEC is the override-feedback value from the secondary in percent.

366 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 28 PID w/Feedforward Control Algorithm
28.5 Override Feedback Processing

Reverse control
In Reverse-Control, if OROFFSET is:
• On (CV = ORFBSEC * + GAIN * ERROR) the PIDFF point's CV is initialized
as—
CV = ORFBSEC - K * (KFF * FF + BFF) * (PVP – SPP)
• Off (CV = ORFBSEC * + GAIN * ERROR) the PIDFF point's CV is initialized
as—
CV = ORFBSEC - K * (KFF * FF + BFF)

ATTENTION
ORFBSEC is the override-feedback value from the secondary in percent.

R688 HPM High-Performance Process Manager Control Theory 367

08/2019 Honeywell
28 PID w/Feedforward Control Algorithm
28.5 Override Feedback Processing

368 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 29. PID w/External Reset-Feedback Control
Algorithm
29.1 Functional Overview
REFERENCE - INTERNAL
Refer to the following for information concerning:
• PID Control Algorithm, Functional Overview.
• PID w/Feedforward Control Algorithm, Functional Overview.

Family
The PID with External Reset-Feedback control algorithm is a member of the Regulatory
Control algorithms.
Purpose
The PID with External Reset-Feedback (PIDERFB) control algorithm is used as a
controller that either directly moves a control device (valve) in the process, or provides
an input to another data point. It is identical to the PID Control Algorithm, Purpose,
except as defined herein.
Description
The PID with External Reset-Feedback (PIDERFB) algorithm is a regulatory control
function that, like the PID Control Algorithm, Description, operates as a proportional-
integral-derivative (PID) controller except that it accepts a:
• reset-feedback signal from another data point
− typically the PV of the secondary PID data point that is receiving its setpoint
from this data point.
− to be combined with the PID's incremental output, before the full-value output is
accumulated.
• tracking-value signal.

R688 HPM High-Performance Process Manager Control Theory 369

08/2019 Honeywell
29 PID w/External Reset-Feedback Control Algorithm
29.1 Functional Overview

The intent of this algorithm is to prevent windup when it has a secondary data point,
typically a PID point that may or may not be responding to the output of this data point.

TIP
The PID with External Reset-Feedback algorithm also permits you to
integrate third-party hand/auto stations to an HPM control strategy.

REFERENCE - INTERNAL
For additional information regarding:
• details of the PID with External Reset-Feedback (PIDERFB) Control
Algorithm, refer to PID Control Algorithm, Functional Overview.
• the use and integration of hand/auto stations with the HPM, refer to the
topic Hand/Auto Stations, for the PIDERFB control algorithm.

Inputs and Outputs

As shown in the figue belowthe PIDERFB algorithm requires three input connections:
• from PV Processing (PVAUTO).
• RFB (Reset Feedback Value)—typically from the PV of another data point which is
receiving its setpoint from this data point.
• TRFB (Tracking Value)—typically the PV or SP of another data point that is
receiving its setpoint from this data point.
The number of inputs can be increased to four, allowing the SP to be fetched with an
input connection.

370 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 29 PID w/External Reset-Feedback Control Algorithm
29.1 Functional Overview

Figure 29-1 PIDERFB Control Algorithm Functional Diagram

Setpoint
Processing

CAS
To
SPP PIDERFB CV OP
Secondary
AUTO
PVP
Operator or
User-Written
From PV Algo
Program
or IOP
S1 Tracking Switch Control
TRFB Tracking Value*
RFB Reset Feedback Value**

* Typically PV or SP of Secondary PID

PID Forms: Interactive (Real) ** Typically PV of Secondary PID

Noninteractive (Ideal)

Equations: A: Full PID

B: PI on error, D on PV c hange only
C: I on error, PD on PV c hange only
D: Integral control only

Reset Feedback Action: Scaled, integrated CV - RFB dev iation is added

to incremental PID output before full-value output
accumulation.

Output destination can be to a secondary data point in the HPM or to any desired
destination using control output connection (that is, any addressable parameter of any
accessible slot).
The tracking switch-control signal (S1) is usually stored with an output connection from
a Logic slot (or a program). If the switch control is On, the CV value from this data point
is replaced by the tracking value. If, for some reason, the secondary is not using the
output of this data point, S1 can be set to On by logic external to the PIDErfb, which
causes this point's CV to track the secondary's PV. When the secondary begins to accept
OP from this point for control, S1 is set to Off (by the external logic), and CV is then at
the same value as the controlled variable (PV), so there is no bump and normal control
can resume.

R688 HPM High-Performance Process Manager Control Theory 371

08/2019 Honeywell
29 PID w/External Reset-Feedback Control Algorithm
29.2 Options and Special Features

PIDERFB sample application

In a simple application , both the reset-feedback signal and the tracking value may come
from the PV of the secondary data-point.
Figure 29-2 PIDERFB Control Algorithm Example Application

P ID E R FB
SPP OF F
+/- O u tp u t
P ID
PVP A ccu m CV OP SP P ID
S1
PV
On

S ca lin g an d T RF B
I nt e gra tio n R FB

29.2 Options and Special Features

Relationships to the PID control algorithm
All of the following PID Control-algorithm options and special features apply to the PID
Feedforward Algorithm:
• Interactive and Non-interactive PID forms
• Control terms
• Single term control
• Direct and Reverse control action
• PV tracking
• Gain options
• Output suppression
• Restrictions and recommendations for some values
• Bias options
• Operating modes
• Remote Cascade options
• Restart or Point Activation
• Error Handling
372 HPM High-Performance Process Manager Control Theory R688
Honeywell 08/2019
 29 PID w/External Reset-Feedback Control Algorithm
29.2 Options and Special Features

Error Handling, RFB and TRFB inputs

If S1 is Off, and the reset-feedback input has a bad value, the data-point mode doesn't
change and the CV value goes bad (NaN). When the RFB input is again good, the CV
value is initialized (see “Initialization” in Section 29) and the dynamic terms are returned
to a steady state. If configured for external initialization, an initialization request is sent
to the primary data point.
If S1 is On, and the tracking-value input has a bad value, the data-point mode doesn't
change and the CV value goes bad (NaN). When the TRFB input is again good, the CV
value is initialized (see “Initialization” in Section 29) and the dynamic terms are returned
to a steady state. If so configured, an initialization request is sent to the primary data
point.
Output connections
The output of this algorithm can be to any desired destination using control output
connections.

ATTENTION
Note the following with regards to output connections with the PIDERFB
algorithm:
• Fieldbus does not support a control connection output when the
Regulatory Control point is configured for the PIDERFB algorithm.
• Initialization and windup protection normally associated with control
output connections are not performed with this algorithm. That is,
initialization occurs only when S1, the tracking switch-control signal, is
true.
• Output connections store the value of the OP after converting to
engineering units.
• See “Control Output Connection” in Section 27.6, for restrictions on the
number of output connections and destinations for this algorithm.

Engineering Unit ranges

PV Engineering unit range (PVEULO and PVEUHI) and the output engineering unit
range (CVEULO and CVEUHI) must be specified. The SP engineering unit range
(SPEULO and SPEUHI) always follows the PV range.
Operating modes
The PIDERFB algorithm operates in the following modes:
• Man
• Auto

R688 HPM High-Performance Process Manager Control Theory 373

08/2019 Honeywell
29 PID w/External Reset-Feedback Control Algorithm
29.2 Options and Special Features

• Cas
• Bcas — If RCASOPT = Spc or Ddc or DdcRsp
Remote Cascade Options
All Remote Cascade Options are supported: Spc, Ddc, DdcRsp and Rsp.

374 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 29 PID w/External Reset-Feedback Control Algorithm
29.3 Hand/Auto Stations

29.3 Hand/Auto Stations

Functions
The functions listed in the following table are supported by the HPM to integrate a third-
party hand/auto station.
Table 29-1 Hand/Auto Station Functions

Function Description

Output Ability to manipulate the output of the hand/auto station (when in

Auto position) from the PID, and to initialize the PID output to allow
the hand/auto station to switch bumplessly to auto position.

Mode Indication that the hand/auto station is in "hand" (or Local Manual)
position at the group display of the PID driving the output.

PV and SP Indication of PV and SP at the hand/auto station, and optionally the

ability to raise or lower the PID SP from the hand/auto station. PV
and SP may be from the PID driving the output, or from a different
PID. For example, in a single loop case, the PV, SP and output all
come from the same PID, but in case of a temperature flow
cascade, the PV and SP come from the temperature controller, and
the output is driven by the flow controller.

Interface requirements
In order for the interface to be generic (to allow support for hand/auto stations from many
different vendors), all signals are wired into the HPM through analog and digital IOPs.
This requires a total of two AI slots, one AO slot, and two DI slots in addition to the
requirements if no hand/auto station support is desired.
The I/O signals listed in the following table must be supported by the third-party
hand/auto station.
Table 29-2 Hand/Auto Station I/O Signals

I/O signals Description

PV_IN Analog input used to display the PV value on the hand/auto station.
The signal from the analog transmitter is wired into this input as
well as to the HPM through an AI IOP.

CV_IN Analog input from the controller. It represents the control value
position requested by the HPM's PID.

R688 HPM High-Performance Process Manager Control Theory 375

08/2019 Honeywell
29 PID w/External Reset-Feedback Control Algorithm
29.3 Hand/Auto Stations

I/O signals Description

CV_OUT Analog output. This output drives the control valve. When the
hand/auto station is in auto position, CV_OUT should track the
CV_IN input; when in local manual position, it can be manipulated
by the raise/lower keys.

CV_OUT is also fed back to the HPM through an AI IOP

for initialization of the PID output. The corresponding AI
FTA must not be grounded (the zero-ohm resistor to
ground at the FTA should be removed). Also the output
current drive capability of the hand/auto station must be
sufficient to handle an additional 250 ohm resistor used to
convert 4-20 milliamps to 1-5 volts.

MAN_STS Digital output indicating that the hand/auto station is in local manual
position.

SP_IN Analog input used to display the SP value on the hand/auto station.
The setpoint of the HPM's PID controller is connected to this input
through an AO IOP.

SP_OUT Analog output generated by the hand/auto station to change the SP

value of the HPM's SP.

SP_CHNG Digital output requesting the HPM to accept a new SP (equal to

SP_OUT) from the hand/auto station.

ATTENTION
SP_IN and SP_CHNG are not required if SP raise/lower capability is not
supported.

376 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 29 PID w/External Reset-Feedback Control Algorithm
29.3 Hand/Auto Stations

Configuration and wiring

The figures “Hand/Auto Station control configuration and wiring diagram “ and
“Hand/Auto Station logic point configuration and wiring diagram “ illustrate the control
function configuration and wiring necessary to interface a third-party Hand/Auto Station
to the HPM using the PIDERFB algorithm.

Figure 29-3 Hand/Auto Station Control Configuration and Wiring Diagram

PID_PRIM #1 PID_SEC #1

PV OP
SP
SP OP
SPP S1 TRFB

LOGIC #2 LOGIC #2 LOGIC #2

AI_PV AO_PV DI_SPCH AI_SP DI_MAN AO_CV AI_CV

SP_IN SP_ CHNG SP_OUT MAN_STS CV_IN

PV_IN CV_OUT
ANALOG DISPLAY SERVICE

Input Output
From NOTE: #1 SP, AND PV MAY BE CONNECTED TO THE PID_SEC IN A To
SINGLE LOOP CONTROL SITUATION.
Process Process
#2 SEE THE NEXT PAGE FOR DETAILS OF THE LOGIC SLOT
CONFIGURATION.

R688 HPM High-Performance Process Manager Control Theory 377

08/2019 Honeywell
29 PID w/External Reset-Feedback Control Algorithm
29.4 Equations

Figure 29-4 Hand/Auto Station Logic Point Configuration and Wiring

Diagram

INPUT LOGIC BLOCKS OUTPUT

CONNECTIONS CONNECTIONS

DI.MAN.PVFL L1
(ANALOG_DSP.MAN_MODE)
OR
ALG S01 PID_SEC.S1
AO_CV.INITREG L2

PID_PRIM.SP L3 AO.SP.OP
(ANALOG_DSP.SP_IN)

AI.SP.PV L4 PID_PRIM.SPP
(ANALOG_DSP.SP_OUT) ENB

DI_SP.PVFL L5
(ANALOG_DSP.SP_CHNG)

29.4 Equations
Background
The available equations in the PID with External Reset-Feedback (PIDERFB) control
algorithm are identical to those of the PID algorithm except with regard to the tracking
switch control feature (S1).

REFERENCE - INTERNAL
Refer to the following for information concerning equations in the PID control
algorithm:
• Background.
• Equation A where – P, I, and D act on the error.
• Equation B where – P and I act on the error, D acts on PV changes.
• Equation C where – I acts on the error, and P and D act on PV changes.
• Equation C where – Integral (I) control only is supported.

Tracking Switch Control impact

If the Tracking Switch Control is active (value of S1 = On), then each parameter

378 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 29 PID w/External Reset-Feedback Control Algorithm
29.5 Initialization

If S1 is... the Equation is... then...

On A, B, C, or D

Off A, B, or C

Where:
• CV = Full-value output in percent, PID combined with CVRFB.
• CVPID = The incremental output of the PID computation. This is an internal
parameter and is not available to displays nor to user-written programs.
• CVRFB = The scaled, integrated deviation of RFB from CV. This is an internal
parameter and is not available to displays nor to user-written programs.
• K = Gain.
• K1 = External, reset-feedback gain.
• RFB = The external, reset-feedback signal in engineering units. Default =
NaN.

• rfb

• s = The Laplace operator.

• S1 = The switch-control flag. Default = Off.
• TRFB = The tracking value in engineering units. Default = NaN.
• T1 = The integral term in minutes per repeat.

29.5 Initialization
Background
Initialization normally associated with output connections is not performed with this
algorithm. Output connections store the value of the OP (after converting to engineering
units based on CVEULO and CVEUHI) to the secondary.

R688 HPM High-Performance Process Manager Control Theory 379

08/2019 Honeywell
29 PID w/External Reset-Feedback Control Algorithm
29.6 Override Feedback Processing

29.6 Override Feedback Processing

Background
Override-feedback for the processing for the PIDERFB control algorithm is the same as
described for the PID algorithm.

TIP
Use of PIDERFB in override strategies is not recommended.

380 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 30. PID Position Proportional Controller
30.1 Functional Overview
Family
The PID Position Proportional control algorithm is a member of the Regulatory Control
algorithms.
Purpose
The PID Position Proportional (PIDPOSPR) control algorithm is typically used in place
of the Position Proportional Control Algorithm, Purpose, to operate a motor driven valve
without position feedback.
Description
The PID Position Proportional (PIDPOSPR) control algorithm consists of two parts:
• PID Control Algorithm, Description.
• Position Proportional Control Algorithm, Description.
The PIDPOSPR Control Algorithm is a regulatory control function that can be viewed as
a normal PID Control Algorithm joined in cascade with a Position Proportional Control
Algorithm. The PISPOSPR functions the same as the PID algorithm except that it does
not support OP (and OP related parameters OPEU, OPHILM, and so on) and CV (and
CVEUHI, CVEULO). The end part of the algorithm behaves exactly as a POSPROP
algorithm. The POSPROP component, which uses the del_cv of the normal PID as its PV
to generate raise and lower pulses, behaves exactly as a Position Proportional Control
Algorithm.
Figure 30-1 PID Position Proportional Control Algorithm Functional
Diagram

PV Lower
PID del_cv POSPROP
SP Raise

R688 HPM High-Performance Process Manager Control Theory 381

08/2019 Honeywell
30 PID Position Proportional Controller
30.2 Options and Special Features

30.2 Options and Special Features

Modes
The PIDPOSPR algorithm operates in the following modes:
• Man
• Auto
• Cas
• Bcas — If RCASOPT = Spc or Ddc or DdcRsp

ATTENTION
When the Mode is:
• Man—output pulses are issued on operator demand.
• Auto, Cas, Bcas—normal computation is performed.

Remote Cascade Options

Only the SPC option is supported.
Output Manipulation in Manual Mode
In Manual mode, the output can be manipulated from the group and detail displays using
the Raise/Lower keys. At the time of configuration, you must define "manual output
pulse time (MANOPTIM)." When the operator presses the Raise key (single up-arrow),
raise output pulse of width equal to MANOPTIM is issued. When the operator presses
the fast raise key (double up-arrow), raise output pulse to width equal to 10 times
MANOPTIM is issued. Lower output pulses can be similarly generated.
Windup Feedback Limit Switches
Output high and low flags can be fetched using the input connection parameters Output
High and low Flag Input Source (OPHISRC) and (OPLOSRC), respectively. These flags
serve the same function as the similar flags for POSPROP.

382 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 30 PID Position Proportional Controller
30.2 Options and Special Features

Local Manual Support

The Local Manual state is supported and it can be fetched with an input connection using
the input parameter Local Manual Source (LMSRC).
Analog Output Related Parameters
Parameters related to the analog output value do not apply and are defaulted to the same
values as those similar parameters in the PosProp algorithm.
Safety Shutdown
The Shutdown flag, when turned on, causes the mode to go to MAN with OPR attribute
and the output is derived based on the value of a new parameter SAFOPCMD as defined
in the following table.
Table 30-1 PIDPOSPR Safety Shutdown SAFOPCMD Parameter Value

If SAFOPCMD is... then...

Idle No more output pulses are issued.

Raise Raise pulses are issued until the PV is > EUHI, or OPHIFL
is ON. If the PV is bad, the test for PV > EUHI is ignored.

Lower Lower pulses are issued until the PV is < EUHI, or

OPLOFL is ON. If the PV is bad, the test for PV < EUHI is
ignored.

R688 HPM High-Performance Process Manager Control Theory 383

08/2019 Honeywell
30 PID Position Proportional Controller
30.2 Options and Special Features

Bad PV/Mode Shed

For PidPosPr (and PosProp) algorithms, Shed Hold, Shed Low, High, and Shed Safe are
interpreted as defined in the following table

Table 30-2 PIDPOSPR Bad PV/Mode Shed

Item Interpretation/Action

BADCTLOP Action taken for PIDPosPr (and PosProp).

No Shed IDLE, No more output pulses are issued.

Shed Hold IDLE.

Shed High Raise, Raise pulses are issued until PV > EUHI or OPHIFL is ON. If
the PV is bad, the test for PV > EUHI is ignored.

Shed Low Lower, Lower pulses are issued until the PV < EUHI or OPLOFL is
ON. If the PV is bad, the test for PV < EUHI is ignored.

Shed Safe Handled like Shutdown based on the value of SAFOPCMD.

384 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 30 PID Position Proportional Controller
30.3 Equations

30.3 Equations
Background
Only one equation is available for the PIDPOSPR algorithm. It is calculated as defined in
Equations, if CYCLE_TIMER has expired.
Equation legend
When reviewing the Equations, please note that:

Item Definition

ACCUMULATED_DEL_CY = Accumulations of del_cv (of the PID part) during

this cycle.

K1 = Gain constant for the POSPROP part of the

algorithm. It is renamed K1 (was K for the
POSPROP algorithm) to avoid confusing it with
the PID gain constant K.

DEADBAND = Error deadband in percent (range = 0.0 to 100.0;

default = 5.0).

OPHIFL = High output windup flag.

OPLOFL = Low output windup flag.

RAISRATE = Raise stroke rate in percent per second. Default =

100.0% per second. Range > 0.0.

LOWRRATE = Lower stroke rate in percent per second. Default =

100.0% per second. Range > 0.0.

RAISETIM = Raise pulse time in seconds. Default = N/A.

Clamped to the lower of MAXPULSE or
CYCLETIM. If smaller than MINPULSE, no pulse
is issued.

LOWERTIM = Lower pulse time in seconds. Default = N/A.

Clamped to the lower of MAXPULSE or
CYCLETIM. If smaller than RP*MINPULSE, no
pulse is issued.

RT = Deadtime ratio (Default = 1).

R688 HPM High-Performance Process Manager Control Theory 385

08/2019 Honeywell
30 PID Position Proportional Controller
30.3 Equations

Item Definition

DEADTIME = Additional pulse time required to overcome friction

in the motor when it begins to move or change
direction. It is added to the computed pulse time
except when the pulse issued last cycle time was
in the same direction (as the pulse this time) and
the pulse width was equal to CYCLETIM. Default
= 0.0.

Equations
When the conditions of the following table are met, PIDPSOPR raise/lower pulse width
equation can be used to determine the pulse raise or lower pulse width issued by the
PISPOSPR algorithm.
Table 30-3 PIDPOSPR Raise/Lower Equation Decision

If... then...
((ACCUMULATED_DEL_CV > DEADBND) AND (OPHIFL = OFF)) Issue a raise pulse
((ACCUMULATED_DEL_CV < DEADBND) AND (OPHIFL = OFF)) Issue a lower pulse

ATTENTION
If neither of the above are true, then the cycle timer will be reset to the
beginning.

Table 30-4 PIDPSOPR raise/lower pulse width equation (RAISETIM)

If PIDPOSPR then a pulse width equal to the following is issued...

indicates...

Raise

Lower

386 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 31. Position Proportional Control Algorithm
31.1 Functional Overview
Family
The Position Proportional control algorithm is a member of the Regulatory Control
algorithms.
Purpose
The Position Proportional (POSPROP) control algorithm is used to pulse two digital
outputs to drive the process variable toward the setpoint.
Description
As illustrated in the following figure, the POSPROP algorithm would typically be used to
step a valve open or closed, to raise or lower a rotary device, or to move plates of a pulp
mill refiner together or apart.

Figure 31-1 POSPROP Example Control Strategy

R688 HPM High-Performance Process Manager Control Theory 387

08/2019 Honeywell
31 Position Proportional Control Algorithm
31.1 Functional Overview

Operator AM Prog Local

Entry Store Cascade

Target Value or Setpoint Processing

SP

100% of Scale

From PV Algo
PV POSPROP PV
or I/O Module
0 % of Scale

LOWER

RAISE

Inputs and outputs

The POSPROP algorithm requires only one input and the number of inputs is defaulted
to one. However, the SP can be fetched with an input connection. PV Source selection is
supported if the point is configured as a full point. The Advisory (ASP) and Target Value
(TV) options of SPOPT (Setpoint Option) are supported.
Digital outputs are pulsed at a time interval specified by the CYCLETIME parameter and
the pulse width is proportional to the error signal.
The Raise/Lower digital outputs are stored to the destinations specified by the parameters
RAISDSTN and LOWRDSTN, respectively. The only valid output destinations are to
pulsed (but not PWM type) digital outputs. The pulse can be ONPULSE or OFFPULSE.

388 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 31 Position Proportional Control Algorithm
31.2 Options and Special Features

Figure 31-2 POSPROP Control Algorithm Functional Diagram

Fro m In itiali zi ng Pr ima ry

or
A M C ontro l Strate gy

SP

RA IS DSTN Dig ital Ou tput

Fro m PV A lgo o r IO P PV PO S PRO P
LO W RDSTN Dig ital Ou tput

31.2 Options and Special Features

Modes
The PIDPOSPR algorithm operates in the following modes:
• Man
• Auto
• Cas
• Bcas — If RCASOPT = Spc or Ddc or DdcRsp

ATTENTION
When the Mode is:
• Man—output pulses are issued on operator demand.
• Auto, Cas, Bcas—normal computation is performed.

Output Manipulation in Manual Mode

In Manual mode, the output can be manipulated from the group and detail displays using
the Raise/Lower keys. At the time of configuration, you must define "manual output
pulse time (MANOPTIM)." When the operator presses the Raise key (single up-arrow),
raise output pulse of width equal to MANOPTIM is issued. When the operator presses
the fast raise key (double up-arrow), raise output pulse to width equal to 10 times
MANOPTIM is issued. Lower output pulses can be similarly generated.

R688 HPM High-Performance Process Manager Control Theory 389

08/2019 Honeywell
31 Position Proportional Control Algorithm
31.2 Options and Special Features

Windup Feedback Limit Switches

Output high and low flags can be set to indicate the status of the limit switches
representing the valve position. When OPHIFL is set, the Raise output pulses are not
generated. When OPLOFL is set, Lower output pulses are inhibited.
OPHIFL and OPLOFL are usually set by output connections on Logic slot based on limit
switch feedback (brought into the system through digital inputs) from the process.

ATTENTION
In manual mode, the operator can manipulate the output Raise/Lower pulses
regardless of the status of the OPHIFL and the OPLOFL.

Raise/Lower Output Destinations

The Raise/Lower digital outputs are stored to the destinations specified by RAISDSTN
and LOWRDSTN, respectively. The only valid outputs are to ONPULSE or OFFPULSE
of digital outputs configured as Status type.
Engineering Unit Ranges
The PV Engineering unit ranges (PVEULO and PVEUHI) must be specified. The
setpoint engineering unit range (SPEULO and SPEUHI) always follows the PV range.
The output engineering unit range (CVEULO and CVEUHI) does not apply.
Analog Output Related Parameters
The standard control slot parameters that are normally related to the analog output value
do not apply because analog outputs are not valid destinations for outputs from this
algorithm. Other parameters associated with analog outputs cannot be fetched or stored
by any system function. Internally, they are defaulted such that they do not have any
effect on the system functions.

390 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 31 Position Proportional Control Algorithm
31.2 Options and Special Features

Table 31-1 Analog Output Related Parameters

Parameter Internal Default

CV NaN

CVEUHI 100.0

CVEULO 0.0

OP -6.9% of Full Scale

OPEU N/A

OPHILM 105.0%

OPLOLM -5.0%

OPROCLM NaN

OPMCHLM 0.0

SAFEOP N/A

NOCOPTS 1

INITMAN Off

R688 HPM High-Performance Process Manager Control Theory 391

08/2019 Honeywell
31 Position Proportional Control Algorithm
31.3 Equations

31.3 Equations
Background
Only one equation is available for the POSPROP algorithm. It is calculated as defined in
Equations, if CYCLE_TIMER has expired.
Equation legend
When reviewing the Equations, please note that:

Item Definition

PVP = PV in percent.

SPP = SP in percent.

DEADBAND = Error deadband in percent (range = 0.0 to 100.0; default =

5.0).
OPHIFL = High output windup flag.

OPLOFL = Low output windup flag.

CYCLETIM = Cycle time in seconds. Range: 0.25 to 1000.0; Default = 10.0.

RAISRATE = Raise stroke rate in percent per second. Default = 100.0%

per second. Range > 0.0.
LOWRRATE = Lower stroke rate in percent per second. Default = 100.0%
per second. Range > 0.0.
RAISETIM = Raise pulse time in seconds. Default = N/A. Clamped to the
lower of MAXPULSE or CYCLETIM. If smaller than
MINPULSE, no pulse is issued.
LOWERTIM = Lower pulse time in seconds. Default = N/A. Clamped to the
lower of MAXPULSE or CYCLETIM. If smaller than
RP*MINPULSE, no pulse is issued.
K = Gain constant. Range = 0.0 to 10.0; Default = 1.0.

RP = Pulse ratio (Default = 1).

RT = Deadtime ratio (Default = 1).

392 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 31 Position Proportional Control Algorithm
31.3 Equations

Item Definition

DEADTIME = Additional pulse time required to overcome friction in the

motor when it begins to move or change direction. It is added
to the computed pulse time except when the pulse issued last
cycle time was in the same direction (as the pulse this time)
and the pulse width was equal to CYCLETIM. Default = 0.0.
MAXPULSE = Maximum pulse time limit. If computed pulse time is greater
than this, it is clamped to the lower of MAXPULSE or
CYCLETIM. Default = 60 seconds.
MINPULSE = Minimum pulse time limit for raise pulse. If computed pulse is
smaller than this, no pulse is issued. Default = 0.0 seconds.

Equations
When the conditions of the following table are met, the table POSPROP raise/lower
pulse width equation can be used to determine the pulse raise or lower pulse width issued
by the POSPROP algorithm.

Table 31-2 POSPROP Raise/Lower Equation Decision

If... then...
(PVP < (SPP - DEADBAND)) AND (OPHIFL = Off) Issue a raise pulse
(PVP > (SPP + DEADBAND)) AND (OPLOFL = Off) Issue a lower pulse

ATTENTION
If neither of the above are true, then the cycle timer will be reset to the
beginning.

R688 HPM High-Performance Process Manager Control Theory 393

08/2019 Honeywell
31 Position Proportional Control Algorithm
31.3 Equations

Table 31-3 POSPROP Raise/Lower Pulse Width Equation

If the table then a pulse width equal to the following is issued...

“POSPROP
raise/lower
equation
decision”
indicates...

Raise
RAISETIM

Lower
LOWERTIM

394 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 31 Position Proportional Control Algorithm
31.4 Initialization

31.4 Initialization
Raise and lower outputs
The Raise and Lower outputs are either set to OFF (or their normal states) and the cycle
is restarted when forward calculation is resumed after initialization.
Setpoint
The SP is set equal to the PV (subject to the setpoint limits) when any of the following
conditions exist:
• the mode is Man.
• the slot is being processed for the first time after becoming active.
• this slot is a secondary within a local (inside the same HPM box) cascade control
strategy, and it is going through one-shot control initialization.

ATTENTION
The one-shot control initialization occurs:
• when the control initialization request flag (CTRLINIT) is On,
• when this slot is being processed for the first time after the HPM state
has been changed to RUN (Ok),
• when just recovering from a bad PV.
The position proportional control algorithm is forced to initialize when
outputting to a digital output point that has its INITREQ parameter = ON.

R688 HPM High-Performance Process Manager Control Theory 395

08/2019 Honeywell
31 Position Proportional Control Algorithm
31.4 Initialization

396 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 32. Ratio Control Algorithm
32.1 Functional Overview
Family
The Ratio Control control algorithm is a member of the Regulatory Control algorithms.
Description
The Ratio Control (RATIOCTRL) algorithm calculates a setpoint for a PID algorithm
that is the desired ratio of a controlled variable to an uncontrolled variable. The value of
the controlled variable is maintained at a specified ratio of the value of the uncontrolled
variable. The data point that uses this algorithm usually uses Calculator PV algorithm to
calculate the measured value of the ratio for displays and reports.
This Ratio-control algorithm has several advantages, including the display of the actual
ratio attained as calculated by the Calculator PV algorithm and direct control of the ratio
through the SP of the Ratio algorithm.
Figure 32-1 RATIOCTL Algorithm Functional Diagram

Actual Ratio from

PV Calculator Algo
Value Necessary to
Maintain the Ratio
From Initializing
Primary PV
CAS

SP RATIOCTL CV OP To Secondary
(Typically, SP
AUTO X2 for a PID)
Operator or
User-Written
Output
Program
Processing

Uncontrolled Filtered
Variable Value of X2
16 120

TIP
Ratio control can also be accomplished with the ratio-bias options of the PID
Control Algorithm or PID w/Feedforward Control Algorithm.

R688 HPM High-Performance Process Manager Control Theory 397

08/2019 Honeywell
32 Ratio Control Algorithm
32.1 Functional Overview

Application
The RATIOCTL algorithm is typically used in the control of the flow of a gas or fluid, as
a ratio of an another flow. For example, in a furnace, the air supply might be controlled
as a ratio of the fuel supply. If more heat is required to maintain combustion efficiency,
the fuel flow is increased and the air flow can be increased as a ratio of the fuel-flow
increase.
The following figure shows an example of such an application. In this example, the:
• data point that uses the Ratio-control algorithm also uses the Calculator PV
algorithm to calculate the actual ratio achieved, for display or printing.
• Calculator PV should use the filtered value (X2FILT) of the uncontrolled variable.

398 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 32 Ratio Control Algorithm
32.1 Functional Overview

Figure 32-2 Ratio Control Example Application

PVCALC = C1*P1/P2 = 0.7*17.143/6.00 = 2.00

P2 Calculator PVAUTO PV available for displays and reports
PV Algorithm 2.00
P1
PVMAN,PVSUB PV

"Other" PV CV = /SP*X2/K1 = 2*6/0.7 = 17.143

Flow
X2 RATIOCTL
=6.00 CV OP
GPM SP SP
Desired Ratio = 2.00
X2FILT

PV PID

17.143 GPM
Controlled Flow

F
16 121

To evaluate this example, see “Equations” in Section 32.3 and you will note that the
same scale factor, 0.7, is used for P1 in the PV algorithm and for K1 in the Ratio-control
algorithm. The resulting scaled ratio between the "other" flow and the controlled flow is
2.00/0.7 = 2.857, so if the "other" flow is 6.00 gallons per minute, the controlled flow
must be 6.00*2.857 = 17.143 gallons per minute.
The 0.7 scale factor is used for C1 and K1 in the example. This illustrates that the same
scale factors and bias values must be used with the PV algorithm and the Ratio-control
algorithm (K1 = C1, K2 = C2, B1 = C3, and B2 = C4). This is so that the actual ratio
calculated by the PV algorithm will be the same as the desired ratio (2.00) when the loop
is stable. If the scale factor in C1 and K1 were 1.0, the controlled flow would stabilize at
the "other" flow, multiplied by the ratio. In the example, the controlled flow would be
6.00*2.00 = 12.00 gallons each minute. In any case, the controlled flow stabilizes at a
value equal to the "other" flow, multiplied by the desired ratio, as modified by any scale
factors other than 1.0 or any bias values other than 0.

R688 HPM High-Performance Process Manager Control Theory 399

08/2019 Honeywell
32 Ratio Control Algorithm
32.2 Options and Special Features

32.2 Options and Special Features

Control input connections
This algorithm requires two input connections, for PV processing and X2. The number of
input connections is defaulted to 2; however, it can be increased to 3, allowing the SP to
be fetched with an input connection.

Engineering unit ranges

The PV engineering unit range (PVEULO and PVEUHI) must be specified. The setpoint
engineering unit range (SPEULO and SPEUHIU) always follows the PV range. The
output engineering unit range (CVEULO and CVEUHI) is derived from the secondary if
the number of output connections is greater than 0; otherwise, it must be specified.

Role of the Calculator PV algorithm

Any data point that uses RATIOCTL should use the Calculator PV algorithm (7.7.9).
X2FILT, the filtered value of the uncontrolled variable X2 is connected to P2 and the
variable controlled by the PID algorithm is connected to P1. The scale factors and bias
values in the Calculator PV algorithm must have the same values as their counterparts in
the Ratio Control algorithm:

RATIOCTL CALCULATOR
K1 C1
K2 C2
B1 C3
B2 C4

Thus, Calculator can calculate the actual (measured) ratio attained, and when the
PVSOURCE is Auto, that value is available in the PV parameter of the data point for use
on displays and reports.

Operating Modes
The RATIOCTL algorithm operates in the following modes:
• Man
• Auto
• Cas
• Bcas—if RCASOPT = Spc
Remote cascade options
Only the Spc option is supported.
400 HPM High-Performance Process Manager Control Theory R688
Honeywell 08/2019
 32 Ratio Control Algorithm
32.2 Options and Special Features

Restart or Point Activation

On a cold or warm restart or when the RATIOCTL data point is activated, initialization
takes place.
Error Handling
If the value status of the X2 input is bad, the CV value is changed to bad (NaN). The data
point remains in the same mode. When the X2 input again has normal status,
initialization takes place as described.
Operator entered bias
In R600 or later, the Algorithm includes an operator entered bias. This Bias parameter
(BO) value is added after all other calculations to obtain the CV for print. For equivalent
operation when migrating from PRE R600 Releases set BO = 0.0.
X2 filter
At the X2 input to the Ratio Control block, the value of the uncontrolled variable is
filtered by a single lag filter. Parameter X2TF determines The X2 filter time (0 - 60
minutes) and X2FILT is the filtered value of X2. The X2FILT value appears on the point
detail display. This filter is active only if the point is in the AUTO or CASC mode.
When X2TF is set for 0.0 minutes lag time, X2 is not filtered as was the case for the
algorithm prior to Release 500.
The default value of X2TF = 0.0.

R688 HPM High-Performance Process Manager Control Theory 401

08/2019 Honeywell
32 Ratio Control Algorithm
32.3 Equations

32.3 Equations
Background
The available equations with the Ratio Control Algorithm are:

• Calculator PV • Ratio Control

Equation legend
When reviewing the equations, please note that for the:
• Calculator PV equation—
− PVCALC = The calculated, actual ratio achieved.
− C1 = P1 scale factor. Must equal K1 of the RATIOCTL algorithm Default value =
1.0.
− C2 = P2 scale factor. Must equal K2 of the RATIOCTL algorithm Default value =
1.0.
− C3 = Bias constant P1 input. Should be the same value as B1 in the RATIOCTL
algorithm (Default value = 0).
− C4 = Bias constant P2 input. Should be the same value as B2 in the RATIOCTL
algorithm (Default value = 0.
− P1 = The controlled process variable (Source should be the same as the PV of the
PID controller that is RATIOCTL's secondary).
− P2 = The filtered value (X2FILT) of the uncontrolled process variable (If there is
a PID-controller controlling this other flow, the PV of that PID could be the
source for P2 and X2).
• Ration Control equation—
− B = The overall bias value (= BO + BI).
− BI = Internal bias.
− BO = Fixed output bias.
− CV = The calculated output in engineering units.
− SP = The desired ratio input.
− X2FILT = The filtered value of the uncontrolled process variable X2.
− BI = Internal Bias.
− B1 = Bias constant. Should be the same value as C3 in the CALCULTR PV
algorithm. Default = 0.

402 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 32 Ratio Control Algorithm
32.3 Equations

− B2 = Bias constant for the X2 input. Should be the same value as C4 in the
CALCULTR PV algorithm (Default = 0).
− K1 = The ratio scale factor. Must equal C1 of the CALCULTR PV algorithm.
− K2 = The scale factor for X2. Must equal C2 of the CALCULTR algorithm.
Equations
The equations used in the Ratio Control algorithm are defined in the following table.
Table 32-1 Ratio Control Algorithm Equations

Algorithm Equation

Calculator PV (C1 * P1 + C 3)
PVCALC =
(C 2 * P 2 + C 4)
Ratio Control SP * ( K 2 * X 2 FILT + B 2) − BI )
CV = +B
K1

R688 HPM High-Performance Process Manager Control Theory 403

08/2019 Honeywell
32 Ratio Control Algorithm
32.4 Initialization

32.4 Initialization
Operation
When the data point is initialized, an initialization request is sent to the primary, and the
initialization value to be applied by the primary to the SP input is calculated and sent to
the primary.
Initialization ramping bias
The bias (B) is made up of two components, BO and BI, where BO is the operator
entered bias and BI is the internal bias. Parameter RATE1 specifies the decay rate for the
Internal Bias, BI. The value of BI is set during the algorithms initialization and decays to
zero at a rated defined by RATE1.
If RATE1 is set to NaN, the initialization ramping value is set to 0.0 and the initialization
value for the primary is determined by back calculation compatible with Pre-R500
functions. (When migrating from R4xx or R5xx to R600, the fixed bias term BO should
be defaulted to 0.0.) When RATE1 = NaN, then:
K1 * (CV − BO) + BI
INITVAL =
K 2 * X 2 FILT + B 2
If RATE1 is set to a non-zero value, and the Ratio Control block is in Cascade mode, the
SP value is back calculated. During initialization, an internal bias that is equal to the
difference between the old CV value and the new CV value is added to the output
calculation to produce a bumpless output Internal Bias (BI) is calculated as follows
(where CVold is the last calculated CV value before initialization):
SP * ( K 2 * X 2 FILT + X 2) − BI
BI = CVold – - BO
K1
If the primary accepts the initialization value (INITVAL), then BI turns out to be zero.
If the primary does not accept the initialization value, then BI turns out to be non-zero. If
not zero, the internal bias (BI) decays at the rate specified by RATE1. RATE1 is
specified in engineering units per minute. If RATE1 = 0, then BI does not decay but
remains fixed.
If the Ratio Control block operates in Auto mode during initialization when the mode
changes from manual to auto, the internal bias (BI) is added to the output. BI decays at
the rate specified by RATE1 as described for Cascade mode.
The default value of RATE1 = NaN.

404 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 32 Ratio Control Algorithm
32.5 Override Feedback Processing

32.5 Override Feedback Processing

When the data point's secondary uses an Override Selector algorithm, the following
functions take place if the RATIOCTL algorithm if it is in Cas mode:
• the override status is sent to the primary data point in PTORST (Point Override
Status).
• If the status in PTORST is not selected, a feedback value, calculated as follows, is
sent to RATIOCTL's primary data point (where ORFBSEC is the override-feedback
value received from the secondary data point)
K1 * (ORFBSEC − B) + BI
ORFB =
K 2 * X 2 FILT + B 2

Figure 32-3 Override Feedback Processing

From Initializing
Primary
CAS

SP RATIOCTL
AUTO CV OP X1 CV
X2 Override
X3 SELECTOR
X4

To I NITVAL PTORST
Primary PTORST ORFBSEC
ORFBSEC
ORFBSEC is not an external parameter.

R688 HPM High-Performance Process Manager Control Theory 405

08/2019 Honeywell
32 Ratio Control Algorithm
32.5 Override Feedback Processing

406 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
35 Incremental Summer
35.5 Override Feedback Processing

33. Ramp and Soak Control Algorithm

33.1 Functional Overview
Family
The Ramp and Soak (RAMPSOAK) control algorithm is a member of the Regulatory
Control algorithms.
Description
This algorithm is typically used as a setpoint programmer. It produces an output that
consists of up to 12 alternate ramps and soak periods—a total of 24 segments. Twelve
pairs should be enough to cover most applications commonly encountered; however, if
longer ramp and soak sequences are required, four such algorithms can be configured to
push to a control switch algorithm. Then, using logic, the switch could select one of the
ramp and soak algorithms.
When not used in connection with the switch algorithm, output from this algorithm is
usually used as the setpoint for a secondary data point that uses a PID algorithm to
control a process variable, according to the ramps and soak periods. The PV of a data
point that uses RAMPSOAK is normally the PV of the PID point.

432 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
33 Ramp and Soak Control Algorithm
33.1 Functional Overview

Figure 33-1 Ramp and Soak Control Algorithm Functional Diagram

PV RAMPSOAK CV OP SP PID
CV OP
PV
Outpu t
Processing

FT

SOAKT3
SOAKV3
SOAKT2
RATE3 SOAKT4
CV SOAKV2 RATE4
SOAKT1
RATE2 SOAKV4
SOAKV1
RATE1

Time

Application
RAMPSOAK is principally used for automatic temperature cycling in furnaces and
ovens. It can also be used for automatic startup of units, and for simple batch-sequence
control where the batch sequence is part of a process that is otherwise a continuous
process.

408 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 33 Ramp and Soak Control Algorithm
33.1 Functional Overview

Sequencing
The Ramp and Soak control algorithm supports both Single and Cyclic sequencing.
Once started, the configured sequence of ramps and soak periods repeats itself, if it is not
stopped by an operator or by a user-written program. A Universal Station operator can
put the point in Man mode to freeze the sequence, and then return it to Auto to continue
the sequence.
A configuration parameter called cycle option (CYCLEOPT = Single or Cyclic) is
provided that optionally permits the cycle to stop after completing a single cycle. This
works as follows:
• CYCLEOPT = Single
− When the mode is changed from Man to Auto, the algorithm cycles through the
configured rampsoak sequence until the last soak segment is completed. At this
point, the mode is switched back to Man and the current segment ID is set to
RAMP1 (the first segment). Another sequence can now be executed by simply
switching the mode back to Auto.
• CYCLEOPT = Cyclic
− When the mode is changed from Man to Auto, the algorithm cycles through the
configured rampsoak sequence until the last soak segment is completed. At this
point, the current segment ID is set to RAMP1 (the first segment) and the whole
cycle is repeated.
Operational modes
The operating modes establish the operating state of the RAMPSOAK algorithm as
follows:
• Man mode, where—
− the sequence is stopped and the ramp/soak timers are not running.
− the Ramp and Soak actions are suspended.
− this allows the user to enter starting output value for the Ramp/Soak profile and
to change the value during profile.
− the timers are stopped and hold the last value.
− the value in CV is replaced by the OP value (after converting to EUs).
− SP = CV (SP doesn't affect the output but can be seen at Universal Stations and
user-written programs).
• Auto mode, where—
− the sequence is running.

R688 HPM High-Performance Process Manager Control Theory 409

08/2019 Honeywell
33 Ramp and Soak Control Algorithm
33.1 Functional Overview

− If the current segment is a ramp, and if the guaranteed ramp conditions are OK,
CV changes at the ramp rate. Should the CV overshoot the next soak value, it is
clamped at that value and, the remaining soak-time (REMSOAKT), the current-
segment (CURSEGID), and the mark timers and flags are updated.
− If the guaranteed ramp conditions are not OK, the mark timers are stopped.
− If the current segment is a soak, and if the point just changed from Man to Auto,
or just started the soak segment, and the guaranteed soak time conditions are not
OK then, the soak timer doesn't start, CV remains at its last value, the mark
timers are stopped.

ATTENTION
If the polarity of the ramp rate is opposite to the soak target value, the output
jumps to the soak target value. That is, the ramp segment for this ramp/soak
cycle is omitted and the next segment is invoked.

Changing remaining Soak Time and Current Segment

When the RAMPSOAK point is in Man mode, an operator at a Universal Station can
change the remaining soak time (REMSOAKT) if the current segment is a soak.
Also, when the point is in Man mode, an operator can change the current segment
(CURSEGID).
When the mode is returned to Auto the sequence continues, as modified by these
changes. If the segment was changed, the sequence resumes with the new segment,
which can be a ramp or a soak.
Because changes to these parameters don't change the mark functions (see “Mark Timer
functions” in Section 33.1), except if CURSEGID is a lower segment than the mark
segment (SnSEGID), operators should not be allowed to change REMSOAKT or
CURSEGID when the mark functions are configured.

410 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 33 Ramp and Soak Control Algorithm
33.1 Functional Overview

Guaranteed Soak-Time
This feature guarantees that the PV is at the proper soak value before the soak-time
measurement begins.
If, when a soak segment begins or is resumed by switching from Man to Auto, the PV is
not within a user-specified deviation (MXSOKDEV) from the SP value (SP always
equals CV), the soak timer doesn't start. When the deviation is within the MXSOKDEV
value, the timer is started and continues, even if the deviation again exceeds
MXSOKDEV.
Because the PV could be above or below SP, it is the absolute value of the deviation that
is checked against MXSOKDEV.
To bypass this check you can change MXSOKDEV to NaN.
The soak timer can also be kept from starting when HOLDCMD is On. This allows you
to use a Logic Slot to set HOLDCMD to hold the soak timer until some other condition is
met.

ATTENTION
HOLDCMD also affects the guaranteed ramp function.

Guaranteed Ramp Rate

This feature guarantees that the PV keeps up with the desired value indicated by SP (SP
always tracks CV).
You can specify a maximum ramp-deviation value in MXRMPDEV. There are two
conditions that cause the ramp to stop to wait for the PV to catch up with SP. They are
• RATEn > 0 and PV < (SP - MXRMPDEV)
• RATEn < 0 and PV > (SP + MXRMPDEV)
These checks are bypassed if MXRMPDEV contains NaN.
Another condition that stops the ramp is HOLDCMD containing On. You can use a logic
slot to set HOLDCMD to stop or hold the ramp until some condition that you specify is
met.
The content of HOLDCMD also affects the guaranteed soak-time feature.

R688 HPM High-Performance Process Manager Control Theory 411

08/2019 Honeywell
33 Ramp and Soak Control Algorithm
33.1 Functional Overview

Figure 33-2 Wait Time Between Phases

Soak Timer Begins

By assuring that PV = proper soak value, the

user is assured of, for example, the proper
RAMP wait time between phases of a warm up or that
= SP temperature is held for the proper length of
PV time during heat treating.

Figure 33-3 Ramping Waits for the Process

By ensuring that the ramping "waits" for the

process to catch up, we never have a large
SP error caused by setpoint change.

PV

412 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 33 Ramp and Soak Control Algorithm
33.1 Functional Overview

Mark Timer functions

Two flags are provided with the RAMPSOAK algorithm to indicate to other data points
that a specified time has elapsed from the beginning of a specified ramp segment or soak
segment. These mark-timer flags are S1 and S2.
Each of these flags has three associated parameters that specify the segment in which the
flag is set On, the time counted from the beginning of the segment, and the time from the
beginning of the segment until the end time (when the flag is set Off). These parameters
are listed in the following table.
Table 33-1 Mark Timer Parameters

Flag Segment Beginning Time End Time

S1 S1SEGID S1BGNTIM S1ENDTIM

S2 S2SEGID S2BGNTIM S2ENDTIM

Figure 33-4 Ramp/Soak Mark Timers

NOTE
For example S1SEGID = 2
S1BGNTIM = 5 min
S1ENDTIM = 6 min • S1BGNTIM must be less than
Pulsewidth = ENDTIM-BGNTIM or equal to S1ENDTIM.
(Same is true for S2 parameters.)
SEG1 SEG2
5 6 • S1ENDTIM is not required to
—
—
—
—
—— —
—— —

terminate the marker within the

segment specified by S1SEGID. For
example, if Segment 2 is only 5.5
minutes long, then the marker will
remain on until 6 minutes after the
S1 start of Segment 2 (which is 0.5
minutes into Segment 3).
Timer Starts

R688 HPM High-Performance Process Manager Control Theory 413

08/2019 Honeywell
33 Ramp and Soak Control Algorithm
33.1 Functional Overview

The S1 or S2 flag is turned on at the number of minutes after the specified segment
begins, as is specified in SnBGNTIM. The corresponding flag is turned Off at the
number of minutes after the specified segment begins, as specified in SnENDTIM.
The following functions also take place:
• At the end of the last segment in the sequence, the S1 and S2 flags are turned Off
and the timers are reset.
• When a ramp or a soak segment is held up by the guaranteed-ramp or the
guaranteed-soak functions, the mark timers are suspended.
• The mark timers suspend when the data point is in Man mode and the S1 and S2
flags are unchanged.
• If the remaining soak time (REMSOAKT) is changed (in Man mode), the mark
timers are not affected.
• If the current segment (CURSEGID) is changed (in Man mode) to a segment that is
earlier than or equal to a segment specified by SnSEGID, the corresponding mark flag
goes to Off and its timers are reset. If a later segment is specified in CURSEGID, the
flags and timers are not affected.
Long sequences
A sequence of more than 12 ramp and soak segments can be attained by interconnecting
RAMPSOAK points. A Logic Slot can be used with a Switch Algorithm (see “

414 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 33 Ramp and Soak Control Algorithm
33.1 Functional Overview

Switch Control Algorithm” in Section 1) to select any of the four RampSoak Algorithm
data points.
Longer sequences can be accomplished by setting the S1 Mark Flag at the end of the last
soak segment (S1 must be on for at least one sample time).
A Logic point reads the S1 Mark Flag and, using a pulse Logic Block (Pulse width can
be one sample time), sets the corresponding S input on the Switch Algorithm. This
causes the next RampSoak to become selected and all non-selected RampSoaks are INIT.
The Switch Algorithm should be configured for tracking and Equation B.

432 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
33 Ramp and Soak Control Algorithm
33.1 Functional Overview

Figure 33-5 Using a Logic Slot to Achieve Additional Rampsoak Segments

RSK1

SP OP
X1

PV S1

To Logic
OP
RSK2
SP OP
X2

PV S1 S1

S2
To Logic
TRACKING
EQUATION B

LOGIC

RSK1 .S1 L1 SWITCH.S2

PUL SE

L2 SWITCH.S1
PUL SE

PROCESSING ORDER:

LOGIC RSK1 RSK2 SWITCH

416 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 33 Ramp and Soak Control Algorithm
33.1 Functional Overview

Engineering unit ranges

Engineering Unit Ranges; Setpoint , Output and Deviation Limits
The PV engineering unit range (PVEULO and PVEUHI) and the output engineering unit
range (CVEULO and CVEUHI) must be specified. The setpoint engineering unit range
(SPEULO and SPEUHI) always follows the PV range.
If the RAMPSOAK data point uses a PV algorithm, the setpoint EU range is the same as
the PV EU range, and can't be differently configured. You should configure this point's
PV EU range to be the same as the SP EU range of the secondary point that is receiving
this point's output.
Output and Deviation limits
Output limits are defaulted to -6.9% to 106.9% and cannot be changed. Deviation limits
(MXRMPDEV and MXSOKDEV) apply to all segments in the sequence.

ATTENTION
Setpoint limits are not available.

Restart or point activation

On a cold restart, a warm restart, or when the data point is activated, the mode goes to
Man and the CV value is NaN. All timers are reset, and the current segment ID is made
equal to the first ramp segment.
No special action occurs on a hot restart and the operation continues from where it was.
Control input connections
The ramp soak control algorithm requires only one control input connection (for PV).
The number of control input connections is fixed at one.
In a typical application, the output of this algorithm provides the SP of a secondary
controller (which is usually a PID control algorithm). The PV of the secondary controller
is then fetched with a control input connection into the PV of the RAMPSOAK. If used
in some different way such that the PV is not available from the secondary, the PV of the
RAMPSOAK should be fetched from its own SP parameter.

R688 HPM High-Performance Process Manager Control Theory 417

08/2019 Honeywell
33 Ramp and Soak Control Algorithm
33.2 Equations

33.2 Equations
There are no configurable equations for the RAMPSOAK algorithm. The ramp and soak
segments are specified in the following:
• Number of ramp/soak segment-pairs in the sequence—NORSSEQ (Default = 2).
• Ramp Rates, EUs per minute—RATE1 through RATE12 (Default = NaN).
• Soak values—SOAKV1 through SOAKV12 (Default = NaN)
Soak times, in minutes—SOAKT1 through SOAKT12 (Default = 0).

418 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 34. Auto Manual Control Algorithm
34.1 Functional Overview
Family
The Auto Manual control algorithm is a member of the Regulatory Control algorithms.
Description
In cascade mode, this algorithm calculates a control output that is equal to the input value
plus a bias value. The bias value is normally provided by an operator. In manual mode,
the output is controlled by an operator or a user-written program.
Figure 34-1 Auto Manual Control Algorithm Functional Diagram

CAS
o o
MAN
From Primary o
Data Point
Output
CAS Processing
o
o X1
o To
MAN CV OP
Secondary

To
Primary INITVAL

CV = X1 +B

Where :

X1 = Input (usually from a Primary PID controller)

B = BO + BI

B = Overall Bias, consisting of:

Equation A:

BO = Operator-entered bias = K * X2 for Equation B

BI = Initialization Bias Component

R688 HPM High-Performance Process Manager Control Theory 419

08/2019 Honeywell
34 Auto Manual Control Algorithm
34.1 Functional Overview

Equation A is designed to provide "bumpless" returns to cascade operation, even though

its primary data point may not accept the initialization value from the AUTOMAN data
point. Equation B provides automatic balancing of the biases between several auto
manual stations and "bumpless" closing of cascades, with ramping of the initialization
component.
Use
The AUTOMAN control algorithm typically serves as the ultimate secondary data point
in a cascade-control strategy. As such it directly drives the control element (valve)
through an analog output slot (a slot using a PID algorithm).
Figure 34-2 AUTOMAN Serving as Ultimate Secondary in a Fan-Out
Configuration

PRIMARY Output
DATA POINT Processing

o CAS
o AUTOMAN CV OP
o
Man
Analog Output
Slot Using PID
Algorithm
To Additional
Secondary
Data Points

This algorithm is very useful for a secondary data point that is one of two or more
secondaries of the same primary data point (a "fan-out" configuration). In such a
configuration, AUTOMAN can provide a "bumpless" output even if its primary doesn't
accept AUTOMAN's initialization request, but accepts one from one of its other
secondaries. This might happen because the AUTOMAN point is temporarily out of the
cascade because it is inactive or because it is in Man mode.
For an example of output from a PID controller to two auto manual stations, see the
example under “Equation B” in Section 34.3).
You cannot write to the X1 parameter of this algorithm from an AM using a control
output connection.

420 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 34 Auto Manual Control Algorithm
34.2 Options and Special Features

34.2 Options and Special Features

Bumpless returns to cascade
To support the use of this algorithm as one of the secondaries in a fan-out configuration,
special handling of the bias value is provided. When the data point is configured for
external initialization, the bias value, B, consists of two components (where B0 = the
internal adjustment-value range, usually 0, and BI = the internal storage for operator-
entered or program entered bias values).
B = BO + BI
When the user or a program enters a bias value in B while in cascade operation, that
value goes to B0 and BI is forced to zero. BI is an internal parameter that cannot be
accessed by a user. B cannot be entered in Equation B.
When the cascade connection is broken (in Man mode, initialization-manual input, and
so on) a value is calculated for the primary to initialize to, as follows:
INITVAL = CV - BO
When cascade operation resumes, the value in BI is calculated as follows (where Opprim
= the actual output value from the primary data point (X1 input)):
BI = INITVAL - OPprim
If the primary data point did accept AUTOMAN's initialization value, BI turns out to
contain zero. If the primary did not accept INITVAL, BI contains a value that causes CV
to contain the value it had just before the cascade closed. In either case, CV does not
"bump."
If BI has a value other than zero, then internal bias behavior depends on the value
specified by the user in the RATE1 parameter. RATE1 is specified in engineering units-
per-minute or NaN. If RATE1 is set to NaN, then the internal bias instantaneously
changes to 0 and may cause a bump in the output. If a positive value is entered in
RATE1, the value of BI ramps to zero at a rate specified in the RATE1 parameter. Thus,
while the output doesn't "bump" it does ramp to the new value called for by the input
from the primary.

R688 HPM High-Performance Process Manager Control Theory 421

08/2019 Honeywell
34 Auto Manual Control Algorithm
34.2 Options and Special Features

Operating modes
The AUTOMAN algorithm supports three operating modes:

• Man • Cas • Bcas if RCASOPT = Ddc

Remote cascade options

Only the Ddc option is supported.
Engineering unit ranges
You must configure the X1 input range in XEULO and XEUHI. The output engineering
unit ranges (CVEULO and CVEUHI) always follow the X input ranges.
Restart or point activation
On a cold or warm restart or when the data point is activated, initialization takes place as
described under Bumpless returns to cascade. On a hot restart, initialization does not
occur.
Error handling
If the X1 input has a bad-value status (or Equation B and X2 is bad), the CV value is bad
but the data point remains in the same mode. When the bad input returns to normal, CV
is recalculated and an initialization request is sent to the primary.

422 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 34 Auto Manual Control Algorithm
34.3 Equations

34.3 Equations
Background
This algorithm has two equations.
Equation legend
For Equation A
• B = B0 + BI)
For Equation B:
• CV = Control algorithm output in Engineering Units
• X1= Initializable input pushed from primary
• B = Bias Value, and
• B = (K * X2) + BI
• X2 = input connection fetched with input connection #1
• BI = Initialization Bias Component
Equation A
Equation A is as follows:
CV = X1 + B
X1 is the input that is typically pushed from the primary PID controller and B is the
overall bias, which consists of the operator set bias component (BO) and the initialization
bias component (BI).
This form of the equation requires NO input connection. The number of input
connections is defaulted to 0; however, it can be increased to 1, allowing the X1 input to
be fetched with an input connection (X1 fetched by connection number 1).

R688 HPM High-Performance Process Manager Control Theory 423

08/2019 Honeywell
34 Auto Manual Control Algorithm
34.3 Equations

Equation B
Equation A is as follows:
CV = X1 + B
X1 is the input that is typically pushed from the primary PID controller and B is the
overall bias, which consists of the automatic bias adjustment (K * X2) and the
initialization bias component (BI). X2 is fetched with an input connection (#1) from a
calculated input. Bumpless closing of cascades is provided the same as in Equation A
(with ramping of the initialization component). The overall Bias B is a read-only
parameter and cannot be stored to.
Equation B requires only one input connection — X2. The number of input connections
is defaulted to one; however, it can be increased to two, allowing the X1 input to be
fetched with input connection #2.
Equation examples
If a PID controller outputs to two auto manual stations, the operator may want the total
required offset between the outputs of the two auto manual stations to be distributed
equally above and below the PID's output. The operator can store the bias (= half the
required offset) to the first auto manual station (configured for Equation A). The second
auto manual must be configured with Equation B, have K of -1.0, and get its X2 input
from the B0 parameter of the first one. Thus, whenever the operator changes B0 of the
first auto manual point, the bias of the second point tracks automatically.
Alternately, the strategy could be configured so that the bias value is held in a numeric.
Each auto manual point would then fetch the numeric value into its X2 input. In this
configuration, bias balancing is achieved by setting K on the two auto manual stations to
+0.5 and -0.5, respectively.

424 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 34 Auto Manual Control Algorithm
34.4 Initialization

34.4 Initialization
Initialization value = CV - B. For additional information, refer to Bumpless returns to
cascade.

34.5 Override Feedback Processing

When the data point's secondary uses an Override Selector algorithm , the following
functions take place:
• If this point is in Cas mode, Override Status PTORST is returned to this point
through special processing.
• If that status is "not selected," an override-feedback value is calculated as follows,
and it is passed on to the AUTOMAN data point's primary.
ORFB = ORFBSEC - B
Figure 34-3 AUTOMAN Override Feedback Processing

From Initializing Output (OP)

Primary Processing

CAS
o
o X1 CV X1
o X2 Override
AUTO MAN SELECTOR CV
MAN X3
X4

PTORST-(Selected)
To INITVAL
Primary PTORST ORFBSEC
ORFBSEC

ORFBSEC is not an external parameter

R688 HPM High-Performance Process Manager Control Theory 425

08/2019 Honeywell
34 Auto Manual Control Algorithm
34.5 Override Feedback Processing

426 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 35. Incremental Summer
35.1 Functional Overview
Family
The Incremental Summer control algorithm is a member of the Regulatory Control
algorithms.
Description
This algorithm calculates the sum of the incremental changes in up to four input values.
The output is obtained by adding the sum of the changes in all inputs, after each input is
multiplied by a scale factor.
Figure 35-1 Incremental Summer Control Algorithm Functional Diagram

X1
X2 To
INCRSUM CV OP
X3 Secondary
X4

Output
Processing

Equation:

CV = (last value) + sum of changes in all inputs

Inputs and outputs

This algorithm requires no input connections. The number of input connections is
defaulted to 2, but it can be increased to up to four. For each input connection, the user
must also specify the destination parameter, X1, X2, X3 or X4.
The primaries usually use PID algorithms, and are connected to an INCRSUM data point.
The output from the INCRSUM data point is connected to the secondary. This is
sometimes referred to as a "fan-in connection."

Figure 35-2 Incremental Summer Input and Output Connections

R688 HPM High-Performance Process Manager Control Theory 427

08/2019 Honeywell
35 Incremental Summer
35.2 Options and Special Features

PID
X1
PID X2
INCRSUM CV OP SP Secondary
X3
PID Data Point
X4 PV
PID

Use
This algorithm is typically used where more than one primary data point is used to
manipulate the setpoint of the same secondary data point.

35.2 Options and Special Features

Handing inputs from PID outputs
Special handling of the outputs of PID data points is necessary in the Incremental
Summer, because it is the dynamic operation of the PID that is significant—the full-value
output is not significant. As the process variables change, PID outputs have no direct
relation to the input, therefore they are said to be "floating." The incremental summer
responds only to changes in the PID outputs, and calculates a full-value output to be
applied to the control device (valve) in the process or to the secondary data point.
While the PID algorithms handle SPs, PVs, and outputs as percentages of the configured
range, the Incremental Summer performs its calculations in engineering units.
To prevent a primary PID point in Auto or Cas mode from winding-up beyond its own
output limits, every time the Incremental Summer point is processed it changes the PID's
output value to its own CV value after converting to percent. This does not affect the
dynamic changes in the PID outputs.
If a primary PID is in Man mode, the PID's CV is not changed by the Incremental
Summer.
Certain restrictions apply to the PID points that are the Incremental Summer point's
primaries. Each must:
• have only one control-output connection.
• reside in the same HPM box.
• be a normal PID or a PID Feedforward.
Engineering unit ranges
You must configure the X-input ranges in XEULO and XEUHI. The output engineering
unit ranges (CVEULO and CVEUHI) always follow the X input ranges.

428 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 35 Incremental Summer
35.2 Options and Special Features

Changing the output with user written programs

User-written CL programs in the AM or user-written programs in a Computing Module
can directly store new values in the CV parameter of the Incremental Summer's data
point while the Incremental Summer point is in BCas mode, or if in CAS mode and
RCASOPT is not = DDC, and normally operating. This causes a shift in the CV value but
the dynamic changes continue, because the Incremental Summer dynamically increments
or decrements CV each time the point is processed.
Operating modes
This algorithm operates only in Man and Cas modes, and in Bcas if RCASOPT = Ddc.
Because the output of each PID primary tracks the OP output value of the INCRSUM
data point, switching this point from Man to Cas does not "bump" the process.

ATTENTION
The dynamic correction calculated by a PID primary appears as a change in
that data point's output after it is processed again and the Incremental
Summer actually uses this change as its input. The full-value outputs of PIDs
connected to the Incremental Summer have no meaning.

Remote cascade options

Only the Ddc option is supported.
Restart or point activation
On a warm restart, or point activation, initialization takes place as described under
Initialization.

R688 HPM High-Performance Process Manager Control Theory 429

08/2019 Honeywell
35 Incremental Summer
35.3 Equations

Bad control handling

When an input becomes bad ( = NaN), it is not used in the calculation. No bad control
alarm is generated. When the bad input returns to a normal value, its use in the output
computation is resumed in the CV calculation without "bumping" the value. This feature
allows adding multiple feedforward signals to the output of a PID controller.

ATTENTION
If a single feedforward input is needed, the PID feedforward control algorithm
should be used.

35.3 Equations
Equation legend
When CV is calculated:
• CV(n) = Current full value of the output of this algorithm in engineering units.
• CV(n-1) = Past full value from the data point (value from the last time the data point
was processed).
• m = The number of inputs actually used (m = 1 through 4).
• K1 through Km = User-specified scale factors (gains). K1 through K4 default to 1.0.
• X1(n) through Xm(n) = Current values of each X input in use.
• X1(n-1) through Xm(n-1) = Past value of each X input (value from the last time the
data point was processed).
Equations
CV is calculated as follows:
CV(n) = CV(n-1) + K1*[X1(n) - X1(n-1)]
+ K2*[X2 - X2(n)(n-1)]
.
.
.
+ Km*[Xm(n) - Xm(n-1)]

35.4 Initialization
Initialization occurs in Man mode when the output is indisposable, or when recovering
from a bad CV value (NaN), as follows:
• An initialization request is sent to all primary data points (up-to-four).
• The Incremental Summer's CV value and past values are initialized as—

430 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 35 Incremental Summer
35.5 Override Feedback Processing

CV(n-1) = CV
X1(n-1) = X1
.
.
.
Xm(n-1) = Xm

35.5 Override Feedback Processing

Override control strategies
If the Incremental Summer's secondary is an Override Selector data point, and its
Override Status (PTORST) is not selected, the CV of the INCRSUM data point is set
equal to the override feedback value. During the next pass of forward calculation, the
incremental summer computes its CV in the normal fashion.

TIP
This is very useful for cases where several feedforward signals are added to
the output of a PID controller (the addition done by the incremental summer
algorithm) and the overall result is fed to an override selector. Because the
output of the PID controller tracks the output of the incremental summer,
which in turn tracks the output of the override selector when not selected, the
output of the PID controller is prevented from winding up when not selected
by the override.

R688 HPM High-Performance Process Manager Control Theory 431

08/2019 Honeywell
35 Incremental Summer
35.5 Override Feedback Processing

432 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 36. Switch Control Algorithm
36.1 Functional Overview
Family
The Switch control algorithm is a member of the Regulatory Control algorithms.
Description
This algorithm operates as a single-pole, 4-position rotary switch. An operator, a user-
written program, or user-configured logic can change the position of the switch, thereby
selecting any one of the four inputs to be the control-algorithm output value, CV.
Figure 36-1 Switch Control Algorithm Functional Diagram

Position Controller by Operator,

User-Written Program, or
User-Configured Logic

X1
MAN
X2 CV OP
From up to 4
Other Data
Points CAS
X3
X4 Output
Processing

Equation A: Operator Controls Switch Position

Equation B: Program or Logic Controls Switch Position, Operator can store to

SELXINP if all S1-S4 flags are OFF

You cannot write to X1 from an AM Regulatory point using a control output connection.
Inputs and outputs
This algorithm requires no input connections. The number of input connections is
defaulted to 2; however, it can be increased to up to 4. For each input connection, the
user must also specify the destination parameter as X1, X2, X3 or X4.

R688 HPM High-Performance Process Manager Control Theory 433

08/2019 Honeywell
36 Switch Control Algorithm
36.1 Functional Overview

Use
The Switch control algorithm is used to allow the operator to alter control strategies by
selecting any of four inputs to be passed on to the output, if Equation A is chosen. If
Equation B is chosen, a Logic Slot can change the switch position, or the operator can
store to SELXINP if all four input selection flags (S1, S2, S3, and S4) are Off.
You can use SWITCH to select inputs from differing sources and to pass them on to a
single destination or you can use more than one SWITCH data point to switch a single
source to differing destinations. The following figure shows an example of each of these
situations.
Figure 36-2 Switch Control Algorithm Examples

Either A, B, C, or D is Connected to E:

A
X1
B
X2
SWITCH CV OP SP E
X3
C
X4
D

F is connected to G or H, or to both G and H:

F X1 SWITCH CV OP SP G

X1 SWITCH CV OP SP H

434 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 36 Switch Control Algorithm
36.2 Options and Special Features

36.2 Options and Special Features

Engineering unit ranges
The X-input engineering unit ranges (XEULO and XEUHI) must be specified for X-
inputs. The output engineering unit ranges (CVEULO and CVEUHI) always follow the
X-input ranges.
Switch position control
The Switch control algorithm provides two equations:
• Equation A – Operator Switching, where an operator can change the switch
position by—
− altering the value in SWITCH data-point parameter SELXINP—The value in
SELXINP specifies the Xn input selected. The corresponding S1, S2, S3, or S4
switch indicator goes On and the other three switch indicators go Off.
− changing the desired switch indicator from Off to On—When one of the S1, S2,
S3, or S4 indicators is changed to On, all others go Off. SELXINP then
indicates the position selected.

TIP
Changing the desired switch indicator from Off to On is very useful when
operating with custom displays. The displays can be built to allow the
operator to see the positions and strategies selected unless S1 through S4
are all OFF.

ATTENTION
When the configuration is changed from Equation B to Equation A, ensure
the following:
• No external connections exist for S1, S2, S3, or S4 connections of the
switch.
• If connections exist from external sources, ensure that these connections
are active and are On.

• Equation B – Automatic Switching, where logic or user written programs switch

between inputs—
− turning an S1, S2, S3, or S4 indicator On does not turn the others Off.
− the switch position is changed by storing On and Off in the S1-S4 parameters as
defined in the following table.

R688 HPM High-Performance Process Manager Control Theory 435

08/2019 Honeywell
36 Switch Control Algorithm
36.2 Options and Special Features

Table 36-1 SELXINP Parameter Status

S1 S2 S3 S4 Xn SELXINP

On – – – X1 SELECTX1

Off On – – X2 SELECTX2

Off Off On – X3 SELECTX3

Off Off Off On X4 SELECTX4

Where "–" means On or Off does not affect the switch position.
S1 has the highest priority, S4 has the lowest.

ATTENTION
In the HPM, an operator is allowed to change the switch position, by storing
to the SELXINP parameter when configured for Equation B, if all input
selection flags (S1, S2, S3 or S4) are Off.

436 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 36 Switch Control Algorithm
36.2 Options and Special Features

Tracking
You may configure the SWITCH algorithm for the tracking option, which causes non-
selected inputs to track the selected input value. This allows the switch position to be
changed without "bumping" the output.
When tracking option is configured, the primaries connected to non-selected inputs can
be initialized. Should one of the primaries not accept the initialization value from the
SWITCH data point, the output may bump when that input is selected. (A primary might
not accept an initialization value because it has more than one secondary and accepts
initialization from one of its other secondaries.)

ATTENTION
For the tracking option to work, the Switch input must come from an HPM
primary Regulatory Control point. The output destination from the RegCtl
point must specify the Switch point (that is, the Switch input must be pushed
from the RegCtl point).
When SWITCH is included in an override control strategy, the tracking option
must be configured.

Operational modes
The Switch-control algorithm operates in the following modes:
• Man
• Cas
• Bcas if RCASOPT = Ddc
Remote cascade options
Only the Ddc option is supported.
Restart or point activation
On a cold or warm restart, or when the SWITCH data point is activated, initialization
takes place, as configured (see “Initialization” in Section 36.4).
On a hot restart, normal operation resumes with no initialization.
Error handling
If a selected input has a bad-value status, the CV value goes bad (NaN), but the operating
mode does not change. When the status of the selected input is again good, CV is
recalculated, an initialization request is sent to the primary data point.

R688 HPM High-Performance Process Manager Control Theory 437

08/2019 Honeywell
36 Switch Control Algorithm
36.3 Equations

36.3 Equations
Background
The Switch control algorithm provides two equations:
• Equation A – Operator Switching, where an operator can change the switch
position.
• Equation B – Automatic Switching, where logic or user written programs switch
between inputs.
Equation legend
In Equations A and B:
• n = 1, 2, 3, or 4.
• CV= The control output value in engineering units.
• SELXINP = The selected-input. Default = SelectX1.
• S1 through S4 = Switch indicators.
• M = The number of inputs configured. Default = 2.
Equations
Equations A and B:
CV = Xn

ATTENTION
Equations A and B differ in controlling aspect of the switch position. For
additional details, refer to Switch position control.

438 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 36 Switch Control Algorithm
36.4 Initialization

36.4 Initialization
When an initializing condition occurs, an initialization request is sent to the selected
primary and the initialization value is the present CV value.
If the tracking option is configured (see “” in Section 36.2), the non-selected primaries
are continually initialized.

36.5 Override Feedback Processing

If this data point's secondary is an Override Selector point and if this point is in Cas
mode, when override-feedback processing takes place, override status and an override
value are passed to this point's primary. The status is in parameter PTORST.
If PTORST indicates not selected, the value passed to the selected primary in ORFB is
equal to the value received from the secondary in ORFBSEC.

R688 HPM High-Performance Process Manager Control Theory 439

08/2019 Honeywell
36 Switch Control Algorithm
36.5 Override Feedback Processing

440 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 37. Override Selector Control Algorithm
37.1 Functional Overview
Family
The Override Selector control algorithm is a member of the Regulatory Control
algorithms.
Description
The Override Selector Algorithm is used with up-to-four PID inputs, all of which are
initializable. The input with the highest value or the input with the lowest value is
selected and passed on to the output of this data point. The algorithm can operate as a
simple selector or an override option can be configured that prevents PID points in an
override-control strategy from winding up.
If the override option is configured (OROPT = On), an operator can put the ORSEL point
in a bypass state and any of the inputs can be bypassed; that is, not used in the algorithm
calculation. Four logical parameters are provided to select the input to be bypassed.
These parameters are BYPASSX1, BYPASSX2, and so on. There is an additional
parameter, BYPASS. When BYPASS = On, the input Xn for which BYPASSXn is On is
initialized (equal to the selected input) and not used in the calculation of the output.
When all four inputs are bypassed, the output is maintained at the last values.
All bypass parameters can be stored by the operator, or any system function, but only the
BYPASS parameter is available for changing at the group display level.
To ensure proper loop initialization, the OROFFSET parameter should be set to On when
OROPT = On.

R688 HPM High-Performance Process Manager Control Theory 441

08/2019 Honeywell
37 Override Selector Control Algorithm
37.1 Functional Overview

Figure 37-1 Override Selector Control Algorithm Functional Diagram

Output
Processing

CAS
X1 To
CV
X2 ORSEL Secondary
MAN X3
X4 ORFBSEC

From
Init.
Primaries Feedback Value
Sel To Primaries
Notsel,
Notcon

CAS

MAN

Selected, Not Selected,

Not Connected Status to
Primaries (Parameter PTORST)

Equation A: HI Selector
Equation B: LO Selector

Inputs and outputs

This algorithm requires no input connections. The number of input connections is
defaulted to 0; however, it can be increased to up to 4. For each input connection, a
destination parameter X1, X2, X3 or X4 must be configured.
Use
This algorithm can be used, without the override option, as a simple selector that selects
either the highest or the lowest of the connected and active inputs. With the override
option, it is used for override-control strategies where a process variable is measured and
normally controlled, but where another variable is selected to constrain the controlled
variable, under a specified condition. This is often referred to as "multivariable-constraint
control."
The figure Override control strategy example illustrates an override strategy. The X1
input to the ORSEL point is normally selected and applied as the setpoint to the fuel-flow
442 HPM High-Performance Process Manager Control Theory R688
Honeywell 08/2019
 37 Override Selector Control Algorithm
37.1 Functional Overview

controller. If the value of the air flow multiplied by some ratio exceeds the fuel-flow
setpoint, the air flow constrains the fuel flow.
In a strategy like that illustrated in the following figure, Equation A, the override option
is configured. PID data points connected to non-selected inputs are prevented from
"winding up" by forcing their outputs to track the override feedback signal (ORFBSEC).
The simple selector (override option not configured) can be set up to initialize one input,
but not all inputs, by using control-input connections for the inputs that are not to be
initialized, and by using a control-output connection from the point that is connected to
the input to be initialized.
Figure 37-2 Override Control Strategy Example

SP A ir
PV Cont.

Air

Setpoint X1 ORSEL Fuel

SP
Ratio X2 PV Cont.

F
Fuel
If X2 exceeds X1, air flow
constrains fuel flow.

R688 HPM High-Performance Process Manager Control Theory 443

08/2019 Honeywell
37 Override Selector Control Algorithm
37.2 Options and Special Features

37.2 Options and Special Features

Bypass
When configured as an override selector, any of the inputs X1, X2, X3, and X4 can be
individually bypassed (not used in the algorithm calculation). Four logical parameters are
provided to select the input to be bypassed. These parameters are BYPASSX1,
BYPASSX2, BYPASSX3, and BYPASSX4. An additional parameter, BYPASS is
provided. When BYPASS is On, the input Xn for which BYPASSXn is On is initialized
(set equal to the selected input) and not used in the calculation of the output. When all
four inputs are bypassed, the output is maintained at the last value.
These parameters are available only when the override option is configured (OROPT = On).
All bypass parameters can be stored by the operator, or any system function, but only
BYPASS is available for changing at the group display level.

ATTENTION
When a selected input is bypassed, all parameters go through 1-shot
initialization.

Engineering unit ranges

The engineering-units ranges for the X1 through X4 inputs must be configured in
parameters XEUHI and XEULO. These parameters contain the high and low values for
the range, which is the same for all four inputs. The output engineering unit ranges
(CVEULO and CVEUHI) always follow the X-input range.
Operating modes
Because a data point that uses ORSEL is always a secondary to at least one other data
point, this algorithm operates only in the following modes:
• Cas
• Man
• Bcas if RCASOPT = Ddc
Remote cascade options
Only the Ddc option is supported.
Restart or point activation
On a warm restart, or on activating the data point, the CV is initialized to the value
returned from the secondary and an initialization request is sent to all of the primaries.

444 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 37 Override Selector Control Algorithm
37.3 Equations

Error handling
In Cascade mode with BYPASS Off, if any input has a Bad-Value status, CV's value is
bad (NaN) and the mode doesn't change when the CV value goes bad. Also, in Cascade
mode with BYPASS On, any non-bypassed input (BYPASSXn=Off) that has a Bad-
Value status causes CV to go bad (NaN).
If a bad input, that was causing CV to be Bad, returns to Normal, CV returns to normal,
CV is made equal to OP, and all bypassed primaries are initialized (see “Initialization” in
Section 37.4).
Processing order
Processing order is always important, but especially for the ORSEL strategy. ORSEL
functions will not work properly if point processing order is incorrect.

37.3 Equations
Background
The Override Selector control algorithm provides two equations:
• Equation A—Select the higher of the connected, active inputs.
• Equation B—Select the lower of the connected, active inputs.

R688 HPM High-Performance Process Manager Control Theory 445

08/2019 Honeywell
37 Override Selector Control Algorithm
37.4 Initialization

Equation legend
For either equation:
• CV = The control-algorithm output in engineering units.
• X1 through X4=The four available inputs.
• M = The number of inputs configured. Default = 2.
• SELXINP = The selected input; SelectX1 through SelectX4.

ATTENTION
With SELXINP if more than one input has the highest (EqA) or the lowest
(EqB) value, the lower-numbered input is selected.
For example, if X2 and X3 have exactly the same highest value (EqA)
SELXINP contains SelectX2.

Equations
In Equation A:
CV = highest of X1 through Xm
In Equation B:
CV = lowest of X1 through Xm

37.4 Initialization
Initialization requests from secondary points are ignored as long as the ORSEL output is
disposable.
If the ORSEL is initialized because it is in Manual mode, the output is indisposable, or it
has just returned from bad control status, CV is made equal to INITVAL from the
secondary, and SELXINP is set to None. When the ORSEL is in Manual mode, an
initialization request is passed on to all primaries with an initialization value equal to CV.
When the ORSEL is initializing because the output is indisposable or it is returning from
bad control, an initialization request is passed on to all primaries whose input are
bypassed (BYPASS = On and BYPASSXn = On) with an initialization value equal to
CV.

446 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 37 Override Selector Control Algorithm
37.5 Override Feedback Processing

37.5 Override Feedback Processing

Background
If the override option is configured, PID points connected to non-selected inputs are
prevented from "winding up" by forcing their outputs to track the override-feedback
signal (ORFBSEC).
Override offset
A configuration parameter called Override Offset (OROFFSET = On) is provided to
control the behavior of any PIDs connected to the non-selected inputs. If Override Offset
is configured, the output of the PID whose override status is not selected is set equal to
the override feedback value, plus gain times error (after converting to percent). If the
override offset is not configured, the output of the PID whose override status is not
selected is set equal to the override feedback value (after converting to percent).
Override feedback initiation
If the override option is configured for the ORSEL point and the ORSEL point is in Cas
mode and not initializing, it propagates override-feedback information to its primary
points and on "upstream."
When BYPASS is Off, the appropriate NotCon, Sel, NotSel status is given to ORSEL's
primaries in PTORST, and the override-feedback value that is passed to the primaries is
calculated as (where ORFBSEC, an internal parameter, is the feedback value from the
secondary):
ORFBSEC = CV
If, under the above conditions, BYPASS is On, the status sent to the primary connected
to the non-bypassed selected input is Sel, NotCon is sent to the bypassed primaries and
they are all initialized. NotSel is set to the non-bypassed non-selected primaries.
If there is more than one Override-Feedback data point in a strategy, only the one nearest
the final control element (the "most downstream" point) initiates override feedback.

R688 HPM High-Performance Process Manager Control Theory 447

08/2019 Honeywell
37 Override Selector Control Algorithm
37.5 Override Feedback Processing

Override feedback propagation

Override-feedback propagation is the passing of status and feedback values, from the
initiating Override Feedback Selector, "upstream" through one or more other data points.
If a "downstream" Override Feedback Selector requests status and value propagation, an
"upstream" Override Feedback Selector" propagates the value and status "upstream," only if
each of the following is true:
• it is configured as an Override Selector (override configured).
• it is in Cas mode.
• its output is disposable.
When these conditions are met (where PTORST = Point Override Status, SEL = selected,
and ORFBSEC = feedback value from the secondary):

If... then... else...

PTORST = SEL ORFB = CV ORFB = ORFBSEC

PTORST status sent to the selected primary is the same as that received from the
secondary. If BYPASS is:
• False, the status to all other primaries is NotSel.
• True, non-selected inputs are initialized, so the status sent to them is NotCon.

448 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 38. Multiply Divide Control Algorithm
38.1 Functional Overview
Family
The Multiply/Divide (MULDIV) control algorithm is a member of the Regulatory
Control algorithms.
Description
The Multiply/Divide algorithm calculates a control output (CV) by multiplying and
dividing combinations of three inputs: X1, X2, and X3.
Figure 38-1 Multiply/Divide Control Algorithm Functional Diagram

Output
X1 Proc essing
X2 MULDIV CV OP To Secondary

X3

To Primary INITVAL 16 122

Each of the three input variables can be multiplied by a scale factor, and then a bias value
added to them. or example, input X1 can be multiplied by a scale factor K1 and a bias
value of B1 added to the result. In a similar way, input X2 can be multiplied by K2 and
bias value B2 added and X3 can be multiplied by K3 with B3 added.
The resulting product can also be multiplied by an overall scale factor K and an overall
bias B added.

ATTENTION
X1 is an initializable input.
X2 and X3 can be used only as inputs and their data cannot be stored from
another source. Their data has to be fetched.

Inputs and outputs

For equations A, B, and C, the number of input connections is defaulted to 1. It can be
increased to 2 allowing the X1 input to be fetched with an input connection. X1 is
fetched by connection number 2.
For equations D and E, the number of input connections is defaulted to 2. It can be
increased to 3, allowing the X1 input to be fetched with an input connection. X1 is
fetched by connection number 3.

R688 HPM High-Performance Process Manager Control Theory 449

08/2019 Honeywell
38 Multiply Divide Control Algorithm
38.2 Options and Special Features

Use
This algorithm is normally part of a cascade control strategy. Typically, its primary is a
data point that is using a PID algorithm, and its secondary is another data point that is
also using a PID algorithm. The Multiply/Divide algorithm can also provide an input to
an Override Selector algorithm.

38.2 Options and Special Features

Ramping bias
The ramping rate for the internal bias is specified by the RATE1 parameter which is
configured in terms of engineering units per minute. When RATE1 is set to 0, the
internal bias BI does not decay and remains fixed. If RATE1 is set to NaN, the internal
bias BI does not decay but instantaneously changes to 0 during initialization. This will
cause a bump in the output.
Engineering unit ranges
The X input range is configured by XEULO and XEUHI. The output range CVEUHI and
CVEULO is derived from the secondary if the number of output connections is greater
than 0. Otherwise it must be configured.
Operational modes
The RegCtl Multiply/Divide algorithm operates in the following modes:
• Man
• Cas
• Bcas if RCASOPT = Ddc
Remote cascade options
Only the DDC option is supported.
Error handling
If any of the inputs have a bad value, the CV value is bad but the point remains in the
same mode. When the bad input returns to normal, CV is recalculated and an
initialization request is sent to the primary.

38.3 Equations
Background
The Multiply/Divide algorithm can be configured using anyone of five equations.
Equation legend
For each equation:

450 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 38 Multiply Divide Control Algorithm
38.4 Initialization

• CV = Current full value of the output of this algorithm in engineering units.

• K = Overall scale factors (gain). The default is 1.0.
• K1 through K3 = User-specified scale factors (gains) for inputs X1 through X3. The
default is 1.0.
• X1 through X3 = Current values of each X input in use.
• B1 through B3 = User-specified bias for inputs X1 through X3. The default is 0.
• B = Overall bias (see “Initialization” in Section 38.4). The default is 0.
Equations
The Multiply/Divide algorithm can be configured using the equations defined in the
following table.

Table 38-1 Multiply/Divide Equations (CV)

Equation Description

A CV = K * (K1 * X1 + B1) * (K2 * X2 + B2) + B

38.4 Initialization
Background
Input X1 is an initializable input and initialization is accomplished with an internal
ramping bias. The Bias B is made up of two components, BO and BI, where BO is the
operator entered bias and BI is the internal bias component. The internal bias decay rate
parameter RATE1 specifies the decay rate of the internal bias BI.

R688 HPM High-Performance Process Manager Control Theory 451

08/2019 Honeywell
38 Multiply Divide Control Algorithm
38.4 Initialization

Normal cascade operation

During normal cascade operation, when a user enters a bias B, the value goes into BO
and BI is set to zero. When the cascade is broken, input X1 goes into initialization.

452 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 38 Multiply Divide Control Algorithm
38.4 Initialization

Initialization and ramping bias equations

The following table lists the initialization and internal ramping bias equations used with
Equations A through E. The internal ramping bias value BI is calculated when the
cascade operation resumes (where CVlast is the last calculated CV before initialization).

ATTENTION
For Equation A, if the Primary:
• accepts the INITVAL, then the value of BI turns out to be 0.
• does not accept INITVAL, the BI turns out to be a non-zero value that
would cause a bumpless CV output. Then BI will decay to zero at the
rate specified by RATE1 which is specified in terms of engineering units
per minute.

Table 38-2 Multiply/Divide Initialization Equations (INITVAL)

Equation Description

Equation A

Initialization

Internal BI = CVlast – K * (K1 * X1 + B1) * (K2 * X2 + B2) –BO

ramping
bias

Equation B

Initialization

Internal
ramping
bias

Equation C

Initialization

R688 HPM High-Performance Process Manager Control Theory 453

08/2019 Honeywell
38 Multiply Divide Control Algorithm
38.4 Initialization

Equation Description

Internal
ramping
bias

Equation D

Initialization

Internal
ramping
bias

454 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 38 Multiply Divide Control Algorithm
38.5 Override Feedback Processing

38.5 Override Feedback Processing

Background
When the point's secondary uses an override selector algorithm, the following function
takes place. If the point is in Cascade mode, override status PTORST is returned to this
point through special processing. If the status is not selected, an override feedback value
is calculated as follows and it is passed to the primary of the Multiply Divide Algorithm.
Override feedback equations
The feedback value calculations for each of the equations are defined in the following
table.
Table 38-3 Multiply/Divide Override Feedback Equations (ORFB)

Equation Description

R688 HPM High-Performance Process Manager Control Theory 455

08/2019 Honeywell
38 Multiply Divide Control Algorithm
38.5 Override Feedback Processing

456 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 39. Regulatory Control Summer Algorithm
39.1 Functional Overview
Family
The Regulatory Control Summer control algorithm is a member of the Regulatory
Control algorithms.
Description
As illustrated in the following figure, the Regulatory Control Summer algorithm
calculates a control output (CV) by summing up to four inputs: X1, X2, X3, and X4.
Figure 39-1 Regulatory Control Summer Functional Diagram

X1
Output
X2 RegCtl Proc essing
SUMMER
X3 CV OP To Secondary
X4

To Primary INITVAL

Each of the inputs can be scaled by their gains K1, K2, K3, and K4. The output can be
scaled by an overall gain K and overall bias value B can be added to the result.
If only one input (X1) is used, then only the overall gain parameter K and the overall bias
B are configurable.

ATTENTION
X1 is an initializable input.
X2, X3 and 43 can be used only as inputs and their data cannot be stored
from another source. Their data has to be fetched.

R688 HPM High-Performance Process Manager Control Theory 457

08/2019 Honeywell
39 Regulatory Control Summer Algorithm
39.2 Options and Special Features

Inputs and outputs

The number of input connections is defaulted to: (number of inputs – 1). It can be
increased by 1, allowing X1 to be fetched using an input connection.
Use
This algorithm is normally part of a cascade control strategy. It can be used to calculate a
sum of up to four control inputs. It can provide an input to an override-selector algorithm.

39.2 Options and Special Features

Ramping bias
The ramping rate for the internal bias is specified by the RATE1 parameter which is
configured in terms of engineering units per minute. When RATE1 is set to 0, the
internal bias BI does not decay and remains fixed. If RATE1 is set to NaN, the internal
bias BI does not decay but instantaneously changes to 0 during initialization. This will
cause a bump in the output.
Engineering unit ranges
The X input range is configured by XEULO and XEUHI. The output range CVEUHI and
CVEULO is derived from the secondary if the number of output connections is greater
than 0. Otherwise it must be configured.
Operational modes
The Summer algorithm operates in the following modes:
• Man
• Cas
• Bcas if RCASOPT = Ddc
Remote cascade options
Only the DDC option is supported.
Error handling
If any of the inputs have a bad value, the CV value is bad but the point remains in the
same mode. When the bad input returns to normal, CV is recalculated and an
initialization request is sent to the primary.

458 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 39 Regulatory Control Summer Algorithm
39.3 Equations

39.3 Equations
Background
The equations used when processing Regulatory Control Summer algorithm depends on
the number of configured inputs.
Equation legend
For both equations:
• CV = Current full value of the output of this algorithm in engineering units.
• K = Overall scale factors (gain). The default is 1.0.
• K1 through K4 = User-specified scale factors (gains) for inputs X1 through X4. The
default is 1.0.
• X1 through X4 = Current values of each X input in use.
• B = Overall bias (see “Initialization” in Section 39). The default is 0.
Equations
For Regulatory Control Summer algorithms configured for:
• one (1) input, the equation is—
CV = K * X1 + B
• two (2) to four (4) inputs, the equation is (where n = the number of inputs)—
CV = K * (K1 * X1 + K2 * X2 ...+ Kn * Xn) + B

R688 HPM High-Performance Process Manager Control Theory 459

08/2019 Honeywell
39 Regulatory Control Summer Algorithm
39.4 Initialization

39.4 Initialization
Initializable input
Input X1 is an initializable input and initialization is accomplished with an internal
ramping bias.

Bias
The Bias B is made up of two components, BO and BI, where BO is the operator entered
bias and BI is the internal bias component. the internal bias decay rate parameter RATE1
specifies the decay rate of the internal bias BI.

Cascade
When the cascade is:
• broken—
− input X1 goes into initialization
− the initialization value to the primary is calculated as:

INITVAL =

• resumes—
− the internal ramping bias value BI is calculated (where CVlast is the last
calculated CV before initialization):
BI = CVlast - K * (K1 * X1+K2 * X2...Kn * Xn) -B0

ATTENTION
When only the X1 input is used, the following equations apply:

INITVAL =
BI = CVlast - K * X1 - B0)

39.5 Override Feedback Processing

Background
When the point's secondary uses an override selector algorithm:
• If the point is in Cascade mode, override status PTORST is returned to this point
through special processing.

460 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 39 Regulatory Control Summer Algorithm
39.5 Override Feedback Processing

• If the status is not selected, an override feedback value is calculated as follows and it
is passed to the primary of the Summer.
Override feedback value
The feedback value for equations with:
• one (1) input, the equation is—

ORFB =

• two (2) to four (4) inputs, the equation is (where n = the number of inputs)—

ORFB =

R688 HPM High-Performance Process Manager Control Theory 461

08/2019 Honeywell
39 Regulatory Control Summer Algorithm
39.5 Override Feedback Processing

462 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 40. Output SWITCH Select Algorithm
40.1 Functional Overview
Family
The Output Select algorithm (OPSELECT) is a member of the Regulatory Control
algorithms. The OPSELECT regulatory control algorithm has been added to the HPM in
R650.
Description

This algorithm allows you to implement a control strategy that switches one input to one
of four different outputs, as specified by the $SELCTOP parameter. An operator, a user-
written program, or user-configured logic can change the output selected by $SELCTOP.
The algorithm operates as a single pole, 4-position rotary switch as shown in the
following figure.
Figure 40-1O P SELECT Control Algorithm Functional Description

In the figure shown above, the user control strategy provides the output value to the X1
input. The X1 input can be connected to any one of 4 outputs. Typically, the outputs are
connected to analog output points (AO.OP), or to the inputs of other regulatory control
points (such as SP inputs of PID regulatory control points).
For the default configuration shown above, The X1 input is connected to $CV1 which
becomes the overall CV for the OPSELECT algorithm. The CV undergoes output
processing to determine the overall output value OP that becomes the OP of the selected
output. OP is calculated from CV which is stored into $OP1 (OP of the selected output).

R688 HPM High-Performance Process Manager Control Theory 463

08/2019 Honeywell
40 Output SWITCH Select Algorithm
40.1 Functional Overview

In the default configuration, the $SELCTOP parameter value SELOP1 selects $OP1 as
being the algorithm output value. Additionally, when $OP1 is selected by parameter
$SELCTOP, flag S1 of the regulatory control point is set to ON.
The OP values of the unselected outputs are calculated from their CV values. The CV
values of the unselected outputs are set to their default values ($CDEF2-$CDEF4) that
are configured by the user.
In this case, the unselected outputs ($OP2-$OP4) are set to default values that are
specified by parameters $CDEF2-$CDEF4, respectively. (The $CDEF1 parameter
provides the default value for $OP1 when $OP1 is unselected). Additionally, the flags
(S2-S4) of the unselected outputs are set to OFF, to indicate that $OP2-$OP4 have not
been selected.
As an example, if the user changes the value of $SELCTOP parameter to SELOP3, then
the $OP3 value becomes the algorithm output value and outputs $OP1, $OP2, and $OP4
are set to their default values as specified by parameters $CDEF1, $CDEF2, and
$CDEF4. In addition, flag S3 is set to ON and flags S1, S2, and S4 are set to OFF.
The user can also change the values of flags S1-S4 to select the respective output, as
described later in this section.
Inputs and Outputs
Control Input Connections
The OPSELECT algorithm does not require input connections because another
regulatory control point can write a value to parameter X1.
By default, the number of input connections (NOCINPTS) is
0. However, it can be changed to 1 in which case, the user
must specify the destination parameter as X1.

Number of Output Connections

Using the parameter $NOPCONN, you can specify the number of output connections
(total number of PUSH and FETCH connections) configured for the OPSELECT
regulatory control point. A maximum number of 4 output connections can be configured.

464 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 40 Output SWITCH Select Algorithm
40.1 Functional Overview

Control Output Connections

The number of control output connections (NOCOPTS) parameter:
• Specifies the number of control-output PUSH connections that can be
configured for the OPSELECT point (for example, if the connection is made to
the SP input of a PID point).
• Should be equal to or less than the number of output connections specified by
the $NOPCONN parameter.
• Determines the order of PUSH/FETCH outputs based on the configuration.
The number assigned to the NOCOPTS parameter specifies the number of
PUSH outputs and the remaining outputs become FETCH outputs.
The control output PUSH connection can be connected either to valid destination
parameters of another regulatory control point, or to valid parameters of IOPs.

ATTENTION
You cannot combine the regulatory control point and IOP point output PUSH
connection for the same OPSELECT point.

ATTENTION
A difference between the OPSELECT regulatory control point and other
regulatory control points is that the control outputs of most regulatory control
points can have up to 4 connections, but the OPSELECT algorithm can have
only one output connection for each $OPn.

The $SELCTOP parameter value cannot be changed to a non-configured output position.

For example, if $NOPCONN=3, $SELCTOP cannot be set to SELOP4 because only 3
connections are configured. This restriction is also applicable to flags S1-S4). If
OPSELECT point is not able to drive the output to the selected output, BADOC<n>FL is
ON and the bad output connection alarm is activated.

ATTENTION
Bad output connection checks are not performed for the non-selected
outputs.

R688 HPM High-Performance Process Manager Control Theory 465

08/2019 Honeywell
40 Output SWITCH Select Algorithm
40.1 Functional Overview

Unselected Outputs
The OPSELECT regulatory control point provides parameters $CDEF1-$CDEF4. With
these parameters, the user can specify the default values for the four outputs when the
outputs are unselected. The values of the parameters can be set by an engineer, by a user-
written CL program.
For example, if the selected output is $OP1, then the 4 output CV values are set as
follows:
$CV1 = X1 + B
$CV2 = $CDEF2
$CV3 = $CDEF3
$CV4 = $CDEF4
If the selected output is changed to $OP2, then the 4 output CV values change to the
following values:
$CV1 = $CDEF1
$CV2 = X1 + B
$CV3 = $CDEF3
$CV4 = $CDEF4
Bumpless Output Transfer
The OPSELECT regulatory control point provides bumpless output transfer when you
change the selected output using the ramping bias function. Because unselected outputs
do not support the ramping bias function, a bump occurs in the output when changing
from the selected to the unselected state.

Output Hold Option

When the selected output is changed, an unselected output can be configured to hold the
last value by specifying its default value $CDEFn as NaN. The initial value of $CVn =
NaN when $CDEFn = NaN.
For example, if $CDEF1 = NaN, output $CV1 holds the last value when the selected
output is changed from 1 to 2.
Bias
To configure the operator-entered bias value (BO), enter the bias value in parameter B.
This value is also BO value. Whenever B is changed, the internal bias BI is forced to
zero.

466 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 40 Output SWITCH Select Algorithm
40.1 Functional Overview

Cascade Scenario
A typical cascade strategy using the OPSELECT algorithm is shown in the following
figure. The output of a PID block is connected to the input of OPSELECT, and the
outputs of OPSELECT are connected to 4 analog output points.
Figure 40-2 Switching Example

The output of the PID is channeled to AO2 by setting $SELCTOP = SELOP2. If

OPSELECT is in cascade mode, the OPSELECT propagates the windup status of the
selected output ($OP2) to the PID block.
Use
The regulatory control OPSELECT function performs the output switching function. This
algorithm is normally part of control strategy that switches one input to any one of up to
four different outputs.

R688 HPM High-Performance Process Manager Control Theory 467

08/2019 Honeywell
40 Output SWITCH Select Algorithm
40.2 Options and Special Features

40.2 Options and Special Features

Modes
The OPSELECT regulatory control point can be operated in the manual or cascade mode.
The mode attribute parameter (MODATTR) can be configured for operator, program, or
none.

Manual mode
In manual mode, the operator controls the selected output by changing the value of
output value OP.

Cascade mode
In cascade mode, the CV of the selected output ($CV1, $CV2, $CV3 or $CV4) is set to a
value X1 +B.
$CVn = X1 + B
where,
$CVn is the CV of the selected output
B = BO + BI
where,
B = Bias value
BO = Operator entered bias value
BI = Initialization bias component
Ramping Bias
The ramping rate for the internal bias is specified by the RATE1 parameter (configured
as engineering units per minute). Ramping bias is applicable only to the selected output.
When RATE1 is set to 0.0 (default value), the internal bias BI remains fixed. If RATE1
is set to NaN, then the internal bias BI does not ramp but instantaneously changes to 0
during initialization. This may cause a bump in the output.
If an OPSELECT regulatory control point is configured with a default value (0.0) for
RATE1 and loaded, and when the point is set to the CAS mode, or output switching is
done in the CAS mode, the output will not ramp but remains at the same value. However,
initialization bias is calculated and whenever the user changes the value of RATE1, the
selected output starts ramping.
Engineering Unit Ranges
The X1 input range is specified by the range parameters XEUHI and XEULO. The
output engineering range values (CVEUHI and CVEULO) track the X1 input range

468 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 40 Output SWITCH Select Algorithm
40.2 Options and Special Features

values. When the XEUHI or XEULO value is changed and the value of any $CDEFn is
crossing the new limit (either high or low), then a configuration error message is
displayed and the new value for XEUHI or XEULO is not stored.
Windup Handling
This algorithm supports the regulatory control windup propagation function. When the
selected output value exceeds the user specified limits, the appropriate windup status is
propagated upstream so that any PID blocks in the cascade chain does not windup.
OP Limits
The OP value of the selected output is limited by OPHI and OPLO limits configured by
the user. Similar to the other regulatory control functions, OPSELECT regulatory control
point supports OP minimum-change limiting and OP rate-of-change limiting functions.
However, rate-of-change and minimum-change limiting are not processed on the first
scan whenever switching occurs whenever $SELCTOP is changed, and the first OP
receives the value of the selected secondary, and then the OPHI and OPLO are applied to
the OP.
Point Activation
When the OPSELECT regulatory control point is activated after a cold start, the outputs
$CV1, $CV2, $CV3 and $CV4 are initialized to NaN.

R688 HPM High-Performance Process Manager Control Theory 469

08/2019 Honeywell
40 Output SWITCH Select Algorithm
40.3 Equations

40.3 Equations
Background
The OPSELECT regulatory control point supports two equations, Equation A and
Equation B.
Equation A
If equation A is configured, an operator at the Universal Station can change the switch
position by using any one of the following methods.
• By altering $SELCTOP parameter value. The value of $SELCTOP specifies
the selected output. In addition, one of the four flags (S1, S2, S3 or S4), that
represent the selected output is set to ON and the other three switches are set to
OFF.
• By changing the desired flag (S1, S2, S3 or S4) from OFF to ON. When one of
the flags is set to ON, the other three flags are set to OFF and the $SELCTOP
parameter indicates the selected output.
For example, if the OPSELECT regulatory control point is configured for equation A, the
operator can connect input X1 to output $CV1 by setting $SELCTOP = SELOP1. The
S1 flag is set to ON and the other three flags (S2, S3 and S4) are set to OFF. The overall
CV of the algorithm is equal to $CV1 and the overall OP value is calculated based on the
value of CV. The output of selected output $OP1 is set equal to the overall OP.
The CV's of the unselected outputs are set to their default values (that is, $CV2 =
$CDEF2, $CV3 = $CDEF3, and $CV4 = $CDEF4). $OP2 is calculated from $CV2,
$OP3 is calculated from $CV3, and $OP4 is calculated from $CV4.
To change the selected output from 1 to 2, the operator can either change the setting of
$SELCTOP to SELOP2 or change the setting of flag S2 from OFF to ON.
Equation B
Equation B is primarily intended for automatic switching of outputs using CL programs.
If the OPSELECT regulatory control algorithm is configured for equation B, the switch
position can be changed by storing to the $SELCTOP parameter only if all the flags (S1–
S4) are OFF. Setting one flag to ON does not set the other flags to the OFF state. The
switch position may be selected by setting the flags to ON and OFF as shown in the
following table.

S1 S2 S3 S4 $SELCTOP

ON X* X X SELOP1

470 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 40 Output SWITCH Select Algorithm
40.3 Equations

OFF ON X X SELOP2
OFF OFF ON X SELOP3
OFF OFF OFF ON SELOP4
OFF OFF OFF OFF Remains at last
selected value**

*X indicates ON or OFF.
**If the flags change to a state where all are OFF, the selected output remains at the last
setting.
For example, the OPSELECT regulatory control point is configured for equation B so
that the regulatory control point can be controlled by a CL program. The X1 input can be
connected to $CV1 by setting S1 = ON and the other three flags (S2, S3 and S4) can be
set to OFF or ON because S1 has the highest priority and S4 has the lowest priority.
To change the selected output from 1 to 2, either set S1 = OFF and S2 = ON or set all the
flags (S1-S4) to OFF and then set $SELCTOP = SELOP2. If all the flags are set to OFF,
the selected output initially remains unchanged at SELOP1. The selection changes to
SELOP2 only when the $SELCTOP parameter is set to SELOP2. All the flags have to be
initially set to OFF because with equation B, $SELCTOP can be stored only if all the
flags are OFF.

Red Tag
If REDTAG or SHUTDOWN is ON, then the output cannot be switched by operating
$SELCTOP or by operating S1-S4, because output changes are not allowed.

R688 HPM High-Performance Process Manager Control Theory 471

08/2019 Honeywell
40 Output SWITCH Select Algorithm
40.4 Initialization

40.4 Initialization
Input X1 is an initializable input and it is initialized using an internal ramping bias if the
selected output is indisposable.
For example, if output 2 is selected and the analog output slot AO2 is inactive, the
OPSELECT regulatory control point goes into the initialization state (INIT). This state is
propagated upstream to the PID block which also goes into the initialization state and an
initialization value (INITVAL) equal to CV – BO is propagated to the PID block.
If AO2 is activated, the cascade operation resumes and the initialization bias (BI =
INITVAL – X1) is calculated.
If the PID block output initializes to INITVAL, then BI is set to zero. If the PID does not
initialize to INITVAL, BI contains a non-zero value and results in a bumpless $CV2
output.
If BI contains a value other than zero, the internal bias behavior depends on the value
specified in the RATE1 parameter. The value of BI ramps to zero at a rate configured in
RATE1 (engineering units per minute).

ATTENTION
Although this algorithm has 4 output connections, only the status of the
selected output determines the INITMAN state of this algorithm.

472 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 41. Box Data Points
41.1 Box Data Point Background
Global variables
The HPM provides the following global variables:
• 16,384 Flag variables.
• Up to 16,384 Numeric variables.
• Up to 16,384 8-character String variables.
• Up to 4096 Time variables.
• 64 Timer variables.
The full 16,384 flags and 64 timer variables are always present. Numerics, strings, and
times are configured by HPM Node Specific Configuration parameters such as
NSTRING (number of strings). Configuration is determined by considering the Memory
Units needed for your system. Box global variables do not require any PUs. Some
specific types of points (for example, Process Module) provide similar local variables.
Box Data Point Types
The HPM supports the following Box Data Points:

• Box Flag • Box Numeric

• Box Timer • Box Time
• Box String

ATTENTION
With TPN R682, you can take a backup of box parameters and restore all the
values later. The backup and restore option can be accessed through the
target BOX PARAM BACKUP RSTR in the DEB. In DEBEC, the commands
“BPB” and “BPR” can be used for backup and restore operations
respectively.

R688 HPM High-Performance Process Manager Control Theory 473

08/2019 Honeywell
41 Box Data Points
41.1 Box Data Point Background

474 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 42. Box Flag Data Point
42.1 Functional Overview
Family
The Box Flag data point is a member of the HPM Box Data Points.
Description
A Box Flag Data Point is a 2-state (On and Off) point that is used for storing a Boolean
value. The value can be supplied by the operator, by the sequence program, by an output
connection from another HPM point, by any HPM (or PM) box on the same UCN, or by
a node on the LCN. There are 16384 Flag Data Points (slots) available in an HPM box.
The first 2047 flag points are tagable and can be configured as Full or Component points.
The first 4095 Box Flags are accessible from the LCN. The remaining flags must be
accessed through an array point.
Flag data points are not scheduled and only off-normal alarms are processed. Their states
change when they are accessed by other functions such as an operator or a user-written
program.
Tag name
Flag points do not require a tag name. They can be accessed by !BOX.fl(i) or
$NMxxNyy.fl(i) where xx is the network number and yy is the HPM node number. After
configuration, flag variables are initialized to Off. A functional diagram of the Flag Data
Point is shown in the following figure.
As shown in this figure, the input to the flag point is provided by parameter PVFL, which
can be On or Off. PVFL will set the flag-point PV state to the same state as PVFL. The
PV is then available as an output from the flag point and its current state can be accessed
by other points in the HPM and in the system.
PVFL will also light the STATE1 and STATE0 boxes on the Universal Station Displays,
depending on its state. If PVFL is On, the STATE1 (upper) box will be lighted; if PVFL
is Off, the STATE0 (lower) box will be lighted.

R688 HPM High-Performance Process Manager Control Theory 475

08/2019 Honeywell
42 Box Flag Data Point
42.1 Functional Overview

Figure 42-1 Box Flag Data Point Functional Diagram

Alarming
The first 1024 flag points (slots) can be configured for off-normal alarming. An alarm
will be generated when the PV of the flag point is changed from STATE0 (Off) to
STATE1 (On)

476 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 43. Box Numeric Data Point
43.1 Functional Overview
Family
The Box Numeric data point is a member of the HPM Box Data Points.
Description
Numeric Data Points store numeric values that can be used for batch/recipe operations, or
they can be used as a scratch pad to store the intermediate results of calculations. The
values in a numeric point are real numbers that have been entered by the operator, or by a
sequence program, or other system elements. Box Numeric Data.
Point types
Up to 16,384 Numeric slots can be configured as part of each HPM box. Numeric slots
do not require a tag name. They can be accessed by !BOX.nn(i) or $NMxxNyy.nn(i)
where xx is the network number and yy is the HPM node number. After configuration,
numeric variables are initialized to NaN. An Array point must be used to access index
numbers greater that 4095 over the LCN.
With R660, the first 2047 numeric slots can be configured as alarmable points when they
are configured as Full points. If they are to be configured as Component points, there is
no alarming capability.
Access
These points are accessible to the sequences in the same HPM box, to any HPM (or APM
or PM) box on the same UCN, and to any node on the LCN. The first 2047 Numeric
points are tagable and can be configured as named data points. The first 4095 Box
Numerics are accessible from the LCN. The remaining Numeric variables can be
accessed through an array point.
Non-alarmable numeric data points are not scheduled and are not processed. Their
parameter values change when they are accessed by a system activity, such as by an
operator or a sequence program.

R688 HPM High-Performance Process Manager Control Theory 477

08/2019 Honeywell
43 Box Numeric Data Point
43.1 Functional Overview

Alarming
With R660, PV trip point alarming capability is available for HPM Box Numeric data
points. By using the $NNUMALM parameter in the HPM Box Data Point you can
specify the maximum number of HPM Box Numeric slots that are to be processed for PV
trip point alarming.

Figure 43-1 Box Numeric Data Point Functional Diagram

478 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 43 Box Numeric Data Point
43.1 Functional Overview

ATTENTION
To use the new feature, please note the following:
• For a new node: The default value for $NNUMALM parameter is set to 0.
• For an existing node (after migrating to R660 software): Idle the HPM,
reconstitute the HM Box Data Point, and change the value of the
$NNUMALM parameter to the desired number of alarmable numeric
points in the HPM Box Data point. The value of the parameter can be
changed in the Parameter Entry Display. After changing the parameter,
load the revised HPM Box Data Point into the HPM and then start up the
HPM.
• If a NIM receives more than 50 numeric-point alarms within 5 seconds,
the reporting of the remaining alarms is delayed.

REFERENCE - INTERNAL
For additional information on the alarming parameters, refer to the PM Family
Parameter Reference Dictionary.

R688 HPM High-Performance Process Manager Control Theory 479

08/2019 Honeywell
43 Box Numeric Data Point
43.1 Functional Overview

480 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 44. Box Timer Data Point
44.1 Functional Overview
Family
The Box Timer data point is a member of the HPM Box Data Points.
Description
The Box Timer Data Point allows the operator and the sequence program to time the
process events, as required. This type of data point keeps track of the elapsed time after
the timer has been started and provides an indication when the elapsed time has reached
the predefined limit.
Figure 44-1 Box Timer Data Point Functional Diagram

Minutes, Seconds

TIMEBASE

Preset Time SP SO Status (PV = SP)

TIMER
PV Current Time Value
DATA
Start POINT
RV Remaining Time
Stop (SP - PV)

Reset C STATE Stopped, Running

O
Reset/Restart M
M

Point types
Box Timer Data Points are component points and cannot be configured as full points.
Points per box
There are 64 Timer Data Points in each HPM Box, and like box numeric and flag points,
timer data points do not require a tag name. These points are accessible to the sequences
in the same HPM box, to any HPM (or APM or PM) box on the same UCN, and to any
node on the LCN. A functional diagram of the Timer Data Point is shown in this section.

R688 HPM High-Performance Process Manager Control Theory 481

08/2019 Honeywell
44 Box Timer Data Point
44.1 Functional Overview

Use
To use a Timer Data Point, an operator or the sequence program loads a preset time value
(the length of time that the timer is to run in seconds or minutes) into parameter SP. Once
the preset value is entered, the timer is started by setting parameter COMMAND to Start.
(The timer can also be stopped, reset, or reset and restarted through the COMMAND
parameter.)
Time
The time value in PV starts at zero and increments toward the preset time value when the
timer is processed. (The timer is processed once each second.) The RV parameter
indicates the time remaining until the timer reaches its limit (SP - PV). When PV = SP,
the status parameter SO is set to On to indicate that the time limit has been reached. The
values in PV and SP can range from 0 to 32000 seconds or minutes, as configured.
Parameters
To access, use!BOX.TMSP(n) or !BOX.TMCMD(n).

482 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 45. Box Time Data Point
45.1 Functional Overview
Family
The Box Time data point is a member of the HPM Box Data Point.
Description
Time variables may be used to store date/time information such as the date machinery
was put in service, when the machinery was serviced last, when the machinery was last
used, and so on.
Time variables
The HPM box provides up to 4096 global Time variables. The maximum limit is
determined by the Node Specific Configuration parameter NTIME (number of times).
Time variables are not configurable with a tag name.
Access
They can be accessed by !BOX.TIME(i) or $NMxxNyy.TIME(i) where xx is the network
number and yy is the HPM node number. The first 4095 Box Times are accessible from
the LCN. An array point must be used to access number 4096. After configuration, time
variables are initialized to 0.

R688 HPM High-Performance Process Manager Control Theory 483

08/2019 Honeywell
45 Box Time Data Point
45.1 Functional Overview

484 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 46. Box String Data Point
46.1 Functional Overview
Family
The Box String data point is a member of the HPM Box Data Points.
Description
String variables can be used to store descriptive text data such as the brand name or
model of machinery, who to contact for service, and so on.
Variables per box
The HPM box provides up to 16,384 8-character String variables. The upper limit is
determined by the Node Specific Configuration (box) parameter NSTRING (number of
strings). The first 4095 Box Strings are accessible from the LCN. An array point must be
used to address strings with an index of greater than 4095.
Tag names
String variables are not configurable with a tag name.
Access
They can be accessed by !BOX.STRn(i) where n is the string length or
$NMxxNyy.STRn(i) where xx is the network number and yy is the HPM node number.
Initialization
After configuration, string variables are initialized to spaces.

R688 HPM High-Performance Process Manager Control Theory 485

08/2019 Honeywell
46 Box String Data Point
46.1 Functional Overview

486 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 47. Array Points
47.1 Array Background
Description
Array points provide access to two sources of data:
• HPM box global variables.
• external data from/to Serial Interface devices.
HPM box global variables
An Array point can:
• an Array point can define a section of the box variables as its own data (see the
following figure).
• access to single variables over the LCN is limited by the upper index (4095), but
using an Array point you can access upper Flag, Numeric, String, and Time variables.
• the Array point can access and fetch string data in lengths of 8, 16, 32, or 64
characters.
Figure 47-1 Array Point Access to Box Global Variables

H PM M
Array
Point

Access to Bo x V ariab les in arrays o f:

0 - 1 02 3 Bo o le an s (Fla gs)
0 - 2 40 R ea l Nu m be rs (Nu m erics)

16124

R688 HPM High-Performance Process Manager Control Theory 487

08/2019 Honeywell
47 Array Points
47.1 Array Background

External data from/to serial interface devices

An Array point can:
• scan and image (read) large quantities of data from a Serial Interface (SI) IOP can be
scanned and imaged (read).
• be used as if it were local data to the Array point (see the following figure).
• write through the Serial Interface.
Figure 47-2 Serial Interface to an Array Point

HPM
SI IOP

HPMM

(up to 80 SI
Array points)

Power
Adapter

16 Arrays 16 Arrays
To Field FTA FTA To Field
Devices 1 2 Devices

Each Array point can contain up to 512 Booleans (Flags), or 16 Reals (Numerics) or 32
Integers (Numerics), or 64 byte-sized Integers (Numerics), or 64 ASCII Characters (Strings)
16 125

488 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 47 Array Points
47.2 Node Specific Configuration Requirements

47.2 Node Specific Configuration Requirements

Parameters
Array point configuration begins with HPM Node Specific Configuration. You can
allocate up to 256 array points through the parameter NARRSLOT. Other Node Specific
Configuration parameters that affect the Array point are—
• NNUMERIC - the number of Box Numerics (in multiples of 16) that you want
available.
• NSTRING - the number of Box Strings that you want available (in multiples of 16).
• Note that Box Strings are only available as 8-character strings.
• NTIME - the number of Box Times (in multiples of 32) that you want available.
• SCANPER - if you intend to access Serial Interface data, this parameter specifies the
period at which the HPMM scans SI data and maps it to the Array points.
Maximum number of points
The HPMM can scan SI IOP data at three rates and this determines the maximum number
of Array points with SI connections that you can have are defined in the following table.
Table 47-1 Maximum Si/Array Points

SCANPER Max. # of SI/Array Points

1 Second 80

0.5 Second 40

0.25 Second 20

Module type
Finally, you must select SI as the Module Type on the IO Module Configuration pages
for each SI IOP board that you wish to implement.
Note that 16,384 box flags are always available. The number of variables of each
particular global box variable data type available to an Array point is further limited by
configuration parameters for the Array point.

47.3 Array Parameter Names

Data elements in the Array point are referred to by the Array point tagname, type of
variable and index number (i). For example ARR01.FL(9). The complete list is provided
in the following table.
Table 47-2 Array Parameter Names
R688 HPM High-Performance Process Manager Control Theory 489
08/2019 Honeywell
47 Array Points
47.4 Array Point Use with HPM Box Global Variables

Variable Parameter

Flags FL(i)

Numerics NN(i)

Strings STRn(i)

Times TIME(i)

In the case of strings, n refers to the string length, 8, 16, 32, or 64. For example
STR32(4).

47.4 Array Point Use with HPM Box Global Variables

Configuration
When the External Data Option parameter (EXTDATA) on the Array point configuration
screen form is set to NONE, the Array point parameters provide indirect access to flag,
numeric, string, and time HPM box global variables.
Note that an Array point is just a convenient way of referring to related data; the actual
data comes from the HPM box global variables (in this case). When accessing one of
these variables by the Array point tag name, the HPM translates the request to a specific
HPM box global variable.
When accessing the HPM box global variables, each Array point allows the configuration
as defined in the following table.

Table 47-3 HPM Box Global Variables

Box Global Number of Array Point Range of Range of Array

Variable Elements Starting Index Starting Index Size

Flags 1–16,384 FLSTIX 1–16,384 0–1023

Numerics 1–NNUMERIC NNSTIX 1 to NNUMERIC 0–240

Strings 1–NSTRING STRSTIX 1 to NSTRING 0–240

Times 1–NTIME TIMESTIX 1 to NTIME 0–240

String length
The Array point parameter STRLEN specifies string length as 8, 16, 32, or 64 characters
and this determines the format in which strings are presented on the Array point Detail

490 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 47 Array Points
47.4 Array Point Use with HPM Box Global Variables

Display. Regardless of the value of STRLEN, Array point string data can still be
referenced using the STR8, STR16, STR32, or STR64 formats.
The following figure shows how longer character string lengths can be fetched from the
8-character format HPM box global string variables (provided that the access requested is
within the configured section). For example, if the Array point string starting index is set
to 301 and adequate HPM box string variables are configured (in 8-character format), a
request for the 64 character Array point parameter STR64(2) will fetch Box.STR8(309)
through Box.STR8(316). If only part of a longer character string can be been fetched, the
available portion is fetched. An array index error results when none of the requested
string is available.

R688 HPM High-Performance Process Manager Control Theory 491

08/2019 Honeywell
47 Array Points
47.4 Array Point Use with HPM Box Global Variables

Figure 47-3 String Array with Starting Index Set to 301

STR32(1)

STR16(1) STR16(2)

BOX.STR8(301) BOX.STR8(302) BOX.STR8(303) BOX.STR8(304)

STR64(1)

BOX.STR8(305) BOX.STR8(306) BOX.STR8(307) BOX.STR8(308)

BOX.STR8(309) BOX.STR8(310) BOX.STR8(311) BOX.STR8(312)

STR32(4)
STR64(2)
STR16(7) STR16(8)

BOX.STR8(313) BOX.STR8(314) BOX.STR8(315) BOX.STR8(316)

Descriptors
You can enter 4 descriptors up to 64 characters long, 1 for each type of variable. These
descriptors are typically used to describe the array variables. They appear on the Array
point Detail Display. Refer to the Process Operations Manual for examples.
Access Lock
Parameter SPLOCK determines store access to the variables. Configuration choices are
Operator, Supervisor, Engineer, or Program.

492 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 47 Array Points
47.4 Array Point Use with HPM Box Global Variables

Array point example

Array point ARR100 is configured to represent the ingredients necessary to make
product X. The parameters are configured as follows:

Parameter Meaning Example Entry

PTDESC point descriptor "Product X ingredients"

FLSTIX flag starting index 0

NFLAG number of flags in array 0

NNSTIX numerics starting index 2001

NNUMERIC number of numerics in array 75

STRLEN string length 16

STRSTIX strings starting index 1001

NSTRING number of strings in array 75

TIMESTIX times starting index 0

NTIME number of times in array 0

SPLOCK set point lock Operator

NNDESC numeric descriptor "Product X Ingredient Amounts"

STRDESC strings descriptor "Product X Ingredient Descriptions"

The 75 numerics list the amounts of all possible ingredients. The 75 strings describe each
ingredient. The descriptor entries (for NNDESC and STRDESC in this case)
subsequently appear on the point Detail Display and describe the ingredients.
Additional Array points could be configured to store other attributes of each of the 75
ingredients, such as specific gravities, and so on.
After loading the Array point, the parameters AR100.STR16(1 to 75) can be used to refer
to the ingredients for Product X. The parameters AR100.NN(1 to 75) can be used to refer
to the amount of each ingredient for Product X.

R688 HPM High-Performance Process Manager Control Theory 493

08/2019 Honeywell
47 Array Points
47.5 Serial Interface to Array Points

On the Detail Display, array variables appear in a table numbered from 1 through the end
of the array. Note that by choosing the starting index to end in 1 in the above examples,
the box variables and array variables correspond more conveniently. For example,
ARR100.NN(70) is mapped to box variable NN(2070) and appears on the Detail Display
as N0070.

47.5 Serial Interface to Array Points

Background
When the Array point’s EXTDATA parameter is set to IO_FL, IO_NN, or IO_STR,
(flags, numerics, or strings, respectively), communications is through the Serial Interface
(SI) and the point is often referred to as an SI Array point. A maximum of 80 Array
points can interface with SI IOP modules depending on the box parameter SCANPER.
External data access
The Array point accesses external data from the serial device through its Flag, String, and
Numeric parameters. For each Array point, only one type of variable (Strings, Flags, or
Numerics) can be used for Serial Interface communications. Non-selected parameters
still refer to the HPM Box variables. For example, if the EXDATA selection is IO_FL,
the number and starting index for flags refers to Serial Interface data through the selected
FTA, while numeric, string, and times references from this array point are to the HPM
box variables.
The following illustrates communications between the Array point and the serial IO
subsystem. The plug in FTA module adapts I/O requirements for the specific serial
interface.

494 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 47 Array Points
47.5 Serial Interface to Array Points

Figure 47-4 Signal Path Between SI Subsystems and Array Point

R688 HPM High-Performance Process Manager Control Theory 495

08/2019 Honeywell
47 Array Points
47.5 Serial Interface to Array Points

Serial interface IOP slots

The SI IOP module has 32 slots available. Up to 16 slots can communicate through FTA
number 1, and up to 16 slots can communicate through FTA number 2. An array point
automatically communicates through any available slot on the SI IOP connected to the
FTA specified during Array point configuration.
Accessing SI array data
Serial Interface IOP data mapped to an Array point is accessed through the Array point
Numeric(NN(i)), Flag (FL(i)), and String (STRn(i)) parameters.
Because the HPMM regularly scans data from the Serial Interface, read access to SI
Array data does not require an IOL prefetch cycle (that is, CL programs are not delayed
while data is being fetched).
SI array point configuration
When the Array point is configured to obtain input from a serial interface (EXTDATA =
IO_FL, IO_NN, or IO_STR), additional parameters appear on the configuration screen
form. These are:
• the SI IOP module number IOPNUM.
• the FTA number, 1 or 2 FTANUM.
• the serial link device address DEVADDR.
• FTA scan priority, low or high SCANPRI.
PTEXECST Parameter for HPM SI array points
With R670, SI Array points are provided with the PTEXECST parameter to set the point
ACTIVE or INACTIVE. The new parameter is stored in the HPM database checkpoint
file and the value of PTEXECST is restored on loading the checkpoint.
This parameter is similar to the PTEXECST parameter available in other point types.
You can disable the serial communication for the specified array point using the
PTEXECST parameter. This does not affect any other parameters of the array point.

ATTENTION
PTEXECST parameter is applicable only to the array points configured for
serial communication and is not applicable if EXTDATA is set to NONE.

Accessing the PTEXECST parameter

The keylock access to the PTEXECST parameter is Supervisor. The default value is
INACTIVE on point load. You can change the PTEXECST parameter to ACTIVE or
INACTIVE by any one of the following ways:

496 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 47 Array Points
47.5 Serial Interface to Array Points

• DATACHNG schematic.
• CL programs.
• Detail Display of a point.
• Alter Parameters function.
• ACT/INACT command from Command Processor.
• Custom Schematics.
You can view this parameter using the following tools:
• System Documentation Tool.
• Find Names.
Read/Write access for this parameter is provided through:
• Network Gateways to other LCNs.
• TPS applications that are capable of parameter access.
Access errors
If you access the PTEXECST parameter when the EXTDATA of an SI Array point is set
to NONE, the following error messages are displayed.

Access Method EXTDATA Error Message

Schematic NONE Unable To Access Point/P

Command Processor NONE Cannot Activate/Inactivate Pt

CL program NONE Parameter PTEXECST not on this data

point

Alter Parameters NONE (29) PARAM ID ERROR

R688 HPM High-Performance Process Manager Control Theory 497

08/2019 Honeywell
47 Array Points
47.5 Serial Interface to Array Points

PTEXECST states
The states of the PTEXECST parameter are as follows:
• Inactive: If an SI Array point is set to INACTIVE, the serial communication between
the SI Array point and the device is stopped. The data parameters (FL [], NN [], or
STR []) return bad values (-----) as in the case of a communication failure. The
communication with the serial device is suspended, but the configuration of the SI
Array point is retained. In the INACTIVE state, no soft failure or system error is
reported. If the point is set back to ACTIVE, you need not change the configuration.
The preserved values are restored on activation. If more than one point is connected
to one device, all the points are to be set to INACTIVE for stopping the
communication.
• Active: If the PTEXECST of an SI Array point (configured for a particular device) is
set to ACTIVE, the configuration is downloaded to the FTA and the serial
communication is established. In the ACTIVE state, the point can report
communication errors, if any.
Journal entries
If the PTEXECST parameter is changed using the DATACHNG schematic, a Detail
Display, the Command Processor or the Alter Parameters function, the changes are
journaled in the Process Change Journal and the Process Alarm Journal. Any changes
made through AM/CL are logged in the journal specified in the AM/CL debugger.
Loading an SI Array point
You cannot load an SI array point if the PTEXECST is ACTIVE. However, the point can
be loaded with PTEXECST as ACTIVE if the HPM or the SI IOP is IDLE.
Switching off the serial device
Before switching off a serial device, set all the associated SI Array points to INACTIVE.
If all the points are inactivated, there are no soft failures on the FTA and SI IOP. The IOP
Status Display shows no errors or soft failures and the system status LED does not blink.
The SI IOP Detail Display indicates, “No array points are configured to this FTA” as the
FTA error status. No error is displayed if the point is set to INACTIVE before the device
is turned off.
Deleting an SI Array point
Before deleting an SI Array point, set the PTEXECST parameter to INACTIVE.
Migration
When migrating to R670, the default value of the PTEXECST parameter is automatically
set to ACTIVE. With R670, when an APM checkpoint is migrated to an HPM, the
PTEXECST parameters of the SI Array points are automatically set to ACTIVE. If a pre-

498 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 47 Array Points
47.5 Serial Interface to Array Points

R670 checkpoint is restored, the value of PTEXECST parameter is automatically set to

ACTIVE.
Disabling an SI Array point
The communication to the device is disabled only if all the SI Array points connected to
the same device are set to INACTIVE. The configuration of the INACTIVE points are
downloaded to the FTA and the FTA stops communicating with these points. It does not
affect the other ACTIVE points configured for the same FTA and the device.
Communication errors and soft failures are reported when the serial device has at least
one ACTIVE point.
In a multi-drop scenario, if all the array points connected to one device are set to
INACTIVE, the device stops reporting any communication errors. However, the serial
communication is not disturbed on the active devices. These active devices in the multi-
drop can report communication errors.
Modbus and Allen-Bradley interface parameters
An SI Array point typically interfaces with an AEG Modicon Generic Modbus Controller
or an Allen-Bradley programmable logic controller. Other devices that use the Modicon
RTU protocol may communicate through the Modbus Controller to an SI Array point.
Your Honeywell representative can provide a list of qualified devices.

R688 HPM High-Performance Process Manager Control Theory 499

08/2019 Honeywell
47 Array Points
47.5 Serial Interface to Array Points

AUXDATA Parameters
These parameters are for use with the Generic Modbus interface. They should be set to
NaN (dashes) when communicating with an Allen-Bradley PLC. Likewise, when the
Modbus interface is being used, the AB_DATA parameters should be set to NaN.

Parameter Specifies

AUXDATA1 Modbus Coil Keep Alive Address

AUXDATA2 Wait time before message retry

AUXDATA3 EIA protocol and modem control

AUXDATA4 Baud rate and Parity

Allen-Bradley data parameters

These parameters are for use with the Allen-Bradley interface. They should be set to NaN
(dashes) when communicating with a Modbus. Likewise, when the Allen-Bradley
interface is being used, set AUXDATA parameters to NaN.
The following table is only a general overview of the AB_Data parameters.

Parameter Specifies

AB_DATA1 The PLC family

AB_DATA2 The PLC file number

AB_DATA3 The Data type

AB_DATA4 The Scan rate

Array Type and Size

Most of the remaining SI Array parameters considerations deal with a starting index and
array size (number of flags, numerics or strings).
When used with the Serial Interface, the starting index parameters: FLSTIX (Flag),
NNSTIX (Numeric), or STRSTIX (String) refer to a register address in the serial device.
This register is scanned over the appropriate range as set by the array size.

500 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 47 Array Points
47.6 Status and Error Checking

The concept of array type, size, and starting index is the same as described for mapping
to HPM box variables, but for Serial Interface data, the limits are as follows:

Array Type Array Size Starting Index Range

Flag 0 -512 0 - 99,999

Numeric (real) 0 – 16 0 - 99,999

Numeric (integer) 0 – 32 0 - 99,999

String 0 -8* 0 - 99,999

* 64 characters maximum configured any way from eight 8-character strings to one
64-character string

47.6 Status and Error Checking

Status reporting
Several Array point parameters are provided for status reporting. Error information
appears on the Array Point Detail displays and the SI IOP Detail Status display, or can be
tested with CL. The following parameters should be checked periodically:
• BADPVFL provides an overall database status (ON = bad). The overall status is bad
when there are communication problems or the SI module is in Idle. When the overall
status is bad, an attempt to access numeric, flag, or string data results in a bad access
status. Consequently, CL programs should check BADPVFL or INITREQ before
using SI data.
• INITREQ, when set to ON, indicates that the write to the SI module cannot be
completed.
• ERRCODE provides an 8-character error string.

ATTENTION
Note that BADPVFL and INITREQ are always OFF if not using SI data
(EXTDATA = None).

47.7 Read-Back Check for Device Control/Digital

Composite Points
Device Control or Digital Composite points can have digital output connections through
an SI/Array point to a field subsystem. The field device or its interface may interrupt or
change the output and not provide any indication of the change.
R688 HPM High-Performance Process Manager Control Theory 501
08/2019 Honeywell
47 Array Points
47.8 CL Notes

If flag data is mapped back from the SI/Array point, a digital output read-back check
determines the actual value of the output. After a new output state is stored to the digital
output connections, the read-back check is delayed for a time period equal to the
feedback-time parameter (FBTIME) or 4 seconds, whichever is greater. This delay
allows the SI/Array output enough time to reach even a slow responding field device
before causing a Command Disagree alarm (see “Any transitions in the PV input state
can be used for triggering event-initiated processing of points in the Application Module
(AM). It is configured by entering EIP for the event-report-option parameter EVTOPT.
The user must enter the tag name of the AM or CM point using the EIPPCODE
parameter.
Commanded State (OP)” in Section 0 and “Alarms” in Section 48.4).
If a discrepancy then exists between OPFINAL and OP, the operator is advised. If
OPFINAL does not agree with any of the defined states, its state is displayed as NONE.

47.8 CL Notes
All Array point data (flags, numerics, and so on) can be accessed by a CL program
(without impacting IOL prefetch limitations). Refer to the Control Language/Advanced
Process Manager Reference manual for additional information.
The CL/HPM compiler issues a warning when external Array point data (data read from
a Serial Interface) is used in a LOCAL declaration. This is done because the data is not
truly local, but resides in the external device connected to the Serial Interface IOP.

502 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 48. Device Control Points
48.1 Functional Overview
Purpose
The Device Control (DevCtl) point provides a way to manipulate a device, typically a
motor, and a way to view the strategy through a single point. In addition, this point helps
the operator to graphically trace the source of an interlock condition.
You can allocate up to 160 Device Control points (NDEVSLOT) or combinations of
standard and fast DevCtl (NFASTDEV) points during Node Specific Configuration.
Features
Some of the features of the device control point are as follows:
• Permits a custom logic design (within the strategies provided by the device control
point) of an interlocked motor control strategy.
• Allows configuration of a seal-in circuit function.
• Allows configuration of a state change function.
• Accommodates single- and dual-speed single direction motors, reversible single-
speed motors and motor-operated valves.
Description
The following figure is a block diagram of the Device Control Point. It can be thought of
as a combination Digital Composite Point, Logic Point, and Regulatory PV Data
Acquisition point. The left side of this drawing provides a concept of the input processing
capabilities, while the right side of the drawing illustrates the output concept.

R688 HPM High-Performance Process Manager Control Theory 503

08/2019 Honeywell
48 Device Control Points
48.1 Functional Overview

Figure 48-1 Device Control Point Functional Diagram

Input Processing Output Processing

Digital Input Digital Input

#1 Source #1 Status

Digital Input Digital Input

#2 Source #2 Status Digital Output
Destination(s)
Local Manual Local Manual
Source Input

SECVAR Output
Commanded State
Logical Input Logical Output
Output #1
Sources, 1 to 12 Destination(s)
State Command

Permissive
State #1

Interlock
State #1
Alarms
Output #0
State Command

Permissive
State #0

Interlock Override Interlock

State #0 Alarm Descriptor

Secondary Safety Override

Gates, Interlock
Primary 1 and 2
Output #2
Gates, State Command
1 to 4
Permissive Actual Output Last
State #2 Stored to Device

Interlock
State #2

Primary and
Secondary Input
Gates, 1 to 12

504 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 48 Device Control Points
48.2 Input Connections

Digital composite section

Two digital inputs, a Local Manual input, and the Digital Output(s) make up the Digital
Composite part of the point as shown in the upper part of the preceding figure. All of the
properties of the Digital Composite point described in Section 4 apply to this part of the
Device Control point.
Logic section
The left side of the preceding figure shows how up to 12 logic inputs are brought into the
point. The gates that follow allow the inputs to be inverted, delayed, compared, and so
on. The resulting signals can drive other gates, interlocks, permissives, or output
commands.
Two logic outputs can be configured to output most real or logical data from the point.
Regulatory PV section
An analog input referred to as the secondary variable (SECVAR) is provided. It is
typically used to monitor motor current. You can configure alarms to indicate when this
input exceeds specified limits and you can accumulate statistics on levels and durations
for this input.
Processing order
The DevCtl point processing order should be regarded as: the regulatory PV section first,
then the logic section, and finally the digital composite section.

48.2 Input Connections

Digital inputs
Up to two digital inputs connections can be allocated with NODINPTS (number of
Digital Inputs). The input source is defined by DISRC(1) and DISRC(2), which are
thereafter referred to as D1 and D2. The input source(s) can be specified as a tag
name.parameter or a hardware reference address. Allowable sources are:

• Digital Input Points —PV • Logic Slot Flags

• Digital Output Points —SO • ProcMod Flags

• Logic Slot gate outputs • DevCtl Flags

• PM Box Flags —PV • Array Point Flags

R688 HPM High-Performance Process Manager Control Theory 505

08/2019 Honeywell
48 Device Control Points
48.2 Input Connections

These sources must be in the same HPM box as the Device Control point. The PV state is
calculated from the inputs the same way as for a Digital Composite Point.
Other configuration for this section such as box color, and so on is the same as for a
Digital Composite Point. You can specify the PV states, options, and alarming.
Logic inputs
The following figure presents a simpler way of looking at just the Logic Inputs, their
associated gates, how the outputs can be routed, and possible destinations.
Looking at the logic gates in the following figure, you should note the concept of
Primary or Secondary Input Gates and Primary or Secondary gates. This terminology is
used throughout the following discussions and on the point configuration screens.
Figure 48-2 Logic Gates and Destinations

LOGIC INPUTS INTERLOCKS,

PERMISSIVES,
PRIMARY SECONDARY AND
LISRC(1) INPUT INPUT COMMANDS
GATE GATE
1 1
2 2 PRIMARY OPCMD
3 • 3 GATES
• SOCMD (0)
• PG1
SOCMD (1)
• PG2
SOCMD (2)
• PG3
• PG4
SECONDARY SI0
PRIMARY • SECONDARY
LISRC(12) • GATES
INPUT INPUT
• I0, I1, I2
GATE GATE SG1
12 12 SG2
P0, P1, P2

You can designate up to 12 Logical inputs (NOLINPTS) and enter an 8-character ASCII
descriptor for each input (LIDESC(n) where n is 1–12). The ASCII descriptor can be
changed by a CL program or a person with Engineer access level.

506 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 48 Device Control Points
48.2 Input Connections

Each input source is specified by Logic input source parameter LISRC(n) and you can
use:
• any Boolean, integer, enumeration, self-defining enumeration, or real parameter
from within the HPM, or another UCN node.
• the PV flag or BADPVFL for a Digital Input point from within the HPM.
• the SO or INITREQ parameters for a Digital Output point from within the HPM.
• any IOP parameter (up to a maximum of six).
Logic inputs (LISRC(1) – LISRC(12) are referenced within the configuration pages as
L1 – L12.
The parameter LIBADOPT allows substitution of Off, On, or the last good value (Hold)
in case a logic input goes bad.

ATTENTION
Every logic input that you specify must eventually be used to drive some
output, permissive, or interlock.

Primary and secondary logic input gates

• Algorithms—
− The following figure shows the various choices for the Primary Input Gate
algorithm (parameter PIALGID(n)) and the Secondary Input Gate algorithm
(parameter SIALGID(n)).
• Primary Input Gate Algorithms—
− Null means the input is passed unchanged to the output.
− Comparison algorithms for the Primary Input Gate such as GT, GE, and so on
compare the input to parameter PINN(n) where n is the gate number. PINN(n)
contains a real number entry of your choice. Algorithms ending in 2 such as
GT2, GE2, and so on, compare the input to a primary input source specified by
PISRC(n) where n is the gate number. This allows you to compare the
configured input to one of the logic inputs (L1 – L12). Gate(n) output goes true
when the comparison succeeds.
− In_Set algorithm compares the gate input with a table of ten numerics
(NNINSET(n)) and the output goes true if the input equals any value in the set.
You must enter the ten numeric values which can range from 0 to 32,767.
Primary Input gates that use comparison algorithms can have a deadband value
(PIDEADBD(n) for each gate:
• For GT, GT2, GE, GE2, LT, LT2, LE, or LE2 gates, the deadband only applies on a
true to false comparison. For example, assume that one of these gates is configured
R688 HPM High-Performance Process Manager Control Theory 507
08/2019 Honeywell
48 Device Control Points
48.2 Input Connections

for L1 (input) greater than 50 and the deadband value = 5. The gate output goes true
when L1 is greater than 50, but does not go false unless L1 falls below 45.
• For EQ, EQ2, NE, and NE2 gates, the deadband value defines the range of
comparison. For example, an EQ gate is configured with input numeric PINN(n) = 6
and deadband parameter PIDEADBD(n) =2. The output is true when the input source
is between 4 and 8.
Figure 48-3 Primary and Secondary Logic Input Gate

Primary Secondary
L(n) Input Gate Input Gate SIDSTN(n)
1 –12 1 –12

PIALGID(n) SIALGID(n)

Algorithms
• NULL • INVERT

• GT - Greater than PINN(n) • GE - Greater than or equal to PINN(n)

• LT - Less than PINN(n) • LE - Less than or equal to PINN(n)

• EQ - Equal to PINN(n) • NE - Not equal to PINN(n)

• GT2 - Greater than PISRC(n • GE2 - Greater than or equal PISRC(n)

• LT2 - Less than PISRC(n) • LE2- Less than or equal PISRC(n)

• EQ2 - Equal to PISRC(n) • NE2 - Not equal to PISRC(n)

• IN_SET • NULL

• DLY - Delay • ONDLY - On Delay

• OFFDLY - Off Delay • PULSE

• MAXPULSE • MINPULSE

508 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 48 Device Control Points
48.2 Input Connections

Secondary input gate algorithms

These include various types of delays. Your entry (0 – 8000 seconds) in parameter
SIDLYTIM(n) determines the delay (per gate).
• Delay—The Delay algorithm causes a one cycle delay of the input value (at the
execution rate of the point). Parameter SIDLTYM does not apply to this gate.
• On Delay—On Delay starts counting when the input switches from Off to On. If the
input is still On when the time runs out, the output is set to On. When the input signal
switches Off, the output is set to Off immediately and the timer (if running) is
stopped.
• Off Delay —Off Delay starts counting when the input switches from On to Off. If
the input is still Off when the timer runs out, the output is set to Off. When the input
signal switches On, the output is set to On immediately and the timer (if running) is
stopped.
• PULSE —Pulse provides a fixed pulse output when the input switches from Off to
On. The pulse width is specified by SIDLYTIM(n). Another output pulse cannot be
generated until the preceding pulse has completed.
• MAXPULSE—MAXPULSE provides a pulse output when the input switches from
Off to On. If the input switches Off before the specified time, the output is also set to
Off immediately. If the input stays On longer than the timer period, the output pulse
shuts Off at the end of the timer period.
• MINPULSE—MINPULSE provides a pulse output when the input switches from
Off to On. If the input switches Off before the specified timer period, the output is
extended until the period is over. If the input stays On longer than the timer period,
the output pulse follows the input pulse.

R688 HPM High-Performance Process Manager Control Theory 509

08/2019 Honeywell
48 Device Control Points
48.2 Input Connections

Secondary input gate destinations

The output destination from each Secondary Input Gate is specified by SIDSTN(n).
• None (gate not used).
• Interlocks SI0, I0, I1, or I2.
• Permissive Interlocks P0, P1, or P2.
• OPCMD, SOCMD0, SOCMD1, or SOCMD2.
• Primary Gates PG1, PG2, PG3, or PG4.
• Secondary Gates SG1 or SG2.
Figure 48-4 Secondary Input Gate

Secondary
Input Gate SIDSTN(n)
1–12
(Destination)

ATTENTION
Every Secondary Input Gate that you configure must have an output
destination specified.

Primary and secondary logic gates

You can configure up to four Primary Gates (NOPGATE) and up to two Secondary
Gates (NOSGATE). Each gate can have up to six inputs. The inputs are determined by
specifying them as destinations from other gates. It isn’t necessary to use these gates if
you do not need the functions they provide.
The following figure illustrates the Primary and Secondary Gate algorithm, lists the
algorithm choices.
Figure 48-5 Primary and Secondary Logic Gates

Primary Secondary
Gate PGDSTN(n) Gate SGDSTN(n)
1–4 1– 2

PGALGID(n) SGALGID(n)

Table 48-1 Primary and Secondary Logic Gate Algorithms

510 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 48 Device Control Points
48.2 Input Connections

Primary Logic Gate Algorithms Secondary Logic Gate Algorithms

AND PAND AND PAND

OR POR OR POR

NAND PNAND NAND PNAND

NOR PNOR NOR PNOR

XOR PXOR XOR PXOR

Primary Gate Inputs—Inputs to the Primary Gates can only come from Secondary
Input Gates. Up to six inputs is available.
Secondary Gate Inputs—Inputs to the Secondary Gates can come from any of the 12
Secondary Input Gates or any of the four Primary Gates.
Primary and Secondary Gate Algorithms—both the Primary and Secondary Gates
have identical algorithms. Algorithms beginning with a P have a pulsed output when the
gate is enabled. Pulse width is specified by parameter PGPLSWTH(n) for Primary Gates
or SGPLSWTH(n) for Secondary Gates. Pulse width can range from 0–8000 seconds.
Primary and secondary gate destinations

ATTENTION
Every Primary and Secondary Gate must have an output destination
specified.

Primary Gate Destinations—Parameter PGDSTN(n) directs outputs from Primary Gate

n to any one of the destinations shown in the following figure.
• None (gate is unused).
• Interlocks SI0, I0, I1, or I2.
• Permissive Interlocks P0, P1, or P2.
• OPCMD, SOCMD0, SOCMD1, or SOCMD2.
• Secondary Gates SG1 or SG2.

Figure 48-6 Primary Logic Gate Destinations

R688 HPM High-Performance Process Manager Control Theory 511

08/2019 Honeywell
48 Device Control Points
48.2 Input Connections

Primary
Gate PGDSTN(n)
1–4
(Destination)

Secondary Gate Destinations—Parameter SGDSTN(n) directs outputs from Secondary

Gate n to any one of the destinations shown in the following figure.
• None (gate is unused).
• Interlocks SI0, I0, I1, or I2.
• Permissive Interlocks P0, P1, or P2.
• OPCMD, SOCMD0, SOCMD1, or SOCMD2.
• Secondary Gates SG1 or SG2.
Figure 48-7 Secondary Logic Gate Destinations

Secondary
Gate SGDSTN(n)
1–2
(Destination)

Detail display presentation

A graphic representation of the logic connections is presented on the point’s detail display.
The Detail display of logic configuration shown in the following figure is typical of the
Override Interlock section of this display. The Logic Input descriptors you choose
(LIDESC(n)) appear instead of the numbered inputs shown in the example. Heavy lines
indicate power flow and allow the operator to determine which input is driving an
interlock such as shown in the following figure, where Input _7 is driving the override
interlock.

512 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 48 Device Control Points
48.2 Input Connections

Figure 48-8 Detail Display of Logic Configuration

OVERRIDE
STOP
Input_4 AND OR
2 3

Input_5

Input_6

Input_7

Secondary input variable input

This Regulatory PV section of the DevCtl point provides an analog input for a Secondary
Variable (SECVAR). The Secondary Variable input connection is specified by parameter
SVSRC as a tag name.parameter or hardware address reference. Typically this input is
used to monitor motor current, flow rate, valve position, and so on.
During configuration you can specify-
• descriptors–(SVDESC and SVEUDESC).
• the high/low engineering unit range–(SVEUHI/SVEULO).
• the target value (setpoint)–(SVTV).
• the high and high high trip point–(SVHITP and SVHHTP).
You can also specify the alarm priorities, an alarm deadband, and the secondary variable
alarm mask time. Mask time (MASKTIM) specifies the time from 1–1000 seconds that
alarms are inhibited after an output change.
Several historical items related to the Secondary Variable can be accumulated and
reported on the Maintenance Statistics Display section of the point’s Detail Display.
These are—
• the peak value of the secondary variable on the last run.
• the duration of the first peak above the full load high trip limit.
• the time that the secondary variable is continuously greater than its high trip limit.

R688 HPM High-Performance Process Manager Control Theory 513

08/2019 Honeywell
48 Device Control Points
48.2 Input Connections

The following figure shows how the Secondary Variable appears on the point detail
display. The thick bar represents the actual value. The lower vertical dash represents the
target value (SVTV). The Secondary Variable high alarm priority trip point in percent
(SVHITPP) and high high alarm trip point in percent (SVHHTPP) are represented by the
other two small vertical dashes.
Figure 48-9 Secondary Variable Representation on the Point Detail Display

SVHITPP SVHHTPP

SVTV

The colors of SVHITPP and SVHHTPP are described in the following table.
Table 48-2 SVHITP and SVHHTP Colors

Network Config. Red SVHITP Color SVHHTP Color

Color Alarm Priority

Two Alarm Colors SVHIPR = SVHHPR =

Low Hi Emg. Low Hi Emg.

Low Red Red Red Red Red Red

High Yel Red Red Yel Red Red
Emergency Yel Yel Red Yel Yel Red

Three Selectable Depends on color selected in NCF Depends on color selected in NCF
Alarm Colors

When SVHITPP is configured = SVHHTPP, a single vertical dash represents both

values. Its color is determined in the same way as for SVHHTPP. The Red Color Alarm
Priority is configured during the Console Data part of Network Configuration.
The bar graph color for the Secondary Variable in percent (SVP) depends on the
Secondary Variable High alarm Flag, the High High alarm Flag, and the Secondary
Variable High and High High alarm priorities.
If the two-color alarm option is selected in the Network Configuration File (NCF), SVP
color is described in the following table.

514 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 48 Device Control Points
48.2 Input Connections

Table 48-3 SVP Bar Graph Color Chart

Condition Result

1 If SVHIFL and SVHHFL are both FALSE SVP color is Cyan

2 If SVHIFL is TRUE, then the following table determines when SVP color is
RED
Network Configuration Red Color Alarm SVHIPR =
Priority =

Low Hi Emg
Low Red Red Red
High N/A Red Red
Emergency N/A N/A Red

3 If SVHHFL is TRUE, then the following table determines when SVP color is RED.

Network Configuration Red Color Alarm SVHHPR =

Priority =

Low Hi Emg
Low Red Red Red
High N/A Red Red
Emergency N/A N/A Red

4 For all other conditions SVP color is Yellow

If the three color alarm option was selected in the NCF, the SVP color is based on the
color choices in the NCF.
Local Manual Input
Parameter LMSRC allows you to designate a logical input for the local manual signal.
The source can be specified as a tag name.parameter or as a hardware reference address.
Parameter LMREV permits the input to be inverted.
When the LOCALMAN flag is true, it indicates that the device’s state is being controlled
directly by external hardware. The Device Control point’s output tracks the PV (the
actual state of the device). When the device is taken out of Local/Manual, the output of
the point matches the current state of the device being controlled.

R688 HPM High-Performance Process Manager Control Theory 515

08/2019 Honeywell
48 Device Control Points
48.3 Output Connections

48.3 Output Connections

Digital outputs
The number of digital outputs (up to three) is determined by parameter NODOPTS. State
Outputs destinations for STxOPy (where x = 0, 1, 2 and y = 1, 2, 3) are assigned by
parameter DODSTN(n) where n = 1–3 (depending on the number of outputs configured).
Acceptable destinations are:

• Digital Output Point–Latched Output • Digital Output Point–Pulsed Output

• Logic Slot Flag • HPM Box Flag

• Process Module Slot Flag • Device Control Slot Flag

• Array Point Flag

Destinations
Destinations are specified as a tag name.parameter or a hardware address and they must
be in the same HPM as the Device Control point. If a hardware address is used, it must
have one of the following forms (where nnnn = 1 to 16,384):
!BOX.FL(nnnn)
!DOmmSss.S0
Output commands
There are two ways to command the output:
• when MODATTR = Operator, the operator can command it.
• when MODATTR = Program, a Logic point or CL program can command it.
OPCMD controls State 0 and State 1. SOCMD(n) controls State 0, State 1, and State 2.
Inputs to OPCMD or SOCMD can come from any of the following logic gates:
• the Primary Gates.
• the Secondary Gates.
• the Secondary Input Gates.
logic gates. Both OPCMD or SOCMD can be configured to drive the output, but you
should use only one of these on a given point. When interlock logic does not drive
OPCMD or SOCMD, they can be written from outside (for example from a Logic point,
a CL Program, and so on)

516 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 48 Device Control Points
48.3 Output Connections

Do not configure two different logic outputs to drive OPCMD and

CAUTION SOCMD of the same Device Control Point.

The state of OP is calculated from signals generated by the primary and secondary gates
through OPCMD or SOCMD, as well as LOCALMAN and REDTAG.
OP can be commanded to state 1 or state 0 using the OPCMD parameter. When OPCMD
is commanded ON, OP is set to state 1. When OPCMD is commanded OFF, OP is set to
State 0. OPCMD can be used when three states are defined, but will only command OP
to state 1 or state 0.
SOCMD(i) provides a command for each state (i = 0, 1, or 2). Unlike OPCMD, the
output state is commanded when SOCMD(i) goes from OFF to ON. For example, if
SOCMD(1) is commanded ON, State 1 goes true. Then if SOCMD(0) is commanded
ON, State 0 is commanded. It does not matter that the logic for SOCMD(1) is still
commanding an ON condition. In order to return to State 1, SOCMD(1) must command
an OFF, and then an ON condition.
Interlocks Permissives and Overrides
The ON command is sent to the output only if the permissives and interlocks are in a
state to permit the output. If the ON state is allowed, ON becomes the Output Final
OPFINAL output. OP and OPFINAL may be different; for example, if the seal in option
is activated.
The following figure illustrates the interlock system associated with the Device Control
Point’s digital outputs. This illustration is described thoroughly in Section 4 for the
Digital Composite point and is reproduced here for convenience.

R688 HPM High-Performance Process Manager Control Theory 517

08/2019 Honeywell
48 Device Control Points
48.3 Output Connections

Figure 48-10 Interlocks and Permissives Functional Diagram

Operator
Commanded State Off
(OP) from Operator Off

On On
Commanded State NMODATTR OROPT BYPASS
(OP) from Program Program

Commanded
STATE 2 State STATE 1

STATE 0
Permissive
Interlocks ON ON ON
(P1, P0, & P2 are OFF P2 OFF P0 OFF P1
controlled by
Logic Blocks)

STATE 2 STATE 0 STATE 1

ON OFF
STATE 2 I2
Override
Interlocks
(I2, I1, & I0 are
controlled by ON OFF
Logic Blocks) STATE 1 I1

ON OFF
STATE 0 I0

OFF
Safety ON
Interlock STATE 0 SI0

Output Connections
(Up to 3 Outputs)
PULSEWTH OUTPUT STxOPy
STCHGOPT STATE
STxOPy
SEALOPT GENERATOR
MOMSTATE (OPFINAL) STxOPy
x = 0, 1, 2
y = 1, 2, 3

518 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 48 Device Control Points
48.3 Output Connections

Seal-in —If the seal-in circuit is configured, it will unlatch the digital output contacts on
detection of the PV not following the output command as happens on a device drop out
(for example, a stopped motor). This condition is true any time the PV is not in state 1 or
state 2 and either a command disagree alarm or an uncommanded state change alarm is
present.
If the seal in option is enabled when the above condition is detected, the output
destinations are set to the state corresponding to OP of state 0, but OP is not altered. The
actual state commanded to the output destinations can be observed on the lower part of
the group display as OPFINAL. OPFINAL appears in reverse video when not equal to
OP.
Inputs—Inputs to the interlocks can come from the output of —
• any of the Secondary Input Gates.
• any of the Primary Gates.
• either of the Secondary Gates.
Inputs to the interlocks can also be written to from outside if not driven by any interlock
logic (like OPCMD and SOCMD(n). Parameter LOGICSRC allows you to enter the
name of an external point (if any) that is controlling interlocks and permissives. The
entry then appears on the Detail Display.
Break Before Make Option—When OP is commanded from State 1 to State 2 (that is,
from forward to reverse), or from State 2 to State 1, OP will first go to State 0 (that is,
stop) and remain there for a configured pause time before going to the commanded state.
Digital outputs on the detail display
The following figure shows how the commanded digital output appears on the detail
display for a two state and for a three state output.
Figure 48-11 Output Indicators on the Point Detail Display

START FORWARD

STOP OFF

REVERSE

The right half of any state box (when filled) indicates the commanded state. The left half
of any state box (when filled) indicates the PV has changed to that state.

R688 HPM High-Performance Process Manager Control Theory 519

08/2019 Honeywell
48 Device Control Points
48.3 Output Connections

Two dashes in a state box means that operator commands for that state are not permitted.
This can be caused because an interlock is active, when a program is controlling the
point, or the permissive for the state is off.
Logic output connections
The Device Control point can have up to two (NOLOPTS) Logic Output connections.
The following figure illustrates the Logic Output connection strategy. LOSRC is the
logic source, LOENBL is the flag that enables the gate, and LODSTN is the output
destination.
Figure 48-12 Logic Output Connections

LOSRC(n) Out
LODSTN(N)
LOENBL(n) Enable

LOSRC(n), the logic source can come from—

• L1–L12, the logic inputs.
• FL1–F12, the local flags (you can set FL7–FL12 Off or On).
• NN1–NN8, the local numerics (you can enter the values).
• D1 or D2, the digital inputs.
• P0, P1, or P2, permissive interlocks.
• SI0, I0, I1, or I2, Safety and other Status Overrides.
• PISO1–PISO12, Primary Input Gate output value.
• SISO1–SISO12, Secondary Input Gate status output.
• PGSO1–PGSO4, Primary Gate status output.
• SGSO1–SGSO2, Secondary Gate status output.
• PINN1–PINN12, Primary input comparison numerics.
• SECVAR, the secondary variable.
LOENBL(n), the output enable signal can come from—
• L1–L12, the logic inputs.
• FL1–F12, the local flags.
• D1 or D2, the digital inputs.
• P0, P1, or P2, permissive interlocks.
• SI0, I0, I1, or I2, Safety and other Interlock Overrides.
520 HPM High-Performance Process Manager Control Theory R688
Honeywell 08/2019
 48 Device Control Points
48.3 Output Connections

• PIS01–PISO12, Primary Input Gate output value.

• SISO1–SISO12, Secondary Input Gate status output.
• PGSO1–PGSO4, Primary Gate status output.
• SGSO1–SGSO2, Secondary Gate status output.
LODSTN(n), the destination point.parameter to which the output is pushed can be either
an ASCII tag name or the hardware address of a point. The destination parameter can be
any type parameter (a conversion is made internally to write the correct data type to the
destination). If a hardware address is used it must be of the form !BOX, !AOmmSss, or
!DOmmSss, where mm is an Analog output or Digital Output IOP module number and ss
is the slot number within that module.

R688 HPM High-Performance Process Manager Control Theory 521

08/2019 Honeywell
48 Device Control Points
48.4 Alarms

48.4 Alarms
The Device Control Point provides the following alarms:
• BADPVFL, Bad process variable alarm.
• BADSVFL, Bad secondary variable alarm.
• CMDDISFL, Command disagree alarm.
• CMDFALFL, Command fail alarm.
• OFFNRMFL, PV off normal state alarm.
• OVRDI0FL, OVRDI1FL, OVRDI2FL , Override interlock alarms.
• OVRDSIFL, Safety Override alarm flag.
• SVHHFL, Secondary variable high high alarm.
• SVHIFL, Secondary variable high alarm.
• UNCMDFL, Uncommanded state alarm.
BADPVFL indicates that a digital input has detected a bad PV value.
CMDDISFL, the command disagree flag indicates that the field device did not go to the
commanded state within the allowed time.
CMDFALFL, the command fail alarm (also called the crack timer) is generated if the PV
does not change within the time specified by the command fail timeout parameter
(CMDFALTM) after the OP is commanded to a new state. This alarm is useful for motor
driven valves with states of OPEN, INBETWEN, and CLOSED. Alarm priority for the
command fail alarm is determined by the Command Disagree Priority (CMDDISPR)
parameter.
OFFNRMFL indicates that an Off Normal alarm has been detected.
The Secondary Variable high and high high alarms indicate the analog input SECVAR
has exceeded the configured limits and BADSVFL indicates the input value is NaN.
UNCMDFL, the uncommanded state alarm indicates that a field device changed state
without being command to do so.
The override interlock alarms and the safety override alarm indicate that an override is
active. Also refer to the Override descriptor description below.
Override interlock alarm descriptor
When an interlock is tripped, the Device Control point traces the cause of the interrupt
and presents the logic descriptor LIDESC(n) for that input on the Detail Display just
above the MAN/P-MAN indicator.

522 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 48 Device Control Points
48.5 Maintenance Statistics

48.5 Maintenance Statistics

If the Maintenance Support Option is enabled (MAINTOPT = ON), various maintenance
statistics are calculated and displayed on the maintenance page of the point’s Detail
Display. These statistics are available as standard parameters so they can be accessed by
CL programs, schematics, and so on, and can be saved on a history module.
A program can reset the maintenance statistics at any time by setting the point’s reset flag
parameter (RESETFL) to ON. The operator can only reset the statistics when the point is
in REDTAG.
During configuration, you can enter a maximum time allowed. The parameter
MAXTIMnH, n = 0, 1 or 2 sets the maximum time in hours. The maximum number of
transitions allowed into each state since the last reset is configured with parameter
MAXTRANn (where n = 0, 1 or 2). There is no alarming if the values are exceeded, but
CL programs can compare maximum specified values with accumulated values.
The Maintenance Statistics are presented in a plain English format. In addition, the
display contains a REDTAG target.
If you select the REDTAG target and press ENTER, the point’s REDTAG parameter is
set to ON and a RESET target appears. Selecting the RESET target (and pressing
ENTER) resets the points maintenance statistic values. If you select REDTAG, (and
press ENTER) the REDTAG condition clears and the RESET target disappears.

R688 HPM High-Performance Process Manager Control Theory 523

08/2019 Honeywell
48 Device Control Points
48.5 Maintenance Statistics

524 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
49 HPM Control Performance
49.1 Background

49. HPM Control Performance

49.1 Background
Control loops
The High-Performance Process Manager is a high-performance device capable of an
assured rate of 800 regulatory control loops per second. Users can customize their control
configuration to meet the application requirements.
Parallel processing architecture
The parallel processing architecture of the High-Performance Process Manager allows
the control processing capability of the HPM to be totally independent of other HPM
functions such as data requests for HPM data from the Network Interface Module and
other UCN devices, the number of I/O points built and alarming functions. Therefore,
only two factors must be considered when configuring the control processing: control
slot type and the scheduled frequency of execution, otherwise referred to as scan rate.

49.2 Control Slot Types

The following control slot types are resident in the High-Performance Process Manager
Module.

Slot Type Max No. of Points (Slots) Applicable Parameter

Digital Composite 999 NDCSLOT

Device Control 400 NDEVSLOT

Logic Slot 400 NLOGSLOT

Process Module 250 NPMSLOT

Regulatory PV 400 NPVSLOT

Regulatory Control 250 NCTLSLOT

Array 500 NARRSLOT

525 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
49 HPM Control Performance
49.3 Scan Frequency

REFERENCE - INTERNAL
For more information on any of these slot types, refer to the appropriate
sections of this document.
• Section 13, Digital composite point
• Section 14, Logic points
• Section 15, Process Module points
• Section 16, Regulatory PV point
• Section 26, Regulatory Control point
• Section 47, Array points
• Section 48, Device Control point
• HPM Control Functions and Algorithms manual.

Point mix
The point mix is defined by specifying the number of slots of each type using the
NDCSLOT, NLOGSLOT, NPMSLOT, NPVSLOT, NCTLSLOT, NDEVSLOT, and
NARRSLOT parameters that are found on the UCN/PM Configuration Form. This
configuration form allows the user to specify the particulars of the HPM Box Data Point.
Slot number for each point type
The slot numbers for each point type range from 1 to the user-specified maximum
number listed in the above chart. For example, if NPVSLOT is set to 35, the RegPV
points can be configured in any RegPV slot from slot 1 to slot 35. Similarly, if
NLOGSLOT is set to 40, the logic points can be configured to run in any logic slot from
slot 1 to slot 40. The point types and slot numbers are used for the initial configuration of
a data point and for specifying the processing order.

49.3 Scan Frequency

Background
Regulatory type (RegPV, RegCt1) and digital type (DigComp, DEVCTL, and Logic)
slots can be configured for scanning at different rates as specified by the SCANRATE
parameter and by the Fast Slots parameters. SCANRATE deals with the base scan rate
for all points of a certain type. The Fast Slots parameters allow a specified number of
regulatory or digital type slots to be processed at a quarter second rate without regard to
the base scan rate for the rest of the group. These are HPM Box Data Point parameters.
Array points are not processed (require zero PUs) so they are not affected by the
SCANRATE parameter.

526 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 49 HPM Control Performance
49.3 Scan Frequency

Scan rate
The scan rates indicate the number of times that all slots of that particular type (except
Fast Slots) are scanned and processed each second. For example, a scheduled frequency
of 1/4 sec for the regulatory slots indicates that all the regulatory slots in this HPM will
be scanned and processed four times each second. The scan rate has an impact on the
number of slots that can be processed as described in Determining Processing and
Memory Capacity.
The following chart contains the scheduled frequency of the respective entries for the
SCANRATE parameter.
Table 49-1 Scheduled frequency of SCANRATE parameters

SCANRATE Scheduled Frequency

Parameter Entry
RegCtl, RegPV Logic, DigComp, ProcMod
DevCTL

Reg1Log1 1 sec 1 sec 1 sec/ 500 ms

Reg1Log2 1 sec 1/2 sec 1 sec/ 500 ms

Reg1Log4 1 sec 1/4 sec 1 sec/ 500 ms

Reg2Log2 1/2 sec 1/2 sec 1 sec/ 500 ms

Reg2Log4 1/2 sec 1/4 sec 1 sec/ 500 ms

Reg4Log4 1/4 sec 1/4 sec 1 sec/ 500 ms

Note : The cycle time for ProcMod is decided by $NSFPMS parameter.

Fast slots parameters

Fast Slots parameters allow a specified number of the regulatory control, regulatory PV,
digital composite, or logic slots to be processed at a quarter second rate without regard to
the scan rate for the rest of the group. When fast slots are specified, they are the lower
numbered slots for that type. For example, if there are 50 regulatory control slots and 15
are specified as Fast (NFASTCTL = 15), then slots 1-15 are scanned every quarter
second, and slots 16-50 are scanned at the rate specified by the parameter SCANRATE.
The Fast Slots parameters are defined in the following table.

R688 HPM High-Performance Process Manager Control Theory 527

08/2019 Honeywell
49 HPM Control Performance
49.3 Scan Frequency

Table 49-2 Fast slots parameters

Parameter Max. Description

Number

NFASTCTL 200 Number of Fast Regulatory Control slots

NFASTDC 999 Number of Fast Digital Composite slots

NFASTPV 200 Number of Fast Regulatory PV slots

NFASTLOG 200 Number of Fast Logic slots

NFASTDEV 200 Number of Fast Device Control slots

$NSFPMS 100 Number of Semi Fast Process Module slots

If the SCANRATE parameter is configured for four times per second, then all of the
points for those types are scanned at the quarter second rate. The number of fast slots is
forced to the same as the total number of slots for that type (provided that the total
number of slots is less than or equal to the maximum number of fast slots). For example,
if SCANRATE = REG1LOG4, then the number of Fast Logic slots parameter
(NFASTLOG) are set equal to the number of Logic slots (NLGSLOT).
ATTENTION
With TPN R684, the limit of HPM Regulatory PV slots and fast Regulatory PV
slots are increased from 125 to 400 and 125 to 200, respectively. This
increase in the range allows the users to increase the value of NPVSLOT and
NFASTPV.

TIP
The PERIOD parameter shows the processing period in seconds. Refer to
the High-Performance Process Manager Parameter Reference Dictionary for
additional information.

Point processing executive

The point processing executive in the HPMM runs at quarter-second (or 250
milliseconds) intervals or "cycles." (Each quarter second cycle is further divided into
two sub cycles to provide a breakpoint for database synchronization.) Slot scheduling
determines the assignment of slots to cycles and the ordering within a cycle. This
operation is automatically performed at the load of the box data point.

528 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 49 HPM Control Performance
49.3 Scan Frequency

The processing load is distributed as evenly as possible between the four cycles using the
following logic:
• All of the 1/4 second slots are processed in every cycle.
• 50% of the processing load of the 1/2 second slots is processed in cycles 1 and 3; the
other 50% in cycles 2 and 4.
• 25% of the processing load of the 1 second slots is processed in each of the four
cycles.
Processing order
The processing order of the slots within a cycle is determined based on the point type as
follows (from left to right):

RegPV Fast RegPV ProcMod Logic Fast Logic

RegPV Fast RegPV ProcMod Logic Fast Logic
DevCtl Fast DevCtl DigComp Fast DigComp
RegCtl Fast RegCtl

Within each point type, the slots are processed in the descending order of the slot number
(that is, from highest slot number, down to one).
I/O Data Scanning
The frequently used I/O parameters in the following table are automatically scanned in
the HPMM.

I/O Point Type Scanned Parameters IOP Scan Period

Analog Input PV, PVSTS, PVHHFL, 1/4 second for HLAI,

PVLLFL, PVHIFL,PV, PVSTS, 1/4 second for FBUS AI
PVHHFL, PVHIFL, PVLOFL,
PVLOFL, PVLLFLPVLLFL, LLAI, PI, and STIM
PVROCNFL,PVROCPFL, 1/2 second for LLMUX & RHMUX
BADPVFL

Digital Input PVFL, BADPVFL 1/4 sec for DI and DISOE,FBUS DI

Digital Output SO and INITREQ 1/4 sec for DO and DO_32

R688 HPM High-Performance Process Manager Control Theory 529

08/2019 Honeywell
49 HPM Control Performance
49.3 Scan Frequency

ATTENTION
CL programs or control functions running in the HPMM do not require an I/O
Link prefetch when reading any of the scanned parameters, and thus I/O Link
prefetch related restrictions do not apply.

Scanned parameters in error cases

Reading any of the scanned IOP data never generates a communication error even if the
IOP is failed. The following table summarizes the value of the scanned parameters in
error cases and when the I/O module itself is in IDLE state or the point is INACTIVE.

Error Condition Module Type Default Data

Module Idle/ HLAI, LLAI, PI, PV = NaN

Point Active LLMUX, RHMUX, PVSTS = Bad
STIM, FBUS AI All alarm flags = OFF

DI, DISOE, PVFL = OFF (INPTDIR = Direct)

FBUS DI PVFL = ON (INPTDIR = Reverse)
BADPVFL = ON

DO, DO_32 SO = Last Value

INITREQ = ON

Module Fail/ HLAI, LLAI, PI, PV = NaN

Communication LLMUX, RHMUX, PVSTS = Bad
Error STIM, FBUS AI Alarm flags = OFF
Alarm flags = Last Value (Comm Err)

DI, DISOE, PVFL = OFF (INPTDIR = Direct)

FBUS DI PVFL = ON (INPTDIR = Reverse)
BADPVFL = ON

DO, DO_32 SO = Last Value

INITREQ = ON

Wire Cut HLAI, LLAI, PI, PV = NaN

LLMUX, RHMUX, PVSTS = Bad
STIM, FBUS AI All alarm flags = OFF

DI, DISOE, PVFL = OFF (INPTDIR = Direct)

FBUS DI PVFL = ON (INPTDIR = Reverse)
BADPVFL = ON

DO, DO_32 SO = Last Value

INITREQ = ON

530 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 49 HPM Control Performance
49.4 Determining Processing and Memory Capacity

49.4 Determining Processing and Memory Capacity

Processing units
The processing power of the HPM control processor is measured in terms of "Processing
Units (PUs)." Each control processor has an assured rate of 800 PUs per second. Each
slot type consumes a certain amount of PUs subject to the scheduled frequency.
Processing units relationship to scheduled frequency
The relationship between the scheduled frequencies and the Processing Units for the slot
types are contained in the following table. Please note that slots use more Processing
Units at faster frequencies.

Slot Type Pus per Second at Scheduled Frequencies

1/4 Second 1/2 Second 1 Second

Digital Composite 0.4 PU 0.2 PU 0.1 PU

Device Control 4 PU 2 or 4 PU 1 or 2 PU
Logic 4 PU 2 PU 1 PU

Process Module N/A 2 or 4 PU 1 or 2 PU

Regulatory PV 4 PU 2 PU 1 PU

Regulatory Control 4 PU 2PU 1 PU

Array 0 PU 0 PU 0 PU

String 0 PU 0 PU 0 PU

Timer 0 PU 0 PU 0 PU

Flag 0 PU 0 PU 0 PU

Numeric 0 PU 0 PU 0 PU

Numeric 1/40 PU 1/40 PU 1/40 PU

(w/PV Alarming)

Note: With TPN R684, the number of PUs consumed by the configured HPM Regulatory
PV point type increases with the increase in the value of NPVSLOT and NFASTPV.
HPM needs these extra processing units to execute the additional HPM Regulatory PV
slots.

R688 HPM High-Performance Process Manager Control Theory 531

08/2019 Honeywell
49 HPM Control Performance
49.4 Determining Processing and Memory Capacity

Process Module points

When configuring each HPM, you can choose how many processing units are allocated
for its Process Module points.

If SEQPROC equals... then...

1_PU one PU is allocated per Process Module point per scan

and up to 200 Process Module points can be scheduled in
a single quarter-second cycle.

2_PU two PUs are allocated per Process Module point per scan
and up to 100 Process Module points can be scheduled in
a single quarter-second cycle.

In batch applications where many small sequences are needed and you want all of them
loaded at the same time, 1_PU is the appropriate choice for parameter SEQPROC.

ATTENTION
Process module points in software releases R230 (and earlier) always used
two processing units, therefore, parameter SEQPROC should be set to 2_PU
if updating from R230 and earlier versions.

With R682, you can process the Process Module points every 500ms. The process
module points to be scanned twice a second must be placed in the lower numbered slots.
These points are configured for twice a second execution by the parameter $NSFPMS
(Number of Semi Fast Process Module Points) in the HPM Node Specific Configuration.
HPM must be in idle state to modify the value of $NSFPMS. When the HPM is set to
RUN state the points are automatically processed twice a second. Note that you must
modify and compile the sequence programs, and load them to the corresponding points
for the rearrangement of the slots to take effect.

532 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 49 HPM Control Performance
49.4 Determining Processing and Memory Capacity

HPM requires more Processing Units to execute this scan. The following is the PU
consumption for twice a second execution of Process Module points.

If SEQPROC equals... then...

1_PU two PUs are allocated per Process Module point per scan
and up to 100 Process Module points can be scheduled
in a single quarter second cycle.

2_PU four PUs are allocated per Process Module point per scan
and up to 50 Process Module points can be scheduled in
a single quarter second cycle.

The number of Process Module points processed twice a second is restricted to a

maximum of 100 points.

ATTENTION
Both NIM and HPM must to be loaded with R682 for the scan to function. Any
configuration error with mismatch in personality can lead to system failure or
abnormal behavior.

R688 HPM High-Performance Process Manager Control Theory 533

08/2019 Honeywell
49 HPM Control Performance
49.4 Determining Processing and Memory Capacity

Memory unit capacity

HPMM capacity is measured in terms of Memory Units. For the point database and
sequence programs, the maximum capacity is 22,000 Memory Units (MU) allocated as
defined in the following table.
Table 49-3 Memory unit capacity

Slot Type Memory Units Per Point

Digital Composite 5

Logic 15

Process Module 15

Regulatory PV 12

Regulatory Control 13

String 1/8 (Note 1)

Sequence Programs 1

Numerics 1/16 (Note 1)

Numerics (w/PV Alarming) 1/4 (Note 1)

Flags 0

Device Control 30

Array 8

Times 3/32 (Note 1)

Timer 0
Note 1:
8 strings = 1 MU
16 Numerics = 1 MU
4 Numerics (w/PV Alarming) = 1 MU
32 Times = 3 MU

534 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 49 HPM Control Performance
49.4 Determining Processing and Memory Capacity

Memory unit constraints

Any mix of the slot types can be used, but the mix is subject to the following constraints
• Point mix used must not exceed 800 Processing Units or 22,000 Memory Units per
HPM.
• Absolute number of each slot type per HPM cannot exceed the maximum shown in
the following table (regardless of the available PUs).
Table 49-4 Memory unit constraints

Slot Type Maximum Number Comments

Digital Composite 999

Device Control 400

Process Module 250

Regulatory PV 400 With TPN R684

Regulatory Control 250

Logic 400

Array 500 80 external max.

Numeric 16,384 First 2047 can have tags

Numeric w/PV Alarming 2047 or NNUMERIC Whichever is less

String 16,384

Time 4096

Timer 64

Flag 16,384 2047 can have tags

Note: With TPN R684, the number of MUs consumed by the configured HPM
Regulatory PV point type increases with the increase in the value of NPVSLOT. HPM
needs these extra memory units to store the additional HPM Regulatory PV slots.

Processing and memory capacity examples

ATTENTION
Invalid configurations are displayed as errors when the information is being

R688 HPM High-Performance Process Manager Control Theory 535

08/2019 Honeywell
49 HPM Control Performance
49.4 Determining Processing and Memory Capacity

loaded into the HPM through the Universal Station or GUS.

Example 1
The following illustrates a possible configuration, showing the PU calculations.

Point Type Points Freq PUs/Slot Total PUs/Slot Type

Regulatory PV 100 1 sec 1 PU 100 X 1 = 100 PU
Process Module 200 1 sec 1 PU 200 X 1 = 200 PU
Logic 100 1 sec 1 PU 100 X 1 = 100 PU
Device Control 150 1 sec 1 PU 150 X 1 = 150 PU
Digital Composite 300 1 sec 0.1 PU 300 X .1 = 30 PU
Regulatory Control 150 1 sec 1 PU 150 X 1 = 150 PU
Total PUs for this HPM 730 PUs

Example 2
The following illustrates a possible configuration, showing the PU calculations.

Point Type Points Freq PUs/Slot Total PUs/Slot Type

Regulatory PV 40 1/2 sec 2 PU 40 X 2 = 80 PU
Process Module 100 1 sec 1 PU 100 X 1 = 100 PU
Logic 25 1/4 sec 4 PU 25 X 4 = 100 PU
Device Control 50 1/4 sec 4 PU 50 X 4 = 200 PU
Digital Composite 150 1/4 sec 0.4 PU 150 X .4 = 60 PU
Regulatory Control 80 1/2 sec 2 PU 80 X 2 = 160 PU
Total PUs for this HPM 700 PUs

536 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 49 HPM Control Performance
49.4 Determining Processing and Memory Capacity

Example 3
The following illustrates a possible configuration, showing the PU calculations.
Point Type Points Freq PUs/Slot Total PUs/Slot Type

Regulatory Control 100 1 sec 1 PU 100 X 1 = 100 PU

Fast Regulatory 50 1/4 sec 4 PU 50 X 4 = 200 PU

Control

Total PUs for Reg Ctrl points 250 PUs

Note: If you have 100 RegCtrl points and 50 Fast Reg Ctrl points, the total PUs for
Reg Ctrl points is 250. This is because the 50 Fast Reg Ctrl points is actually part of
the 100-Reg Ctrl points. Fast Regulatory Control points are processed four times a
second.

Process Module 200 1 sec 1 PU 200 X 1 = 200 PU

(SEQPROC =
1_PU)

Semi-fast Process 100 1/2 sec 2 PU 100 X 2 = 200 PU

Module

Total PUs for Process Module points 300 PUs

Total PUs for this HPM 550 PUs

Note: If you have 200 process module points and 100 semi-fast process module
points, the total PUs for process module points is 300. This is because the 100 semi-
fast process module points are actually part of the 200 process module points. Semi-
fast process modules points are processed twice a second.

R688 HPM High-Performance Process Manager Control Theory 537

08/2019 Honeywell
49 HPM Control Performance
49.5 Overrun Handling

49.5 Overrun Handling

Background
The HPM has the capability to handle most configurations of up to 800 PU without
encountering an overrun. Overruns occur when a specific task cannot be completed in the
allowed time. The following overruns are possible in the HPMM:
• Point Processing.
• I/O Link Access.
• UCN Access (Peer-to-Peer Communication).
Point processing overrun
A point processing overrun occurs when the slots that are scheduled to be processed
during any subcycle cannot be finished within the allocated time of 125 msec. When this
occurs, all the points are processed to completion (nothing is aborted), but the following
subcycle is delayed until the next 125 msec subcycle. Also, the current hour point
processing-overrun counter is incremented by 1.
One of the primary causes of point processing overruns is several long sequence
programs that are processing on the same subcycle. If a point processing overrun occurs
for four seconds in a row (on any subcycle within each second), a point
processingoverload soft failure is generated. The soft failure is reset when an overrun
does not occur for eight seconds.
For each subcycle, the current hour and previous hour point processing-overrun counters
are maintained in the HPMM and displayed on the UCN Detailed Status Displays to help
track down the cause of the overrun.
I/O link access overrun
This type of overrun occurs when parameter read or write access requests, from slots
residing in the HPMM to I/O Processors in the same HPM, are not completed within a
cycle time. This indicates that too many parameter access requests were attempted
through the I/O link within the last cycle (250 msec). When this occurs, point processing
is delayed by 125 msec and the I/O link overrun counter is incremented by 1. This
continues until the requested data becomes available.
The anticipated average number of I/O link accesses (from HPMM points within the
same HPM) is 120 parameters for each 250 msec cycle. Access overruns can be expected
when the number of I/O link accesses exceeds 200 parameters for each 250 msec cycle.

If an I/O link overrun occurs for four seconds in a row (on any cycle within each second),
an I/O link access-overload soft failure is generated. The soft failure is reset when an
overrun does not occur for eight seconds.
538 HPM High-Performance Process Manager Control Theory R688
Honeywell 08/2019
 49 HPM Control Performance
49.5 Overrun Handling

Although most IOL activity is periodic and can be accounted for, there are some
functions that are less predictable. These functions include event and alarm collection,
point configuration, checkpoint save/restore and synchronization of IOPs. IOL overruns
and blank displays may be experienced if any of these activities becomes excessive.
For each cycle, the current hour and previous hour I/O link access-overrun counters are
maintained in the HPMM and displayed on the UCN Detailed Status Displays to help
track down the cause of the overrun.
I/O link bandwidth considerations
The amount of I/O Link bandwidth available for I/O scanning per second is divided into
1000 units called Link Units (LUs). A Link Unit is roughly equivalent to one parameter
read or one parameter write per second.
.
Link unit calculations
AI, DO and DI PV connections, including point status and alarms, are scanned and
therefore not counted in the point processing section of the sheet.
Except for Serial Interface Modules, which are configurable, PV scan times are fixed at
1/4 second (except the LLMUX and RHMUX scan time is 1/2 second) and AOs are not
scanned. Digital Composite and Device Control Outputs only change when commanded.
The resulting DO connection load can be estimated from the maximum number of
commanded state changes per second.
Every parameter write from either a CL sequence or the UCN is followed by an
unpredictable number of write message status reads. This number depends on several
system variables. On the average, it has been observed to take approximately three LUs.

R688 HPM High-Performance Process Manager Control Theory 539

08/2019 Honeywell
49 HPM Control Performance
49.5 Overrun Handling

Table 49-5 HPM Link Unit Calculation Sheet

PV and Event Status Scan
I/O Module # IOPs LUs
AO, AO16, SI X 2 =
DI, DISOE, DI24V X 9 =
DO, DO32 X 7 =
LLAI, PI X 14 =
LLMUX, RHMUX X 20 =
HLAI, SDI, STI X 22 =
Each secondary IOP* X 2 =
Subtotal
Point Processing & SI Scan
Type # Pts. LUs
CL prefetches X 1 =
CL poststores X 4 =
AO connections (.25s) X 8 =
AO connections (.5s) X 4 =
AO connections (1s) X 2 =
DO connections (.25s) X 4 =
DO connections (.5s) X 2 =
DO connections (1s) X 1 =
SI Array Point Scan (.25s) X 16 =
SI Array Point Scan (.5s) X 8 =
SI Array Point Scan (1s) X 4 =
SI Array Element Write (.25s) X 4 =
SI Array Element Write (.5s) X 2 =
SI Array Element Write (1s) X 1 =
Subtotal
UCN Parameter Access
Type # Pts. LUs
Read (.5s) X 2 =
Read (1s) X 1 =
Write (.25s) X 16 =
Write (.5s) X 8 =
Write (1s) X 4 =
Subtotal
Total = LUs
*Redundant IOP Max = 1000 LUs

540 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 49 HPM Control Performance
49.5 Overrun Handling

TIP
To prevent I/O Link overruns, the total LUs consumed per second should not
exceed 1000.

HPM link unit monitoring

Page 2 of the HPM Local UCN Statistics display provides a convenient way to check I/O
Link Unit usage. The statistic I/O LINK BANDWIDTH FREE displays the percent free
(of the 1000 LUs available). This display is illustrated in the High Performance Process
Manager Service manual along with some suggestions on correcting Link Unit overruns.
Also, I/O Link overrun counts are displayed for each 1/4-second cycle on the HPM
Scheduling Display.
UCN access overrun
This type of overrun occurs when parameter read or write access requests to other HPMs
(or other nodes) on the same UCN are not completed within the given time (0.75
seconds).
When this type of access overrun occurs, the UCN access-overrun counter is incremented
by 1, but point processing is not delayed. The sequence programs that access data from
other UCN devices remain suspended until a response becomes available (or a
communication time-out occurs). For input connections at RegPV, RegCtl, and logic
slots that require data from the UCN, the last fetched value is used until new data
becomes available, or a time-out occurs.
If the UCN access overrun occurs for 8 seconds in a row (on any cycle within each
second), a UCN access-overload soft failure is generated. The soft failure is reset when
an overrun does not occur for 16 seconds.
For each subcycle, the current hour and previous hour UCN access-overrun counters are
maintained in the HPMM and appear on the UCN Detailed Status Displays to help track
down the cause of the overrun.
Peer-to-peer UCN overruns and soft failures
Two consecutive peer-to-peer time-outs are required to count as a UCN overrun. More
than one UCN overrun in 8 consecutive seconds causes a soft failure. The soft failure
automatically clears when 16 consecutive seconds do not contain any UCN overruns.
The following figure illustrates the HPM Scheduling Display. This display can be
accessed through the HPM Status Display/Detail Display target; then under CONTROL
CONFIGURATION, choose SCHEDULE INFO.

R688 HPM High-Performance Process Manager Control Theory 541

08/2019 Honeywell
49 HPM Control Performance
49.5 Overrun Handling

TIP
Check this display for overruns, especially if your process module points
contain a large number of statements per step (as long as all of the
sequences in a subcycle average out to 20 statements per step, no overruns
will occur).

When onserving this display, note that:

• Along the left side, the type of point and execution order appears.
• The four 1/4 second cycles and their subcycles divide the display into columns.
• The numbers in each column represent the point slots.
• All of the points in a subcycle run consecutively in descending order (compare to the
drawing in 3.1.2.3).
• Overruns (if any) for the point processing executive (PPX) and the I/O Link (IOL)
appear across the bottom for the cycle or subcycle affected.
Figure 49-1 Display for Peer to Peer UCN overruns and soft failures

542 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 49 HPM Control Performance
49.6 Performance Monitoring

49.6 Performance Monitoring

The Toolkit displays are available to check various performance statistics. These displays
show the number of nodes requesting and responding, and the percent of time the HPM
Communications and Controller CPUs are not busy. They also show the maximum,
minimum, and average request/response times for transactions between peer nodes and
other statistics. Section 10 of the Engineer’s Reference Manual explains how to use the
Toolkit displays.
A peer-to-peer communication efficiency statistic is displayed on the Control
Configuration page of the HPM Detail Display. Also refer to the HPM Implementation
Guidelines for other performance information.

49.7 UCN Device Resource Utilization Display

With R680, the number of available/consumed PUs, MUs and IOL bandwidth can be
viewed through the UCN Device Resource Utilization display. The display can be
accessed through the target UCNDEVUT in the PERFMENU or CONTROL CONFIG in
the Control Configuration Display of xPM.
The schematic displays the following resource utilization statistics for each slot type:
• Total number of PUs, MUs and IOL bandwidth consumed by the HPM node.
• Maximum number of PUs, MUs and IOL bandwidth available for a HPM node.
• Number of free units in PUs, MUs and IOL bandwidth for a HPM node.
• % loaded.
The free units in PUs, MUs and IOL bandwidth are indicated in different colors as
follows:
• If the free unit is greater than 30%, the value is backlit in green.
• If the free unit is between 20% and 30%, the value is backlit in yellow.
• If the free unit is less than 20%, the value is backlit in red.
In addition to the Resource Utilization statistics, the schematic displays the following:
• Link to IOPMDATA, control configuration, and the schedule information schematic
for the selected HPM node.
• Number of points configured per slot type.
• Point mix of the selected HPM node.
• Available PUs, MUs and IOL bandwidth.

R688 HPM High-Performance Process Manager Control Theory 543

08/2019 Honeywell
49 HPM Control Performance
49.7 UCN Device Resource Utilization Display

Section 21 of the Process Operations Manual explains how to view the UCN Device
Resource Utilization Display. Section 10 of the Engineer’s Reference Manual explains
the details of the displays.

544 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 50. Database Considerations
50.1 Background
Point mix and scan rate
The point mix and the scan rate are configured as a part of the HPM Box Data Point. The
term Point Mix refers to the number of points and box variables. The Scan Rate
parameter specifies the Regulatory/Logic scan cycle. The box data point is accessed from
the Node Specific Configuration display.
Changing the point mix and scan rate
The HPMM box state must be IDLE in order to load changes to the point mix or scan
rate.
When changes are made to the point mix or scan rate in the HPMM, points that exist in
both the old and new point mixes are preserved. Therefore, changes can be made to the
point mix or scan rate without defaulting the currently loaded point database.

To prevent the accidental removal of points in the HPM, all configured

CAUTION points (system entities) that are being removed due to a reduction in
the point mix must be deleted. This action will ensure that the points
(and tagnames) are removed from the NIMs as well.
Untagged box numerics used by points or CL programs could be
inadvertently deleted by reducing the number of box numerics.

Careful consideration must be taken before reducing the number of slots of any type in an
HPM with points built or tagged from multiple remote NIMs. Because the point database
is distributed between the HPM and the NIM and because the tagname resides in the
NIM portion of the database, if the user fails to delete a configured point that is being
removed before reducing the point mix, the tagname will remain on the remote NIM(s).
At this time, an attempt to delete the point or access its point detail display will fail
because the HPM and NIM databases are no longer synchronized. In this situation, in
order to delete any such point(s), first change the NIM load scope parameter
(LOADSCOP) to NIMONLY, then delete the point(s), and then reset the NIM load scope
to its previous state.

R688 HPM High-Performance Process Manager Control Theory 545

08/2019 Honeywell
50 Database Considerations
50.1 Background

Backup and Restore box parameters

With TPN R682, you can take a backup of the box parameters to a file and later use the
file for restoring the values. The backup and restore option is available in xPM and is
also applicable for HPM simulator box parameters.
The backup and restore option is available for the following box parameter type:
• STRINGS
• NUMERICS
• FLAGS
• TIMES
You can take a backup or restore for box parameters through DEB and DEBEC. In DEB
you can perform a backup or restore operation using the BOX PARAM BACKUP RSTR
target. In DEBEC you can use the command “BPB” and “BPR” for backup and restore
operations respectively.
xPM must be in run state (IDLE, OK) to perform backup/restore. Multiple users can
save backups in different locations. You can take a backup of the same parameter from
different workstations at the same time. Similar to other DEB functionalities, file
manager errors are reported, if the same file is selected by more than one user at the same
time.

REFERENCE - INTERNAL
Refer to the Data Entity Builder Manual for information on how to backup and
restore box parameters.

546 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 50 Database Considerations
50.1 Background

Loading Box data point configurations

When you attempt to load the HPM Box Data Point configuration to the HPMM, the
point mix/scan rate combination is validated versus the criteria listed below. If any of
these criteria are not met, the Box Data Point is not loaded to the HPM and an
appropriate error message is displayed at the Universal Station or GUS. Also note these
considerations:
• The requested number of points of a given type cannot exceed the maximum number
of points allowable for that point type (refer to Determining Processing and Memory
Capacity).
• The number of MU's required by the new point mix and any currently loaded CL
programs cannot exceed the HPMM's user database maximum size (refer to
Determining Processing and Memory Capacity).
• The total number of PU's required by the point mix/scan rate combination cannot
exceed the HPMM's maximum processing capacity (refer to Determining Processing
and Memory Capacity).
• Tagnames cannot exist in the local NIM database. Any currently configured points
(slots with tagnames) cannot be removed by a reduction in the point mix (unless the
tagname resides on a remote NIM only). Before reducing the number of slots of any
type, first delete all points in the slot range being eliminated.
• Regulatory Control, Regulatory PV, Device Control, Digital Composite or Logic
points that are being removed due to a reduction in the number of points of that type
must have a point execution state (PTEXECST) of INACTIVE. Note that the point
execution state parameter is set to the default value of INACTIVE if the point was
properly deleted from the system.
• Process Module points that are being removed due to a reduction in the number of
points must not have currently loaded CL programs (SEQEXEC should = NL). Note
that a loaded CL program is automatically removed by first deleting the Process
Module point from the system.

R688 HPM High-Performance Process Manager Control Theory 547

08/2019 Honeywell
50 Database Considerations
50.1 Background

• Box variables that are removed due to a reduction in the number of box variables
cannot be mapped into any existing Array point that will remain in the new point mix.

TIP
If changes are not required in the point mix, the HPM Box Data Point can be
loaded while in the RUN state. For example, a new I/O Processor can be
added without interrupting control by simply loading the HPM box data
configuration (with the new I/O Processor added) while in the RUN state).

Point building relationship to box configuration

Point building follows box Configuration. Each point is configured to run in a slot inside
the HPMM. The first time through a power-up cycle (HPMM box state transition from
ALIVE to IDLE), the database of each slot (included in the default point mix) is
defaulted to a null configuration. You can build or load a point configuration into each
slot. When a point is deleted, the database of the slot containing the point is defaulted to
the null configuration.

548 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 51. Point Execution State
51.1 Background
Slot processing in the HPMM is performed only when the HPMM box state is RUN.
Only those slots whose point execution state (PTEXECST) is Active are processed. The
point's execution state must be Inactive in order to modify any of the configuration
parameters (for example, engineering unit range, PV or control algorithm ID,
input/output connections, and so on). When a point is made Inactive, all the calculated
variables (like PV, CV, alarms, and so on) are set to their default values ("NaN" for real
numbers and OFF for Logical). The point execution state cannot be changed back to
Active until all the configuration parameters are specified.

51.2 Run-Idle-Run Transition

The following table defines the effect on data points when the HPMM is switched from
RUN to IDLE and back to RUN.

Data Points Effect of RUN

Logic Blocks Execution halts, then resumes once box is running again.

CL Programs Execution stops. Program needs to be restarted once PM is

running again. Refer to parameter RSTROPT.

Timers The timer stops and needs to be restarted once the box is
running. Time accumulation starts from where it left off unless
reset deliberately.

Other Point Types Processing stops and outputs are held. Processing resumes
when the HPM is running again.

R688 HPM High-Performance Process Manager Control Theory 549

08/2019 Honeywell
51 Point Execution State
51.3 Warm/Cold Restart

51.3 Warm/Cold Restart

Starting an HPM
The HPM is started through the HPM Status display. Warm/Cold startup refers to the
behavior of algorithms under initialization. When going from the idle to run state, the
operator can choose between warm and cold startup (for each HPM). After a checkpoint
restore, either a warm or cold startup is possible.
Cold startup
Usually requires operator intervention, that is, the operator must change some point states
from manual to their normal operating mode. On a cold startup, all Regulatory Control
points that output to the field go to manual mode. For Regulatory Control points that
drive other Regulatory Control points (even in another HPM), a cold start does not cause
a change from the previous mode.
Warm startup
If you choose warm startup, Regulatory Control points remain in the previous mode and
are back-initialized for a bumpless transfer to automatic control with their previous
output value.
Power-up Restart
If RAM memory was not lost since the previous operation, a power-up restart is possible
without reloading the program. In this case, the HPM will return to its previous Idle/Run
state. If the state is Run, all points behave as if a cold restart was performed.
Point behavior during startup
Some points behave differently during startup regardless of the startup mode:
Regulatory PV Totalizer points—you can configure the point to continue or stop
accumulation on restart (see parameter PVEQN).
Process Module point—you can configure sequence execution to restart from the
beginning or remain off and be restarted by the operator (see parameter RSTROPT).
Regulatory Control Ramp Soak—Point is always set to Manual mode.

550 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 51 Point Execution State
51.3 Warm/Cold Restart

Status conditions
The following table summarizes the important status conditions for Warm/Cold restart
functions.

Point Type Parameter Status After...

Power Off/On Cold Start Warm Start
Regulatory Control MODE Manual Manual Last Mode
(except Ramp/Soak) (Back-
Outputs to IOP initializes; goes
on control)
Regulatory Control MODE Manual Last Mode1 Last Mode.
(except Ramp/Soak) (Back-
Outputs to another initializes; goes
RegCtl point on control)
Regulatory Control MODE Manual Manual Manual
Ramp Soak
Regulatory PV PV Cont. NaN Cont.
Totalizer2 Totalizing Totalizing
PVEQN = A, B, C PVSTS Uncertn Bad Uncertn
STATE Running Stopped Running
Regulatory PV PVSTS Bad Bad Bad
Totalizer
STATE Stopped Stopped Stopped
PVEQN = D, E, F
Process Module SEQEXEC Run Run Run
RSTROPT = Restart
PROCMOD Norm Norm Norm
Process Module SEQEXEC Loaded Loaded Loaded
RSTROPT = Off
PROCMOD Off Off Off
Timer PV Last Good Last Good Last Good
Value3 Value3 Value3
STATE Stopped Stopped Stopped
1) Control is halted by the final point in then cascade which always outputs to an IOP.
2) Count may be inaccurate if rollover occurs in IOP.
3) The last good value can come from HPM RAM memory if battery power is continuously
available; otherwise, from the last checkpoint stored on the History Module.

R688 HPM High-Performance Process Manager Control Theory 551

08/2019 Honeywell
51 Point Execution State
51.3 Warm/Cold Restart

552 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 52. Peer-to-Peer Communication
52.1 Background
Peer-to-peer communication allows information to be passed between devices on the
UCN and can be initiated from the High-Performance Process Manager, the Advanced
Process Manager, the Process Manager, the Logic Manager, or the Safety Manager.

52.2 Implementation
Mechanisms for implementation
The HPM provides the following two convenient mechanisms for implementing peer-to-
peer communications functions:
• Input Connections.
• Output Connections.
• CL Read/Write Statement.
Both communication mechanisms offer location-independent access to data from another
UCN device using the "Tagname.Parameter" notation.
Refer to for a summary of peer-to-peer communications.
Input connections
The RegPV, RegCtl, DevCtl, and Logic slots can use standard input connections to
obtain data from other UCN devices. When such a connection is configured, it is scanned
at the rate of twice per second, regardless of the scan rate of the slot in which it is
configured. The data obtained is saved internally and used (more than once if the slot is
running faster than twice a second) until the next time that it needs data. Peer-to-peer
data is requested .75 seconds before it is needed. The data obtained from another UCN
device can therefore be up to .75 second old by the time it is used. A maximum of 100
input connections can be configured for each HPMM.

TIP
We recommend that input connections be used for continuous peer access
that requires a 1/2 second update (see “Run-Idle-Run Transition” in
Section 51.2).

Output connections
The RegCtl, DevCtl, and Logic slots can use standard output connections to provide
outputs to other UCN devices. Output connections are processed when the slot is
processed, thus outputs are updated four times per second, two times per second, or once

R688 HPM High-Performance Process Manager Control Theory 553

08/2019 Honeywell
52 Peer-to-Peer Communication
52.2 Implementation

per second depending on the point processing rate. The number of output connections per
HPMM is not limited.

TIP
We recommend that output connections be used for regulatory-control
cascades between UCN devices (see “Run-Idle-Run Transition” in
Section 51.2).

Table 52-1 Peer-to-peer implementation summary

Peer-to-Peer Configuration Limits Handling of Failure/Recovery Recommended

Mechanism (Per HPM) of Peer Node

Input 100 distinct Analog Use for continuous

Connections parameters used by On failure, bad value (NaN) is (1/2 second) update
points, not including substituted. of data required for
CL Read. RegPV, RegCtl,
Digital DevCTL, or Logic
Slots.
Addressed by Logic Slot. On
failure, ON, OFF, or last value is
substituted based on user
configuration. On recovery from
failure, accessed values are
then used.

Output Not limited Regulatory Control Cascade Use for regulatory

Connections Primary initializes. control cascades
between nodes.
Logic Output
Store does not occur. On
recovery from failure,
regulatory control clears
initialization and resumes
control. Subsequent output
changes are stored on
transition.

554 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 52 Peer-to-Peer Communication
52.3 Restrictions

Peer-to-Peer Configuration Limits Handling of Failure/Recovery Recommended

Mechanism (Per HPM) of Peer Node

CL Read 16 values per Process If requested read transaction Use for on-demand
Statement Module Data Point not completed, CL program data required by CL
per second branches to specified error programs. Use for
location. Program fails when continuous (1
error option not used. On second) update of
failure recovery, program data required for
behavior is based on user RegPV, RegCtl,
code, or requires operator DevCTL, or Logic
interaction if failed. Slots.

CL Write 16 values per Process Same as above. Same as above.

Statement Module Data Point (Use of Read or
per second Write statements is
based on user
preference)

CL/HPM configuration limits

Characteristics and configuration limits for CL/HPM read/write peer access are as
follows:
• A user-written CL/HPM sequence program executing in the HPMM can use explicit
read/write statements to read parameter values from other UCN devices and write
parameter values to other UCN devices.
• Any time a read/write statement is executed, the sequence program is suspended
until the following cycle when the response becomes available (normally one
second).

TIP
We recommend that the CL read/write technique be used for on-demand
peer access, and for continuous peer access that requires a 1-second
update.

52.3 Restrictions
Point type restrictions
Certain restrictions exist on the type of data that can be accessed through peer-to-peer
communication. These restrictions vary with the point type. The following table defines
the type of data that can be accessed for each point type or connection type.

R688 HPM High-Performance Process Manager Control Theory 555

08/2019 Honeywell
52 Peer-to-Peer Communication
52.3 Restrictions

Connection Type Allowed Data

RegCtl.CISRC No restrictions

RegCtl.CODSTN RegCtl.SP and RegCtl.X1

RegPV.PISRC No restrictions

Logic.LISRC No restrictions

Logic.LODSTN No restrictions

DevCTL.LISRC No restrictions

DevCTL.LODSTN No restrictions

DigComp No Peer-to-peer connections allowed

DevCtl No Peer-to-peer connections allowed

ProcModl Read Statement No restrictions

ProcModl Write Statement No restrictions

556 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 52 Peer-to-Peer Communication
52.3 Restrictions

Performance related limits

In addition to the configuration constraints, there are performance-related limits on
parameter access that affect the overall peer-to-peer throughput capability. Actual
performance for each HPM varies depending on specific system configuration; however,
any HPM should be capable of handling a total load of up to 1000 parameters per second.
In addition to parameter throughput-related constraint, the number of devices
concurrently communicating to a single High-Performance Process Manager is another
factor that influences performance.
The interaction of the above constraints must be considered primarily in applications in
which an extreme communication load is continuous. In this type of application, the
following configuration recommendations maximize peer-to-peer throughput capability.

TIP
Adopt a single approach for all peer-peer communications; use either
input/output connections or CL read/write statements. If a 1-second update is
adequate and cascade interconnection is not required, the CL read/write
approach offers increased capability (quantity/throughput) for peer data
access.
For CL read/write approach:
• consistently use same method (either CL reads or CL writes).
• the Process Module Data Points that are continually affecting peer-to-
peer communication should be grouped on the same 1/4-second cycle.

R688 HPM High-Performance Process Manager Control Theory 557

08/2019 Honeywell
52 Peer-to-Peer Communication
52.3 Restrictions

558 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 53. Hardware References
53.1 Hardware Reference Addressing
Referencing I/O point parameters
The HPM allows the referencing of parameters of I/O points (AO, DI, DO) on a
hardware basis within the same HPM using the standard input/output hardware
connection reference syntax (user-written sequence programs can reference DI points).
This type of addressing does not affect the point count in the NIM and these “untagged”
references can be quickly built, but there are several disadvantages. Untagged points are
not easily visible in the system so you must use the Command Processor Find Names
function to see the connections. Note that operating displays cannot include untagged
points.
Untagged references
The use of untagged references is not recommended, however, I there might be a reason
to use them or some may be present in an existing system. If you use them keep good
records.
Hardware reference address format
The hardware reference address point format is
!MTmmSss.Parameter
Where:
• MT is the IOP type such as AO, DI, DO, or PI.
• mm is the number of the IOP card (1-40) in the card file.
• ss is the input or output slot number on the specified IOP card.
• Parameter is the parameter whose value is to be written to by an output connection,
or a parameter whose value is to be read by an input connection.

TIP
Standard status displays are available to show which points are associated
with each hardware module.

The following are examples of hardware reference addresses:

Hardware Address Example

AO Processor Output !AO12S03.OP

R688 HPM High-Performance Process Manager Control Theory 559

08/2019 Honeywell
53 Hardware References
53.1 Hardware Reference Addressing

Hardware Address Example

OP parameter

of Slot #3

of AO Processor #12

DI Processor PV !DI05S07.PVFL

PVFL parameter

of Slot #7

of DI Processor #5

DO Processor Output !DO15S12.SO

(Status or Latched) SO parameter

of Slot #12

of DO Processor #15

DO Processor ON Pulse Command IDO15S12.SO

ONPULSE parameter

of Slot #12

of DO Processor #15

DO Processor OFF Pulse Command !DO15S12.OFFPULSE

OFFPULSE parameter

of Slot #12

of DO Processor #15

560 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 53 Hardware References
53.1 Hardware Reference Addressing

ATTENTION
The AI address !AimmSss.Parameter is not supported because the analog
input point does not have a useable default database.

Find Names function

You can use the Find Names function to provide the node number, module type, point
type, and slot number for all connections. This function is especially helpful to find the
hardware reference points. Refer to the Command Processor manual for information on
the Find Names utility.

R688 HPM High-Performance Process Manager Control Theory 561

08/2019 Honeywell
53 Hardware References
53.1 Hardware Reference Addressing

562 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 54. Redundancy
54.1 Background
The HPM can contain optional redundant HPMM modules and certain types of optional
redundant IOP modules (currently HLAI, STIM, AO, DI, DISOE, and DO modules).
During HPM Node Specific configuration, the user specifies which modules are
redundant and, for IOPs, the file/card locations of the redundant partners. Refer to "HPM
Operational Considerations" in the High-Performance Process Manager Implementation
Guidelines manual for more information.

REFERENCE - INTERNAL
Refer to "HPM Operational Considerations" in the High-Performance Process
Manager Implementation Guidelines manual for more information.

54.2 IOP Module Switchover

If a redundant HPMM module or synchronized redundant IOP module fails, switchover
is automatic and transparent to the user (input and set output operations are unaffected).
Data acquisition, alarming, and control strategies are automatically managed by the
system.

54.3 HPM Redundancy Parameters

The principal parameters that pertain to HPM redundancy are:

• ACTPRIM • IOMFILEA/B • POSITION

• FTACONN • IOREDOPT • SYNCHSTS

• IOMCARDA/B • PKGOPT • WITHBIAS

REFERENCE - INTERNAL
Refer to these parameters in the PM Family Parameter Reference Dictionary
for additional information.

R688 HPM High-Performance Process Manager Control Theory 563

08/2019 Honeywell
54 Redundancy
54.3 HPM Redundancy Parameters

564 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 55. Point Reservation
55.1 Background
To support batch applications, you need to be able to reserve certain points that represent
shared devices for particular batches. The HPM allows CL programs to reserve
Regulatory Control, Regulatory PV, Logic, Digital Composite, Device Control, Process
Module, and Array points for exclusive use.

55.2 Establishing Point Reservation

Point reservation is accomplished using a 16-character string parameter (USERID). This
string has special logic so that two programs cannot reserve the same point at the same
time. This string can always be stored by the operator, but a program can only store a
nonblank string when the USERID itself is currently blank. This should eliminate race
conditions.
To keep programs from failing, storing an invalid string does not generate an error; it will
just not do anything. The program should read the string back after the store to verify that
it was accepted. To handle retries, a given value of the string can be stored any number of
times. All blanks can be stored at any time to release the point. Programs must be careful
not to release points that other programs or the operator have reserved. A special string
starting with three or more dashes may be used to indicate that a point cannot be reserved
and only the operator can clear this string.

R688 HPM High-Performance Process Manager Control Theory 565

08/2019 Honeywell
55 Point Reservation
55.2 Establishing Point Reservation

566 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 56. Status Messages
56.1 Availability
The Status Message function is available for RegCtl, RegPV, Logic, DigComp, DevCtl,
ProcMod, and Array points. One table of messages is configurable for each NIM.

56.2 Configuration
During UCN Node Configuration for the NIM, you can enter up to 15 Message Text
Items, (MSGTXT(n)). The entry is an 8-character ASCII string. Message text item 0
defaults to NONE and is not configurable. The actual number of Message Text items that
you can enter is determined by parameter NMSGTXT, the number of Message Text
items.

56.3 Operator Interaction

On the point’s Detail display, the operator can select STSMSG and choose any message
from the table of Message Text items that appears. That Message Text item then replaces
the current contents of STSMSG and, if nothing of higher priority is currently displayed,
appears as a comment at the lower left of the display. The Status Message also appears in
place of the “Red Tag” message when Red Tag is on.

56.4 CL Interaction
If a point is not in Red Tag, a CL program can store a message (in STSMSG). When Red
Tag is on, only the engineer or supervisor can store the message.

R688 HPM High-Performance Process Manager Control Theory 567

08/2019 Honeywell
56 Status Messages
56.4 CL Interaction

568 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 57. Mode and Mode Attribute Selection List
57.1 Background
This R630 function allows an engineer to remove the MODE/MODATTR selections
from the operator’s standard-display MODE selection lists. This prevents the data point
from being placed in the wrong mode and from having the wrong mode attribute
assigned. This function is implemented using the $MODESEL parameter.

57.2 Configuration
This function is implemented by the user configuring a mode selection list using the
$MODESEL parameter to determine the applicable modes and mode attribute. During
normal operation, the mode selection list is displayed on the standard displays (Detail,
Group, Standard Change Zone, Enhanced Change Zone, GUS Faceplate, GUS Group,
and GUS Change Zone) when the mode is selected.
However, changes to the control mode parameters using AM/CL and custom schematics
remain unaffected.
The $MODESEL parameter can be modified from a custom schematic with Engineer key
level access or from AM/CL.
Any change made to the $MODESEL parameter affects the value of MODEAPPL, that
is, if $MODESEL is configured to disallow the AUTO mode, then the corresponding
boolean in the MODEAPPL parameter will be reset to FALSE. The mode attribute entry
(PROG) in the mode selection list can be disallowed by setting $MODESEL(5) to
FALSE.

R688 HPM High-Performance Process Manager Control Theory 569

08/2019 Honeywell
57 Mode and Mode Attribute Selection List
57.2 Configuration

The allowable modes and mode attribute that can apply to an HPM point are dependent
on the point types as shown in the tables below. Any of these modes can be configured so
that the mode is not shown on the mode selection list.

Analog Digital Device

Output Composite Control
Allowable Modes/Mode Attribute
Man Man Man
Cas Prog Prog
Prog

Regulatory Control
Control Algorithms
Null Rampsoak AutoMan PID
IncrSum PIDErFb
MulDiv PIDFF
OrSel PIDPosPr
Summer PosProp
Switch RatioCtl
Allowable Modes/Mode Attribute
Man Man Man Man
Prog Auto Cas Auto
Prog Bcas Cas
Prog Bcas
Prog

570 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
 57 Mode and Mode Attribute Selection List
57.2 Configuration

ATTENTION
The PROG mode attribute is not applicable to Control Module (CM) points.

By default, all the modes and mode attributes applicable for a point are allowed in the
mode selection list.

ATTENTION
The MAN, AUTO, and NORM keys on the operator keyboard do not function
if the desired mode change (MAN or AUTO or the value contained in
NMODE) has been disallowed from the mode selection list.

ATTENTION
If parameter EXTSWOPT (External Mode Switching Option) is enabled, its
restrictive qualities will take precedence over $MODESEL.

R688 HPM High-Performance Process Manager Control Theory 571

08/2019 Honeywell
57 Mode and Mode Attribute Selection List
57.2 Configuration

572 HPM High-Performance Process Manager Control Theory R688

Honeywell 08/2019
Honeywell Process Solutions
1860 W. Rose Garden Lane
Phoenix, AZ 85027 USA