CBP1 PDF

RS3t
ControlBlock
Configuration
Manual
Performance Series 1, Release 4.0
Sept 1999
U.S. Manual PN: 1984-2646-2100
A-4 Size Manual PN: 1984-2646-2111
1984-2646-5007
1984-2646-5017
EFisher-Rosemount Systems, Inc., 1987--1999.
All rights reserved.
Printed in the U.S.A.
Components of the RS3 distributed process control system may be protected by U.S. patent Nos. 4,243,931; 4,370,257; 4,581,734. Other
Patents Pending.
RS3 is a mark of one or more of the Fisher-Rosemount group of companies. All other marks are property of their respective owners. The
contents of this publication are presented for informational purposes only, and while every effort has been made to ensure their accuracy,
they are not to be construed as warranties or guarantees, express or implied, regarding the products or services described herein or their
use or applicability. We reserve the right to modify or improve the designs or specifications of such products without notice.
Fisher-Rosemount Systems, Inc.

12000 Portland Avenue South
Burnsville, Minnesota 55337 U.S.A.
Telephone: (612) 895-2000

TWX/Telex: 192177
FAX: (612) 895-2044
Comment Form
RS3t Manuals
ControlBlock Configuration Manual 1984-2646-21x0
Please give us your feedback to help improve this manual.

Never Rarely Sometimes Usually Always
1. Do you actually use this manual when
you are:
D configuring ______ ______ ______ ______ ______
D making changes or enhancements ______ ______ ______ ______ ______
D operating the system ______ ______ ______ ______ ______
D troubleshooting ______ ______ ______ ______ ______
D other __________________________ ______ ______ ______ ______ ______
2. Does this manual answer your questions? ______ ______ ______ ______ ______
3. What could be changed in this manual to make it more useful?
Errors and Problems: Please note errors or problems in this manual, including chapter and page number,
if applicable; or send a marked-up copy of the affected page(s).
May we contact you about your comments? j Yes j No
Name ______________________________________________
Company ______________________________________________
Phone ______________________________________________
Date ______________________________________________
Fisher-Rosemount FAX #: (612) 895-2044 Thank you!
Name
Place
Company stamp
here
Address
Fisher-Rosemount Systems, Inc.

RS3 User Documentation
Mail Station G30
12000 Portland Avenue South
Burnsville, MN 55337
U.S.A.
Seal with tape.

CB: v
RS3t
ControlBlock Configuration Manual
About This Manual
D Chapter 1 Describes ControlBlocks, Inputs and Outputs, and

Block Directory and Block Status screens
D Chapter 2 Continuous Faceplate configuration, PID functions,
and Continuous and Discrete functions
D Chapter 3 Block links and their associated RS3 screens
D Chapter 4 Continuous Diagram screen
D Chapter 5 Configuring Discrete Faceplates
D Chapter 6 RS3 logic, logic steps, and Discrete Diagram
screen
D Chapter 7 RS3 System and User flags, Console flags, and
status bits
D Chapter 8 Autotuning
D Chapter 9 Data compression
Changes for This Release
D Updated document frontmatter.

D Chapter 7: Changes to the valid data flag. Redundant controller
switch causes the valid data flag to reset for one scan.
D Chapter 7: Added section on testing the rise and fall of an
individual flag.
RS3: ControlBlock Configuration Manual About This Manual

CB: vi
Revision Level for This Manual
For This Refer to This Document:

Software
Version: Title Date Part Number
P1R4.0 ControlBlock Configuration Manual
P1R1.0 ControlBlock Configuration Manual Sept 1999 1984-2646-21x0
18R2 ControlBlock Configuration Manual August 1994 1984-2646-18x1
18R1 ControlBlock Configuration Manual October 1993 1984-2646-18x1
17 ControlBlock Configuration Manual August 1992 1984-2646-17x1
16 ControlBlock Configuration Manual January 1992 1984-2646-16x1
15 ControlBlock Configuration Manual January 1991 1984-2646-15x1
References to Other Manuals
References to other RS3 user manuals list the manual, chapter, and
sometimes the section as shown below.
Sample Entries:
For ..., see CC: 3. For ..., see CC: 1-1.
Manual Title Chapter Manual Title Chapter-Section
Abbreviations of Manual Titles

AL = Alarm Messages
BA= ABC Batch
CB= ControlBlock Configuration
CC= Console Configuration
DT = Disk and Tape Functions
IO = I/O Block Configuration
OP= Operator’s Guide
OV= System Overview and Glossary
PW= PeerWay Interfaces
RB= Rosemount Basic Language
RI = RNI Release Notes and Installation Guide
RP = RNI Programmer’s Reference Manual
SP = Site Preparation and Installation
SV = Service

CB: vii
Reference Documents
Prerequisite Documents
You should be familiar with the information in the following documents

before using this manual:
Related Documents
System Overview Manual and Glossary 1984-2640-21x0
Software Release Notes, Performance Series 1 1984-2818-0110
Software Loading and Upgrade Procedure,
Including Batch 1984-2818-0210
You may find the following documents helpful when using this manual:
ABC Batch Quick Reference Guide 1984-2818-1103
ABC Batch Software Manual 1984-2654-21x0
Alarm Messages Manual 1984-2657-19x1
Configuration Quick Reference Guide 1984-2812-0808
Console Configuration Manual 1984-2643-21x0
ControlBlock Configuration Manual 1984-2646-21x0
Disk and Tape Functions Manual 1984-2644-21x0
I/O Block Configuration Manual 1984-2645-21x0
Operator’s Guide 1984-2647-19x1
PeerWay Interfaces Manual 1984-2650-21x0
Rosemount Basic Language Manual 1984-2653-21x0
RNI Programmer’s Reference Manual 1984-3356-02x1
RNI Release Notes and Installation Guide 1984-3357-02x1
Service Manual, Volume 1 1984-2648-21x0
Service Manual, Volume 2 1984-2648-31x0
Site Preparation and Installation Manual 1984-2642-21x0
Software Discrepancies for Performance Series 1 1984-2818-0311
User Manual Master Index 1984-2641-21x0

Contents
Chapter 1: Introduction to ControlBlocks
Section 1: What is a ControlBlock? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-1

Role of a ControlBlock in a Typical Control Loop . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-2
How ControlBlocks Relate to I/O Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-2
How Values are Scaled in a Control Loop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-3
Internal Scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-3
Display Scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-3
ControlBlock Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-4
ControlBlock Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-5
Configuring the Major Function of a ControlBlock . . . . . . . . . . . . . . . . . . . . . . . 1-1-6
ControlBlock Configuration Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-8
Moving Within a ControlBlock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-9
Moving Between ControlBlocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-10
How to Use Access Arrows on ControlBlock Configuration Screens . . . . . . . 1-1-12
Section 2: Types of ControlBlock Inputs and Outputs . . . . . . . . . . . . . . . . . 1-2-1

ControlBlock Inputs and Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2-1
ControlBlock Discrete Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2-3
ControlBlock Discrete Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2-4
ControlBlock Continuous Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2-5
ControlBlock Continuous Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2-6
Section 3: Block Directory and Block Status Screens . . . . . . . . . . . . . . . . . 1-3-1

Viewing Information About Configured Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3-2
Viewing the Block Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3-4
Section 4: Hints for Configuring ControlBlocks . . . . . . . . . . . . . . . . . . . . . . . 1-4-1

Configuration Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4-1
Configuration Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4-2
Chapter 2: Configuring ControlBlock Functions
Section 1: Configuring Common Fields on the Continuous Faceplate . . 2-1-1

Calling Up a Continuous Faceplate Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1-3
Configuring a Continuous Faceplate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1-5
Effect of Block Mode on the Block Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1-9
RS3: ControlBlock Configuration Manual Contents

CB: x
Common Fields on the Continuous Faceplate Screen . . . . . . . . . . . . . . . . . . . . . . 2-1-10
Section 2: Configuring PID Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-1

PID Controller Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-1
PID Control Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-2
Proportional Term . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-5
Integral Term . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-6
Derivative Term . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-8
Feedforward . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-10
Velocity Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-11
Configuring PID Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-13
Configuring Feedforward Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-17
Configuring Setpoint Tracking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-19
Response to Open Loop Situations
in a Feedback Control Loop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-20
Open Input Situations (Hold Forward) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-21
Open Output Situations (Back Balancing or Tracking) . . . . . . . . . . . . . . . . . . . 2-2-23
Tracking in a Cascade Control Loop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-25
Tracking Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-26
Configuring Tracking in a Cascade Control Loop . . . . . . . . . . . . . . . . . . . . . . . . 2-2-27
Cascade Control Scheme—Secondary in Auto Mode . . . . . . . . . . . . . . . . . 2-2-28
Cascade Control Scheme—Secondary in Manual Mode . . . . . . . . . . . . . . 2-2-30
Cascade Control Scheme—Secondary Output Constrained . . . . . . . . . . . 2-2-32
Configuring Ratio and Bias . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-33
Ratio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-34
Bias . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-36
Configuring Gap and Deadband . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-38
Gap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-40
Deadband . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-41
Tuning PID Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-42
Tuning Display Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-44
Tuning Display Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-46
Adaptive Tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-47
Section 3: Configuring Other ControlBlock Continuous Functions . . . . . 2-3-1

Delay Period—Dead Time (DT) Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-2
Dead Time Input A Plots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-7
Dead Time Function Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-8
Process Modeling Applications—Lead/Lag (LL) Function . . . . . . . . . . . . . . . . . . . 2-3-10
Configuring the Lead/Lag Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-14
Operator Selectable Block Output—Manual (MAN) Function . . . . . . . . . . . . . . . . 2-3-16
User-defined ControlBlock—Math (MATH) Function . . . . . . . . . . . . . . . . . . . . . . . . 2-3-17
Equations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-19
Computing the Continuous Output Q . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-20
Computing the Value of a Continuous Input . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-20
Example of Temperature-correcting Air Flow Measurement . . . . . . . . . . . . . . 2-3-21
Example of Calculating the Sum of Flows Using a Math Block . . . . . . . . . . . . 2-3-24

CB: xi
Part 1: Scaling and Summing the Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-24

Part 2: Scaling the Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-26
Example of Tracking Through a Math Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-27
Tracking Using the “Max Gain” Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-27
Tracking Using the “Back Calc” Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-28
Nonlinear Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-29
Piecewise Linear Interpolator (PLI) Function . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-29
Polynomial (POLY) Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-29
Using Line Segments to Approximate a Curve—PLI Function . . . . . . . . . . . . 2-3-30
Example of a Piecewise Linear Interpolator Function Application . . . . . . . 2-3-32
Using a Polynomial Equation to Approximate a Curve—POLY Function . . . . 2-3-34
Example of a Polynomial Function Application . . . . . . . . . . . . . . . . . . . . . . . 2-3-36
Adjustable Ratio and Bias Capabilities—Ratio/Bias (RB) Function . . . . . . . . . . . 2-3-38
Configuring the Ratio Term on Faceplates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-41
Configuring the Bias and Pre-bias Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-41
Configuring the Bias Term on Continuous Links and
Continuous Faceplate Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-42
Selector Function—Signal Selector (SS) Function . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-43
Totalizer Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-47
Configuring a Setpoint Totalizer Function—TOTSP Function . . . . . . . . . . . . . 2-3-47
Configuring a Stack Totalizer Function—Stack Totalizer (TOT) Function . . . 2-3-51
Configuring Setpoint or Stack Totalizers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-55
Rate-limited Function—Velocity Limiter (VLIM) Function . . . . . . . . . . . . . . . . . . . . 2-3-57
Section 4: Configuring ControlBlock Discrete Functions . . . . . . . . . . . . . . 2-4-1

User Defined Discrete ControlBlock—Discrete (DISC) Function . . . . . . . . . . . . . 2-4-2
Preconfigured Motor Controller Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-3
Preconfigured Information for a Motor Controller . . . . . . . . . . . . . . . . . . . . . . . . 2-4-4
Unconfigured Information for a Motor Controller . . . . . . . . . . . . . . . . . . . . . . . . 2-4-4
Effect of Block Mode on Motor Controller Operation . . . . . . . . . . . . . . . . . . . . . 2-4-5
Discrete Motor Controller (DMC) Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-6
Links Required for DMC Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-7
Configuration Options for a DMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-8
Continuous Links Screens for a DMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-10
Discrete Links and Discrete Faceplate Screens for a DMC . . . . . . . . . . . . 2-4-11
DMC Input Functions and Output Conditions . . . . . . . . . . . . . . . . . . . . . . . . 2-4-12
Discrete Auto Sequence Motor Controller (DASMC) Configuration . . . . . . . . 2-4-14
Links Required for DASMC Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-16
Configuration Options for a DASMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-17
Continuous Links Screens for a DASMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-19
Discrete Links and Discrete Faceplate Screens for a DASMC . . . . . . . . . 2-4-20
DASMC Input Functions and Output Conditions . . . . . . . . . . . . . . . . . . . . . 2-4-21
Discrete Dual Speed Motor Controller (DDSMC) Configuration . . . . . . . . . . . 2-4-23
Links Required for DDSMC Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-24
Configuration Options for a DDSMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-25
Continuous Links Screens for a DDSMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-27
Discrete Links and Discrete Faceplate Screens for a DDSMC . . . . . . . . . 2-4-28

CB: xii
DDSMC Input Functions and Output Conditions . . . . . . . . . . . . . . . . . . . . . 2-4-29

Discrete Dual Direction Motor Controller (DDDMC) Configuration . . . . . . . . . 2-4-31
Links Required for DDDMC Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-32
Configuration Options for a DDDMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-33
Continuous Links Screens for a DDDMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-35
Discrete Links and Discrete Faceplate Screens for a DDDMC . . . . . . . . . 2-4-36
DDDMC Input Functions and Output Conditions . . . . . . . . . . . . . . . . . . . . . 2-4-37
Preconfigured Valve Controller Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-39
Preconfigured Information for a Valve Controller . . . . . . . . . . . . . . . . . . . . . . . . 2-4-40
Unconfigured Information for a Valve Controller . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-40
Effect of Block Mode on Valve Controller Operation . . . . . . . . . . . . . . . . . . . . . 2-4-41
Discrete Valve Controller (DVC) Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-42
Links Required for DVC Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-43
Configuration Options for a DVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-44
Continuous Links Screens for a DVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-46
Discrete Links and Discrete Faceplate Screens for a DVC . . . . . . . . . . . . . . . 2-4-47
DVC Input Functions and Output Conditions . . . . . . . . . . . . . . . . . . . . . . . . 2-4-48
Discrete Auto Sequence Valve Controller (DASVC) Configuration . . . . . . . . . 2-4-50
Links Required for DASVC Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-51
Configuration Options for a DASVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-52
Continuous Links Screens for a DASVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-54
Discrete Links and Discrete Faceplate Screens for a DASVC . . . . . . . . . . 2-4-55
DASVC Input Functions and Output Conditions . . . . . . . . . . . . . . . . . . . . . . 2-4-56
Discrete Motorized Valve Controller (DMVC) Configuration . . . . . . . . . . . . . . . 2-4-58
Links Required for DMVC Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-59
Configuration Options for a DMVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-61
Continuous Links Screens for a DMVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-63
Discrete Links and Discrete Faceplate Screens for a DMVC . . . . . . . . . . . 2-4-64
DMVC Input Functions and Output Conditions . . . . . . . . . . . . . . . . . . . . . . . 2-4-66
Section 5: Hints for Configuring ControlBlock Functions . . . . . . . . . . . . . . 2-5-1

Chapter 3: Configuring Block Links
Section 1: Introduction to Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1-1

What is a Link? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1-1
Destination Block: ControlBlock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1-2
Destination Block: Output Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1-2
Block Link Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1-3
Block Links Within a Controller Processor Card . . . . . . . . . . . . . . . . . . . . . . . . . 3-1-3
Block Links Into and Out of Controller Processor Cards . . . . . . . . . . . . . . . . . . 3-1-4
Block Links Into and Out of ControlFiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1-5
Block Links Between PeerWays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1-6

CB: xiii
Section 2: Continuous Links Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-1

Calling Up a Continuous Links Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-3
CB Continuous Links Screen Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-4
Invalid Link Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-4
Continuous Input Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-8
Scaling of Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-9
Types of Scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-9
Transmitter Scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-9
Internal or Normalized Scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-9
Display Scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-9
Scaling Sensitivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-11
Displaying Out-of-Range Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-12
Configuring Display Scaling to Match a Linked Source or a Register . . . . . . . 3-2-14
Matching the Scaling of Another Register . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-14
Scaling Dependent on Another Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-14
Converting Links to Engineering Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-16
Types of Conversions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-17
Configuring Conversion of Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-18
Reminders That Links Have Been Converted . . . . . . . . . . . . . . . . . . . . . . . . 3-2-20
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-22
Section 3: Discrete Links Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3-1

Calling Up a Discrete Links Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3-3
Discrete Links Screen Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3-4
Discrete Input Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3-6
Section 4: Configuration Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-1

Linking Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-1
Number of Controller Processor Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-2
Limit Within Controller Processors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-2
Limit Into and Out of Controller Processors . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-3
Number of ControlFile Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-5
Number of PeerWay Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-8
Limits for a PeerWay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-8
Limits for an HIA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-10
Viewing the Number of ControlFile Links Available . . . . . . . . . . . . . . . . . . . . . . 3-4-13
Viewing the Links of a ControlFile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-19
Tracing a Link to a Destination Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-21
Hints for Using Fewer Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-23
Use an Intermediate ControlBlock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-23
Use a ControlBlock Output Link Packet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-25
Free Space and Idle Time Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-27
Section 5: Hints for Configuring Block Links . . . . . . . . . . . . . . . . . . . . . . . . . 3-5-1


CB: xiv
Chapter 4: Configuring a Continuous Diagram Screen
Section 1: Configuring ControlBlock Alarm Points . . . . . . . . . . . . . . . . . . . . 4-1-1

Types of Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1-1
Setting ControlBlock Alarm Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1-2
Alarms for Continuous Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1-2
Deviation Alarms for Continuous Input A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1-4
Deadbands for Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1-6
Alarms for the Continuous Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1-8
Configuring Alarm Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1-10
Section 2: Configuring a Continuous Diagram Screen . . . . . . . . . . . . . . . . . 4-2-1

Calling Up a Continuous Diagram Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2-3
Continuous Diagram Screen Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2-4
Section 3: Hints for Configuring a Continuous Diagram Screen . . . . . . . . 4-3-1

Chapter 5: Configuring a Discrete Faceplate Screen
Section 1: Discrete Faceplate Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1-1

Calling Up a Discrete Faceplate Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1-3
Discrete Faceplate Screen Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1-4
Section 2: Configuring a Discrete Faceplate . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2-1

Discrete Faceplate Positions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2-2
Displaying a Discrete Variable State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2-4
Displaying a Continuous Variable Value or Units . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2-7
Displaying a System or User Flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2-9
Displaying a Message Pair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2-11
Displaying Static Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2-13
Section 3: Hints for Configuring Discrete Faceplates . . . . . . . . . . . . . . . . . . 5-3-1

Chapter 6: Configuring Logic Steps
Section 1: Introduction to Logic Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1-1

Screens for Configuring ControlBlock Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1-2
Logic Step Evaluation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1-4
Order of Logic Steps is Important . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1-4

CB: xv
Input Changes on the Following Cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1-5

Scaling and Logic Step Evaluation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1-6
Section 2: Configuring a Discrete Diagram Screen . . . . . . . . . . . . . . . . . . . . 6-2-1

Calling Up a Discrete Diagram Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2-2
Discrete Diagram Screen Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2-4
Configuring a Logic Step to Generate an Alarm or Event Message . . . . . . . . . . . 6-2-7
Section 3: Configuring Logic Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-1

Configuring Conditions Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-2
Configuring an Emulation Logic Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-4
Configuring a Set/Clear Logic Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-6
Configuring Action Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-8
Configuring an On Logic Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-10
Configuring an Off Logic Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-12
Configuring a Rise Logic Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-14
Configuring a Fall Logic Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-16
How to Write Logic Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-18
Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-18
Continuous Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-18
Discrete Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-19
Mathematical and Logical Operators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-20
Logic Statement Order of Precedence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-23
Using Variables and Operators in Combined Expressions . . . . . . . . . . . . . 6-3-23
Logic Statement Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-24
Comments in Logic Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-25
Applications for Logic Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-26
Using a Set/Clear Statement to Detect a Change in State . . . . . . . . . . . . . . . . 6-3-26
Using an Action Statement to Override a Block Action . . . . . . . . . . . . . . . . . . . 6-3-28
Block Actions Affecting the Output, Q . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-28
Block Actions Affecting the Linked Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-30
Section 4: Logic Statement Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4-1

Count Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4-3
Delay Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4-5
Duty and Period Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4-7
Timer Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4-12
Wait Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4-14
Ramping a Variable (ramp function) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4-16
Using the Clock Time or Date (time function) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4-18
Changing the Logic Step Mode (setuauto and setuman functions) . . . . . . . . . . . . 6-4-20
Changing or Testing the ControlBlock Operating Mode . . . . . . . . . . . . . . . . . . . . . 6-4-22
Changing the Operating Mode of the Block Being Configured
(setmode n function) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4-22
Testing for Block Mode (mode n function) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4-24
Testing the Block Mode of the Block Being Configured . . . . . . . . . . . . . . . . 6-4-24
Testing the Block Mode of Another Block . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4-25

CB: xvi
Changing or Testing the Controller Processor Operating

Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4-26
Testing the Controller Processor Mode (ifstand function) . . . . . . . . . . . . . . . . . 6-4-26
Setting the Controller Processor Card Mode (sstand and snorm functions) . 6-4-28
Inhibiting ControlBlock Alarms (inhibit function) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4-30
Inhibiting and Enabling the Controller Processor Alarms and Events
(inha and enba functions) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4-32
Specifying a Result Dependent Upon a Conditional State
(if?then:else function) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4-34
Resetting a Stack Totalizer (treset function) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4-37
Section 5: Hints for Configuring Logic Steps . . . . . . . . . . . . . . . . . . . . . . . . . 6-5-1

Chapter 7: Using System Flags and User Flags
Section 1: Introduction to Flags and Flag Logic . . . . . . . . . . . . . . . . . . . . . . . 7-1-1

What is a Flag? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1-1
Transfer of Data Between Linked Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1-2
Flag Notation for Logic Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1-4
Example of a Logic Step for Testing an Individual Flag . . . . . . . . . . . . . . . . . . . 7-1-5
Testing the Rise and Fall of an Individual Flag . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1-6
Binary and Hexadecimal Notation of Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1-7
Binary Notation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1-7
Hexadecimal Notation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1-7
Example of a Logic Step for Testing All Flags at Once . . . . . . . . . . . . . . . . . . . 7-1-9
Section 2: Input and Output Block Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2-1

Transfer of Flags: I/O Block Linked to a ControlBlock . . . . . . . . . . . . . . . . . . . . . . 7-2-2
I/O Block Flag Bit Representations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2-3
Testing for I/O Block Flag Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2-9
Section 3: ControlBlock Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-1

Transfer of Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-2
ControlBlock Linked to a ControlBlock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-2
System Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-2
User Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-4
Within a ControlBlock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-6
System Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-6
ControlBlock Flag Bit Representations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-7
Testing for ControlBlock Flag Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-10
Testing for ControlBlock Flags from a Continuous Input . . . . . . . . . . . . . . . . . . 7-3-11
Testing for System Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-11
Testing for User Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-12
Testing for ControlBlock Discrete Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-13

CB: xvii
Testing for ControlBlock Flags Within a Block . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-15

Testing for ControlBlock Discrete Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-16
Testing All Discrete Inputs Using the Discrete Output User Flags . . . . . . . . . . 7-3-17
Manipulating ControlBlock Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-18
Section 4: Console Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4-1

Transfer of Flags: Console Node Linked to a ControlBlock . . . . . . . . . . . . . . . . . . 7-4-1
Console Flag Bit Representations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4-3
Testing for Console Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4-4
Section 5: Testing Block Status Bits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5-1

What are Status Bits? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5-1
Block Status Bit Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5-2
Testing Block Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5-5
Section 6: Hints for Configuring Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6-1

Chapter 8: Configuring Autotuning ControlBlocks
Section 1: Autotuning Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1-1

Guidelines for Autotuning ControlBlocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1-2
Using Autotuning ControlBlocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1-3
Special Autotuning Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1-4
Section 2: Configuring Autotuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2-1

Configuring the Continuous Faceplate Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2-2
Configuring the ATC Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2-3
Configuring General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2-4
Open Loop Stable Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2-7
Configuring Detailed Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2-8
Loop Damping Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2-12
Minimum Period Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2-13
Using an ATPID Block to Tune Another Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2-14
Section 3: Operating an Autotuning ControlBlock . . . . . . . . . . . . . . . . . . . . . 8-3-1

1. Begin Autotuning Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3-2
2. Enable Autotuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3-3
3. Create a Setpoint Disturbance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3-4
4. Wait for the Evaluation to Finish . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3-6
5. Enter New PID Values into the Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3-8
6. Repeat Disturbances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3-10
7a. Enter New PID Values into Nonvolatile Memory . . . . . . . . . . . . . . . . . . . . . . . . 8-3-11
7b. Disconnect ATPID Block and Resume Normal Operations . . . . . . . . . . . . . . . 8-3-12
Section 4: Autotune Event Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4-1
Section 5: Reference Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5-1

Message Pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5-1

CB: xviii
Autotuning Evaluation States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5-2

Discrete Faceplate Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5-3
Continuous Links Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5-4
Discrete Links Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5-5
Chapter 9: Data Compression
Section 1: Introduction to Data Compression . . . . . . . . . . . . . . . . . . . . . . . . . 9-1-1

What is Data Compression? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1-1
Analog Data Compression Algorithms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1-2
Zero Slope (Box Car) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1-2
Backward Slope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1-4
Combined Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1-5
Discrete Data Compression Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1-6
Compression Ratio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1-7
Section 2: How the System Compresses Data . . . . . . . . . . . . . . . . . . . . . . . . . 9-2-1

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2-2
How Events are Generated from Analog Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2-3
Deadbands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2-3
Forced Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2-4
On/Off Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2-4
Analog Event Throttling and Compression Ratio Cutoff . . . . . . . . . . . . . . . . . . 9-2-5
How Events are Generated from Discrete Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2-6
Masking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2-6
Discrete Event Throttling and Compression Ratio Cutoff . . . . . . . . . . . . . . . . . 9-2-7
How Events are Stored . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2-8
How Events are Transmitted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2-9
Eligible Gateways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2-9
Retry Rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2-9
Alarms Produced by Data Compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2-10
Compression Ratio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2-10
Storage Buffer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2-11
Section 3: Configuring Compressors in a Data Compression Block . . . . 9-3-1

Special Data Compression Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3-2
Basic Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3-3
Configuring an Analog Compressor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3-6
Configuring a Discrete Compressor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3-11
Section 4: Hints for Configuring Data Compressors . . . . . . . . . . . . . . . . . . . 9-4-1

1984-2646-7200
1984-2646-7210
RS3t
Chapter 1:
Introduction to ControlBlocks

Display Scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-3




Display Scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-3
RS3: Introduction to ControlBlocks Contents

CB: ii





CB: iii
List of Figures
Figure Page
1.1.1 Role of a ControlBlock in a Typical Control Loop . . . . . . . . . . . . . . . . . . 1-1-2
1.1.2 Flow of Values Through a Typical Control Loop . . . . . . . . . . . . . . . . . . . 1-1-3
1.1.3 ControlBlock Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-4
1.1.4 Unconfigured ControlBlock Continuous Faceplate Screen . . . . . . . . . . 1-1-6
1.1.5 Moving Within a ControlBlock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-9
1.1.6 Moving Between ControlBlocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-11
1.1.7 Example of Access Arrows on a ControlBlock Configuration
Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-13
1.2.1 ControlBlock Functional Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2-2
1.2.2 ControlBlock Discrete Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2-3
1.2.3 ControlBlock Discrete Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2-4
1.2.4 ControlBlock Continuous Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2-5
1.2.5 ControlBlock Continuous Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2-6
1.3.1 Block Directory Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3-2
1.3.2 Block Status Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3-4

CB: iv
List of Tables
Table Page
1.1.1 ControlBlock Major Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-5
1.1.2 ControlBlock Configuration Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-8
1.1.3 Access Arrows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-12
1.3.1 Block Directory Screen Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3-3
1.3.2 Block Status Screen Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3-5

CB: 1-1-1
Section 1:
What is a ControlBlock?
This section describes the components of a ControlBlock, the role of a

ControlBlock within a control loop, the functions and modes of a
ControlBlock, and the ControlBlock configuration screens.
The RS3 uses three types of blocks: input blocks, output blocks, and
ControlBlocks. ControlBlocks are computational blocks where
calculations and logic functions are performed. ControlBlocks can
perform continuous (analog) or discrete functions depending on the
type of ControlBlock function that you select. ControlBlocks can contain:
D Up to 15 continuous inputs and 15 discrete inputs per block
D One continuous output and 16 discrete outputs per block
All analog and discrete outputs receive their commands from some type
of ControlBlock. ControlBlocks are linked to other ControlBlocks or
input/output (I/O) blocks so that data can be transmitted between
blocks.
Blocks that are transmitting data between one another are considered
to be linked together. Continuous and discrete inputs from other blocks
can be brought into the ControlBlock for use in the ControlBlock
calculations. Once the ControlBlock completes the calculations, the
resulting outputs can be sent to other ControlBlocks or I/O blocks. For
information about what block links are and how block links are
configured, see Chapter 3.
RS3: Introduction to ControlBlocks What is a ControlBlock?

CB: 1-1-2
Role of a ControlBlock in a Typical Control Loop
Calculations and functions for a control loop are performed within a

ControlBlock. The shaded box in Figure 1.1.1 shows the role of a
ControlBlock in a typical control loop.
You can configure a ControlBlock to act as a proportional-integral-

derivative (PID) controller, motor controller, or valve controller; as a
stack totalizer, signal selector, or another type of signal modifier; or, as a
math block or a discrete block. In addition, ControlBlocks can perform
alarm checking and generate alarm messages.
How ControlBlocks Relate to I/O Blocks
ControlBlocks receive field inputs from input blocks. After performing its
configured function, the ControlBlock sends its output to output blocks
for communication to Field Interface Cards.
Field Field
Device Controller Processor Device
FIC or Input Control- Output

FEM Block FIC
Block Block
Operator Entry
Figure 1.1.1. Role of a ControlBlock in a Typical Control Loop

CB: 1-1-3
How Values are Scaled in a Control Loop
Figure 1.1.2 shows how values are transmitted through a control loop,
beginning with a 4--20 mA signal that is converted to a 0--1 value for
internal use by the RS3 control system. The RS3 control system uses a
0--1 value to perform all I/O block and ControlBlock functions and
calculations.
ControlBlocks and I/O blocks have both internal and display scaling.
Internal Scaling
A 0--1 value, which is called an internal scaling value, is for internal

control system use only. This internal scaling value can be displayed to
the user on faceplates and console screens using a display scaling
function.
Display Scaling
The scaling value that is displayed to the user is called a display scaling
value. This value corresponds to the internal scaling value and is in
terms of the plant units. You configure the display scaling value as
desired. Configure the display scaling value for ControlBlock continuous
variables A through O and Q on the Continuous Links screen, using the
“Eng Zero” and “Eng Max” fields. ControlBlock inputs use the same
display scaling as the input block to which it is linked unless you
configure the scaling information differently. Each ControlBlock input
can have a different display scaling, if desired.
Field Field
Device Device
FIC or Input Control- Output

FEM FIC
Block Block Block
4--20 0--1 0--1 0--1 0--1 4--20
mA value value value value mA
signal signal
Figure 1.1.2. Flow of Values Through a Typical Control Loop

CB: 1-1-4
ControlBlock Addresses
ControlBlock addresses are derived from the Controller Processor card

slot address on which the software block resides and from a sequential
number that is assigned to each software block. The number of blocks
per Controller Processor depends on the type of Controller Processor:
D Up to 126 blocks for an MPCII or an MPC5
D Up to 99 blocks for an MPCI
Figure 1.1.3 shows an example of a ControlBlock address, =16A--12.
=16A --12
Controller Processor Address ControlBlock Number

01 -- 126 MPCII / MPC5
01 -- 99 MPCI
(This does not correspond to
a physical address.)
Dash
(Differentiates the ControlBlock from an I/O Block)
Figure 1.1.3. ControlBlock Addressing

CB: 1-1-5
ControlBlock Functions
The function you assign to the ControlBlock is considered the major

function of the ControlBlock. This function defines the primary
calculations that the ControlBlock performs. These calculations can be
either continuous or discrete functions. Table 1.1.1 lists the ControlBlock
major functions. For a discussion of each of the ControlBlock functions,
see Chapter 3.
Table 1.1.1. ControlBlock Major Functions
Function
Mnemonic Description of the Function
Category
Continuous MAN Manual (User-defined)
Functions P Proportional-only control
I Integral-only control
D Derivative-only control
PI Proportional and Integral control
ID Integral and Derivative control
PD Proportional and Derivative control
PID Proportional, Integral, and Derivative control
IB Integral-only control with Bias
LL Lead/Lag
DT Dead Time
TOT Stack Totalizer
TOTSP Setpoint Totalizer
RB Ratio/Bias
SS Signal Selector
VLIM Velocity Limiter
POLY 7th Order Polynomial
PLI Piecewise Linear Interpolator
MATH User-defined
ATPID Autotuning (ATP, ATPI, and ATPD do not function)
Discrete DISC Discrete (User-defined)
Functions DMC Motor Control
DASMC Auto Sequence Motor Control
DDSMC Dual Speed Motor Control
DDDMC Dual Direction Motor Control
DVC Valve Control
DASVC Auto Sequence Valve Control
DMVC Motorized Valve Control
RBL *Rosemount Basic Language Control
* Requires an RBL image

CB: 1-1-6
Configuring the Major Function of a ControlBlock
You configure the major function of a ControlBlock on the Continuous

Faceplate screen. If you select a ControlBlock with a continuous major
function, the Continuous Faceplate screen appears as the major
faceplate. If you select a ControlBlock with a discrete major function, the
Discrete Faceplate screen appears as the major faceplate. Table 1.1.1
lists the RS3 control system major functions and associated
mnemonics.
- To call up a ControlBlock Faceplate screen, type:
[TAG/ADDRESS] ControlBlock tag or address [ENTER]
or
TA: ControlBlock tag or address [ENTER]
Figure 1.1.4 shows an unconfigured Continuous Faceplate screen.
- To select the desired ControlBlock function:

1. Determine the desired function:
-- Cursor to the field and type the mnemonic for the function
type
or
-- Press [NEXT OPTION] repeatedly to select the desired
function.
2. Press [ENTER].
CB CONTINUOUS FACEPLATE 25-Jan-90 10:42:34
Addr =1C-12 Function ÞNONE (Unconfigured)

Block Not Configured
CONFIG 1
Figure 1.1.4. Unconfigured ControlBlock Continuous Faceplate Screen

CB: 1-1-7
- To configure the major function of an unconfigured

ControlBlock:
1. Select the desired function.
— Cursor to the “Function” field and type in the mnemonic for
the desired function
or
— Press [NEXT OPTION] repeatedly to select the desired
function.
2. Press [ENTER].
The CB Faceplate screen changes according to the continuous
or discrete function selected.
- To change the major function of a ControlBlock:

1. Cursor to the “Function” field and type NONE [ENTER].
2. Select the desired function.
— Cursor to the “Function” field and type in the mnemonic for
the appropriate function
or
— Press [NEXT OPTION] repeatedly to select the appropriate
function.
3. Press [ENTER].
The ControlBlock function is now changed.

CB: 1-1-8
ControlBlock Configuration Screens
Generally, you will use some or all of the different configuration screens
when configuring a ControlBlock function. In most cases, the screen
you use depends on whether the function is continuous or discrete.
Table 1.1.2 lists the screens that are used to configure a ControlBlock.
Table 1.1.2. ControlBlock Configuration Screens
For a complete
ControlBlock Screen Used to configure ...
description, see ...
The block major function, the continuous faceplate, the
Continuous Faceplate operator entry limits, and other information of a Chapter 2
ControlBlock.
Discrete Faceplate The discrete faceplate of a ControlBlock. Chapter 5
Continuous Links The continuous input links of the ControlBlock. Chapter 3
Discrete Links The discrete input links of the ControlBlock. Chapter 3
The continuous input alarm limits, plant units, and other
Continuous Diagram Chapter 4
information of a ControlBlock.
Discrete Diagram The ControlBlock logic steps of a ControlBlock. Chapter 6
Provides a list of destination blocks that request values
Block References Chapter 3
from the ControlBlock.

CB: 1-1-9
Moving Within a ControlBlock
Using ControlBlock Screens

You can use the ControlBlock configuration screens to move within a
ControlBlock and access its ControlBlock data. Figure 1.1.5 shows the
ControlBlock configuration screens for a ControlBlock and explains how
to move among those screens within a ControlBlock.
Use [EXCH] to move from a continuous screen of one type to its
corresponding discrete screen and vice versa. For example, press
[EXCH] from a Continuous Links screen to call up the Discrete Links
screen.
Using Keyboard Keys

You use the console [BLOCK LINKS], [BLOCK FACEPLATE],
[BLOCK DIAGRAM], and [BLOCK REFERENCES] keys to call up the
ControlBlock configuration screens for a particular ControlBlock.
CB CONTINUOUS CB DISCRETE
FACEPLATE [ EXCH ] FACEPLATE
[ PAGE ] CB CONTINUOUS [ EXCH ]

LINKS
CB DISCRETE LINKS
H to O
CB CONTINUOUS
LINKS
A to G [ EXCH]
[ PAGE ] [ PAGE ]
DIAGRAM DIAGRAM
A a
[ EXCH ]
BLOCK REFERENCES
[ PAGE ] =
[PAGE AHEAD]
and
[PAGE BACK]
Figure 1.1.5. Moving Within a ControlBlock

CB: 1-1-10
Moving Between ControlBlocks
You can use the ControlBlock configuration screens to move from one
ControlBlock to another and to access data for those ControlBlocks.
Figure 1.1.6 shows how to use ControlBlock screens to move between
ControlBlocks.
Use [PAGE AHEAD] and [PAGE BACK] to move from a ControlBlock

screen of one type to the same type of screen for another ControlBlock.
You cannot move from a Diagram screen to the Diagram screen of the
previous or next ControlBlock.

CB: 1-1-11
[ PAGE ]=[ PAGE AHEAD ] and [ PAGE BACK ] keys
ControlBlock ControlBlock =1A--4 ControlBlock

=1A--3 =1A--5
[ PAGE ] Continuous [ PAGE ]

Faceplate
[ PAGE ] Discrete [ PAGE ]

Faceplate
[ PAGE ] Continuous [ PAGE ] Continuous [ PAGE ]

Links A to G Links H to O
[ PAGE ] Discrete [ PAGE ]

Links
Continuous
Diagram A
Discrete
Diagram a
[ PAGE ] Block [ PAGE ]

Reference
Figure 1.1.6. Moving Between ControlBlocks

CB: 1-1-12
How to Use Access Arrows on ControlBlock Configuration

Screens
Fields on the ControlBlock configuration screens are often preceded by

an arrow that indicates what type of user has access privileges for that
field: configuror, supervisor, or operator. Access privileges allow you to
manipulate or make entries to the field by cursoring to the arrow and
pressing the desired keys. Table 1.1.3 lists each access arrow and its
corresponding user. Figure 1.1.7 shows a sample screen with the
various access arrows. The shaded box in Figure 1.1.7 displays the
user whose access key is inserted in the console.
Fields that are lacking an arrow are for display only and cannot be
manipulated. Many fields, however, allow user access only when a
ControlBlock is in a particular mode, such as Manual.
Table 1.1.3. Access Arrows
Arrow User with Access Privileges Key

Þ Configuror Configuror (Conf)
® Supervisor (and Configuror) Supervisor (Supr)
> Operator (and Supervisor, Configuror) Operator (Oper)

CB: 1-1-13
No arrow indicates a field A supervisor arrow indicates a

that is for display only. No field that can be manipulated only
entries are allowed. by a supervisor or configuror.
CB CONTINUOUS DIAGRAM 23-Jan-90 11:47:12

Tag Descriptor
Addr Function PID Controller
Sample TimeÞ.5 S Alarm PriorityÞ
Þ50.00 PV OPR Alm Ent
> PV ALARMS: Crit Þno
PV Hi Crit ®100 Adv Þno
Þ50.00 LS
PV Hi Adv ®None
Output
Þ RS PV Lo Adv ®None
>50.18
PV Lo Crit ®0
Þ FF
PV Rate ®2/S
Plant UnitÞ0
Þ E PV DdBand Þ10.00
Auto Lock Þno
Dev Adv ®40.00
F
Þ Dev Crit ®40.00
Block Mode> LOCAL
CONFIG 1
A configuror arrow indicates a An operator arrow indicates a field

field that can be manipulated only that can be manipulated by an
by a configuror. operator, supervisor, or configuror.
Figure 1.1.7. Example of Access Arrows on a ControlBlock Configuration Screen

CB: 1-1-14

CB: 1-2-1
Section 2:
Types of ControlBlock Inputs and Outputs
This section describes the types of ControlBlock inputs and outputs.
ControlBlock Inputs and Outputs
Each ControlBlock contains the following inputs and outputs:

D Up to 15 discrete inputs, called @a through @o
D Up to 16 discrete outputs, called a through p
D Up to 15 continuous inputs, called A through O
D 1 continuous output, called Q
Figure 1.2.1 shows the ControlBlock functional diagram with the

ControlBlock inputs and outputs.
RS3: Introduction to ControlBlocks Types of ControlBlock Inputs and Outputs

CB: 1-2-2
ControlBlock
15 discrete inputs @a a 16 discrete outputs
@b b (logic steps)
@c c
@d d
@e e
@f f
@g g
@h h
@i i
@j j
@k k
@l l
@m m
@n n
@o o
p
15 continuous inputs A
B
C
D
E
F
G
H Q 1 continuous output
I
J
K
L
M
N
O
Figure 1.2.1. ControlBlock Functional Diagram

CB: 1-2-3
ControlBlock Discrete Inputs
Up to 15 discrete inputs @a through @o are available for a

ControlBlock to perform control calculations. Configure these inputs on
the Discrete Links screen. Figure 1.2.2 shows a ControlBlock with 15
discrete inputs @a through @o and the Discrete Links screen for linking
each of the inputs to the ControlBlock.
ControlBlock
15 discrete inputs
@a
@b
@c
CB DISCRETE LINKS @d
@e
INPUT SOURCE INPUT SOURCE
@f
@a @i
@b @j @g
@c @k @h
@i
@h @o @j
@k
@l
@m
@n
@o
Figure 1.2.2. ControlBlock Discrete Inputs

CB: 1-2-4
ControlBlock Discrete Outputs
Discrete functions produce two possible results—true or false. A total of

16 discrete outputs, a through p, are available. Discrete outputs a
through p are also called logic steps a through p. You configure logic
steps on the Discrete Diagram screens. Figure 1.2.3 shows a
ControlBlock with 16 discrete outputs and the Discrete Diagram screens
for configuring the logic steps. There is a separate page for each logic
step.
ControlBlock
CB DISCRETE DIAGRAM
16 discrete outputs
(logic steps) Step Þ p
a
b
c CB DISCRETE DIAGRAM
d Step Þ d
CB DISCRETE DIAGRAM
e
f Step Þ c
CB DISCRETE DIAGRAM
g Step Þ b
h CB DISCRETE DIAGRAM
i Step Þ a
j
k
l
m
n
o
p
Figure 1.2.3. ControlBlock Discrete Outputs

CB: 1-2-5
ControlBlock Continuous Inputs
Up to 15 continuous inputs A through O are available for a ControlBlock

to perform calculations. You configure these inputs on the Continuous
Links screen. Figure 1.2.4 shows a ControlBlock with 15 continuous
inputs and the Continuous Links screens for linking the inputs to the
ControlBlock. There are two Continuous Links screens: one for inputs A
through G and another for inputs H through O.
You can configure alarms for specific ControlBlock continuous inputs on

the Continuous Diagram screen. For more information about configuring
continuous alarms, see Chapter 4.
ControlBlock
15 continuous inputs
CB CONTINUOUS LINKS
INPUT SOURCE Zero Max A
H B
C
I CB CONTINUOUS LINKS
D
J INPUT SOURCE Zero Max E
. A F
O B G
H
C I
J
G K
L
M
N
O
Figure 1.2.4. ControlBlock Continuous Inputs

CB: 1-2-6
ControlBlock Continuous Output
One continuous output, Q, is available as a result of a continuous

function. You configure the alarms for the continuous output on the Q
page of the Continuous Diagram screen. Figure 1.2.5 shows a
ControlBlock with continuous output Q and the Q page of the
Continuous Diagram screen for configuring the output alarms.
ControlBlock
1 continuous output
Q
CB CONTINUOUS DIAGRAM
Q ALARMS:
Dev Adv
Dev Crit
Figure 1.2.5. ControlBlock Continuous Output

CB: 1-3-1
Section 3:
Block Directory and Block Status Screens
This section describes the Block Directory screen and the Block Status
screen, which provide information about configured ControlBlocks and
I/O blocks.
RS3: Introduction to ControlBlocks Block Directory and Block Status Screens

CB: 1-3-2
Viewing Information About Configured Blocks
The Block Directory screen displays information about configured

ControlBlocks and I/O blocks. This screen is for display only; you cannot
make entries from it.
- To call up the Block Directory screen, type:
CBD: [ENTER]
The Block Directory screen for Controller Processor A is displayed first.

I/O blocks are listed first, followed by ControlBlocks. Press [PAGE
AHEAD] to see other blocks in that Controller Processor, and then press
[PAGE AHEAD] to see the blocks for the next Controller Processor.
Press [EXCH] to call up the Block Directory for the Controller Processor.
Figure 1.3.1 shows a sample Block Directory screen for Controller

Processor =3C. Table 1.3.1 describes the types of information provided
in the screen areas.
- To call up a block faceplate screen:

D Cursor to the tag or address of the Identifies the Controller Processor on
desired block and press [SELECT]. which the blocks are configured.
BLOCK DIRECTORY: 3C 01-OCt-90 1:47:12

Steps in Plant Size
Block Tag Type Mode Alarm Manual Unit Stat Dyn Total
=3C-05 AUTOSET DISC AUTO a 2 269 31 300
=3C-06 MANSET DISC OPERATOR 2 131 31 162
=3C-07 MATRIX DISC AUTO 2 95 39 134
=3C-08 FAN DISC AUTO 2 268 87 355
=3C-09 M-1 DMC AUTO 2 58 31 89
=3C-10 Motor-1 DISC AUTO 2 116 72 188
=3C-11 MCC-1 DISC AUTO 2 237 55 292
=3C-14 Valve-1 DVC AUTO 2 109 64 173
=3C-16 VCC-1 DISC AUTO 2 241 55 296
=3C-18 Valve-2 DVC AUTO 2 109 64 173
=3C-20 VCC-2 DISC AUTO 2 241 55 296
=3C-22 Valve-3 DVC AUTO 2 110 64 174
*MORE*
.
Figure 1.3.1. Block Directory Screen

CB: 1-3-3
Table 1.3.1. Block Directory Screen Fields
Field Description
Indicates whether the block is currently in alarm. Not all block alarms trigger an
Alarm
indication.
Block Address of the block.
Mode Current block mode.
Plant Unit User-defined group to which the block is assigned.
Amount of static and dynamic space used by the block and the total amount of
Size
space the block uses. This information is displayed for a configuror only.
For ControlBlocks only, this field displays any steps that are currently in manual
Steps in Manual
mode.
Tag User-defined block tag.
Type Type of block. For ControlBlocks, identifies the ControlBlock function.

CB: 1-3-4
Viewing the Block Status
The Block Status screen displays the configured ControlBlocks and I/O
blocks that are in modes other than Auto or that are in alarm. This
screen is for display only; you cannot make entries from it.
- To call up the Block Status screen, type:
CBS [ENTER]
The Block Status screen for Controller Processor A is displayed first. I/O
blocks are listed first, followed by ControlBlocks. Press [PAGE AHEAD]
to see other blocks in that Controller Processor, and then press [PAGE
AHEAD] to see the blocks for the next Controller Processor. Press
[EXCH] to call up the Block Directory for the Controller Processor.
Figure 1.3.2 shows a sample Block Status screen for Controller

Processor =3C. Table 1.3.2 describes the types of information provided
in the screen areas.
- To call up a block Faceplate screen:

D Cursor to the tag or address of the d Identifies the Controller Processor on w
esired block and press [SELECT]. hich the blocks are configured.
BLOCK STATUS: 3C 01-OCt-90 11:47:12

Steps in Plant Size
Block Tag Type Mode Alarm Manual Unit Stat Dyn Total
=3C-06 MANSET DISC OPERATOR 2 131 31 162
=3C-43 Valve-1 DISC AUTO ALARM 2 210 65 275
=3C-44 Valve-1 DISC OPERATOR 2 109 119 228
=3C-97 VCC-1 PID MANUAL b 2 262 55 317
=3C-98 VCC-1 PID MANUAL 2 191 75 266
=3C-99 VCC-1 PID MANUAL 2 241 50 291
*END*
Figure 1.3.2. Block Status Screen

CB: 1-3-5
Table 1.3.2. Block Status Screen Fields
Field Description
Indicates whether the block is currently in alarm. Not all block alarms trigger an
Alarm
indication.
Block Address of the block.
Mode Current block mode.
Plant Unit User-defined group to which the block is assigned.
Amount of static and dynamic space used by the block and the total amount of
Size
space the block uses. This information is displayed for a configuror only.
Steps in Manual For ControlBlocks only, displays any steps that are currently in manual mode.
Tag User-defined block tag.
Type Type of block. For ControlBlocks, identifies the ControlBlock function.

CB: 1-3-6

CB: 1-4-1
Section 4:
Hints for Configuring ControlBlocks
This section discusses some of the problems that you may encounter
when configuring ControlBlocks and some possible ways to deal with
them. This section also provides tips that are helpful when configuring
ControlBlocks.
Configuration Problems
Listed below are typical problems that occur when configuring

ControlBlocks and possible ways to handle them.
- When reconfiguring a ControlBlock, I can’t access some of the
screen fields to reconfigure an entry.
Try changing the ControlBlock mode. Many fields are accessible
only when the ControlBlock is in a particular mode, such as Manual.
- I can’t reconfigure the major function of a ControlBlock.
Before a ControlBlock can be reconfigured, the current configuration
has to be deleted. On the Continuous Faceplate screen, first
configure the “Function” field as “None” to delete the previous
configuration, and then configure the “Function” field with the
ControlBlock function of your choice.
- I can’t slew the ControlBlock output.
Check the ControlBlock mode to be sure that it is in Manual mode.
The output can only be manipulated when the ControlBlock is in
Manual or Local mode.
- I can’t adjust a ControlBlock value.
The value you are trying to enter is probably outside of the
ControlBlock limits. Either reconfigure the limits or enter a value that
is within the range of the current limits.
RS3: Introduction to ControlBlocks Hints for Configuring ControlBlocks

CB: 1-4-2
Configuration Tips
Listed below are hints to help you when configuring ControlBlocks.

- Accessing screen fields
Remember that you can only access the ControlBlock screen fields
that you have the proper access for, such as configuror, supervisor,
or operator access.
- Calling up ControlBlock screens
When calling up ControlBlocks screens, the screen that is displayed
depends on the major function of the ControlBlock that is configured.
D If the major function is a continuous function, then the Continuous
ControlBlock screens are displayed.
D If the major function is a discrete function, then the Discrete
ControlBlock screens are displayed.
RS3: Introduction to ControlBlocks Hints for Configuring ControlBlocks

RS3t
Chapter 2:
Configuring ControlBlock Functions
Section 1: Configuring Common Fields on the Continuous Faceplate . . 2-1-1

Calling Up a Continuous Faceplate Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1-3
Configuring a Continuous Faceplate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1-5
Effect of Block Mode on the Block Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1-9
Common Fields on the Continuous Faceplate Screen . . . . . . . . . . . . . . . . . . . . . . 2-1-10
Section 2: Configuring PID Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-1

PID Controller Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-1
PID Control Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-2
Proportional Term . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-5
Integral Term . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-6
Derivative Term . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-8
Feedforward . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-10
Velocity Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-11
Configuring PID Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-13
Configuring Feedforward Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-17
Configuring Setpoint Tracking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-19
Response to Open Loop Situations in a Feedback Control Loop . . . . . . . . . . . . . 2-2-20
Open Input Situations (Hold Forward) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-21
Open Output Situations (Back Balancing or Tracking) . . . . . . . . . . . . . . . . . . . 2-2-23
Tracking in a Cascade Control Loop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-25
Tracking Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-26
Configuring Tracking in a Cascade Control Loop . . . . . . . . . . . . . . . . . . . . . . . . 2-2-27
Cascade Control Scheme—Secondary in Auto Mode . . . . . . . . . . . . . . . . . 2-2-28
Cascade Control Scheme—Secondary in Manual Mode . . . . . . . . . . . . . . 2-2-30
Cascade Control Scheme—Secondary Output Constrained . . . . . . . . . . . 2-2-32
Configuring Ratio and Bias . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-33
Ratio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-34
Bias . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-36
Configuring Gap and Deadband . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-38
Gap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-40
Deadband . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-41
Tuning PID Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-42
Tuning Display Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-44
Tuning Display Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-46
Adaptive Tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-47
RS3: Configuring ControlBlock Functions Contents

CB: ii
Section 3: Configuring Other ControlBlock Continuous Functions . . . . . 2-3-1

Delay Period—Dead Time (DT) Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-2
Dead Time Input A Plots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-7
Dead Time Function Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-8
Process Modeling Applications—Lead/Lag (LL) Function . . . . . . . . . . . . . . . . . . . 2-3-10
Configuring the Lead/Lag Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-14
Operator Selectable Block Output—Manual (MAN) Function . . . . . . . . . . . . . . . . 2-3-16
User-defined ControlBlock—Math (MATH) Function . . . . . . . . . . . . . . . . . . . . . . . . 2-3-17
Equations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-19
Computing the Continuous Output Q . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-20
Computing the Value of a Continuous Input . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-20
Example of Temperature-correcting Air Flow Measurement . . . . . . . . . . . . . . 2-3-21
Example of Calculating the Sum of Flows Using a Math Block . . . . . . . . . . . . 2-3-24
Part 1: Scaling and Summing the Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-24
Part 2: Scaling the Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-26
Example of Tracking Through a Math Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-27
Tracking Using the “Max Gain” Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-27
Tracking Using the “Back Calc” Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-28
Nonlinear Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-29
Piecewise Linear Interpolator (PLI) Function . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-29
Polynomial (POLY) Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-29
Using Line Segments to Approximate a Curve—PLI Function . . . . . . . . . . . . 2-3-30
Example of a Piecewise Linear Interpolator Function Application . . . . . . . 2-3-32
Using a Polynomial Equation to Approximate a Curve—POLY Function . . . . 2-3-34
Example of a Polynomial Function Application . . . . . . . . . . . . . . . . . . . . . . . 2-3-36
Adjustable Ratio and Bias Capabilities—Ratio/Bias (RB) Function . . . . . . . . . . . 2-3-38
Configuring the Ratio Term on Faceplates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-41
Configuring the Bias and Pre-bias Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-41
Configuring the Bias Term on Continuous Links and Continuous Faceplate
Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-42
Selector Function—Signal Selector (SS) Function . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-43
Totalizer Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-47
Configuring a Setpoint Totalizer Function—TOTSP Function . . . . . . . . . . . . . 2-3-47
Configuring a Stack Totalizer Function—Stack Totalizer (TOT) Function . . . 2-3-51
Configuring Setpoint or Stack Totalizers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-55
Rate-limited Function—Velocity Limiter (VLIM) Function . . . . . . . . . . . . . . . . . . . . 2-3-57
Section 4: Configuring ControlBlock Discrete Functions . . . . . . . . . . . . . . 2-4-1

User Defined Discrete ControlBlock—Discrete (DISC) Function . . . . . . . . . . . . . 2-4-2
Preconfigured Motor Controller Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-3
Preconfigured Information for a Motor Controller . . . . . . . . . . . . . . . . . . . . . . . . 2-4-4
Unconfigured Information for a Motor Controller . . . . . . . . . . . . . . . . . . . . . . . . 2-4-4
Effect of Block Mode on Motor Controller Operation . . . . . . . . . . . . . . . . . . . . . 2-4-5
Discrete Motor Controller (DMC) Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-6
Links Required for DMC Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-7
Configuration Options for a DMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-8

CB: iii
Continuous Links Screens for a DMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-10

Discrete Links and Discrete Faceplate Screens for a DMC . . . . . . . . . . . . 2-4-11
DMC Input Functions and Output Conditions . . . . . . . . . . . . . . . . . . . . . . . . 2-4-12
Discrete Auto Sequence Motor Controller (DASMC) Configuration . . . . . . . . 2-4-14
Links Required for DASMC Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-16
Configuration Options for a DASMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-17
Continuous Links Screens for a DASMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-19
Discrete Links and Discrete Faceplate Screens for a DASMC . . . . . . . . . 2-4-20
DASMC Input Functions and Output Conditions . . . . . . . . . . . . . . . . . . . . . 2-4-21
Discrete Dual Speed Motor Controller (DDSMC) Configuration . . . . . . . . . . . 2-4-23
Links Required for DDSMC Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-24
Configuration Options for a DDSMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-25
Continuous Links Screens for a DDSMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-27
Discrete Links and Discrete Faceplate Screens for a DDSMC . . . . . . . . . 2-4-28
DDSMC Input Functions and Output Conditions . . . . . . . . . . . . . . . . . . . . . 2-4-29
Discrete Dual Direction Motor Controller (DDDMC) Configuration . . . . . . . . . 2-4-31
Links Required for DDDMC Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-32
Configuration Options for a DDDMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-33
Continuous Links Screens for a DDDMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-35
Discrete Links and Discrete Faceplate Screens for a DDDMC . . . . . . . . . 2-4-36
DDDMC Input Functions and Output Conditions . . . . . . . . . . . . . . . . . . . . . 2-4-37
Preconfigured Valve Controller Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-39
Preconfigured Information for a Valve Controller . . . . . . . . . . . . . . . . . . . . . . . . 2-4-40
Unconfigured Information for a Valve Controller . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-40
Effect of Block Mode on Valve Controller Operation . . . . . . . . . . . . . . . . . . . . . 2-4-41
Discrete Valve Controller (DVC) Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-42
Links Required for DVC Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-43
Configuration Options for a DVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-44
Continuous Links Screens for a DVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-46
Discrete Links and Discrete Faceplate Screens for a DVC . . . . . . . . . . . . . . . 2-4-47
DVC Input Functions and Output Conditions . . . . . . . . . . . . . . . . . . . . . . . . 2-4-48
Discrete Auto Sequence Valve Controller (DASVC) Configuration . . . . . . . . . 2-4-50
Links Required for DASVC Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-51
Configuration Options for a DASVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-52
Continuous Links Screens for a DASVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-54
Discrete Links and Discrete Faceplate Screens for a DASVC . . . . . . . . . . 2-4-55
DASVC Input Functions and Output Conditions . . . . . . . . . . . . . . . . . . . . . . 2-4-56
Discrete Motorized Valve Controller (DMVC) Configuration . . . . . . . . . . . . . . . 2-4-58
Links Required for DMVC Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-59
Configuration Options for a DMVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-61
Continuous Links Screens for a DMVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-63
Discrete Links and Discrete Faceplate Screens for a DMVC . . . . . . . . . . . 2-4-64
DMVC Input Functions and Output Conditions . . . . . . . . . . . . . . . . . . . . . . . 2-4-66
Section 5: Hints for Configuring ControlBlock Functions . . . . . . . . . . . . . . 2-5-1


CB: iv
List of Figures
Figure Page
2.1.1 Continuous Faceplate Screen Among ControlBlock Screens . . . . . . . . 2-1-2
2.1.2 Calling Up a ControlBlock Continuous Faceplate Screen . . . . . . . . . . . 2-1-4
2.1.3 Continuous Faceplate Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1-6
2.1.4 Configuring Operator--enterable Input . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1-8
2.1.5 Continuous Faceplate Screen Common Fields . . . . . . . . . . . . . . . . . . . . 2-1-10
2.2.1 Typical PID Control Loop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-1
2.2.2 Position Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-2
2.2.3 Typical Feedforward Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-10
2.2.4 Continuous Faceplate Screen—Combinations of P, I, and D
Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-13
2.2.5 Continuous Links Screen—PID Function . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-14
2.2.6 Continuous Faceplate Screen—“FF Gain” Field . . . . . . . . . . . . . . . . . . 2-2-17
2.2.7 Continuous Links Screen—Example of Feedforward Control . . . . . . . . 2-2-18
2.2.8 Continuous Faceplate Screen—“LS--PV Track” Field . . . . . . . . . . . . . . 2-2-19
2.2.9 Feedback Control Loop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-20
2.2.10 Hold Forward in an Open Loop Situation . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-22
2.2.11 “Hold” Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-22
2.2.12 Tracking in an Open Loop Situation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-24
2.2.13 Typical Cascade Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-25
2.2.14 Cascade Secondary Block with Local Setpoint Option . . . . . . . . . . . . . 2-2-25
2.2.15 Tracking Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-26
2.2.16 Tracking Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-27
2.2.17 Cascade Control Tracking Block Diagram—Secondary in Auto . . . . . . 2-2-28
2.2.18 Cascade Control Tracking Block Diagram----Secondary in Auto . . . . . . 2-2-29
2.2.19 Cascade Control Tracking—Secondary in Manual . . . . . . . . . . . . . . . . . 2-2-30
2.2.20 Cascade Control Tracking Faceplate Indicators—Secondary in
Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-31
2.2.21 Cascade Control Tracking Faceplate Indicators—Secondary
Output Constrained . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-32
2.2.22 Functional Diagram of PID Controller with Ratio Option . . . . . . . . . . . . 2-2-33
2.2.23 Continuous Faceplate Screen—Ratio Option . . . . . . . . . . . . . . . . . . . . . 2-2-34
2.2.24 Continuous Links Screen—Ratio Option . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-35
2.2.25 Continuous Faceplate Screen—Bias Option . . . . . . . . . . . . . . . . . . . . . . 2-2-36

CB: v
2.2.26 Continuous Links Screen—Bias Option . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-37

2.2.27 Effects of Gap and Deadband on Output (Q) . . . . . . . . . . . . . . . . . . . . . 2-2-38
2.2.28 Gap and Deadband Response to a Constant Small Error . . . . . . . . . . . 2-2-39
2.2.29 Continuous Faceplate Screen—Gap Option . . . . . . . . . . . . . . . . . . . . . . 2-2-40
2.2.30 Continuous Faceplate Screen—Deadband Option . . . . . . . . . . . . . . . . . 2-2-41
2.2.31 Tuning Display Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-43
2.2.32 Tuning Display Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-45
2.2.33 Sample Tuning Display Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-46
2.2.34 Example of Configuring Adaptive Tuning . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-48
2.3.1 Dead Time Functional Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-2
2.3.2 Dead Time Delay Effect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-4
2.3.3 Continuous Faceplate Screen—Dead Time Function . . . . . . . . . . . . . . 2-3-5
2.3.4 Continuous Links Screen—Dead Time Function . . . . . . . . . . . . . . . . . . 2-3-6
2.3.5 Example of a Dead Time Plot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-7
2.3.6 Application of a Dead Time Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-8
2.3.7 Application of Dead Time with Variable Speed Conveyor . . . . . . . . . . . 2-3-9
2.3.8 Typical Feedforward Control with a Lead/Lag Function . . . . . . . . . . . . . 2-3-11
2.3.9 Lead/Lag Functional Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-11
2.3.10 Gain Effect on Block Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-12
2.3.11 Lag Effect on Block Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-12
2.3.12 Lead Effect on Block Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-13
2.3.13 Continuous Faceplate Screen—Lead/Lag Function . . . . . . . . . . . . . . . . 2-3-14
2.3.14 Continuous Links Screen—Lead/Lag Function . . . . . . . . . . . . . . . . . . . . 2-3-15
2.3.15 Typical Manual Function Control Loop . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-16
2.3.16 Continuous Faceplate Screen—Math Function . . . . . . . . . . . . . . . . . . . . 2-3-17
2.3.17 Continuous Links Screen—Math Function . . . . . . . . . . . . . . . . . . . . . . . . 2-3-19
2.3.18 Example of Temperature-corrected Flow . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-21
2.3.19 Continuous Faceplate Screen—Example of
Temperature-correcting Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-22
2.3.20 Continuous Links Screen—Example of Temperature-correcting
Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-23
2.3.21 Example of Flow Summation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-24
2.3.22 Continuous Links Screen—Example of Flow Summation . . . . . . . . . . . 2-3-25
2.3.23 Continuous Faceplate Screen—Example of Flow Summation . . . . . . . 2-3-25
2.3.24 Converting the Output to a 0 to 100% Range . . . . . . . . . . . . . . . . . . . . . 2-3-26
2.3.25 Tracking Through a Math Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-27
2.3.26 Continuous Faceplate Screen—Piecewise Linear
Interpolator Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-30
2.3.27 Continuous Links Screen—Piecewise Linear
Interpolator Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-31

CB: vi
2.3.28 Example of a Piecewise Linear Interpolator Application . . . . . . . . . . . . 2-3-32

2.3.29 Continuous Faceplate—Example of a Piecewise Linear
Interpolator Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-33
2.3.30 Continuous Faceplate Screen—Polynomial Function . . . . . . . . . . . . . . 2-3-34
2.3.31 Continuous Links Screen—Polynomial Function . . . . . . . . . . . . . . . . . . 2-3-35
2.3.32 Example of a Polynomial Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-36
2.3.33 Continuous Faceplate Screen—Example of a Polynomial Application 2-3-37
2.3.34 Ratio/Bias Used as a Boiler Master . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-38
2.3.35 Continuous Faceplate Screen—Ratio/Bias Function . . . . . . . . . . . . . . . 2-3-39
2.3.36 Continuous Links Screen—Ratio/Bias Function . . . . . . . . . . . . . . . . . . . 2-3-39
2.3.37 Example of Bias Bar Scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-42
2.3.38 Signal Selector Functional Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . 2-3-43
2.3.39 Continuous Faceplate Screen—Signal Selector Function . . . . . . . . . . . 2-3-44
2.3.40 Continuous Links Screen—Signal Selector Function . . . . . . . . . . . . . . . 2-3-45
2.3.41 Example of a Signal Selector Function . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-46
2.3.42 Setpoint Totalizer Functional Block Diagram . . . . . . . . . . . . . . . . . . . . . . 2-3-47
2.3.43 Continuous Faceplate Screen—Setpoint Totalizer Function . . . . . . . . . 2-3-48
2.3.44 Setpoint Totalizer Cutoff Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-49
2.3.45 Continuous Links Screen—Setpoint Totalizer Function . . . . . . . . . . . . . 2-3-50
2.3.46 Stack Totalizer Functional Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . 2-3-51
2.3.47 Continuous Faceplate Screen—Stack Totalizer Function . . . . . . . . . . . 2-3-52
2.3.48 Continuous Links Screen—Stack Totalizer Function . . . . . . . . . . . . . . . 2-3-54
2.3.49 Continuous Faceplate Screen—Velocity Limiter Function . . . . . . . . . . . 2-3-58
2.3.50 Continuous Links Screen—Velocity Limiter Function . . . . . . . . . . . . . . . 2-3-59
2.4.1 Typical Discrete Function Control Loop . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-2
2.4.2 Example of a Discrete Motor Controller Control Loop . . . . . . . . . . . . . . 2-4-6
2.4.3 Discrete Faceplate for a Typical DMC . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-7
2.4.4 Default Continuous Faceplate Screen—DMC . . . . . . . . . . . . . . . . . . . . . 2-4-8
2.4.5 Default Continuous Links Screens—DMC . . . . . . . . . . . . . . . . . . . . . . . . 2-4-10
2.4.6 Default Discrete Links Screen—DMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-11
2.4.7 Default Discrete Faceplate Screen—DMC . . . . . . . . . . . . . . . . . . . . . . . 2-4-11
2.4.8 Example of a Discrete Auto Sequence Motor Controller Control Loop 2-4-14
2.4.9 Interlock Function for a DASMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-15
2.4.10 Discrete Faceplate for a DASMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-16
2.4.11 Default Continuous Faceplate Screen—DASMC . . . . . . . . . . . . . . . . . . 2-4-17
2.4.12 Default Continuous Links Screens—DASMC . . . . . . . . . . . . . . . . . . . . . 2-4-19
2.4.13 Default Discrete Links Screen—DASMC . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-20
2.4.14 Default Discrete Faceplate Screen—DASMC . . . . . . . . . . . . . . . . . . . . . 2-4-20

CB: vii
2.4.15 Example of a Discrete Dual Speed Motor Controller Control Loop . . . 2-4-23
2.4.16 Discrete Faceplate for a DDSMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-24
2.4.17 Default Continuous Faceplate Screen—DDSMC . . . . . . . . . . . . . . . . . . 2-4-25
2.4.18 Default Continuous Links Screens—DDSMC . . . . . . . . . . . . . . . . . . . . . 2-4-27
2.4.19 Default Discrete Links Screen—DDSMC . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-28
2.4.20 Default Discrete Faceplate Screen—DDSMC . . . . . . . . . . . . . . . . . . . . . 2-4-28
2.4.21 Example of a Discrete Dual Direction Motor Controller Control Loop . 2-4-31
2.4.22 Discrete Faceplate for a DDDMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-32
2.4.23 Default Continuous Faceplate Screen—DDDMC . . . . . . . . . . . . . . . . . . 2-4-33
2.4.24 Default Continuous Links Screens—DDDMC . . . . . . . . . . . . . . . . . . . . . 2-4-35
2.4.25 Default Discrete Links Screen—DDDMC . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-36
2.4.26 Default Discrete Faceplate Screen—DDDMC . . . . . . . . . . . . . . . . . . . . . 2-4-36
2.4.27 Example of a Discrete Valve Controller Control Loop . . . . . . . . . . . . . . 2-4-42
2.4.28 Discrete Faceplate for a DVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-43
2.4.29 Default Continuous Faceplate Screen—DVC . . . . . . . . . . . . . . . . . . . . . 2-4-44
2.4.30 Default Continuous Links Screens—DVC . . . . . . . . . . . . . . . . . . . . . . . . 2-4-46
2.4.31 Default Discrete Links Screen—DVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-47
2.4.32 Default Discrete Faceplate Screen—DVC . . . . . . . . . . . . . . . . . . . . . . . . 2-4-47
2.4.33 Example of a Discrete Auto Sequence Valve Controller Control Loop 2-4-50
2.4.34 Discrete Faceplate for a DASVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-51
2.4.35 Default Continuous Faceplate Screen—DASVC . . . . . . . . . . . . . . . . . . 2-4-52
2.4.36 Default Continuous Links Screens—DASVC . . . . . . . . . . . . . . . . . . . . . . 2-4-54
2.4.37 Default Discrete Links Screen—DASVC . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-55
2.4.38 Default Discrete Faceplate Screen—DASVC . . . . . . . . . . . . . . . . . . . . . 2-4-55
2.4.39 Example of a Discrete Motorized Valve Controller Control Loop . . . . . 2-4-58
2.4.40 Discrete Faceplate for a DMVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-60
2.4.41 Default Continuous Faceplate Screen—DMVC . . . . . . . . . . . . . . . . . . . 2-4-61
2.4.42 Default Continuous Links Screens—DMVC . . . . . . . . . . . . . . . . . . . . . . . 2-4-63
2.4.43 Default Discrete Links Screen—DMVC . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-64
2.4.44 Default Discrete Faceplate Screen—DMVC . . . . . . . . . . . . . . . . . . . . . . 2-4-65

CB: viii
List of Tables
Table Page
2.1.1 Continuous Faceplate Configuration Line Fields . . . . . . . . . . . . . . . . . . . 2-1-7
2.1.2 Control Block Modes and Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1-9
2.1.3 Continuous Faceplate Screen Common Fields . . . . . . . . . . . . . . . . . . . 2-1-11
2.2.1 Summary of Default PID Control Algorithms . . . . . . . . . . . . . . . . . . . . . . 2-2-3
2.2.2 PID Algorithm Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-3
2.2.3 Proportional Term Algorithms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-5
2.2.4 Derivative Term Algorithms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-8
2.2.5 P, I, and D Configuration Fields on Continuous Faceplate Screen . . . 2-2-15
2.2.6 ControlBlock/AOB Tracking Situations . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-24
2.2.7 Ratio Option Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-35
2.2.8 Bias Option Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-37
2.2.9 Gap Option Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-40
2.2.10 Deadband Option Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-41
2.3.1 ControlBlock Continuous Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-1
2.3.2 Dead Time Function Continuous Faceplate Fields . . . . . . . . . . . . . . . . . 2-3-5
2.3.3 Lead/Lag Function Continuous Faceplate Fields . . . . . . . . . . . . . . . . . . 2-3-15
2.3.4 Math Function Continuous Faceplate Fields . . . . . . . . . . . . . . . . . . . . . . 2-3-18
2.3.5 Piecewise LInear Interpolator Function Continuous Faceplate
Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-31
2.3.6 Polynomial Function Continuous Faceplate Fields . . . . . . . . . . . . . . . . . 2-3-35
2.3.7 Ratio/Bias Function Continuous Faceplate Fields . . . . . . . . . . . . . . . . . 2-3-40
2.3.8 Ratio Term Continuous Faceplate Configuration . . . . . . . . . . . . . . . . . . 2-3-41
2.3.9 Bias/Pre-bias Term Comparison . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-41
2.3.10 Signal Selector Function Continuous Faceplate Fields . . . . . . . . . . . . . 2-3-44
2.3.11 Setpoint Totalizer Function Continuous Faceplate Fields . . . . . . . . . . . 2-3-49
2.3.12 Stack Totalizer Function Continuous Faceplate Fields . . . . . . . . . . . . . 2-3-53
2.3.13 Example of Totalizer Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-55
2.3.14 Maximum Integration Times for Various Input Maximums . . . . . . . . . . . 2-3-56
2.3.15 Velocity Limiter Function Continuous Faceplate Fields . . . . . . . . . . . . . 2-3-58
2.4.1 Discrete Motor Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-3
2.4.2 Effect of Motor Controller Block Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-5
2.4.3 Required LInks for DMC Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-7
2.4.4 Configuration Options--DMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-9

CB: ix
2.4.5 Discrete Input Functions and Output Conditions--DMC . . . . . . . . . . . . . 2-4-12

2.4.6 Continuous Input Functions--DMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-13
2.4.7 Required Links for DASMC Configuration . . . . . . . . . . . . . . . . . . . . . . . . 2-4-16
2.4.8 Configuration Options--DASMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-18
2.4.9 Discrete Input Functions and Output Conditions--DASMC . . . . . . . . . . 2-4-21
2.4.10 Continuous Input Functions--DASMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-22
2.4.11 Required Links for DDSMC Configuration . . . . . . . . . . . . . . . . . . . . . . . . 2-4-24
2.4.12 Configuration Options--DDSMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-26
2.4.13 Discrete Input Functions and Output Conditions--DDSMC . . . . . . . . . . 2-4-29
2.4.14 Continuous Input Functions--DDSMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-30
2.4.15 Required Links for DDDMC Configuration . . . . . . . . . . . . . . . . . . . . . . . . 2-4-32
2.4.16 Configuration Options--DDDMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-34
2.4.17 Discrete Input Functions and Output Conditions--DDDMC . . . . . . . . . . 2-4-37
2.4.18 Continuous Input Functions--DDDMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-38
2.4.19 Discrete Valve Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-39
2.4.20 Effect of Valve Controller Block Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-41
2.4.21 Required Links for DVC Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-43
2.4.22 Configuration Options--DVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-45
2.4.23 Discrete Input Functions and Output Conditions--DVC . . . . . . . . . . . . . 2-4-48
2.4.24 Continuous Input Functions--DVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-49
2.4.25 Required Links for DASVC Configuration . . . . . . . . . . . . . . . . . . . . . . . . 2-4-51
2.4.26 Configuration Options--DASVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-53
2.4.27 Discrete Input Functions and Output Conditions--DASVC . . . . . . . . . . . 2-4-56
2.4.28 Continuous Input Function--DASVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-57
2.4.29 Required Links for DMVC Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-59
2.4.30 Configuration Options--DMVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-62
2.4.31 Discrete Input Functions and Output Conditions--DMVC . . . . . . . . . . . . 2-4-66
2.4.32 Continuous Input Functions--DMVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4-67

CB: 2-1-1
Section 1:
Configuring Common Fields on the Continuous
Faceplate
This section describes how to configure a continuous faceplate and the

common fields on the Continuous Faceplate screen. Fields that are
specific to a particular function are described later in this chapter.
You use the Continuous Faceplate screen to configure the block’s major
function, the continuous faceplate, the output high and low limits, and
other information. The major function of a ControlBlock determines
whether the ControlBlock is to be used to control a process, alter a
signal, or perform a user-defined function. The continuous faceplate
provides a display of up to four continuous values. The output limits
define alarm limits for the continuous output. You can also configure
other information for the ControlBlock depending on its function. The
shaded box in Figure 2.1.1 shows the Continuous Faceplate screen
among the other configuration screens for ControlBlock =1A--4.
RS3: Configuring ControlBlock Functions Configuring Common Fields on the Continuous Faceplate
CB: 2-1-2
ControlBlock =1A--4
FACEPLATE FACEPLATE
[ EXCH ]
CB CONTINUOUS
LINKS
A to G
[ EXCH ]
CB DISCRETE LINKS
[ PAGE ]
CB CONTINUOUS
LINKS
H to O
[ EXCH ]
[ PAGE ] [ PAGE ]
DIAGRAM [ EXCH ] DIAGRAM
A a
BLOCK REFERENCES
[ PAGE ] = [PAGE AHEAD] and [PAGE BACK] keys
Figure 2.1.1. Continuous Faceplate Screen Among ControlBlock Screens
CB: 2-1-3
Calling Up a Continuous Faceplate Screen

- To call up a Continuous Faceplate screen:
D For a continuous function ControlBlock, press
[EXCH], type the tag or address of the ControlBlock, and press
[ENTER].
or
D For a discrete function ControlBlock, press [BLOCK
FACEPLATE], type the tag or address of the ControlBlock, and
press [ENTER]. Press [EXCH].
or
D For a continuous function ControlBlock from a group display or a
Process Graphic display, cursor to a faceplate and press
[SELECT].
or
D For a discrete function ControlBlock from a group display or a
Process Graphic display, cursor to a faceplate and press
[SELECT]. Press [EXCH].
Figure 2.1.2 shows a flowchart of ControlBlock faceplate screens.
CB: 2-1-4
GROUP DISPLAY
or 1. Press [BLOCK FACEPLATE].
2. Type a tag or address and
GRAPHIC DISPLAY
press [ENTER].
Cursor to a faceplate
and press [SELECT]
CB CONTINUOUS CB CONTINUOUS CB CONTINUOUS

FACEPLATE FACEPLATE FACEPLATE
[PAGE] [PAGE]
(previous address) (next address)
[EXCH]
CB DISCRETE
FACEPLATE
[PAGE] = [PAGE AHEAD] and [PAGE BACK] keys
Figure 2.1.2. Calling Up a ControlBlock Continuous Faceplate Screen
CB: 2-1-5
Configuring a Continuous Faceplate
You can configure the continuous faceplate to display values for up to

four ControlBlock continuous inputs and the ControlBlock continuous
output. You can configure the faceplate from the line directly above the
faceplate (the configuration line).
Figure 2.1.3 describes how to configure the items to be displayed on the

continuous faceplate from the configuration line. Table 2.1.1 describes
the configuration line fields.
Figure 2.1.4 shows how to configure a continuous faceplate so that an

input value can be changed by the operator using the slewing keys on
the loop operation panel.
CB: 2-1-6
The input fields determine the

content of the top portion of the
faceplate and the vertical bars.
These arrows show the

faceplate items that are
Þ OUTÞA ÞBÞCÞD related to the first input field
in the configuration line.
A 290.
B 150.
C 132.
D 210.
The output/deviation field in the
configuration line determines the
content of the bottom portion of the 100--
faceplate.
75--
50--
25--
0--
32.47
Faceplate scaling:
0 = Eng Zero
100 = Eng Max
OUT GPM
Figure 2.1.3. Continuous Faceplate Configuration
CB: 2-1-7
Table 2.1.1. Continuous Faceplate Configuration Line Fields
Access Allowable
Field Description
Level Entries
Determines the content of the bottom of the faceplate

including value, horizontal bar, and units.
OUT = continuous output
All other entries display a zero-centered bar that represents
the deviation of the first input field from the second input field.
The entries display different percentages of the engineering
units scale on the horizontal bar. The engineering units scale
is configured on the Continuous Links screen.
DEV = Maximum length of bar is 100% of scale. NONE, OUT,
Output/ DV2 = Maximum length of bar is 50% of scale. DEV, DV2,
Deviation Conf DV3 = Maximum length of bar is 20% of scale. DV3, DV4,
field DV4 = Maximum length of bar is 10% of scale. DV5, DV6
DV5 = Maximum length of bar is 5% of scale.
DV6 = Maximum length of bar is 2% of scale.
As an example, if an input register has an engineering scale of
0 to 200 units and an entry of DV4 (10% of scale), then the
output/deviation bar reaches its maximum length when the
deviation is 10% of scale, or 20 units (10% of 200).
NOTE: If a deviation display is selected, the block output is
not displayed on the faceplate and cannot be adjusted from
the faceplate.
Determines the first input register for the faceplate. The first
First input value shown in the top part of the faceplate is the value of the
Conf NONE, A to O
field first register, and the first bar from the left corresponds to this
register.
Determines the second input register for the faceplate. The

second value shown in the top part of the faceplate is the
Second input NONE, A to O
Conf value of the second register, and the second bar from the left
field corresponds to this register. Default=B
This field defaults to being selected and is highlighted.
Determines the third input register for the faceplate. The third
Third input value shown in the top part of the faceplate is the value of the NONE, A to O
Conf
field third register, and the third bar from the left corresponds to this Default=C
register.
Determines the fourth input register for the faceplate. The

Fourth input fourth value shown in the top part of the faceplate is the value NONE, A to O
Conf
field of the fourth register, and the fourth bar from the left Default=D
corresponds to this register.
NOTE: Bold text indicates default selections.
CB: 2-1-8
The input register that is -

backlighted indicates the To configure
possibility of operator control operator-enterable input:
of the input value by using the D Configure the input value as
setpoint slewing keys on the an *Entry type on the
operator keyboard. Continuous Links screen.
ÞOUTÞAÞBÞCÞD
The possibility of A - To configure a new input

operator control is also 290.
B register as the one that can be
indicated by a vertical 150. changed by the operator:
double arrow in front C 132.
of the variable value. D Cursor to the new input
D 210. register and press [SELECT].
100-- - To have no input registers

configured as changeable by
the operator:
75-- 1. Cursor to the input register
that is backlighted.
2. Press [ENTER] to delete that
50--
input register from the
faceplate.
25-- 3. Reenter the input register
letter.
0--
32.47
OUT
GPM
Figure 2.1.4. Configuring Operator-enterable Input
CB: 2-1-9
Effect of Block Mode on the Block Output
The ControlBlock output is dependent on the block mode. The “Block

Mode” field, located in the lower right corner of all ControlBlock screens,
allows you to enter the ControlBlock mode. Table 2.1.2 lists each of the
ControlBlock modes and describes how the mode affects the behavior
of the continuous output Q for the continuous function ControlBlocks.
NOTE: If the “Block Mode” field blinks between the current block mode
and “Standby”, it means that the Controller Processor is in Standby.
Table 2.1.2. Control Block Modes and Functions
ControlBlock Functions
ControlBlock
Modes PID Functions All Other Continuous Functions
Auto D Q is controller function driven. D Q is function driven.

D Q can be overridden by logic. D Q can be overridden by logic.
D Controller function responds to local
setpoint (LS).
Comp SP D Q is controller function driven. D N/A

D Q can be overridden by logic.
D Controller function responds to local
setpoint (LS), which is determined by
supervisory computer.
D See PW: 1.
DDC D Q is determined by supervisory D Q is determined by supervisory

computer. computer.
D See PW: 1. D See PW: 1.
Local D Operator directly manipulates Q from D Operator directly manipulates Q

console. from console.
D Q cannot be overridden by logic. D Q cannot be overridden by logic.
Manual D Operator directly manipulates Q from D Operator directly manipulates Q

(or Operator) console. from console.
D Q can be overridden by logic. D Q can be overridden by logic.
Remote D Q is controller function driven. D N/A

D Q can be overridden by logic.
D Controller function responds to
remote setpoint (RS).
D This is a normal mode for cascade
secondary.
CB: 2-1-10
Common Fields on the Continuous Faceplate Screen
Certain fields appear on the Continuous Faceplate screen for all

continuous major functions. Figure 2.1.5 shows these common fields.
Table 2.1.3 describes these common fields.
Other fields for Continuous Faceplate screen configuration appear,

depending on the function of the ControlBlock.
D For a description of the fields specific to Proportional, Integral,
and Derivative (PID) type functions, see Section 2.
D For a description of the fields specific to continuous type
functions, excluding PID functions, see Section 3.
D For a description of the fields specific to discrete type functions,
see Section 4.
CB CONTINUOUS FACEPLATE 27-May-92 09:52:59

Shed
Tag > Desc > Mode> NONE >OUT>A>B>C>D
SC>N +--------+
Addr Function > A | .00 |
INPUTS Value Units Tag OUTPUT B | |
>.00 C | |
D | |
100-+--------+
+ |
75-+ |
+ |
50-+ |
+ |
25-+ |
+ |
Output: 0-+--------+
Mn Rate Lim >None | .00 |
OUT | |
High Lim >100.00 | |
+--------+
Low Lim >.00
Block Mode> LOCAL
FULL CONFIG 1
Figure 2.1.5. Continuous Faceplate Screen Common Fields
CB: 2-1-11
Table 2.1.3. Continuous Faceplate Screen Common Fields
Access
Field Description Allowable Entries
Level
Addr N/A Address of the ControlBlock. Display only
LOCAL, MANUAL, Auto,

Block Mode Oper Current block mode.
Computer, Remote
Used with the Supervisory Computer Interface

(SCI) to specify the value to which the SCI can
write. This field only appears when a Shed Mode
is configured.
DDC/CSP Conf If “DDC”, the SCI can write to the output of the DDC, CSP
block. The block acts as if it is in Manual mode.
If “CSP”, the SCI can write to the B value (local
setpoint) of the block. The block acts as if it is in
Auto mode. For PID-type blocks only.
Maximum 24
Desc Conf Block descriptor you assigned.
alphanumeric characters
Function Conf Major function of the ControlBlock. Function mnemonic
Any of the first four input registers that you

configured. Continuous registers A, B, C, and D
Inputs N/A are sometimes referred to and displayed as PV, Display only
LS, RS, FF, or other mnemonics, depending on
the block function.
Value Oper Current value of the associated input. --999999. to 999999.
Units of the associated input value as listed on

Units N/A Display only
the Continuous Links screen.
Tag of the input source. If the source is within this

Tag N/A Display only
ControlBlock, no tag is shown.
Defined by output high and

Output Oper Current continuous output value.
low limits
Output: Manual output rate-of-change limit expressed in None, A to 0

Supr percentage of units per second. This limit applies
Mn Rate Lim only if the block mode is Local or Manual. .00 to 999999.
None, A to O
High Lim Supr High limit of the output. --999999. to 999999.
Default=100.00
None, A to O
Low Lim Supr Low limit of the output. --999999. to 999999.
Default=.00
(continued on next page)
CB: 2-1-12
Table 2.1.3. Continuous Faceplate Screen Common Fields (continued)
Access
Level

(SCI) to specify the SCI write permission for this
SC Conf block. Y (yes), N (no)
If “Yes”, the SCI can write to any writable block
values except those used by DDC or CSP.

(SCI) to specify the block mode when the SCI
Timer on the ControlFile Status screen expires.
Each block in a ControlFile has an SCI timer. The
SCI Timer begins when the Computer button is NONE, MANUAL, AUTO,
Shed Mode Conf
pressed and resets whenever the SCI writes to REMOTE
that block. If the timer expires before an SCI write
occurs, the block goes into the configured Shed
Mode.
Must be configured to use the SCI write function.
Up to 16 alphanumeric
characters, at least one of
Tag Conf Block tag you assigned.
which must be an
alphabetical character
CB: 2-2-1
Section 2:
Configuring PID Functions
This section describes the proportional, integral, and derivative (PID)

ControlBlock functions and the PID algorithm. This section also
describes the action of PID functions in a feedback control loop and in a
cascade control loop. In addition, this section provides the PID function
options.
PID Controller Functions
A ControlBlock with a PID-type function performs some combination of

proportional, integral, and derivative control. Any combination of PID
control can be configured for a ControlBlock (P, PI ,PID, I, ID, PD, D, or
IB). Figure 2.2.1 shows a typical PID control loop.
Field Field
Device Device
Flow measurement or
process variable Open/close
valve
Controller Card
Analog Analog
FIC Input Control
Block Output FIC Q
PV Block Block
Operator controls
the setpoint
Figure 2.2.1. Typical PID Control Loop
RS3: Configuring ControlBlock Functions Configuring PID Functions

CB: 2-2-2
PID Control Algorithm
The default control algorithm used by the PID ControlBlock is a position

algorithm. The actual control algorithm used depends on the
combination of proportional (P), integral (I), and derivative (D) terms you
configure. Figure 2.2.2 shows the relationship of the terms in the
position algorithm. The terms are added to form combinations of PID
control.
You can vary the default algorithm by changing the algorithm used to
calculate each term, by selecting a velocity algorithm instead of the
position algorithm, or by configuring ratio, bias, gap, or deadband.
These options are discussed later in this chapter.
PV PVf
FILTER* P
I + + Q
*Only if D term is selected Kf ´ FF
PV= Linked value of process variable

PVf= Filtered value of process variable FF
P = Proportional term
I = Integral term
D = Derivative term
Kf = Feedforward gain
FF = Feedforward
Q = Output
Figure 2.2.2. Position Algorithm
Table 2.2.1 summarizes the default control algorithms for the possible
combinations of PID control. For variations on each algorithm, see the
discussions of each term on the following pages. Table 2.2.2 defines the
terms of the equations.

CB: 2-2-3
Table 2.2.1. Summary of Default PID Control Algorithms
Block Function Algorithms
PID Q = [K(SP–PV f )] + [I′ + K  

Ts
Ti
T
 
(SP–PV f )] + [K d (PV f′–PVf )]
Ts
P Q = K(SP–PV) + manual reset
I Q = I′ + K  Ts
Ti
(SP–PV)
D Q=K  
Td
Ts
(PVf ′–PV f)
PI Q = [K(SP–PV)] + I′ + K  
Ts
Ti
(SP–PV)]
PD Q = [K(SP–PV f)] + [K  
Td
Ts
(PVf′–PV f)]
ID Q = [I′ + K  
Ts
Ti
T
 
(SP–PV f)] + [K d (PVf′–PV f)]
Ts
Table 2.2.2. PID Algorithm Terms
Parameter Description
Q Function output
K Controller gain or 100/proportional band, as preferred
SP Setpoint
PV Input A—linked value of process variable
PVf Filtered value of process variable. Used if derivative term is selected.
PVf’ Previous value of PVf
I’ Previous value of I
Ts Sample time—the greater of the ControlBlock sample time, if configured, or

the Controller Processor card scan time
Ti Integral time constant
Td Derivative time constant

CB: 2-2-4
The following pages give a brief explanation for each term in the PID
algorithm:
D Proportional term
D Integral term
D Derivative term
D Feedforward
The explanations show how each term is calculated, and note other
possible forms of the terms that can be configured. A short discussion
of the velocity algorithm follows the explanations of the terms in the
position algorithm.
Applications
The less common forms and subsets of the PID algorithm, along with
many of the options, are available for those who need tools to solve
unusual control problems and for advanced applications. This manual,
therefore, does not attempt to suggest applications where these
features might be used.

CB: 2-2-5
Proportional Term
Proportional control responds immediately and directly to a change in

process variable (PV) or setpoint (SP). Proportional control does not act
to reduce the error signal to zero.
The proportional term can be calculated in several ways, depending on:

D The entry you select in the “PI Act” field on the Continuous
Faceplate screen
D Your selection of gain or proportional band on the Console
Configuration screen
Table 2.2.3 shows the algorithms you can configure for calculating the
proportional term.
Table 2.2.3. Proportional Term Algorithms
Entry in “PI Act”

P Term Using Gain P Term Using Proportional Band
Field
ERR (default) P = K (SP--PV) P = SP − PV

PB
PV P = K ´ PV P = PV
PB
SP P = K ´ SP P = SP
PB
Error Squared Option
The Error Squared option modifies the algorithm so that the SP--PV
term is replaced by the term |SP--PV| x (SP--PV).
Select the Error Squared option with the “Opt” field on the Continuous
Faceplate screen. The Error Squared option is available in these terms:
D Error Sq
D Gap/Err Sq
D Ratio/Esq
D Ra/Gap/Esq
D Bias/Esq
D Bi/Gap/Esq
D Vel/Esq
D Ve/Gap/Esq
No new fields appear when you select Error Squared.

CB: 2-2-6
Integral Term
Integral control works to return the process variable to the setpoint.

Integral control compensates for load changes and process
nonlinearities. The integral term continues to increase or decrease with
each iteration until the error signal (SP--PV) is zero. The value of the
integral time (Ti) determines how much the integral term changes with
each evaluation. The smaller the value of integral time, the faster the
controller responds.
Integral term: l = l′ + K TT  (SP – PV)

s
Where I’ is the value of I from the previous

evaluation.
Integral Bilinear (IB) Function
The IB function is an alternate form of an Integral-only controller that

uses the change in the error signal instead of just its current value. The
following equation calculates the output of the IB controller.
Q =I+ TT (SP–PV) +2 (SP′–PV′)

s
i
Select the IB function in the “Function” field on the Continuous

Faceplate screen when you configure the block.
Error Squared Option
The Error Squared option modifies the algorithm so that the SP--PV
term is replaced by the term |SP--PV| x (SP--PV).
For information on selecting the Error Squared option, see the

“Proportional Term” section.

CB: 2-2-7
Integral Windup
To prevent integral windup, the integral term is calculated using the

following alternate algorithm:
I = Q -- P
The alternate algorithm is used automatically if the output is constrained

for any of the following reasons:
D The output is at its limit.
D The control mode is MANUAL or LOCAL.
D Logic is constraining the output.
D An analog output block (AOB) is in MANUAL.
D Tracking is active (constraining the output).
When the constraint goes away, the default algorithm is automatically

used again.

CB: 2-2-8
Derivative Term
Derivative control responds to the rate of change of the process variable

(PV). Derivative control adds to the output immediately to overcome the
momentum of the upset. Derivative control is used where large
measurement lags exist, in conjunction with proportional control or with
proportional and integral control. The larger the derivative time (Td), the
greater the derivative response.
CAUTION
Because derivative action can cause large and sudden
changes in the output, it can cause severe problems if
applied or tuned improperly.
The derivative term can be calculated in several ways, depending on:

D The entry you select in the “D Act” field on the Continuous
Faceplate screen
D Your selection of gain or proportional band on the Console
Configuration screen
Table 2.2.4 shows the algorithms you can configure for calculating the
derivative term.
Table 2.2.4. Derivative Term Algorithms
Entry in
“D Act” D Term Using Gain D Term Using Proportional Band
Field
PV
(default) D=K  
Td
Ts
(PVf′ –PVf) D=  
Td
Ts
PVf′–PV f
PB

SP D=K  
Td
Ts
(SP′–SP) D=  
Td
Ts
SP′–SP
PB

ERR D=K  
Td
Ts
(SP′–PVf′)–(SP–PV f′) D=  
Td
Ts
(SP′–PVf′)–(SP–PV f)
PB


CB: 2-2-9
Input Filtering
If you configure a controller combination that uses the D term, then the
process variable is filtered before it is used in the P, I, and D
calculations.
If filtering takes place, replace PV with PVf in the algorithms for the P
and I terms.
Ts
PV f = PVf′ + (PV + PV′–2PV f′)
Ts + 2Tf
where:
Tf = MAX (2Ts , Td / 8)
or
if D only, as entered on Continuous Faceplate screen
PVf’ = Previous value of PVf
PV’ = Previous value of PV
NOTE: Because of input filtering, the response of a PID controller with

Td = 0 is different than the response of a PI controller with the same
gain and integral time.

CB: 2-2-10
Feedforward
Feedforward improves process control by measuring disturbances to

the process and calculating changes in the control output to offset the
disturbances. An external feedforward signal can be brought into input
D, multiplied by feedforward gain (Kf), and added to the output. The
advantage of adding feedforward to the PID function is that, when
required, the effect of feedforward offsets the effect of the slow integral
time.
Feedforward cannot be used in a PID controller configured with ratio or

bias.
Figure 2.2.3 shows a feedforward control system for a heat exchanger.

The inlet flow transmitter signal is sent to the ControlBlock, which
determines an output to the steam valve that compensates for the
change in flow and maintains the desired outlet temperature.
Steam FF
+
Kf ´ FF
Q ControlBlock
P+I+D
+
SP
PV
Inlet Outlet
Flow FT Temp
TT
Transmitter Transmitter
Heat
Exchanger
Figure 2.2.3. Typical Feedforward Control

CB: 2-2-11
Velocity Algorithm
The commonly used position algorithm calculates the controller output,

Q. The velocity algorithm calculates only the change in output, DQ, from
one evaluation to the next. DQ must be summed with another value,
called the base, to arrive at the output to the final control element.
DQ = DP + DI + DD + Kf DFF
∆P = K {(SP–PV)–(SP′–PV′)}
KT s
∆I = (SP–PV)
Ti
KT d
∆D = (PV–2PV′ + PV′′)
Ts
Q = DQ + base
The base is either:

D The value linked to input E, or
D The previous value of Q if nothing is linked to E.
The D input, when used with the velocity algorithm, must represent only
the change in the feedforward value, DFF.
- To calculate DFF in a logic step:
1. Link the feedforward (FF) variable to input F instead of input D.
2. Configure input D as a *VALUE.
3. Configure input G as a *VALUE.
4. Write the following calculations in an unused logic step
D=F--G; G=F
This set of calculations first subtracts the previous FF value G from the
current value F to compute DFF, then stores the current FF value in G
for the next iteration.

CB: 2-2-12
Select the velocity algorithm in the “Opt” field on the Continuous

Faceplate screen. The algorithm is available in these options:
D Velocity
D Vel/Gap
D Vel/DdB
D Vel/Esq
D Vel/Gap/DdB
D Ve/Gap/Esq
No new fields appear when you select velocity.

CB: 2-2-13
Configuring PID Control
Use the Continuous Faceplate screen to configure controllers for any

combination of P, I, and D control. Figure 2.2.4 shows the Continuous
Faceplate screen. The shaded areas are common to all ControlBlocks
that use a combination of P, I, and D control. Table 2.2.5 describes the
fields in the shaded areas. Some of the fields in the shaded areas are
specific to only one type of control, so some of the fields may not
appear on the screen, depending on the type of controller you have
configured.
Figure 2.2.5 shows the Continuous Links screen for any controller that
uses a combination of P, I, and D control.
For a description of the fields that are common to all continuous function
ControlBlocks, see Section 1.
User-enterable tuning parameters fields User-selectable control action fields
CB CONTINUOUS FACEPLATE
27-Jul-92 09:52:59
Shed
SC>N +--------+
Addr =1A-01 Function >PID Controller PI Act>Err D Act>PV PV | .00 |
INPUTS Value Units Tag OUTPUT LS | .00 |
PV >.00 >.00 >Reverse RS | |
LS >.00 Action FF | |
RS 100-+--------+
FF Opt>None + |
75-+ |
Prop Band >100. Integ Time >1. M Deriv Time >0. S + |
50-+ |
FF Gain >0. Filter Time>0. S + |
25-+ |
LS-PV Track>no Track Input>None + |
Setpoint: Output: 0- +------- +
Rate Lim >None Mn Rate Lim >None | .00 |
OUT | |
High Lim >100.00 High Lim >100.00 | |
+--------+
Low Lim >.00 Low Lim >.00
Block Mode> AUTO
FULL CONFIG 1
User-enterable setpoint limits fields User-selectable tracking fields
“Filter Time” field appears when you

configure derivative control only.
Figure 2.2.4. Continuous Faceplate Screen—Combinations of P, I, and D Control

CB: 2-2-14
CB CONTINUOUS LINKS 27-Jul-92 09:52:59

Tag Descriptor
INPUT SOURCE Conv Hold Eng Zero Eng Max Value Units
PV >*ENTRY Þ.00 Þ100.00 >.00 Þ
LS >*ENTRY PV Þ.00 Þ100.00 >.00 Þ
RS >*NONE LS Þ.00 Þ100.00 Þ.00 Þ
FF >*NONE Q Þ.00 Þ100.00 Þ.00 Þ
E >
F >
G >
Q Þ.00 Þ100.00 >.00 Þ
Steps in Manual Block Mode> AUTO
CONFIG 1
Figure 2.2.5. Continuous Links Screen—PID Function

CB: 2-2-15
Table 2.2.5. P, I, and D Configuration Fields on Continuous Faceplate Screen
Access
Level
Specifies whether the controller output is reverse or

direct acting. The field selections are in accordance
with ISA definitions and describe the response of the
controller output with respect to the error (SP--PV).
Action Conf Reverse, Direct
“Reverse” indicates that an increasing controller
output is the result of a decreasing process variable.
NOTE: If the ControlBlock “Function” is changed,
this field returns to the default.
Lets you vary the algorithm used to calculate the D

term. For more information, see the discussion of the
D Act Conf “Derivative Term” section. SP, PV, Err
Appears when you configure derivative control or a
combination that includes derivative control.
Derivative action time constant (rate time). You must

enter S (seconds), M (minutes), or H (hours) after PV, LS, RS, FF, E to O,
Deriv Time Supr the numeric value. 0 S to 999999 H
Appears when you configure derivative control or a Default=0. S
combination that includes derivative control.
PV, LS, RS, FF, E to O,

Feedforward term gain. For more information, see --999999. to
FF Gain Supr the discussion of the feedforward term in the “PID 999999.
Algorithm” section.
Default=0.
For the definition of filter time, see the discussion of PV, LS, RS, FF, E to O,
Filter Time Supr input filtering in the “Derivative Term” section. 0 S to 999999 H
Appears when you configure derivative control only. Default=0. S
Integral action time constant (reset time). You must

enter S (seconds), M (minutes), or H (hours) after PV, LS, RS, FF, E to O,
Integ Time Supr the numeric value. 0 S to 999999 H
Appears when you configure integral control or a Default=1. M
combination that includes integral control.
Specifies whether the LS input tracks the PV input

when the ControlBlock is in Manual or Local.
LS--PV Track Supr If “Yes”, LS tracks PV when the block mode is Local yes, no
or Manual, or when output is tracking. For more
information, see page 2-2-19.

CB: 2-2-16
Table 2.2.5. P, I, and D Configuration Fields on Continuous Faceplate Screen (continued)
Access
Level
None, Ratio, Bias,

Lets you specify combinations of options to the basic Gap, Dead Band, Error
PID algorithm. For discussions of the algorithm and Sqr, Gap/DBand,
options, see the “PID Algorithm” and “PID Controller Gap/Err Sq, Ratio/Gap,
Options” sections. Ratio/DdB, Ratio/Esq,
Ra/Gap/DdB,
Opt Conf Clarification of abbreviations: Ra/Gap/Esq, Bias/Gap,
Dead Band=DBand=DdB Bias/DdB, Bias/Esq,
Error Squared=Error Sqr=Err Sq=Esq Bi/Gap/DdB,
Ratio=Ra Bi/Gap/Esq, Velocity,
Bias=Bi Vel/Gap, Vel/DdB,
Velocity=Vel=Ve Vel/Esq, Ve/Gap/DdB,
Ve/Gap/Esq
Lets you vary the algorithm used to calculate the P

term. For more information, see the discussion of the
PI Act Conf proportional term in the “PID Algorithm” section. SP, PV, Err
Appears when you configure a combination that
includes proportional and integral control.
Proportional Band or Controller Gain. The field that

appears depends on the “PID Proportional” field on PV, LS, RS, FF, E to O,
Prop Band the Console Configuration screen. (See CC: 1.) .000001 to 999999
Supr (Prop Band of 100) = (Controller Gain of 1)
(or Cont Gain) Default=100. (Band)
Appears when you configure proportional control or a 1. (Gain)
combination that includes proportional control.
None, PV, LS, RS, FF,

Setpoint: Local setpoint rate limit in units/second. Units are the
Supr E to O,
Rate Lim same as the local setpoint.
.0000 to 999999.

E to O,
Local setpoint high limit. Units are the same as the --999999. through
Supr
High Lim local setpoint.
999999.
Default=100.00

E to O,
Local setpoint low limit. Units are the same as the --999999. through
Supr
Low Lim local setpoint.
999999.
Default=.00
Selects input through which backtracking signals are None, PV, LS, RS, FF,
Track Input Conf
sent. E, F

CB: 2-2-17
Configuring Feedforward Control

- To configure a PID block for feedforward control:
1. On the Continuous Links screen, cursor to the “Source” field of
the FF input and enter the tag or address of the feedforward
input source and press [ENTER]. The feedforward input is scaled
to match the input source.
2. On the Continuous Faceplate screen, cursor to the “FF Gain”
field and enter a value other than zero. Be sure that the block is
in Manual mode. A positive gain represents a rise in the
ControlBlock output when the FF input value rises. A negative
gain represents a fall in the ControlBlock output when the FF
input value rises.
3. Determine whether or not the FF input value is to be displayed
on the faceplate. If not, cursor above the faceplate to the letter
“D” and press [ENTER]. The letter D is no longer displayed.
Figure 2.2.6 shows the Continuous Faceplate screen and the “FF Gain”
field. Figure 2.2.7 shows the Continuous Links screen for the
feedforward example.

Shed
Tag >106LIC-1072 Desc> Mode>
NONE>OUT>A>B>C>D
SC>N +--------+
Addr =1A-01 Function >PI Controller PI Act>Err D Act>PV PV |*.0 |
PV >.00 DegC 106TT-1072 >.00 >Reverse RS | |
LS >.00 DegC Action FF |*0. |
100-+--------+
FF 0. GPM 106FT-1073 Opt>None + |
75-+ |
50-+ |
FF Gain >.25 + |
25- + |
Setpoint: Output: 0-+--------+
OUT || |
High Lim >250.00 High Lim >100.00 | |
+--------+
Block Mode> MANUAL
FULL CONFIG 1
Figure 2.2.6. Continuous Faceplate Screen—“FF Gain” Field

CB: 2-2-18
CB CONTINUOUS LINKS 23-Jan-92 11:47:12

Tag 106LIC-1072 Descriptor
Addr 1A-01 Function PI Controller
PV >106TT-107 >no *Þ.0 Þ250.0 0 ÞDegC
LS >*ENTRY PV Þ.0 Þ250.0 >.0 ÞDegC
RS >*NONE LS Þ.0 Þ250.0 >-.3 ÞDegC
FF >106FT-1073 >no Þ0. Þ600 0. ÞGPM
E >
F >
G >
Q Þ.00 Þ100.00 >.00 Þ
Block Mode> MANUAL
CONFIG 1
Figure 2.2.7. Continuous Links Screen—Example of Feedforward Control

CB: 2-2-19
Configuring Setpoint Tracking
Some applications require an operator to make changes manually in the

output of a controller while monitoring another part of the process. For
such cases, you can configure the setpoint to track the process variable
while the controller is in MANUAL or LOCAL mode.
- To configure setpoint tracking:
D Cursor to the “LS--PV Track” field (Figure 2.2.8). Press [OPTION]
until “yes” appears, then press [ENTER]. The setpoint follows the
process variable as long as the controller remains in MANUAL or
LOCAL mode.
When you return the controller to AUTO mode, the setpoint stops
tracking the process variable and remains where it was when you
changed modes.
If you have configured logic that acts on the setpoint, be aware that in
case of a conflict, tracking overrides the logic when the block is in
MANUAL or LOCAL mode.
Back balancing and tracking in a cascade control loop are discussed

later in this section. Tracking in a Math block is discussed in Section 3.
CB CONTINUOUS FACEPLATE 27-Nov-91 09:52:59

Shed
Tag > Desc > Mode>
NONE >OUT>A>B>C>D
SC>N +--------+
PV >.00 >.00 >Reverse RS | |
RS 100- +--------+
FF Opt>None + |
75- + |
50- + |
FF Gain >0. + |
25- + |
LS-PV Track>yes Track Input>None + |
Setpoint: Output: 0- +--------+
OUT || |
High Lim >100.00 High Lim >100.00 | |
+--------+
Block Mode> LOCAL
FULL CONFIG 1
Figure 2.2.8. Continuous Faceplate Screen—“LS--PV Track” Field

CB: 2-2-20
Response to Open Loop Situations

in a Feedback Control Loop
A feedback control loop is functionally a circle, part of which is in the

controller and part of which is in the process, as shown in Figure 2.2.9
Feedback control requires an integrator so that a valve may assume
any position required to bring the measurement to the setpoint. The
integrator is normally in the controller but can reside in the process.
A description follows of situations in which the control loop is broken,

resulting in an open input or open output.
CONTROL SP Automatic
Setpoint
Controller
PV Q
Input
Output
Block
Block
PROCESS
Process Control
Measurement Valve
Device
Process
Dynamics
Figure 2.2.9. Feedback Control Loop

CB: 2-2-21
Open Input Situations (Hold Forward)
One way the loop can be opened is for the path of the process
measurement signal to be broken somewhere between the process and
the input to the controller as shown in Figure 2.2.10. The loop can be
broken in the following ways:
D The transmitter or I/O hardware fails and causes an instrument
alarm (number 1 in Figure 2.2.10.). (For more information on
configuring input blocks so that AIB alarms are generated, see
IO: 2.)
D The input block is switched to Manual mode (number 2 in
Figure 2.2.10).
D The link between the input block and the controller fails (number
3 in Figure 2.2.10).
If any of these actions occur, a Hold Forward flag is sent to the

controller. The Hold Forward flag is used to tell a controller that the input
value is unusable and to prevent controller windup.
The “Hold” field on the ControlBlock Continuous Links screen allows

you to configure whether or not a Hold Forward flag is acted on by the
ControlBlock. The “Hold” field appears on the Continuous Links screen
when you configure a continuous input from another block, as shown in
Figure 2.2.11. A “Hold” field entry of “Yes” specifies that the Controller
holds its last output value if a Hold Forward flag is received for that input
and the Controller has an integral term.

CB: 2-2-22
Setpoint
Controller
PV Q
3
2 Input Output
Block Block
PROCESS
Process Control
1 Measurement Valve
Device
Process
Dynamics
Figure 2.2.10. Hold Forward in an Open Loop Situation

Tag Descriptor
PV >TT101 Þyes *Þ.00 Þ100.00 .00 ÞDEG C
LS >*ENTRY PVÞ.00 Þ100.00 >.00 ÞDEG C
RS >*NONE LSÞ.00 Þ100.00 Þ.00 ÞDEG C
FF >*NONE QÞ.00 Þ100.00 Þ.00 Þ
E >
F >
G >
Q Þ.00 Þ100.00 >.00 Þ
Steps in Manual Block Mode> LOCAL

CONFIG 1
Figure 2.2.11. “Hold” Field

CB: 2-2-23
Open Output Situations (Back Balancing or Tracking)
A loop can also be opened if the path of the output signal is broken
somewhere between the controller and the process. The loop can be
broken in the following ways:
D The 4--20 mA signal path to the valve is opened and detected by
an AOB feedback check (number 1 in Figure 2.2.12).
D An output block is switched to Manual mode (number 2 in
Figure 2.2.12).
D An FIC fails.
If the error signal (PV--SP) changes while the loop is open, the
controller calculates an output adjustment. However, if the loop is open,
changing the controller output has no effect on the process
measurement. If unconstrained, the controller continues calculating
output changes until a limit is reached.
When automatic control is resumed, the calculated output may be

different from the actual valve position and the loop experiences a bump
in the output. Back balancing, or tracking, is used to provide a smooth
transition of control from open loop operation to closed loop operation.
You do not have to configure back balancing. It functions whenever the

output of a controller is linked to an AOB, and the integral term is
configured.

CB: 2-2-24
Setpoint
Controller
PV Q
3
2 Input Output
Block Block
PROCESS
Process Control
1 Measurement Valve
Device
Process
Dynamics
Figure 2.2.12. Tracking in an Open Loop Situation
Table 2.2.6 lists whether or not tracking occurs as a result of various

output situations.
Table 2.2.6. ControlBlock/AOB Tracking Situations
Open Output (AOB in

ControlBlock Mode AOB in Auto AOB in Manual
Auto or Manual)
Local No tracking No tracking No tracking
Manual or DDC No tracking Tracking occurs No tracking
Auto, Remote,
No tracking Tracking occurs Tracking occurs*
or Comp SP
* If the output opens, the value goes bad. The Controller holds at the last good output.
Tracking in a cascade control loop is discussed later in this section.

Configuring setpoint tracking is discussed earlier in this section.
Tracking in a Math block is discussed in Section 3.

CB: 2-2-25
Tracking in a Cascade Control Loop
An example of a cascade control loop is shown in Figure 2.2.13. Data is

input from a field device to a ControlBlock labeled primary. The output
of the primary ControlBlock is linked to the secondary ControlBlock. A
field device also inputs data to the secondary ControlBlock. The output
of the secondary ControlBlock is sent to a control device in the field.
Primary Secondary
ControlBlock ControlBlock
PID Function PID Function
Input PV Input Q Output

PV
Block Block Block
LS
LS Q RS
Operator
AUTO Mode REMOTE Mode
Figure 2.2.13. Typical Cascade Control
For cascade control, link the primary block output to the secondary
block RS input, as shown in Figure 2.2.14. For cascade control of the
secondary block setpoint, set the primary ControlBlock mode to Auto
and the secondary ControlBlock mode to Remote. These are
considered the normal block modes for cascade control. When the
secondary block is in Remote, the operator cannot adjust either its
setpoint or output. When the secondary block is in Auto, the operator
can adjust the secondary setpoint directly.

Tag Descriptor
PV >FT101 Þyes *Þ.00 Þ200.00 .00 ÞGPM
LS >*ENTRY PVÞ.00 Þ200.00 >.00 ÞGPM
RS >PRIMARY *Þ.00 Þ200.00 .00 ÞGPM
FF >*NONE QÞ.00 Þ100.00 Þ.00 Þ
Figure 2.2.14. Cascade Secondary Block with Local Setpoint Option

CB: 2-2-26
Tracking Indicators
Tracking is indicated on continuous faceplates by a double arrow in

front of the tracking variable, as shown in Figure 2.2.15. The arrow
indicates that the variable is now tracking another variable. You cannot
change the block variable when tracking is taking place.
PRIMARY
PV 232.45
LS 231.76
Arrow indicates tracking is

in effect. You cannot
change the output.
OUT Þ11.11
AUTO MODE
Figure 2.2.15. Tracking Indicators

CB: 2-2-27
Configuring Tracking in a Cascade Control Loop
The secondary block Continuous Faceplate screen contains fields that

allow you to configure tracking for the cascade loop. Figure 2.2.16
shows the tracking fields on the screen. To provide loop tracking, we
recommend that you configure these fields for typical cascade control
loops.
The “Track Input” field specifies the input through which a backtracking
signal will be passed. For example, if you specify “Track InputÞRS” in
the secondary control block and link the primary output Q to the RS
input, then the tracking signal from the secondary block is passed back
to the primary output Q.
The “LS--PV Track” field specifies that the LS input follows the PV input.
This field is useful when you put the secondary block in Manual mode,
as described later in this section.

Shed
Tag > Desc > Mode>
NONE >OUT>A>B>C>D
SC>N +--------+
PV >.00 >.00 >Reverse RS | |
RS 100- +--------+
FF Opt>None + |
75- + |
Cont Gain >1. Integ Time >1. M Deriv Time >0. S + |
50- + |
FF Gain >0. + |
25- + |
OUT || |
High Lim >100.00 High Lim >100.00 | |
+--------+
Block Mode> AUTO
FULL CONFIG 1
Figure 2.2.16. Tracking Fields

CB: 2-2-28
Cascade Control Scheme—Secondary in Auto Mode
In a typical cascade control loop, the normal mode of the primary block
is Auto and the normal mode of the secondary block is Remote. If you
switch the secondary block to the nonnormal Auto mode, the operator
can adjust the local setpoint. This opens the primary loop, causing its
output to drift. When the secondary block is switched back to Remote,
the process is disturbed by a step change in the secondary setpoint.
But if you configure “Track InputÞRS” on the secondary block

Continuous Faceplate screen, then the value of LS is sent as a tracking
signal to Q of the primary ControlBlock. If the primary ControlBlock
output is limited or if it is in Local mode, it will not track; therefore, RS
will not reflect the value of LS. Figure 2.2.17 shows the block diagram
and Figure 2.2.18 shows the primary and secondary block faceplates
for this situation.
Primary Secondary
PID Function PID Function
Input PV
Block
PV Q
Input Output
LS Block
Block
LS Q RS
Operator
AUTO Mode AUTO Mode
Track InputÞRS
Figure 2.2.17. Cascade Control Tracking Block Diagram—Secondary in Auto

CB: 2-2-29
If you put the secondary block in Auto,

the secondary LS value, the secondary
RS input value, and the primary Q
output value are the same.
PRIMARY SECONDARY
PV 232.45 PV 11.62
LS 231.76 LS 15.00
RS Þ 15.00
OUT Þ15.00 OUT 11.11
AUTO
AUTO
Figure 2.2.18. Cascade Control Tracking Block Diagram----Secondary in Auto

CB: 2-2-30
Cascade Control Scheme—Secondary in Manual Mode
In a typical cascade control loop, the normal mode of the primary block
is Auto and the normal mode of the secondary block is Remote. If you
switch the secondary block to the nonnormal Manual mode, the
operator can adjust the secondary block output.
Any changes to the secondary block output are necessarily reflected in

the PV input. If you configure “Track InputÞRS” and “LS--PV
TrackÞyes” on the secondary block Continuous Faceplate screen, any
changes in the PV input are reflected in the LS input, the RS input, and
the primary block output Q, as shown in Figure 2.2.19. Figure 2.2.20
shows the primary and secondary block faceplates for this situation.
Primary Secondary
PID Function Input PID Function

Block
PV
PV Q Output
Input LS
Block Block
LS Q RS
Operator
Auto Mode Manual Mode
Track InputÞRS
LS--PV
TrackÞYes
Figure 2.2.19. Cascade Control Tracking—Secondary in Manual

CB: 2-2-31
If you put the secondary block in Manual,

the secondary PV value, the secondary LS
value, the primary output Q value, and the
secondary RS input value are the same.
PRIMARY SECONDARY
PV 232.45 PV 21.22
LS 231.76 LS Þ21.22
RS Þ21.22
OUT Þ21.22 OUT 49.67
AUTO MANUAL
Figure 2.2.20. Cascade Control Tracking Faceplate Indicators—Secondary in Manual

CB: 2-2-32
Cascade Control Scheme—Secondary Output Constrained
It is possible for the output of the secondary control block in a cascade

loop to reach a limit. If this occurs, the primary block may continue to
increase or decrease its output to achieve the setpoint with no further
response from the secondary block.
If you configure “Track InputÞRS” on the secondary block Continuous

Faceplate screen, the primary output is prevented from moving farther
in the direction that saturated the secondary block whenever the
secondary output reaches a limit. Figure 2.2.21 shows the primary and
secondary block faceplates for this situation.
PRIMARY SECONDARY
PV 232.45 PV 21.22
LS 331.76 LS 21.22
If the secondary block output RS 21.22
reaches a limit, the primary
block output is held at its last
value.
OUT Þ21.22 OUT 100.00
AUTO REMOTE
Figure 2.2.21. Cascade Control Tracking Faceplate Indicators—Secondary Output Constrained

CB: 2-2-33
Configuring Ratio and Bias
The PID controller ratio and bias options provide conventional ratio
control. Select these options with the “Opt” field on the Continuous
Faceplate screen. Figure 2.2.22 shows a functional diagram of a PI
controller with the ratio option.
Wild Flow
T
PV
Q
P+I
LS
Flow Controller
Controlled Flow
T
PV
P+I
RS Q
RV
RV x RA +BI = RS
Ratio
Operator
Ratio Flow
Controller
Configuror
Figure 2.2.22. Functional Diagram of PID Controller with Ratio Option

CB: 2-2-34
Ratio
The ratio option allows the operator to change the ratio term and the
configuror to change the bias term.
Select the ratio option with any of these options in the “Opt” field:
D Ratio
D Ratio/Gap
D Ratio/DdB
D Ratio/Esq
D Ra/Gap/DdB
D Ra/Gap/Esq
Figure 2.2.23. shows the Continuous Faceplate screen after the ratio
option is selected. Table 2.2.7 describes the ratio terms on the screen.
Figure 2.2.24 shows the Continuous Links screen for the ratio option.
- To display the ratio on the conti - To adjust the ratio on the contin
nuous faceplate: uous faceplate:
D Replace the C or D input with E. D Place the cursor above the E in
put and press [SELECT].
CB CONTINUOUS FACEPLATE27-May-92 09:52:59

Shed
Tag > Desc > Mode> NONE >OUT>A>B>C>E
SC>N +--------+
PV >.00 >.00 >Reverse RS | |
LS >.00 Action RA | .0000 |
100 +--------+
Opt>Ratio + |
75 + |
50 + |
+ |
25 + |
LS-PV Track>no Ratio >.0000 Bias >.00 Track Input>None + |
Setpoint: Ratio: Output: 0 +--------+
Rate Lim >None Rate Lim >None Mn Rate Lim >None | .00 |
OUT || |
High Lim >100.00 High Lim >1.0000 High Lim >100.00 | |
+--------+
Low Lim >.00 Low Lim >.00 Low Lim >.00
Block Mode> LOCAL
FULL CONFIG 1
Figure 2.2.23. Continuous Faceplate Screen--Ratio Option

CB: 2-2-35
Table 2.2.7. Ratio Option Fields
Access
Level
Ratio (Input E) term, where Constrained by ratio “High Lim” and

Ratio Oper RS = (RV) (RA) + BI “Low Lim” fields.
See Figure 2.2.22. Default=.0000
Maximum rate at which the ratio None, PV, LS, RS, RV, RA, BI,
Ratio:
Supr value can be changed, in G to O
Rate Lim units/second. .0000 to 999999.
None, PV, LS, RS, RV, RA, BI,

G to O,
High Lim Supr Ratio high limit.
--999999. to 999999.
Default=1.0000

G to O
Low Lim Supr Ratio low limit.
--999999. to 999999.
Default=.0000

Tag Descriptor
PV >*ENTRY Þ.00 Þ100.00 >.00 Þ
LS >*ENTRY PVÞ.00 Þ100.00 >.00 Þ
RS >*NONE LSÞ.00 Þ100.00 Þ.00 Þ
RV >*NONE Þ.00 Þ100.00 Þ.00 Þ
RA >*ENTRY Þ.0000 Þ1.0000 >.0000 Þ
BI >*ENTRY Þ.00 Þ100.00 Þ.00 Þ
G >
Q Þ.00 Þ100.00 >.00 Þ
Block Mode> LOCAL
Figure 2.2.24. Continuous Links Screen—Ratio Option

CB: 2-2-36
Bias
The bias option allows the operator to change the bias term and the
configuror to change the ratio term.
Select the bias option with any of these options in the “Opt” field:
D Bias
D Bias/Gap
D Bias/DdB
D Bias/Esq
D Bi/Gap/DdB
D Bi/Gap/Esq
Figure 2.2.25. shows the Continuous Faceplate screen after the bias
option is selected. Table 2.2.8 describes the bias terms on the screen.
Figure 2.2.26 shows the Continuous Links screen for the bias option.
- To display the bias on the contin - To adjust the bias on the

uous faceplate: continuous faceplate:
D Replace the C or D input with F. D Place the cursor above the F
input and press [SELECT].

Shed
Tag > Desc > Mode>
NONE >OUT>A>B>C>F
SC>N +--------+
PV >.00 >.00 >Reverse RS | |
LS >.00 Action BI | .00 |
100 +--------+
Opt>Bias + |
75 + |
50 + |
+ |
25 + |
LS-PV Track>no Ratio >.0000 Bias >.00 Track Input>None + |
Setpoint: Bias: Output: 0 +--------+
OU || |
High Lim >100.00 High Lim >100.00 High Lim >100.00 | |
+--------+
Low Lim >.00 Low Lim >.00 Low Lim >.00
Block Mode> LOCAL
FULL CONFIG 1
Figure 2.2.25. Continuous Faceplate Screen—Bias Option

CB: 2-2-37
Table 2.2.8. Bias Option Fields
Access
Level
Bias (Input F) term, where Constrained by bias “High Lim”

Bias Oper RS = (RV) (RA) + BI and “Low Lim” fields.
See Figure 2.2.22. Default=.00

Bias: Maximum rate at which the bias value
Supr G to O
Rate Lim can be changed, in units/second
.0000 to 999999.

G to O,
High Lim Supr Bias high limit.
--999999. to 999999.
Default=1.0000

G to O
Low Lim Supr Bias low limit.
--999999. to 999999.
Default=.0000

Tag Descriptor
PV >*ENTRY Þ.00 Þ100.00 >.00 Þ
LS >*ENTRY PVÞ.00 Þ100.00 >.00 Þ
RS >*NONE LSÞ.00 Þ100.00 Þ.00 Þ
RV >*NONE Þ.00 Þ100.00 Þ.00 Þ
RA >*ENTRY Þ.0000 Þ1.0000 Þ.0000 Þ
BI >*ENTRY Þ.00 Þ100.00 >.00 Þ
G >
Q Þ.00 Þ100.00 >.00 Þ
Block Mode> LOCAL
Figure 2.2.26. Continuous Links Screen—Bias Option

CB: 2-2-38
Configuring Gap and Deadband
The Gap and Deadband options minimize controller response to

unavoidable cyclic variations of the measurement signal (PV). Select
these options with the “Opt” field on the Continuous Faceplate screen. A
constantly wandering or noisy signal can result in constant small
movements of the final element. These small movements can result in
needless wear of the final control element and be of little benefit to the
process.
Figure 2.2.27 shows the effect of gap and deadband on the output of a
block. Figure 2.2.28 shows the gap and deadband response to a small
constant error. The Gap and Deadband options minimize these effects.
Effect of Gap on Output
PV
Setpoint
Algorithm
Output
Gap
Value
Effect of Deadband on Output
PV
Deadband
Setpoint
Algorithm
Output and Q
Figure 2.2.27. Effects of Gap and Deadband on Output (Q)

CB: 2-2-39
Gap Response to a Constant Small Error
PV
Setpoint
Gap
Algorithm Value
Output
Deadband Response to a Constant Small Error
PV
Deadband
Setpoint
Algorithm
Output and Q
Figure 2.2.28. Gap and Deadband Response to a Constant Small Error

CB: 2-2-40
Gap
D The Gap option modifies the algorithm so that the output (Q)
does not change until the required change exceeds the
predetermined gap value.
D The integral term is always operational.
D A new field (“Gap Value”) appears when you select gap, as
shown in Figure 2.2.29. The default gap value is .01 and has the
same units and scaling as the controller output Q (Table 2.2.9).
D This option is available in “Opt” field selections in the terms Gap,
Ratio/Gap, Gap/Err Sq, Gap/DBand, Ra/Gap/DdB, Ra/Gap/Esq,
Bias/Gap, Bi/Gap/DdB, Bi/Gap/Esq, Vel/Gap, Ve/Gap/DdB, and
Ve/Gap/Esq.

Shed
SC>N +--------+
PV >.00 >.00 >Reverse RS | |
100 - +--------+
Opt>Gap + |
75- + |
50 - + |
FF Gain >0. Gap Value >2 + |
25 - + |
OUT || |
High Lim >100.00 High Lim >100.00 | |
+--------+
Block Mode> LOCAL

FULL CONFIG 1
Figure 2.2.29. Continuous Faceplate Screen—Gap Option
Table 2.2.9. Gap Option Fields
Access
Level
The controller output does not change

unless the calculation calls for a change None, PV, LS, RS, FF, E to O
Gap Value Conf
.01 to 100.00
greater than the “Gap Value”.

CB: 2-2-41
Deadband
D The Deadband option modifies the algorithm so that the output

(Q) does not change until the magnitude of the SP--PV error
exceeds the predetermined deadband value.
D The integral term is operational only if |SP--PV| ³ deadband
value.
D A new field (“Err DdBand”) appears when you select Deadband,
as shown in Figure 2.2.30. The default deadband value is .01
and has the same units and scaling as the process variable PV
(Table 2.2.10).
D This option is available in “Opt” field selections in the terms Dead
Band, Bias/DdB, Gap/DBand, Ratio/DBand, Ra/Gap/DdB,
Bi/Gap/DdB, Vel/DdB, and Ve/Gap/DdB.
CB CONTINUOUS FACEPLATE
27-May-92 09:52:59
Shed
SC>N +--------+
PV >.00 >.00 >Reverse RS | |
100 +--------+
Opt>Dead Band + |
75 + |
50 + |
FF Gain >0. Err DdBand >.01 + |
25 + |
Setpoint: Output: 0 +--------+
OUT || |
High Lim >100.00 High Lim >100.00 | |
+--------+
Block Mode> LOCAL
FULL CONFIG 1
Figure 2.2.30. Continuous Faceplate Screen—Deadband Option
Table 2.2.10. Deadband Option Fields
Ac-
Field cess Description Allowable Entries
Level
The controller output does not change

unless the absolute value of the error is None, PV, LS, RS, FF, E, to O
Err DdBand Conf
.01 to 999999.
greater than the “Err DdBand”.

CB: 2-2-42
Tuning PID Controllers
A supervisor or configuror can tune a PID controller using a Tuning

Display screen. The Tuning Display screen combines faceplates, loop
variables, and trending capabilities on one screen. A configuration
keyboard is required to enter the controller tags. Figure 2.2.31 shows a
sample Tuning Display screen.
- To call up a Tuning Display screen, type:
TD: tuning display number [ENTER]
The Tuning Display screen can contain up to two controller faceplates.

The variable values appear below the faceplate.
The Tuning Display screen contains a trend display window for trending
up to four faceplate variables. The controllers do not have to be
configured in a trend file to be trended on the Tuning Display. Up to 300
data samples are stored for each trended variable. Up to 50 data
samples can be shown on the trend window for a variable. Faceplate
variables are only trended and stored while the Tuning Display screen is
displayed on the console.

CB: 2-2-43
1: LINE 1 TANK A 27-Nov-91 10:18:35

Tag >FCC-773 >FCC-774 +----------+---------+---------+---------+---------+--+
+ +
>100 +---------+--------++ +
+ + |+ +
75 + + |+ +
+ + |+ +
50 + + |+ +
+ + |+ +
25 + + |+ +
+ + |+ +
>0 +-------- +--------|+ +
Output | | |+ +
|-------- |--------+---------+---------+---------+---------+---------+-+
Units | GPM | | 09:53:20 09:58:20 10:03:20 10:08:20 10:13:20
PV -A | 35.00 | .00 | Sample
LSP-B | 76.00 | 7.00 | Freq >1 S
RSP-C | 54.00 | 55. | > Tag/Addr: FCC-774 Function: PID
FF -D | 34.00 | 65. | PI Action Err D Action Err Option None
Output | 99.00 | 1. | Prop
Units |gallons | | Band>99. Int Time>1.08333 H Der Time>0. S
+-------- +--------+ FF
AUTO AUTO Gain>1.
FULL CONFIG 1
Figure 2.2.31. Tuning Display Screen

CB: 2-2-44
Tuning Display Operations
Figure 2.2.32 shows the callouts referenced in this section that describe
the operations that you can perform on the Tuning Display screen.
- To configure a controller:
D Cursor to the > symbol at the top of the screen (callout A) and
type the tag of the controller. A controller must be configured in
this field to be tuned or trended.
- To trend a controller variable:
D Cursor to the desired variable value in the faceplate (callout B)
and press [SELECT].
- To remove a controller variable from the trend display window
but continue trending the variable:
D Cursor to the desired variable value in the faceplate (callout B)
and press [SELECT] or [ENTER].
NOTE: You can use this method to reduce clutter in the trend window.
- To discontinue trending a controller variable:
1. Cursor to the desired variable value in the faceplate (callout B).
2. Press [NEXT OPTION] until the value is white.
3. Move the cursor away from the value.
- To change the color of a controller variable:
1. Cursor to the desired variable value in the faceplate (callout B).
2. Press [NEXT OPTION] until the desired color appears (white
discontinues trending of the variable).
- To change the trend sample frequency:
D Cursor to the “Sample Freq” field (callout C) and enter the
desired value. If you change the “Sample Freq” field, the trend
display and data storage are cleared.
- To use the slidewire:
D Move the cursor into the trend window (callout D), which freezes
the trend display. The time of day and controller variable values
associated with the cursor location are displayed below the trend
window. To view trend data for other times, move the slidewire to
the left or right edge of the trend display and continue rolling the
trackball. To end the slidewire, move the cursor up or down out of
the trend window.

CB: 2-2-45
- To change the controller tuning variables:

D Cursor to the tuning variable (callout E) and make the desired
change.
- To change the controller that has its tuning variables
displayed:
D Cursor to the “Tag/Addr” field (callout F) and press [SELECT].
- To change the faceplate and trend window scaling:
D Cursor to the scaling variables at the left of the faceplate (callout
G) and make any desired changes. The values represent the
percentage of the controller’s engineering units range. The
changes will be reflected in the faceplate bars and the trend
window.
G
A D
1: LINE 1 TANK A 27-Nov-91 10:18:35

Tag >FCC-773 >FCC-774 +----------+---------+---------+---------+---------+--+
+ +
>100 +---------+--------++ +
+ + |+ +
75 + + |+ +
+ + |+ +
50 + + |+ +
+ + |+ +
25 + + |+ +
+ + |+ +
>0 +-------- +--------|+ +
Output | | |+ +
|-------- |--------|+--------+---------+---------+---------+---------+-+
Units | GPM | | 09:53:20 09:58:20 10:03:20 10:08:20 10:13:20
PV -A | 35.00 | .00 | Sample
LSP-B | 76.00 | 7.00 | Freq >1 S
RSP-C | 54.00 | 55. | > Tag/Addr: FCC-774 Function: PID
FF -D | 34.00 | 65. | PI Action Err D Action Err Option None
Output | 99.00 | 1. | Prop
Units |gallons | | Band>99. Int Time>1.08333 H Der Time>0.S
+-------- +--------+ FF
AUTO AUTO Gain>1.
FULL CONFIG 1
B F E C
Figure 2.2.32. Tuning Display Configuration

CB: 2-2-46
Tuning Display Directory
You can configure up to 10 Tuning Display screens for a console.

Assign titles to these screens on the Tuning Display Directory screen.
Figure 2.2.33 shows a sample Tuning Display Directory screen.
- To call up a Tuning Display Directory screen, type:
TDD [ENTER]
TUNING DISPLAY DIRECTORY 21-May-87 15:52:27

Tuning Display Title Block 1 Block 2
1ÞMixing Process Inflow Valve 1 Inflow Valve
2ÞWaste Process FIC-202 FIC-203
3Þ
4Þ
5Þ
6Þ
7Þ
8Þ
9Þ
10Þ
Figure 2.2.33. Sample Tuning Display Directory

CB: 2-2-47
Adaptive Tuning
You can configure a tuning constant to vary based on process

conditions. To do this, use a continuous input as a value for gain,
integral time, or derivative time.
- To configure adaptive tuning:
1. On the Continuous Faceplate screen, enter an unused
continuous variable in the “Cont Gain”, “Integ Time”, or “Deriv
Time” field. Figure 2.2.34 shows an example of a continuous
input as a variable for proportional band.
2. On the Continuous Links screen, scale the variable used for a
tuning constant as follows:
Eng Zero Eng Max Units
Gain 0 1.0 Gain

Ti 0 1.0 sec Ti sec
Td 0 1.0 sec Td sec
Figure 2.2.34 shows an example of scaling.

NOTE: The PID algorithm always interprets the value of the
proportional term as gain when you enter it through a continuous
input.
3. In a logic step, write an equation that calculates the tuning
parameter based on appropriate process conditions, using the
continuous input to store the result of the calculation. For
information on writing logic steps, see CB: 6.
You can perform these steps in any order.

CB: 2-2-48

Shed
Tag > LC-103 Desc> Mode>
NONE >OUT>A>B>C>D
SC>N +--------+
Addr =1D-01 Function >PID Controller PI Act>Err D Act>PV PV |*.0 |
PV >.00 >.00 >Reverse | |
LS >.00 Action | |
100-+--------+
Opt>None + |
75-+ |
Cont Gain >G Integ Time >E Deriv Time >F + |
CB CONTINOUS LINKS 27-Nov-91 09:52:59

Tag > LC-103 Descriptor
Addr =1D-01 Function >PI Controller
PV >106TT-1072 >no *>.0 >250.0 .0 >DegC
LS >*ENTRY PV>.0 >250.0 >.0 >DegC
RS >*NONE LS>.0 >250.0 >-.3 >DegC
FF >*VALUE Q>.00 >100.0 >.00 >
E >*VALUE >0.0 >1.0 >.0 >Ti sec
F >*VALUE >0.0 >1.0 >.0 >Td sec
G >*VALUE >0.0 >1.0 >0. >Gain
Continuous input
Figure 2.2.34. Example of Configuring Adaptive Tuning

CB: 2-3-1
Section 3:
Configuring Other ControlBlock Continuous
Functions
This section describes the ControlBlock continuous functions listed in

Table 2.3.1.
Table 2.3.1. ControlBlock Continuous Functions
Function Page
Description
(Mnemonic) Number
Dead Time (DT) Provides a configurable delay period. 2-3-2
Provides one lead term and two lag terms for modeling process
Lead/Lag (LL) 2-3-10
dynamics.
Provides a manual loading station for operator control of valves and other
Manual (MAN) devices or provides a place where the configuror needs access to logic 2-3-16
steps and is not concerned with the major function of the ControlBlock.
Allows you to define a function containing equations that determine the

Math (MATH) 2-3-17
value of the block output.
Piecewise
Linear
Approximates a curve with a series of straight line segments. 2-3-29
Interpolator
(PLI)
Polynomial
Approximates a curve with a polynomial equation. 2-3-34
(POLY)
Ratio/Bias (RB) Provides adjustable ratio and bias capabilities. 2-3-38
Signal Selector Acts as a general purpose selector that can function in the input or the
2-3-43
(SS) output side of a loop.
Totalizer
Setpoint Acts as an integrator with an output that rolls over and resets to zero
2-3-47
when the output reaches a high limit.
(TOTSP)
Acts as an integrator with an output that resets to zero when the output
Totalizer (TOT) 2-3-51
reaches a high limit or a reset indication, and saves the last three totals.
Velocity Limiter
Provides an output that is a rate-limited function of the input. 2-3-57
(VLIM)
RS3: Configuring ControlBlock Functions Configuring Other ControlBlock Continuous Functions

CB: 2-3-2
Delay Period—Dead Time (DT) Function
The Dead Time function provides a configurable delay period. Use this
function primarily in feedforward or ratio loops to model the dead time in
the process. Figure 2.3.1 shows the Dead Time functional diagram.
Dead time is implemented with a stack of memory slots. Each time the
function is evaluated, an input value is placed into slot 0. The value that
was in slot 0 is moved into slot 1, the value from slot 1 is moved into slot
2, and so on. Input B is used to determine which slot is used for the
block output. The combination of the sample time and the input B value
determines the dead time. The Dead Time function interpolates
between sample times to produce a smooth transition from one sample
time to the next.
Input data A
Slot 0
Slot 1
Slot 2
Determines
which slot to
pick
B Add Q
Slot n A x KA
C x KC
Slot 60
Modification
data C
Figure 2.3.1. Dead Time Functional Diagram

CB: 2-3-3
Two special logic functions exist for the Dead Time ControlBlock.
D The fill function invalidates any numbers currently in the Dead
Time stack and sets the hold forward flag. This allows the Dead
Time stack to be able to fill with numbers (this can be a
combination of valid and invalid numbers). To configure the fill
function, use the format “fill”.
D The vfill function fills the dead time stack with a user-specified
value. To configure the vfill function, use the format “vfill XX”,
where xx is a value or a register.
Configure these functions in the Actions part of a logic step. For more
information about logic steps, see Chapter 6.
The Dead Time function has the following configuration characteristics:

D Dead Time = (block sample time) (B input) (60).
The result of (B input) (60) is rounded off to the nearest integer,
and limited to the range 0--60.
NOTE: The value of 60 used in the Dead Time equations
changes the B input to seconds.
D Dead Time block output = KA (Delayed A input) + KC (C input).
D The “Sample Time” field is located on the Block Diagram screen.
You can specify the sample time in 0.25-second increments up to
999.75 seconds, or in one-second increments up to 999999.
seconds. The sample time applies only when the block is in Auto
mode. Otherwise, the block is evaluated at the cycle time of the
Controller Processor. As a result, we recommend that you specify
“Auto LockÞyes” on the Continuous Diagram screen for a Dead
Time block.
D The “KA” field on the Continuous Faceplate screen defaults
to 0.
D If you configure the Dead Time block only to provide a delay
period and to leave the input unaltered, then configure the “KA”
field as 1 and the “KC” field as 0.
D Configure the block output high and low limits on the Continuous
Faceplate screen to allow all desirable output values.

CB: 2-3-4
Figure 2.3.2 shows the dead time delay effect. Figure 2.3.3 shows the
Dead Time function Continuous Faceplate screen. Table 2.3.2 describes
the fields related to the Dead Time function on the Continuous
Faceplate screen. Figure 2.3.4 shows the Dead Time Continuous Links
screen. For a description of the fields that are common to all continuous
Input 100%
0%
Time
Output 100%
0%
B=10 B=20 B=30
Figure 2.3.2. Dead Time Delay Effect

CB: 2-3-5

Shed
Mode
Tag > Desc > NONE>OUT>A>B>C>
SC>N +--------+
Addr =1A-01 Function >DT Dead Time A | .00 |
INPUTS Value Units Tag OUTPUT B|. 0000 |
A >.00 >.00 C | .0000 |
B >.0000 | |
C >.0000 100-+--------+
+ |
75-+ |
Gain KA >0. Gain KC >0. Dead Time 0. S + |
50-+ |
+ |
25-+ |
+ |
Output: 0- +--------+
OUT || |
High Lim >100.00 | |
+--------+
Low Lim >.00
Block Mode> LOCAL
FULL CONFIG 1
Figure 2.3.3. Continuous Faceplate Screen—Dead Time Function
Table 2.3.2. Dead Time Function Continuous Faceplate Fields
Access
Level
A to O,
Gain on input A. The term A (KA) is determined --999999. to 999999.
Gain KA Conf
after the dead time delay period.
Default=0.
A to O,
Gain on input C. The term C (KC) is added to the
Gain KC Conf --999999. to 999999.
A (KA) term to determine the block output.
Default=0.
Dead Actual current dead time. This value is computed

NA NA
Time from the term (sample time) (60) (B).

CB: 2-3-6

Tag Descriptor
Addr Function DT Dead Time
PV >FIC101 Þ.00 Þ100.00 .00 Þ
B >*ENTRY Þ.0000 Þ60.0 >.00 Þ
C >*ENTRY Þ.00 Þ100.00 >.00 Þ
D >
E >
F >
G >
Q Þ.00 Þ100.00 >.00 Þ
Block Mode> LOCAL
CONFIG 1
Figure 2.3.4. Continuous Links Screen—Dead Time Function
- To configure links for a Dead Time block:

1. On the Continuous Links screen, cursor to the “Source” field for
the A input and enter the tag or address of the input source. The
scaling and units of input A match those of the input source.
2. Calculate the maximum dead time as (60)(sample time). Cursor
to the “Eng Max” field for the B input and enter this number, and
then press [ENTER].
3. Cursor to the “Eng Zero” field for the C input, enter the eng zero
value of input A, and press [ENTER].
4. Cursor to the “Eng Max” field for the C input, enter the eng max
value of input A, and press [ENTER].
5. Cursor to the “Units” field for the C input, enter the units of input
A, and press [ENTER].

CB: 2-3-7
Dead Time Input A Plots
The Dead Time function includes two plots of the Dead Time block
Input-A. Pressing [PAGE AHEAD] from the Dead Time function
Continuous Faceplate screen calls up the first Input-A Time Plot screen,
as shown in Figure 2.3.5. Pressing [PAGE AHEAD] again shows the
second Input-A Time Plot screen. Both screens show the value of
Input-A over time. The first screen shows values as solid bars. The
second screen shows values as a solid line.
CB INPUT-A TIME PLOT 23-Jan-92 11:47:12

Addr
Tag Sample Time.5 S Display Width 30. S
100- -100
75- -75
50- -50
25- -25
0- -0
30.S 25.S 20.S 15.S 10.S 5.S 0.S
CONFIG 2
Figure 2.3.5. Example of a Dead Time Plot

CB: 2-3-8
Dead Time Function Example
Figure 2.3.6 shows an example of the use of the Dead Time function.
Product feeds into a ball mill on a conveyor. Water is added to the
product through a valve. A flow ratio controller determines the amount
of water to add, depending on the value received from the weight
transmitter. There is a delay of 40 seconds from the time that product is
at the weight transmitter until it reaches the ball mill.
The Dead Time block is used to provide a 40-second delay of the

weight transmitter signal. The weight transmitter is the Dead Time block
PV input. The B input is adjusted until the dead time is 40 seconds.
If the Dead Time block sample time is slower than the Controller cycle
time, the Dead Time block output changes at each Controller cycle as it
interpolates between samples.
Flow
Transmitter
Dead Time Flow Ratio

Block Controller
Water
40 seconds
Ball Mill
Weight
Transmitter
Figure 2.3.6. Application of a Dead Time Function

CB: 2-3-9
Figure 2.3.7 shows the same ball mill example, but with a
variable-speed conveyor. A tachometer signal is sent to an unused input
register in the Dead Time block. The Dead Time block calculates the
proper value for the B input to provide the proper delay of the weight
transmitter signal. The variation in delay is not continuous, but
increases in increments of one sample time.
Flow
Transmitter
Dead Time Flow Ratio

Block Controller
Water
Variable Time
Ball Mill
Weight
Transmitter
Figure 2.3.7. Application of Dead Time with Variable Speed Conveyor

CB: 2-3-10
Process Modeling Applications—Lead/Lag (LL) Function
The Lead/Lag (LL) function provides one lead term and two lag terms
for modeling process dynamics. Use this function primarily for
feedforward control and other process modeling applications.
Figure 2.3.8 shows a typical feedforward application. You can use the
Lead/Lag block to provide the desired loop response for this application.
Figure 2.3.9 shows the Lead/Lag block functional diagram.
The Lead/Lag function output is determined by the following equations:
I1 = I1’ + (TS/(TS+2T2)) (K1 (M--M’)--2I1’)

--(1/(TS+2T2)) (2T1K1(M--M’))
I2 = I2’ + (TS/(TS+2T3)) (I1+I1’--2I2’)
Q = I2 + B (Gain KB) + C (Gain KC)
where ... is the ...

TS sample time
T1 lead time
T2 lag time 1
T3 lag time 2
M current PV
M’ PV from previous evaluation
K1 gain on input A
I1 current output of first stage lead lag
I1’ previous output of first stage lead lag
I2 current output of first stage and second stage lead lag
I2’ previous output of first stage and second stage lead lag

CB: 2-3-11
PV Q
Lead/Lag
FF ControlBlock
Steam
Kf x FF
PID
algorithm
Outlet
FF TT Temp
Transmitter
Flow
Transmitter Heat
Exchanger
Figure 2.3.8. Typical Feedforward Control with a Lead/Lag Function
Lead/Lag Function
PV 1 + ST1 I1 1 I2 Add Add Q

1 + ST2 1 + ST3 B ´ Gain KB C ´ Gain KC
Figure 2.3.9. Lead/Lag Functional Diagram

CB: 2-3-12
Figure 2.3.10 through Figure 2.3.12 show the effects of gain, lag, and
lead on the block output (Q).
Lag 1= 0 Q with Gain=2.0

200%
Lag 2= 0
Lead = 0
Q with Gain=1.5
Gain = VARIOUS
Q with Gain=1.0
100%
Q with Gain=0.5
Input
0%
Figure 2.3.10. Gain Effect on Block Output
Q with Q with Q with

Lag=1.0 min Lag=3.0 min Lag=10.0 min
100%
Lag 1= VARIOUS
Lag 2= 0
63.2%
Lead = 0
Gain = 1
0%
Input
Minutes 0 1 3 10
Figure 2.3.11. Lag Effect on Block Output

CB: 2-3-13
Q with Lead=(2.0) Lag

200%
100%
Lag 1= 1
Lag 2= 0
Lead = VARIOUS
Gain = 1
INPUT 0%
Figure 2.3.12. Lead Effect on Block Output

CB: 2-3-14
Configuring the Lead/Lag Function
The Lead/Lag function has the following configuration characteristics:

D If you configure the lead term, you must also configure Lag Time
1 or both lag terms.
D If you need to have a negative lead time, use a continuous
variable as the input to the lead time. Be sure to scale the
continuous variable from 0 to 1.
D You must configure the block output high and low limits to allow
all desirable values to be output.
Figure 2.3.13 shows the Continuous Faceplate screen for the Lead/Lag
function. Table 2.3.3 describes the Lead/Lag screen fields on the
Continuous Faceplate. Figure 2.3.14 shows the Lead/Lag Continuous
Links screen. For a description of the fields that are common to all
continuous ControlBlocks, see Section 1.

Shed
Tag > Desc > Mode> NONE >OUT>A>B>C>
SC>N +--------+
Addr =1A-01 Function >DT Dead Time PV | .00 |
INPUTS Value Units Tag OUTPUT B | .0000 |
PV >.00 >.00 C | .0000 |
B >.0000 | |
C >.0000 100- +--------+
+ |
75- + |
KA KB KC + |
50- + |
Gain >1. >0. >0. Track Input >None + |
Filter Bias Offset 25- + |
+ |
Output: 0- +--------+
Lead Time >.25 S Mn Rate Lim >None | .00 |
OUT || |
Lag Time 1 >.25 S High Lim >100.00 | |
+--------+
Lag Time 2 >0. S Low Lim >.00
Block Mode> LOCAL
FULL CONFIG 1
Figure 2.3.13. Continuous Faceplate Screen—Lead/Lag Function

CB: 2-3-15
Table 2.3.3. Lead/Lag Function Continuous Faceplate Fields
Access
Level
PV, B to O,
Filter Gain KA Conf Gain on input A (PV). --999999. to 999999.
Default=1.
PV, B to O,
Bias Gain KB Conf Gain on input B (Bias). --999999. to 999999.
Default=0.
PV, B to O,
Offset Gain --999999. to 999999.
Conf Gain on input C (offset).
KC
Default=0.
Track Input Conf Selects input to send backtracking signals. None, PV, B, C
PV, B to O,
Lead Time Conf Lead time constant. 0 S to 999999. H
Default=.25 S
PV, B to O,
Lag Time 1 Conf First-order lag time constant. --999999. S to 999999. H
Default=.25 S
PV, B to O,
Lag Time 2 Conf Second-order lag time constant. --999999. S to 999999. H
Default=0. S

Tag Descriptor
Addr Function Lead Lag (LL) Controller
PV >*ENTRY Þ.00 Þ100.00 .00 Þ
B >*ENTRY Þ.0000 Þ1.0000 >.00 Þ
C >
D >
E >
F >
G >
Q Þ.00 Þ100.00 >.00 Þ
Figure 2.3.14. Continuous Links Screen—Lead/Lag Function

CB: 2-3-16
Operator Selectable Block Output—

Manual (MAN) Function
A ControlBlock configured with the Manual function has the block output
(Q) determined by the operator. The Manual function is intended for two
primary uses:
D As a manual loading station for operator control of valves, speed
controls, and other devices.
D As a place for the configuror to get access to logic steps when he
or she is not concerned with the major function of the
ControlBlock.
Figure 2.3.15 shows a typical Manual function control loop. You

configure a ControlBlock for the Manual function on the Continuous
Faceplate screen. All of the screen fields that appear for a Manual
function ControlBlock are described in Section 1. The operator is not
required to make any entries for the block to be functional. However, the
operator can only control the output if the block is in Manual or Local
mode. If the block mode is Auto mode, the output maintains its last
value, because there is no function to change it. If desired, you can
configure logic to change the output.
Field Optional Field

Device Device
Measurement or
process variable Open/close
(not required) valve
CONTROLLER CARD
Analog A Q Analog
FIC Input Control Output FIC
Block
Block Block
Operator controls
the output
Figure 2.3.15. Typical Manual Function Control Loop

CB: 2-3-17
User-defined ControlBlock—Math (MATH) Function
A ControlBlock configured with a Math function allows you to define a

function containing equations that determine the value of the block
output. Enter the equations on the Continuous Faceplate screen and
use the same format as the discrete logic steps of a ControlBlock. For
more information about writing mathematical expressions, see Section
1.
Figure 2.3.16 shows the Math function Continuous Faceplate screen.

Table 2.3.4 describes the Math function fields on the Continuous
Faceplate screen. Figure 2.3.17 shows the Math function Continuous

Shed
Tag > Desc > Mode>NONE >OUT>A>B>C>
SC>N +--------+
Addr =1A-01 Function >MATH User-Defined Function A | .00 |
A >.00 >.00 C | .0000 |
B >.0000 | |
C >.0000 100- +--------+
+ |
75- + |
Equation > + |
50- + |
> + |
25- + |
> + |
0- +--------+
Back Calc > | .00 |
Output: OUT || |
Track Input >None Max Gain >16. High Lim >100.00 | |
+--------+
Low Lim >.00
Block Mode> LOCAL
FULL CONFIG 1
Figure 2.3.16. Continuous Faceplate Screen—Math Function

CB: 2-3-18
Table 2.3.4. Math Function Continuous Faceplate Fields
Ac-
Field cess Description Allowable Entries
Level
Three lines of the calculation that you defined.

Equation Conf NOTE: If an equation is entered that is exactly Maximum of 40 characters.
40 characters, the console beeps until another
screen is called up.
Optional tracking calculation that you defined.

Back Calc Conf The letter V is used to represent the tracking Maximum of 40 characters.
signal received by the Math block.
Track Input Conf Selects input to send backtracking signals. None, A, B, C
Determines the rate of response of the

tracking signal sent along the “Track Input”
entry to the tracking signal received or initiated
by the block.
The larger the “Max Gain” entry, the slower the
response of the tracking signal, as shown in A to O, or
the following equation:
Max Gain Conf --999999, to 999999.
(D tracking signal)=(calc signal -- actual signal)
Default=16
(“Max Gain”)
Tracking will not converge if the loop gain/max
gain is greater than 1.
Field appears only if “Back Calc” field is not
configured.
Determines whether the tracking signal

computed by the back calculation is inverted.
This field can be used to simplify the back
Inverted Conf calculation. No, Yes
Field appears only if “Back Calc” field is
configured.

CB: 2-3-19

Tag Descriptor
Addr Function MATH User-Defined Function
A >*ENTRY Þ.00 Þ100.00 .00 Þ
B
C >
D >
E >
F >
G >
Q Þ.00 Þ100.00 >.00 Þ
Block Mode>LOCAL
Figure 2.3.17. Continuous Links Screen—Math Function
Equations
Multiple equations can be written on an equation line. Equations must

be separated by a semicolon (;). For example, the following is a valid
equation line:
E=A+B;F=2*(B+C)
We recommend that complex expressions be split into smaller

equations that are easier to understand and troubleshoot. Equations
can contain up to 40 characters.

CB: 2-3-20
Computing the Continuous Output Q
Configure equations that compute the continuous output Q using one of

two ways:
D Q=expression
In this method, use the letter Q. This type of equation is
performed when the block is in Manual or Auto mode. For
example:
Q=A+B
This method overrides tracking and also overrides operator entry when
the block is in Manual mode.
D expression
In this method, do not use the letter Q. This type of equation is
performed only when the Math block is in Auto mode. For
example:
A+B
Any equation of the first type overrides all equations of the second type
in a Math block. To be effective, this expression must be the last
equation written in the block faceplate.
Computing the Value of a Continuous Input
Configure equations that compute the value of a continuous input in the

following way:
D Input Register=expression
In this method, place the value of the expression in the specified
continuous input register. For example:
A=B+C

CB: 2-3-21
Example of Temperature-correcting Air Flow Measurement
In this example, a Math block is used to calculate air flow in SCFM

based on measurements of volumetric flow (CFM) and temperature, as
shown in Figure 2.3.18. The flowmeter has been calibrated for a
reference temperature of 200 °F. In this example, pressure is controlled
and has therefore been omitted from the calculation for the sake of
simplicity.
Air Flow
FT--1 TT--1
0 0
0 to 1000 CFM 100 to 300 °F
(at 200 °F) Input B
Corrected Air Flow
MATH
Input A 0 to 1085.7 SCFM
Figure 2.3.18. Example of Temperature-corrected Flow
The following equation can be used to calculate corrected air flow in this
example:
SCFM = CFM  Reference Temp in oRankine

Reference Temp in oRankine
The calculation in this example is performed in steps. Breaking a

complex calculation into parts makes testing and troubleshooting easier
by providing intermediate values. Corrections or modifications can be
made without retyping the whole equation.
The first step is to convert the temperature measurement from °F to

absolute temperature in °R, using the following formula:
T°R = T°F +459.67
The signal received from the transmitter TT--10 (input B) is treated by

the block as having a range of 0 to 1 (0 to 100Þ), which corresponds to
a temperature range of 100 to 300 °F. Remember that the scaling of the
input is used for display only and has no impact on calculations made
within the block. The actual flowing temperature, T°F actual, must
therefore be calculated as follows:
T°F actual = B(span) + Lower Range Value
= B(200) + 100

CB: 2-3-22
Actual absolute temperature is then calculated as follows, and is stored

as input C:
C = B(200) + 100 + 459.67
The second step is calculation of a temperature correction factor, which

is stored as input D.
D=  Reference Temp in ˚Rankine

Actual Temp in ˚Rankine
= 200 +C459.67
The final step is simply to multiply the volumetric flow (input A) by the
correction factor, as shown on the third equation line in Figure 2.3.19.
The Math block Continuous Links screen for the example is shown in
Figure 2.3.20.

Shed
Tag >FLOWCOMP Desc >Temperature Compensator Mode> NONE >OUT>A>B> >
SC>N +--------+
Addr =1A-01 Function >MATH User-Defined Function A | 500.0 |
INPUTS Value Units Tag OUTPUT B | 253.20 |
A >500.0 CFM FLOW1 >480.98 | |
B >253.20 DEG F SENSOR 7 SCFM | |
C 712.87 DEG R SENSOR 9 100-+--------+
D .9620 FACTOR + |
75-+ |
Equation >C=200*B+100+459.67 + |
50-+ |
>D=sqrt+((200+459.67)/C) + |
25-+ |
>A*D + |
0-+--------+
Back Calc > | 480.98 |
Output: OUT || |
+--------+
Low Lim >.00
Block Mode> LOCAL
FULL CONFIG 1
Figure 2.3.19. Continuous Faceplate Screen—Example of Temperature-correcting Flow

CB: 2-3-23

Tag FLOWCOMP Descriptor
Addr =1A-02 Function MATH User-Defined Function
INPUT SOURCE Conv Hold EngZero Eng Max Value Units
A >FT-10 Þno *Þ.00 Þ1000.00 .00 ÞCFM
B >TT-10 Þno *Þ100.00 Þ300.00 100.00 ÞDEG F
C >*VALUE Þ.00 Þ1.00 >559.67 ÞDEG R
D >*VALUE Þ.0000 Þ1.0000 >1.0857 ÞFACTOR
E >
F >
G >
Q Þ.00 Þ1000.00 .00 ÞSCFM
Block Mode> AUTO

CONFIG 1
Figure 2.3.20. Continuous Links Screen—Example of Temperature-correcting Flow

CB: 2-3-24
Example of Calculating the Sum of Flows Using a Math Block
In this example, a Math block is used to sum the values of three flow
transmitters, each with a different range, as shown in Figure 2.3.21.
0 to 100 GPM FLOW

1
FLOW1 + FLOW2 + FLOW3

0 to 250 GPM FLOW S
2
0 to 850 GPM
0 to 500 GPM FLOW

3
Figure 2.3.21. Example of Flow Summation
Part 1: Scaling and Summing the Inputs
First, call up an unconfigured ControlBlock and configure it as a Math

block. Second, on the Continuous Links screen, link the three flow
measurements to inputs A, B, and C as shown in Figure 2.3.22.
Since all three inputs are coming from transmitters via Analog Input
Blocks, each of the three measurements is seen by the calculation as
having a range of 0--100Þ. The scaling entered on the Continuous
Links screen affects only how the values are displayed. It has no effect
on calculations made by the block. To add the three flows together, the
calculation must treat a unit of FLOW2 as being 2.5 times as great as a
unit of FLOW1. Likewise a unit of FLOW3 must be given five times the
weight of a unit of FLOW1. One solution is to write a single equation as
follows:
Q = A + 2.5 * B + 5 * C
This equation is entered on the Continuous Faceplate screen, as shown

in Figure 2.3.23.

CB: 2-3-25

Tag Descriptor
Addr Function MATH User-Defined Function
A >FLOW1 Þno Þ.00 Þ100.00 .00 ÞGPM
B >FLOW2 Þno Þ.00 Þ250.00 .00 ÞGPM
C >FLOW3 Þno Þ.00 Þ500.00 .00 ÞGPM
D >
E >
F >
G >
Q Þ.00 Þ100.00 >.00 Þ
Block Mode> LOCAL

CONFIG 1
Figure 2.3.22. Continuous Links Screen—Example of Flow Summation

Shed
Tag >FLOWCOMP Desc > Mode>
NONE >OUT>A>B>C>
SC>N +--------+
A 50.00 GPM FLOW1 >150.00 C | 50.00 |
B 50.00 GPM FLOW2 GPM | |
C 50.00 GPM FLOW3 100- +--------+
+ |
75- + |
Equation >Q=A+2.5*B+5*C + |
50- + |
> + |
25- + |
> + |
0- +--------+
Back Calc > | 150.00 |
Output: OUT || |
+--------+
Low Lim >.00
Block Mode> LOCAL
FULL CONFIG 1
Figure 2.3.23. Continuous Faceplate Screen—Example of Flow Summation

CB: 2-3-26
Part 2: Scaling the Output
The maximum for the result of this calculation, when all three flows are
at full scale (100Þ), is:
Q = 100Þ + 2.5*100Þ + 5*100Þ = 850Þ
An output of greater than 100Þ is acceptable if the value is to be

displayed numerically or used as an input to another calculation. If,
however, the result is to be displayed as a bar on a continuous
faceplate the calculation must be revised to ensure that the result never
exceeds 100Þ. In this example the simplest solution is to divide the
result by 8.5, as shown in Figure 2.3.24.
The output (Q), as defined on the Continuous Links screen, must then
be scaled such that 100Þ is displayed as 850 GPM, as shown in
Figure 2.3.24.

Shed
Tag >FLOWCOMP Desc > Mode>
NONE >OUT>A>B>C>
SC>N +--------+
A 50.00 GPM FLOW1 >150.00 C | 50.00 |
B 50.00 GPM FLOW2 GPM | |
C 50.00 GPM FLOW3 100- +--------+
+ |
75- + |
Equation >Q=A+2.5*B+5*C + |
50- + |
> + |
25- + |
> CB CONTINUOUS LINKS + |
0- +--------+
Back Calc > | 150.00 |
Output: OUT || |
+--------+
Q Þ.00 Þ850.00 Low Lim >.00
150.00 ÞGPM
Block Mode> LOCAL
FULL Block Mode>AUTO CONFIG 1
Figure 2.3.24. Converting the Output to a 0 to 100% Range

CB: 2-3-27
Example of Tracking Through a Math Block
Figure 2.3.25 shows an example of a Math block that is performing an

intermediate calculation in a cascade control scheme. The secondary
block is configured to send tracking values through the Math block Q
output. The Math block is configured to send tracking values through
the Math block C input to the primary block.
Use the “Max Gain” field or the “Back Calc” field to track values in a
Math block.
Primary
A
Q=A+B+C
Math Block
B
Secondary
Figure 2.3.25. Tracking Through a Math Block
Tracking Using the “Max Gain” Field
“Max Gain” determines the rate of response of the actual tracking value
sent along the Track Input entry to the tracking value (either generated
by Back Calc or received from another block through a forward link).
The larger the Max Gain entry, the slower the response of the tracking
value.
Configure tracking for the example in Figure 2.3.25, using the “Max
Gain“ field on the Continuous Faceplate screen of the Math block. The
change in the tracking value sent through the C input to the primary
block is expressed by the following equation:
(QCALCULATED -- QACTUAL)
DC =
(“MAX GAIN”)

CB: 2-3-28
Tracking Using the “Back Calc” Field
“Back Calc” is used to generate the tracking value to be sent back on

the link specified by the Track Input entry.
Configure tracking for the example in Figure 2.3.25 using the “Back
Calc” field on the Continuous Faceplate screen of the Math block. The
tracking value is determined by the “Back Calc” field equation.
- To determine the “Back Calc” field equation for the example:
1. Determine the equation that calculates the output. In this
example,
Q=A+B+C
2. Substitute the letter V for Q. The letter V represents the tracking
value sent back along the output Q.
3. Solve the equation for the “Track Input” entry. In this example,
the equation is solved for C.
C=V--(A+B)
4. Enter the right side of the solved equation at the “Back Calc” field
on the Continuous Faceplate screen. In this example,
“Back CalcÞV--(A+B)”.
The “Inverted” field appears.
5. Enter the desired selection to “Inverted” field. Select “Yes” if an
increasing tracking input decreases the output. Select “No” if the
output increases, as it does in this example.

CB: 2-3-29
Nonlinear Functions
Use the Piecewise Linear Interpolator (PLI) and Polynomial (POLY)

functions in applications requiring nonlinear functions such as cylindrical
tank linearization, fuel/air ratio control, and compressor surge control.
PLI and POLY provide an approximation of the nonlinear curve.
Piecewise Linear Interpolator (PLI) Function
The Piecewise Linear Interpolator (PLI) function approximates a curve

with a series of straight line segments. Enter up to 96 pairs of input and
output values to approximate the curve.
Polynomial (POLY) Function
The Polynomial (POLY) function approximates a curve with a

polynomial equation. Enter coefficients for up to a seventh order
polynomial to approximate the curve. The POLY function can usually
provide a smoother curve fit than the PLI function. However, it is usually
difficult to determine the required coefficients for the polynomial
equation.

CB: 2-3-30
Using Line Segments to Approximate a Curve—PLI Function
The Piecewise Linear Interpolator (PLI) function approximates a curve

with a series of straight line segments. You enter up to 96 pairs of
input/output values. The PLI function approximates the curve by
creating a series of straight line segments from the input/output values.
When the block receives an input value, the PLI function determines the
output value based on the approximated curve. The PLI function has
the following configuration characteristics:
D You must configure nonzero input/output pairs in ascending order
of input values.
D If a received input value is larger than the input value you
entered for the highest input/output pair, then the resulting output
value is the output value of the highest input/output pair.
Likewise, if a received input value is smaller than the input value
you entered for the lowest input/output pair, then the resulting
output value is the output value of the lowest input/output pair.
Figure 2.3.26 shows the Continuous Faceplate screen for the PLI
function. Table 2.3.5 describes the PLI function fields on the Continuous
Faceplate screen. Figure 2.3.27 shows the PLI function Continuous

Shed
Tag > Desc > Mode> NONE>OUT>A>B>C
SC>N +--------+
Addr =1A-01 Function >PLI Piecewise Linear Interpolator PV | .00 |
PV .00 >.00 C | .00 |
B >.00 | |
C >.00 100- +--------+
+ |
75- + |
Track Input >None Max Gain >16 + |
50- + |
PV OUT PV OUT PV OUT + |
25- + |
1 > 2 > 3 > + |
0- +--------+
4 > 5 > 6 > | .00 |
OUT || |
7 > 8 > 9 > | |
+--------+
10 > 11 > 12 >
Block Mode> LOCAL
FULL CONFIG 1
Figure 2.3.26. Continuous Faceplate Screen—Piecewise Linear Interpolator Function

CB: 2-3-31
Table 2.3.5. Piecewise LInear Interpolator Function Continuous Faceplate Fields
Access
Level
Determines the rate of response of the

tracking signal sent along the “Track Input”
entry to the tracking signal received or
initiated by the block.
The larger the “Max Gain” entry, the slower
the response of the tracking signal, as shown PV, B to O,
Max Gain Conf in the following equation: --999999. to 999999.
(D “Track Input”) Default=16.
= (D received tracking signal)
(“Max Gain”)
Where, if tracking is used, Max Gain is
greater than or equal to the maximum
Doutput/DPV of the configured curve.
PV1 to PV96 of data points (PV1,Out1) to

(PV96,Out 96).
PV1 to PV96 Conf When you have configured the last PV entry --999999. to 999999.
on a page, use the [PAGE AHEAD] key to
access the next 12 data point entries.
OUT1 to OUT96 of data points (PV1,OUT1)

OUT1 to OUT96 Conf --999999. to 999999.
to (PV96,OUT96)

Tag Descriptor
Addr Function PLI Piecewise Linear Interpolator
PV >*ENTRY Þ.00 Þ100.00 >.00 Þ
B >
C >
D >
E >
F >
G >
Q Þ.00 Þ100.00 >.00 Þ
Block Mode> LOCAL
Figure 2.3.27. Continuous Links Screen—Piecewise Linear Interpolator Function

CB: 2-3-32
Example of a Piecewise Linear Interpolator Function Application
Figure 2.3.28 shows a typical PLI application. A transmitter measures

the level of a horizontal cylinder tank. The PLI function calculates a
volume from the tank level using pairs of input/output points that are
entered by the user.
The Continuous Faceplate screen for the PLI example is shown in

Figure 2.3.29.
L4
L3
L2
L1
L0
A Q
LT PLI
100
LEVEL % VOLUME %
75 0 0
12.5 7.2
25 19.6
VOLUME 50 37.5 34.2
(Q)
50 50
62.5 65.8
25
75 80.4
87.5 92.8
0 100 100
0 25 50 75 100
LEVEL (A)
Figure 2.3.28. Example of a Piecewise Linear Interpolator Application

CB: 2-3-33

Shed
SC>N +--------+
Addr =1A-01 Function >PLI Piecewise Linear Interpolator PV | .00 |
PV .00 >.00 C | .00 |
B >.00 | |
C >.00 100- +--------+
+ |
75- + |
50 - + |
PV OUT PV OUT PV OUT + |
25- + |
1 >0.00 >0.00 2 >12.50 >7.20 3 >25.00 >19.60 + |
0- +--------+
4 >37.50 >34.20 5 >50.00 >50.00 6 >62.50 >65.80 | .00 |
OUT || |
7 >75.00 >80.40 8 >87.50 >92.80 9 >100.00 >100.00 | |
+--------+
10 >34.00 >34.00 11 >87.50 >92.80 12 >100.00 >100.00
Block Mode> LOCAL
FULL CONFIG 1
Figure 2.3.29. Continuous Faceplate—Example of a Piecewise Linear Interpolator Application

CB: 2-3-34
Using a Polynomial Equation to Approximate a Curve—POLY

Function
Hand-held calculators are available that can determine the coefficients

for a polynomial from a set of X and Y points. You will need a computer
to find the coefficients for polynomials greater than third-order. The
following equation is used for the POLY function:
Q = K0C + K1(A + B) + K2(A + B)2 + K3(A + B)3 +
K4(A + B)4 + K5(A + B)5 + K6(A + B)6 +
K7(A + B)7
Figure 2.3.30 shows the Continuous Faceplate screen for the POLY
function. Table 2.3.6 describes the POLY fields on the Continuous
Faceplate screen. Figure 2.3.31 shows the Continuous Links screen for
the POLY function. For a description of the fields that are common to all

Shed
SC>N +--------+
Addr =1A-01 Function >POLY Polynomial Function A | .00 |
A .00 >.0000 C | .0000 |
B >.00 | |
C >.0000 100- +--------+
+ |
75- + |
50- + |
+ |
25- + |
K0 >0. K1 >0. + |
Output: 0- +--------+
K2 >0. K3 >0. Mn Rate Lim >None | .0000 |
OUT || |
K4 >0. K5 >0. High Lim >None | |
+--------+
K6 >0. K7 >0. Low Lim >None
Block Mode> LOCAL
FULL CONFIG 1
Figure 2.3.30. Continuous Faceplate Screen—Polynomial Function

CB: 2-3-35
Table 2.3.6. Polynomial Function Continuous Faceplate Fields
Access
Level
Determines the rate of response of the tracking

signal sent along the “Track Input” entry to the
tracking signal received or initiated by the block.
The larger the “Max Gain” entry, the slower the
PV, B to O,
response of the tracking signal, as shown in the
Max Gain Conf following equation: --999999. to 999999.
(D “Track Input”)=(D received tracking signal) Default=16.
(“Max Gain”)
where Max Gain is greater than or equal to the
maximum slope of the curve.
Gain of input C. A to O,
K0 Conf [(K0 * C) is added to the actual POLY --999999. to 999999.
calculation.] Default=0.
A to O,
KN Conf Gain of the (A+B)N term. --999999. to 999999.
Default=0.

Tag Descriptor
Addr Function POLY Polynomial
INPUT SOURCE conv Hold Eng Zero Eng Max Value Units
A >*ENTRY Þ.0000 Þ1.0000 >.0000 Þ
B >*ENTRY AÞ.0000 Þ1.0000 >.0000 Þ
C >*ENTRY Þ.0000 Þ1.0000 >.0000 Þ
D >
E >
F >
G >
Q Þ.0000 Þ1.0000 >.0000 Þ
Block Mode> LOCAL

CONFIG 1
Figure 2.3.31. Continuous Links Screen—Polynomial Function

CB: 2-3-36
Example of a Polynomial Function Application
Figure 2.3.32 shows a typical POLY function application. A transmitter

measures the level of a horizontal cylinder tank. The POLY function
calculates a volume from the tank level using the polynomial equation
coefficients that you entered.
The Continuous Faceplate screen for the example is shown in

Figure 2.3.33.
L4
L3
L2
L1
L0
A Q PV Q to FIELD
LT POLY PI DEVICE
LS
DATA USED TO CALCULATE

100 KN COEFFICIENTS
LEVEL% VOLUME %
75 0 0
12.5 7.2
25 19.6
VOLUME 50 37.5 34.2
(Q)
50 50
62.5 65.8
25
75 80.4
87.5 92.8
0 100 100
0 25 50 75 100
LEVEL
Figure 2.3.32. Example of a Polynomial Application

CB: 2-3-37

Shed
Tag > Desc > Mode> NONE>OUT>A>B>C
SC>N +--------+
Addr =1A-01 Function >POLY Polynomial Function A | 50.00 |
A >50.00 >49.99 C | .0000 |
B >.0000 | |
C >.0000 100- +--------+
+ |
75- + |
50- + |
+ |
25- + |
K0 >0. K1 >0.424 + |
Output: 0- +--------+
K2 >1.728 K3 >-1.153 Mn Rate Lim >None | 49.99 |
OUT || |
K4 >0. K5 >0. High Lim >100.00 | |
+--------+
K6 >0. K7 >0. Low Lim >.00
Block Mode> LOCAL
FULL CONFIG 1
Figure 2.3.33. Continuous Faceplate Screen—Example of a Polynomial Application

CB: 2-3-38
Adjustable Ratio and Bias Capabilities—

Ratio/Bias (RB) Function
The Ratio/Bias (RB) function provides adjustable ratio and bias

capabilities. The Ratio/Bias function output is calculated with the
following equation:
Q = (PV -- Pre--Bias) (Ratio) (Ratio Gain) + Bias
Figure 2.3.34 shows a sample application of an RB function as a boiler

master. Figure 2.3.35 shows the Continuous Faceplate screen for the
Ratio/Bias function. Figure 2.3.36 shows the Continuous Links screen,
and Figure 2.3.36 describes the Ratio/Bias fields on the Continuous
Faceplate screen For a description of the fields that are common to all
PLANT MASTER STEAM PRESSURE

T
PV
P+I+D
Q To Other
Boiler Master
LS
Controllers
BOILER MASTER RATIO / BIAS
PV AIR FLOW CONTROLLER

PV
Q
Q P+I+D
PV x RA x RG + BI = Q
LS
BIAS
Operator
POLY FUEL FLOW CONTROLLER
RATIO
Operator PV
Q
P+I+D
RATIO GAIN
LS
Configuror
Figure 2.3.34. Ratio/Bias Used as a Boiler Master

CB: 2-3-39

Shed
SC>N +--------+
Addr =1A-01 Function >RB Ratio/Bias PV | .00 |
INPUTS Value Units Tag OUTPUT RA | .0000 |
PV >.00 >.00 BI | .00 |
RA >.0000 | |
BI >.00 100- +--------+
+ |
75- + |
+ |
50- + |
Ratio Gain >1. Pre-Bias >.00 Track Input>None + |
25- + |
Bias Bar Scaling: Zero >.00 Full Scale >100.00 + |
Ratio: Bias: Output: 0- +--------+
OUT || |
High Lim >1.0000 High Lim >100.00 High Lim >None | |
+--------+
Low Lim >.0000 Low Lim >.00 Low Lim >None
Block Mode> LOCAL
FULL CONFIG 1
Figure 2.3.35. Continuous Faceplate Screen—Ratio/Bias Function

Tag Descriptor
Addr Function RB Ratio/Bias
PV >*ENTRY Þ.00 Þ100.00 >.00 Þ
RA >*ENTRY Þ.0000 Þ1.0000 >.0000 Þ
BI >*ENTRY QÞ.00 Þ100.00 >.00 Þ
D >
E >
F >
G >
Q Þ.00 Þ100.00 >.00 Þ
Block Mode> LOCAL

CONFIG 1
Figure 2.3.36. Continuous Links Screen—Ratio/Bias Function

CB: 2-3-40
Table 2.3.7. Ratio/Bias Function Continuous Faceplate Fields
Access
Level
None, PV, RA, BI, D to

Bias: Maximum rate at which the bias value can
Conf O,
Rate Lim be changed (applies to operator entry only).
.00 to 999999.
None, PV, RA, BI, D to O,

High Lim Conf Bias high limit. --999999. to 999999.
Default=100.00

Low Lim Conf Bias low limit. --999999. to 999999.
Default=.00
Bias Bar Scaling: Value represented as 0 on the continuous --999999. to 999999.

Conf
Zero faceplate bias bar. Default=.00
Value represented as 100 on the continuous --999999. to 999999.

Full Scale Conf
faceplate bias bar. Default=100.00
PV, RA, BI,D to O,

Pre-Bias Conf Pre-bias term of Ratio/Bias equation. --999999. to 999999.
Default=.00
None, PV, RA, BI, D to

Ratio: Maximum rate at which the ratio value can
Conf O,
Rate Lim be changed (applies to operator entry only).
.0000 thru 999999.

High Lim Conf Ratio high limit. --999999. to 999999.
Default=1.0000

Low Lim Conf Ratio low limit. --999999. to 999999.
Default=.0000
PV, RA, BI,D to O,

Ratio Gain Conf Ratio Gain term of Ratio/Bias equation. --999999. to 999999.
Default=1.
Track Input Conf Selects input to send backtracking signals. None, PV, RA, BI
Limited by Ratio high and

Value RA Oper Ratio (Input B) term of Ratio/Bias equation.
low limits.
Limited by Bias high and

Value BI Oper Bias (Input C) term of Ratio/Bias equation.
low limits

CB: 2-3-41
Configuring the Ratio Term on Faceplates
You can configure the ratio term on the continuous and discrete
faceplates of the Ratio/Bias function. Table 2.3.8 describes continuous
faceplate configuration for various ranges of ratio values. The
continuous faceplate allows the operator to adjust only one term, ratio
or bias.
You can configure the discrete faceplate to allow the operator to adjust
both the ratio and the bias terms. For information about configuring
discrete faceplates, see Chapter 5.
Table 2.3.8. Ratio Term Continuous Faceplate Configuration
Range of Ratio
Configuration Comments
Values
If “Eng ZeroÞ0.00” and “Eng MaxÞ1.00”, then the ratio is

Ratio of 0 to 1
accurately represented on the continuous faceplate.
If “Eng ZeroÞ0”, “Eng MaxÞn”, and “Ratio GainÞn”, then the

Ratio of 0 to n
ratio is accurately represented on the continuous faceplate.
Configuring the Bias and Pre-bias Terms
The bias and pre-bias terms allow adjustments to be made to the

relationship between the PV input and the block output according to the
Ratio/Bias Function equation:
Q = (PV -- Pre-bias) (Ratio) (Ratio Gain) + Bias
Table 2.3.9 compares the characteristics of the bias and pre-bias terms.
Table 2.3.9. Bias/Pre-bias Term Comparison
Bias Term Pre-bias Term
Added to output after ratio applied Subtracted from PV before ratio applied
Operator entry Configuror entry
Can be put on faceplate Cannot be put on faceplate

CB: 2-3-42
Configuring the Bias Term on Continuous Links and Continuous Faceplate Screens
Since the bias directly affects the output Q, you should scale the bias
term the same as Q. That is, one unit of bias should be the same as
one unit of Q. Figure 2.3.37 shows a sample Continuous Links screen
with the bias term and the output Q having the same scaling values.
The actual working range of the bias term is usually narrow; ±10% is
typical. This narrow range is not represented well on the continuous
faceplate. The “Bias Bar Scaling” fields on the Continuous Faceplate
screen allow you to scale the bias term bar differently from the “Eng
Zero” and “Eng Max” scaling fields on the Continuous Links screen.
Figure 2.3.37 shows an example that uses the “Bias Bar Scaling” fields
to represent the bias term better on a continuous faceplate.
CB CONTINUOUS LINKS
INPUT SOURCE Conv Hold Eng Zero Eng Max

BI Þ*ENTRY QÞ.00 Þ100.00
Q Þ.00 Þ100.00
The Continuous Links screen entries for

the bias term and the output Q in this example.
BI .00
The faceplate shows how the bias bar is displayed
on the continuous faceplate when:
· Bias Bar Scaling: ZeroÞ--10.00 Full ScaleÞ10.00
· Bias=0.0
50
Figure 2.3.37. Example of Bias Bar Scaling

CB: 2-3-43
Selector Function—Signal Selector (SS) Function
The Signal Selector (SS) function is a general purpose selector that

functions in either the input or output side of a loop. The selector serves
as a one-of-N switch. Figure 2.3.38 shows the Signal Selector functional
block diagram.
Input Data 75 A
75 96
N
Input Data 12 B U
12 M 75
E
Input Data 23 C R
23 I 23
C
Input Data 96 D A
96 L 12
Input Data 100 E

100 S
O
Output
R Q
Limits
T
I
N
O G
0.00
Number of Inputs (N) Select Number

1 thru 15 0 thru 15
Figure 2.3.38. Signal Selector Functional Block Diagram
Figure 2.3.39 shows the Continuous Faceplate for the Signal Selector
function. Table 2.3.10 describes the Signal Selector fields on the
Continuous Faceplate. Figure 2.3.40 shows the Signal Selector function
Continuous Links screen. For a description of the fields that are
common to all continuous ControlBlocks, see Section 1.

CB: 2-3-44

Shed
SC>N +--------+
Addr =1A-01 Function >SS Signal Selector A | .00 |
A >.00 >.00 C | .00 |
B >.00 | |
C >.00 100- +--------+
+ |
75- + |
No of Inputs >All Track Inputs>None + |
50- + |
Select Number >Low Trackband >5.00 + |
25- + |
+ |
Output: 0- +--------+
OUT || |
High Lim >None | |
+--------+
Low Lim >None
Block Mode> LOCAL
FULL CONFIG 1
Figure 2.3.39. Continuous Faceplate Screen—Signal Selector Function
Table 2.3.10. Signal Selector Function Continuous Faceplate Fields
Access
Level
The number of inputs to be used by the

selector. The inputs used start with input A
and go to input O. For example, if the “No of
No of Inputs Conf 0 to 15, All
Inputs” field is 3, inputs A, B, and C are used
by the selector. All other inputs are ignored.
“All” indicates all configured inputs.
Indicates the nth-highest value to be

selected. 0 to 15
1 selects the highest input, 2 selects the 1 shows High, 0 shows
Select Number Conf
second-highest input, and so on. 0 selects Low
the lowest input. The input value selected is Default=Low
put into the block output.
None, A thru O in any

Track Inputs Conf Inputs used to send backtracking signals. combination
(e.g., ADFHN)
A to O
A value, in percent, that limits the amount of
Trackband Conf .00 to 999999.
windup in deselected controllers.
Default=5.00
NOTE: Bold text indicates the default selections.

CB: 2-3-45

Tag Descriptor
Addr Function SS Signal Selector
A >*ENTRY Þ.00 Þ100.00 >.00 Þ
B >*ENTRY AÞ.00 Þ100.00 >.00 Þ
C >*ENTRY AÞ.00 Þ100.00 >.00 Þ
D >
E >
F >
G >
Q Þ.00 Þ100.00 >.00 Þ
Block Mode> LOCAL

CONFIG 1
Figure 2.3.40. Continuous Links Screen—Signal Selector Function
The Signal Selector function has the following characteristics:

D The selected input value is not altered by the Signal Selector
function. However, the output is affected by the output high and
low limits.
D When the function is selecting controller outputs, the unselected
controllers will be open unless you configure tracking to prevent
windup of all unselected controllers.
D You can use the “Hold” field on the Continuous Links screen with
the Signal Selector function. If the Signal Selector function
detects a hold forward signal from an input and the “Hold” field
value for that input is yes, then the input is not used by the
selector. The Signal Selector itself does not pass a hold forward
signal until all inputs send hold forward signals. This feature is
intended for selectors with inputs from multiple transmitters.
D The inputs have no gain factor. All selectable inputs and the
output should have the same scaling.

CB: 2-3-46
D The “Trackband” field is used with the “Track Input“ field to

prevent windup in controllers that are being used by the Signal
Selector function. As an example, Figure 2.3.41 shows a Signal
Selector function selecting between three PID controllers. The
selected PID controller signal is sent to the output device. The
deselected PID controllers are in open loop situations and
experience windup.
All inputs specified in the “Track Input” field track the selected
controller. The “Trackband” value specifies how close, in percent,
the deselected controllers track the selected controller. For
example, if “Track InputÞA,B,C” and “TrackbandÞ5.00” in
Figure 2.3.41, then input A and input C will be no less than
5.00% lower than input B. Unselected inputs may move toward,
but not away from, the selected input.
High
Signal Selector
Function
PID
Controller Input
A A
PID
Controller Input Output
B Device
B
PID Input
Controller C
C
If “Track InputÞA,B,C” and “TrackbandÞ5.00”,

then input A and input C will be no less than 5.00%
lower than input B.
Figure 2.3.41. Example of a Signal Selector Function

CB: 2-3-47
Totalizer Functions
A Totalizer function may be used to act as a setpoint function or a

stacking function.
Configuring a Setpoint Totalizer Function—TOTSP Function
The Setpoint Totalizer (TOTSP) function is an integrator with an output

that rolls over and resets to zero when the output reaches a high limit.
Figure 2.3.42 shows the TOTSP functional block diagram.
INPUT DATA
A
LOW
CUTOFF
+
SIGNED
INTEGRATOR Q
GAIN
BAND
--
Figure 2.3.42. Setpoint Totalizer Functional Block Diagram
D The Setpoint Totalizer function has the following characteristics:

D The totalizing equation is:
(input A)(gain K)
new total = previous total +
integration time
D The previous total has extended precision to minimize truncation

error for long integration times.
D A positive input value increases the total; a negative input value
decreases the total.

CB: 2-3-48
D Logic steps o and p are set by the Setpoint Totalizer function and
must be cleared by user logic.
— Logic step o is set when overflow occurs; that is, when the
value of the total exceeds the high output limit. When logic
step o is set, the high limit value is subtracted from the total
value.
— Logic step p is set when underflow occurs; that is, when the
value of the total goes below the low limit.
D The setpoint is not used by the TOTSP function.
Figure 2.3.43 shows the TOTSP Continuous Faceplate screen.

Table 2.3.11 describes the TOTSP fields on the Continuous Faceplate
screen. Figure 2.3.44 shows setpoint totalizer cutoff types.
Figure 2.3.45 shows the TOTSP function Continuous Links screen. For
a description of the fields that are common to all continuous

Shed
Tag > Desc > Mode>
NONE >OUT>A>B>C>
SC>N +--------+
Addr =1A-01 Function >TOTSP Setpoint Totalizer PV | .00 |
INPUTS Value Units Tag OUTPUT SP | .00 |
PV >.00 >.00 C | .00 |
SC >.00 | |
C >.00 100- +--------+
+ |
75- + |
Gain K >1 Integ Time>1. M Low Cutoff >.00 + |
50- + |
Cutoff Type>Signed + |
25- + |
+ |
Output: 0- +--------+
OUT || |
High Lim >None | |
+--------+
Low Lim >None
Block Mode> LOCAL
FULL CONFIG 1
Figure 2.3.43. Continuous Faceplate Screen—Setpoint Totalizer Function

CB: 2-3-49
Table 2.3.11. Setpoint Totalizer Function Continuous Faceplate Fields
Access
Level
Determines the values that are totalized.

Refer to Figure 2.3.44.
If “Signed”, any value above the low cutoff
Cutoff Type Conf Signed, Band
is totalized.
If “Band”, any value outside the plus to
minus low cutoff is totalized.
PV, SP, C to O,
Gain K Supr Gain of input A (PV). --999999 to 999999.
Default=1.
Integration time is the time that it takes the PV, SP, C to O,

Integ Time Conf output to go from 0% to 100% when the 0.S to 999999.H
input is at 100%. Default=1. M
PV, SP, C to O,
Low cutoff value. This must be a positive --999999 to 999999.
Low Cutoff Conf
value for a Band “Cutoff Type”.
Default=.00
Signed Cutoff of 10% Band Cutoff of 10%
100% 100%
PASS PASS I
N
F
10% L
10%
O
IGNORE IGNORE W
0% 0%
IGNORE O
U
--10% T
PASS F
L
O
100% 100% W
Figure 2.3.44. Setpoint Totalizer Cutoff Types

CB: 2-3-50
A totalizer stops if it receives

a hold forward on an input.

Tag Descriptor
Addr Function TOTSP Setpoint Totalizer
PV >*ENTRY Þ.00 Þ100.00 >.00 Þ
SP >*ENTRY QÞ.00 Þ100.00 >.00 Þ
C >
D >
E >
F >
G >
Q Þ.00 Þ100.00 >.00 Þ
Block Mode> LOCAL

CONFIG 1
Figure 2.3.45. Continuous Links Screen—Setpoint Totalizer Function

CB: 2-3-51
Configuring a Stack Totalizer Function—Stack Totalizer (TOT)

Function
The Stack Totalizer (TOT) function is an integrator with an output that

resets to zero when it reaches a high limit or a reset indication. The
TOT function input and output registers contain the following values:
D A input register Current PV value
D Q input register Current accumulated total
D B output register Previous Q value
D C input register Previous B value
D D output register Previous C value
Each time the output is reset, its value is placed at the top of a “stack”
consisting of inputs B, C, and D and the stack is shifted down one place.
Figure 2.3.46 shows the Stack Totalizer functional block diagram.
NOTE: To save memory, configure Q at the bottom of the Continuous

Links screen rather than link to Q with each of the totalizers.
Input Data
A
Signed +
Low
Cutoff
Integrator Q
Gain Band --
B Periodic Reset
Figure 2.3.46. Stack Totalizer Functional Block Diagram

CB: 2-3-52
The TOT function is similar to the TOTSP function. Logic steps o and p
are set by the Setpoint Totalizer function and must be cleared by user
logic.
D Logic step o is set when overflow occurs; that is, when the value
of the total exceeds the high output limit. When logic step o is
set, the high limit value is subtracted from the total value.
D Logic step p is set when underflow occurs; that is, when the
value of the total goes below the low limit.
You can configure an action logic statement to reset a stack totalizer

and shift inputs B,C, and D, bypassing the “Periodic Reset” fields on the
Continuous Faceplate screen for the TOT function ControlBlock. See
Chapter 6 for more details on the treset function.
Figure 2.3.47 shows the Stack Totalizer Continuous Faceplate screen.

Table 2.3.12 describes the TOT fields on the Continuous Faceplate
screen. Figure 2.3.48 shows the TOT function Continuous Links screen.
For a description of the fields that are common to all continuous

Shed
SC>N +--------+
Addr =1A-01 Function >TOT Stack Totalizer PV | .00 |
INPUTS Value Units Tag OUTPUT T1 | .00 |
PV >.00 >.00 T2 | .00 |
T1 >.00 T3 | .00 |
T2 >.00 100- +--------+
T3 >.00 + |
75- + |
Gain K >1 Integ Time>1. M Low Cutoff >.00 + |
50- + |
+----------Periodic Reset---------+ Cutoff Type>Signed + |
25- + |
First Reset >01-Jan-80 >00:00:00 + |
Output: 0- +--------+
Reset Period >0 Days >00:00:00 Mn Rate Lim >None | .00 |
OUT || |
Next Reset 01-Jan-80 00:00:00 High Lim >None | |
+--------+
Low Lim >None
Block Mode> LOCAL
FULL CONFIG 1
Figure 2.3.47. Continuous Faceplate Screen—Stack Totalizer Function

CB: 2-3-53
Table 2.3.12. Stack Totalizer Function Continuous Faceplate Fields
Access
Level
Determines the values that are totalized.

See Figure 2.3.44.
If “Signed”, any value above the low cutoff
Cutoff Type Conf Signed, Band
is totalized.
If “Band”, any value outside of the plus to
minus low cutoff is totalized.
PV,T1, T2, T3, E to O or

Gain K Conf Gain of input A (PV). --999999. to 999999.
Default=1.
Integration time is the time that it takes the PV,T1, T2, T3, E to O or
Integ Time Conf output to go from 0% to 100% when the 0.S to 999999.H
input is at 100%. Default=1. M
PV,T1, T2, T3, E to O or

Low cutoff value. Must be a positive value --999999. to 999999.
Low Cutoff Conf
for a Band “Cutoff Type“.
Default=.00
Any calendar date

Periodic Reset Date and time (24-hour clock) of first
Conf Default=01--JAN--80
First Reset* time-based reset.
00:00:00
Periodic Reset Date and time (24-hour clock) of next

NA Display only
Next Reset* time-based reset.
0 to 366 days and any

Periodic Reset Time interval of reset period in days and time of day
Conf
Reset Period* with a 24-hour clock. Default=0 DAYS
00:00:00
Value T1
--999999. to 999999.
Value T2 Conf Value of previous totals.
Default=.00
Value T3
* If periodic reset is not desired, a treset logic function can be configured to reset the totalizer. For more
information about the treset function, see Chapter 6: Configuring Logic Steps.

CB: 2-3-54

Tag Descriptor
Addr Function TOT Stack Totalizer
PV >*ENTRY Þ.00 Þ100.00 >.00 Þ
T1 >*ENTRY QÞ.00 Þ100.00 >.00 Þ
T2 >*ENTRY QÞ.00 Þ100.00 >.00 Þ
T3 >*ENTRY QÞ.00 Þ100.00 >.00 Þ
E >
F >
G >
Q Þ.00 Þ100.00 >.00 Þ
Block Mode> LOCAL

CONFIG 1
Figure 2.3.48. Continuous Links Screen—Stack Totalizer Function

CB: 2-3-55
Configuring Setpoint or Stack Totalizers
You can use a number of factors to configure setpoint or stack

totalizers. Determine the following values for a totalizer:
D Resolution Smallest unit to be totalized. Some examples
are gallons, 10 gallons, cubic feet, and pounds.
The resolution is related to the units of the
process variable input.
D Input maximum Largest input value that can be received.
D Integration time Amount of time in which totalizing occurs. This is
the amount of time that it takes the output to
reach full scale.
Table 2.3.13 shows some sample values for totalizers. Table 2.3.14
shows the maximum integration times possible for various input
maximum values.
Table 2.3.13. Example of Totalizer Values
Integration Time Input Maximum Output Maximum Resolution
24 hours 500 gpm 720000 gallons 1 gallon
24 hours 1000 gpm 144000 (10 gallons) 10 gallons
8 hours 1000 gpm 480000 gallons 1 gallon
168 hours (1 week) 100 gph 16800.0 gallons 0.1 gallon
24 hours 100 gph 2400.00 gallons 0.01 gallons

CB: 2-3-56
Table 2.3.14. Maximum Integration Times for Various Input Maximums
Input Maximum
Resolution Maximum Integration Time
(per minute)
1 unit 100 units 166.67 hours
- To configure “Integ Time” and output “Eng Max” for totalizers:

1. Use the following formula to determine the value:
(input maximum in units/hr) (integration time in hrs).
a. If the resulting value is less than 1,000,000, go to step 2.
b. If the resulting value is greater than 1,000,000, a decision
must be made. The totalizer block cannot display values
higher than 1,000,000. Two options are available:
— Display only the six most significant digits. If this is
acceptable, go to step 2.
or
— Decrease the integration time. Return to the beginning of step
1.
2. Enter the result of step 1 in the output “Eng Max” field on the
totalizer block Continuous Links screen. The output high limit on
the Continuous Faceplate screen changes to reflect the new
“Eng Max“ value. When the output high limit is reached, the
totalizer is reset to the low limit value, plus any overflow.

CB: 2-3-57
Rate-limited Function—Velocity Limiter (VLIM) Function
This algorithm provides an output that is a rate-limited function of the

input. You can configure the rate limits for output rise and fall separately.
Thus a valve can be rate limited when opening and unlimited when
closing. The VLIM algorithm is active when the block is in Auto mode.
If the deviation between the input and the output exceeds the upper and
lower limits that you configured separately, the rate limit can be
different. Thus the output can move faster (or not at all) if the difference
between input and output is too great.
This function is useful for converting a logic signal to a two-speed ramp

for a setpoint or a valve. It is also the only way to rate limit an output
that is in an automatic mode.
Rate limits are expressed in engineering units of the input per second
and are accurate regardless of sample time. If the difference between
output and input is less than the rate limit, the output is exactly equal to
the input.
Figure 2.3.49 shows the Continuous Faceplate for the Velocity Limiter
(VLIM) function. Table 2.3.15 describes the Velocity Limiter fields on the
screen. Figure 2.3.50 shows the VLIM function Continuous Links
screen. For a description of the fields that are common to all continuous

CB: 2-3-58

Shed
Tag > Desc > Mode>
NONE >OUT>A>B>C>D
SC>N +--------+
Addr =1A-01 Function >VLIM Velocity Limiter PV | .00 |
PV >.00 >.00 C | .00 |
B >.00 D | .00 |
C >.00 100- +--------+
D >.00 + |
75- + |
+ |
50- + |
+ |
25- + |
Track PV >no + |
Output: 0- +--------+
Rise Limit >None Fall Limit >None Mn Rate Lim >None | .00 |
OUT || |
Dev Trigger >None Dev Trigger >None High Lim >None | |
+--------+
Rise Hi Lim >None Fall Hi Lim >None Low Lim >None
Block Mode> LOCAL
FULL CONFIG 1
Figure 2.3.49. Continuous Faceplate Screen—Velocity Limiter Function
Table 2.3.15. Velocity Limiter Function Continuous Faceplate Fields
Access
Level
When (Q -- PV) > deviation trigger, the Fall None, PV, B to O,

Dev Trigger (Fall) Conf
High Limit is used. --999999. to 999999.
When (PV -- Q) > deviation trigger, the Rise None, PV, B to O,

Dev Trigger (Rise) Conf
High Limit is used. --999999. to 999999.
Rate limit is used in decreasing direction None, PV, B to O,

Fall Hi Lim Conf
when deviation trigger is exceeded. .00 to 999999.
Normal rate limit in the decreasing None, PV, B to O,

Fall Limit Conf
direction. .00 to 999999.
Rate limit used in increasing direction when None, PV, B to O,

Rise Hi Lim Conf
deviation trigger is exceeded. .00 to 999999.
None, PV, B to O,
Rise Limit Conf Normal rate limit in the increasing direction.
.00 to 999999.
Selects backtracking on the PV (A) input.

Track PV Conf If “Yes”, the PV instantly equals the output no, yes
if the output receives tracking signals.

CB: 2-3-59

Tag Descriptor
Addr Function VLIM Velocity Limiter
A >*ENTRY Þ.00 Þ100.00 >.00 Þ
B >
C >
D >
E >
F >
G >
Q Þ.00 Þ100.00 >.00 Þ
Block Mode> LOCAL

CONFIG 1
Figure 2.3.50. Continuous Links Screen—Velocity Limiter Function

CB: 2-3-60

CB: 2-4-1
Section 4:
Configuring ControlBlock Discrete Functions
This section describes the discrete (or contact) ControlBlock functions:

D User-defined discrete ControlBlock
D Preconfigured motor controller functions
D Preconfigured valve controller functions
Function Page
Function Name For Use With:
Mnemonic Number
The discrete template for display

DISC Discrete 2-4-2
purposes. Logic steps.
DMC Discrete Motor Controller A single-speed electric motor 2-4-6
A single-speed electric motor, which is

Discrete Auto Sequence Motor one of several that must be
DASMC 2-4-14
Controller automatically started in a predetermined
sequence
Discrete Dual Speed Motor

DDSMC A two-speed electric motor 2-4-23
Controller
Discrete Dual Direction Motor

DDDMC A reversible electric motor 2-4-31
Controller
Any valve, such as a solenoid valve,

which requires a contact closure to
DVC Discrete Valve Controller 2-4-42
maintain the open position, closed
position, or both positions.
Similar to DVC, except the valve is one

Discrete Auto Sequence Valve of several that must be automatically
DASVC 2-4-50
Controller
opened in a predetermined sequence.
Motorized valve operators, which

DMVC Discrete Motorized Valve Controller require a contact closure to change 2-4-58
position but not to maintain position.
RS3: Configuring ControlBlock Functions Configuring ControlBlock Discrete Functions

CB: 2-4-2
User Defined Discrete ControlBlock—Discrete (DISC)

Function
The block output (Q) of a ControlBlock configured with the Discrete

function is determined by the operator. The Discrete function is intended
for two primary uses:
D To utilize the discrete faceplate for display purposes.
D As a place for the configuror to get access to logic steps when he
or she is not concerned with the major function of the
ControlBlock.
Figure 2.4.1 shows a typical Discrete function control loop. You

configure a ControlBlock for the Discrete function on the Discrete
Faceplate screen. All of the screen fields that appear for a Discrete
function ControlBlock are described in Chapter 5. The operator is not
required to make any entries for the block to be functional. However, the
operator can only control the output if the block is in Manual or Local
mode. If the block mode is Auto mode, the output maintains its last
value, because there is no function to change it. If desired, you can
configure logic to change the output.
Field Optional Field

Device Device
Measurement or
Process Variable Open/Close
(Not Required) Valve
CONTROLLER CARD
Analog A Q Analog
FIC Control FIC
Input Output
Block
Block Block
Operator Controls
the Output
Figure 2.4.1. Typical Discrete Function Control Loop

CB: 2-4-3
Preconfigured Motor Controller Functions
The preconfigured motor control functions allow a motor to be actuated

automatically by a ControlBlock or manually from a discrete faceplate
on a group display. A function of this type becomes the major function of
the block, using both the discrete and continuous portions of the block.
Table 2.4.1 lists and describes the motor controller functions.
The following features are common to all of the motor controllers:

D Provision for automatic or manual commands.
D Inputs for feedback of actual operating state (on/off).
D Alarming if the device does not respond to the command within a
preset time limit.
D Interlock and shutdown inputs that can override both automatic
and manual operations.
Table 2.4.1. Discrete Motor Controllers
Function
Mnemonic
DMC Discrete Motor Controller A single-speed electric motor
A single-speed electric motor, which is one of

DASMC Discrete Auto Sequence Motor Controller several that must be automatically started in a
predetermined sequence
DDSMC Discrete Dual Speed Motor Controller A two-speed electric motor
DDDMC Discrete Dual Direction Motor Controller A reversible electric motor

CB: 2-4-4
Preconfigured Information for a Motor Controller
A preconfigured motor controller has all of the following information

already configured:
D The discrete steps required to perform logic.
D The discrete and continuous inputs required, with the appropriate
message pairs already chosen for display purposes. The inputs
are preconfigured on the Discrete Links and Continuous Links
screens.
D The Discrete Faceplate screen in order to display all commands
and feedback signals.
You can change any preconfigured information, but you cannot reduce
the number of inputs.
Unconfigured Information for a Motor Controller
You can use the unconfigured continuous inputs, A through E and J

through O, to monitor variables related to the motor, such as motor
current and motor speed. Since the ControlBlock continuous faceplate
is not required for the major block function, you can configure the
continuous faceplate to display information that you define. For more
information about configuring a continuous faceplate, see Section 1.

CB: 2-4-5
Effect of Block Mode on Motor Controller Operation
The operation of a motor controller function ControlBlock depends on

the block mode that you configure. Set the block mode using the “Block
Mode” field in the lower right corner of the ControlBlock configuration
screens. Table 2.4.2 describes the effect of each block mode on the
ControlBlock.
Table 2.4.2. Effect of Motor Controller Block Mode
Block Mode Description
Block responds only to auto commands (Start, Stop, etc.), which are received
Auto
through inputs @d, @e, and @f. Block ignores commands from the keyboard.
Used with the Supervisory Computer Interface (SCI). You must configure the block
shed mode.
Computer Block output value responds to commands from an SCI. If the SCI timer expires
(DDC) before an SCI write occurs, the block responds as the configured shed mode.
No commands are accepted.
NOTE: DDC is not a useful operating mode for a motor controller.
No commands are accepted, but the output state is maintained and alarms and
Local interlocks function as you configured.
NOTE: Local is not a useful operating mode for a motor controller.
Operator Block responds only to keyboard commands (operator-entered), which are received
(or Manual) through inputs @a, @b, and @c. Block ignores auto commands.
Remote Cannot be selected for discrete motor controller functions.

CB: 2-4-6
Discrete Motor Controller (DMC) Configuration
The Discrete Motor Controller (DMC) function is a preconfigured

ControlBlock for use with a single-speed electric motor. Figure 2.4.2
shows a control loop using a DMC function to operate a motor.
Although the DMC function is preconfigured, you must configure several

discrete links and select any desired configuration options.
Contact ControlBlock Contact Single-

Input Block DMC
Confirm Start/stop Output Block Start/stop speed
On outputs timers Electric
Motor
Contact
Input Block
(Optional)
Confirm
Off
Figure 2.4.2. Example of a Discrete Motor Controller Control Loop

CB: 2-4-7
Links Required for DMC Operation
Although the DMC is preconfigured, you must configure several discrete

links for a DMC to become operational. Configure these links on the
Discrete Links screen. Table 2.4.3 summarizes the discrete links that
are required to make the block operational so that it can be used to
control a single-speed motor automatically or manually. Figure 2.4.3
shows the preconfigured discrete faceplate that displays the operation
of the motor.
A DMC also has five preconfigured continuous inputs: F, G, H, I, and J.

The remaining continuous inputs, A through E and K through O, you
can configure as needed.
Table 2.4.3. Required LInks for DMC Configuration
Link: To:
Source (start) Contact Output Block 1. Start output (step a) of the DMC
Source (stop) Contact Output Block, if used 2. Stop output (step b) of the DMC
@g (Confirm On input) 3. Input from a Contact I/O block
@h (Confirm Off input) , if used 4. Input from a Contact I/O block
@d, if used 5. Automatic start signal (Auto mode only) of the DMC
@e, if used 6. Automatic stop signal (Auto mode only) of the DMC
1 OPERATOR
Manual control 2 > start
3 > stop
4
5 --AUTO--
Automatic control 6 start
7 stop
8
9 ---------
10 on cfrm
Configuration options 11 off cfrm
12 tripped
13
14 -OUTPUT-
Motor response 15 run
16 STOP
17 failed
Figure 2.4.3. Discrete Faceplate for a Typical DMC

CB: 2-4-8
Configuration Options for a DMC
After configuring the required discrete links to make the DMC

operational, you can choose from various configuration options for the
DMC. You select configuration options on the Continuous Faceplate
screen and you can change the preconfigured and unconfigured
options.
Figure 2.4.4 shows the default Continuous Faceplate screen for a DMC.
The shaded box in Figure 2.4.4 shows the area where the configuration
options are selected. The Continuous Faceplate screen displays the
DMC timer operation.
Table 2.4.4 lists the DMC options that appear on the Continuous
Faceplate screen. The “Yes” selection implements a desired option. The
“No” selection cancels any undesired option. If a selected entry requires
a timer or counter entry, the entry field appears when you select the
option.

Shed
Tag > Desc > Mode>
NONE >OUT>A>B>C>D
SC>N +--------+
Addr =1A-01 Function >DMC Motor Controller A | .00 |
A >.00 >.00 C | .00 |
B >.00 D | .00 |
C >.00 100- +--------+
D >.00 + |
75- + |
INPUTS F G + |
50- + |
Target >5. >2. + |
Value 0. 0. 25- + |
Units secs secs + |
Func STRT TMR STOP TMR 0- +--------+
| .00 |
Interlock >no Retry >no OUT || |
| |
Confirm Off >no Security Lockup >no +--------+
Ignore Confirm On >no Trip Delay>no Block Mode> LOCAL
FULL CONFIG 1
Figure 2.4.4. Default Continuous Faceplate Screen—DMC

CB: 2-4-9
Table 2.4.4. Configuration Options--DMC
Option Access Function
If “Yes”, @h is expected to be true within a preset time period G

following a Stop command (step b); otherwise an alarm (step h)
Confirm Off Conf occurs.
If “No”, the false state of @g (Confirm On) constitutes a Confirm Off.
If “Yes”, no alarm occurs even though Confirm Off is not received

Ignore Confirm Off Supr when expected. Permits temporary bypass of @h. Field appears only
if “Confirm OffÞyes”.
If “Yes”, no alarm occurs even though Confirm On, Forward,

Ignore Confirm On Supr Reverse, High, or Low is not received when expected. Permits
temporary bypass of @g and /or @i.
If “Yes”, the motor can start or run even though @k is false. Permits
Ignore Interlock Supr
temporary bypass of @k. Field appears only if “InterlockÞyes”.
If “Yes”, @k must be true for the motor to start or to remain running,

Interlock Conf
regardless of the block mode.
If “Yes”, failure of the off confirm while in the off state causes step l to
go on. Step l can be configured to generate an appropriate alarm
MCC Alarm Conf indicating motor control center power failure. (Requires
“Confirm OffÞyes”.)
If “No”, step l stays off.
If “Yes”, the number of unsuccessful starting attempts is limited to a

Retry Conf preset value l, after which a preset time period J must elapse before
further attempts are allowed.
If “Yes”, recovery from a Tripped state, regardless of the block mode,

requires @l (reset) to be true momentarily after the fault has cleared.
Security Lockup Conf
If “No”, a Stop command (Auto or Manual) releases the block from
the Tripped state if the fault has cleared.
If “Yes”, transfer to the Tripped state is delayed by a preset time F

(Start Timer) to allow the motor to ride through momentary power
Trip Delay Conf failures.
If “No”, the block transfers immediately to the Tripped state
whenever a run confirm signal is lost without a Stop command.
.
Target ?
.
Value ?
.
Units ?
.
Func ?

CB: 2-4-10
Continuous Links Screens for a DMC
Figure 2.4.5 shows the default Continuous Links screens for DMC
continuous inputs.

Tag Descriptor
Addr =1A-1 Function DMC Motor Controller
A >*ENTRY Þ.00 Þ100.00 >.00 Þ
B >*ENTRY Þ.00 Þ100.00 >.00 Þ
C >*ENTRY Þ.00 Þ100.00 >.00 Þ
D >*ENTRY Þ.00 Þ100.00 >.00 Þ
E >*ENTRY Þ.00 Þ100.00 >.00 Þ
F >*TIMER Þ0. Þ1. Þ0. Þsecs
G >*TIMER Þ0. Þ1. Þ0. Þsecs
Q Þ.00 Þ100.00 >.00 Þ
Block Mode> LOCAL

CONFIG 1

Tag Descriptor
H >*TIMER Þ0. Þ1. >0. Þsecs
I >*COUNTER Þ0. Þ1. >0. Þtimes
J >*TIMER Þ0. Þ1. >0. Þmins
K >
L >
M >
N >
O >
Block Mode> LOCAL
CONFIG 1
Figure 2.4.5. Default Continuous Links Screens—DMC

CB: 2-4-11
Discrete Links and Discrete Faceplate Screens for a DMC
Figure 2.4.6 shows the default Discrete Links screen for DMC discrete
inputs. Some of the discrete links correspond to a line on the discrete
faceplate, where the status is displayed. Figure 2.4.7 shows the default
Discrete Faceplate screen for a DMC.
CB DISCRETE LINKS 02-Jan-92 15:41:07

Tag Descriptor
INPUT SOURCE Msg State INPUT SOURCE Msg State
@a >*M ON Þ *2 > start @i >*OFF Þ *1 OFF
@b >*M ON Þ *7 > stop @j >*OFF Þ *31 shutdown
@c >*M ON Þ *1 > OFF @k >*OFF Þ *32 interlok
@d >*OFF Þ *2 start @l >*OFF Þ *33 reset
@e >*OFF Þ *7 stop @m >
@f >*OFF Þ *1 OFF @n >
@g >*OFF Þ *22 on cfrm @o >
@h >*OFF Þ *27 off cfrm
Figure 2.4.6. Default Discrete Links Screen--DMC
CB DISCRETE FACEPLATE 27-May-92 09:55:51

Tag > Descriptor > +--------+
1 |OPERATOR|
Addr =1A-01 Function >DMC Motor Controller 2 > start |
3 > stop |
1>*38+ 2>@a 3>@b 4> 5>@39+ 4 | |
OPERATOR *M ON *M ON --AUTO-- 5 |--AUTO--|
6 | start |
7 | stop |
6>@d 7>@e 8> 9> - 10>@g 8 | |
*OFF *OFF *OFF 9 |--------|
10 | on cfrm|
11 |off cfrm|
11>@h 12>j 13> 14>*88+ 15>a 12 | tripped|
*OFF -OUTPUT- 13 | |
14 |-OUTPUT-|
15 | run |
16>b 17>e Overview >17 Unit 1>15 2>16 3>17 16 | STOP |
17 | failed |
Plant Unit >0 Alarm Priority >0 +--------+
Steps in MANUAL Block Mode> AUTO
FULL CONFIG 1
Figure 2.4.7. Default Discrete Faceplate Screen—DMC

CB: 2-4-12
DMC Input Functions and Output Conditions
Table 2.4.5 provides the discrete input functions and the discrete output
conditions for a DMC. Table 2.4.6 provides the continuous input
functions for a DMC. These tables provide the true state of the DMC
inputs and outputs.
Table 2.4.5. Discrete Input Functions and Output Conditions--DMC
Input Function When Input is True: Output Condition Under Which Output is True:
@a Manual Start a Start
@b Manual Stop b Stop
@c User-configurable c User-configurable
@d Automatic Start d Ignore option(s) selected
One of f, g, h, j, or k outputs is true,

@e Automatic Stop e
indicating failure condition
More than one confirm or command input

@f User-configurable f
is true
@g Confirm On g Failed to start within preset time limit
@h Confirm Off h Failed to stop within preset time limit
@i User-configurable i User-configurable
Confirm changed without command,

@j Stop regardless of block mode j
indicating motor has tripped
OK to run
@k k Locked off, waiting for @l (reset) = true
(Required only if “InterlockÞyes”)
· If “MCC Alarm” field is configured to

“yes,” output is true for motor control
Releases security lockup (Required center power loss. Both confirms are off.
@l l
only if “Security LockupÞyes”)
· For all other configuration options, the
step is user-configurable.
@m User-configurable m User-configurable
@n User-configurable n User-configurable
@o User-configurable o User-configurable
NA NA p User-configurable

CB: 2-4-13
Table 2.4.6. Continuous Input Functions--DMC
Input Function
A User-configurable
B User-configurable
C User-configurable
D User-configurable
E User-configurable
Start timer. Counts time between Start command (step a) and

F
Confirm On (@g).
Stop timer. Counts time between Stop command (step b) and

G
Confirm Off (@h).
Preconfigured as *Timer, but not used by DMC function.

H
Function should not be used.
I Retry counter. Used with Retry option.
J Lockout timer. Used with the Retry option.
K User-configurable
L User-configurable
M User-configurable
N User-configurable
O User-configurable

CB: 2-4-14
Discrete Auto Sequence Motor Controller (DASMC)

Configuration
The Discrete Auto Sequence Motor Controller (DASMC) function is a

preconfigured ControlBlock for use with a single-speed electric motor,
which is one of several motors that must be automatically started in a
predetermined sequence. Figure 2.4.8 shows a control loop using an
DASMC function to operate a motor.
This function requires an interlock input from the previous device in the
sequence. Figure 2.4.9 shows the functioning of the interlock signal.
Although the DASMC function is preconfigured, you must configure

several discrete links and select any desired configuration options.
Contact
Input Block Confirm
(Optional) Off
Contact ControlBlock Contact Single-

Input Block DASMC Output Block speed
Start/stop Start/stop Electric
outputs timers Motor
Confirm
On
Interlock
Contact ControlBlock Contact Previous
Input Block Previous Output Block Motor
DASMC Start/Stop
in sequence
Confirm
On
Figure 2.4.8. Example of a Discrete Auto Sequence Motor Controller Control Loop

CB: 2-4-15
Previous Time Delay Single- Motor

Device Starts speed Starts
Interlock Signal true Expires Electric Yes
Motor
Enabled?
In Auto
mode?
Interlock Signal false Delay Active No
Motor Stops
Figure 2.4.9. Interlock Function for a DASMC

CB: 2-4-16
Links Required for DASMC Operation
Although the DASMC is preconfigured, several discrete links are

required for a DASMC to become operational. Configure these discrete
links on the Discrete Links screen. Table 2.4.7 summarizes the discrete
links that are required to make the block operational so that it can be
used to start a single-speed motor automatically in a predetermined
sequence. Figure 2.4.10 shows the preconfigured discrete faceplate
that displays the operation of the motor.
A DASMC has five preconfigured continuous inputs: F, G, H, I, and J.
The remaining continuous inputs A through E and K through O can be
configured as needed.
Table 2.4.7. Required Links for DASMC Configuration
Link: To:
Source (start) Contact Output Block 1. Start output (step a) of the DASMC
Source (stop) Contact Output Block, if used 2. Stop output (step b) of the DASMC
@g (Confirm On input) 3. Input from a Contact I/O block
@h (Confirm Off), if used 4. Input from a Contact I/O block
@d (or configure as a *Toggle or *On function) 5. Automatic enable signal of the DASMC
@e, if used 6. Automatic stop input
7. Confirm On signal from the previous motor in

@k (Interlock)
the sequence
1 OPERATOR
Manual control 2 > start
3 > stop
4
5 --AUTO--
Automatic control 6 enable
7 interlock
8 stop
9 ---------
10 on cfrm
Configuration options 11 off cfrm
12 tripped
13
14 -OUTPUT-
Motor response 15 run
16 STOP
17 failed
Figure 2.4.10. Discrete Faceplate for a DASMC

CB: 2-4-17
Configuration Options for a DASMC
After configuring the required discrete links to make the DASMC

operational, you can choose from various configuration options for the
DASMC. You select configuration options on the Continuous Faceplate
screen and you can change the preconfigured and unconfigured
options.
Figure 2.4.11 shows the default Continuous Faceplate screen for a

DASMC. The shaded box in Figure 2.4.11 shows the area where the
configuration options are selected. The Continuous Faceplate screen
displays the DASMC timer operation.
Table 2.4.8 lists the DASMC options that appear on the Continuous
option.

Shed
SC>N +--------+
Addr =1A-01 Function >DASMC Auto Sequence Motor Controller A | .00 |
A >.00 >.00 C | .00 |
B >.00 D | .00 |
C >.00 100- +--------+
D >.00 + |
75- + |
INPUTS F G H + |
50- + |
Target >5. >2. >10. + |
Value 0. 0. 0. 25- + |
Units secs secs secs + |
Func STRT TMR STOP TMR DELAY ON 0- +--------+
| .00 |
Interlock >yes Ignore Interlock >no Retry >no OUT || |
| |
FULL CONFIG 1
Figure 2.4.11. Default Continuous Faceplate Screen—DASMC

CB: 2-4-18
Table 2.4.8. Configuration Options--DASMC


If “Yes”, no alarm occurs even though Confirm On, Forward, Reverse,

Ignore Confirm On Supr High, or Low is not received when expected. Permits temporary
bypass of @g and /or @i.
If “Yes”, @k must be true for the motor to start or to remain running,

Interlock Conf
regardless of the block mode. (Requires “InterlockÞyes”.)
If “Yes”, failure of the off confirm while in the off state causes step l to
go on. Step l can be configured to generate an appropriate alarm that
MCC Alarm Conf indicates motor control center power failure. (Requires
“Confirm OffÞyes”.)
If “Yes”, the number of unsuccessful starting attempts is limited to a

Retry Conf preset value l, after which a preset time period J must elapse before
further attempts are allowed.

If “No”, a Stop command (Auto or Manual) releases the block from the
Tripped state if the fault has cleared.

If “No”, the block transfers immediately to the Tripped state whenever
a run confirm signal is lost without a Stop command.

CB: 2-4-19
Continuous Links Screens for a DASMC
Figure 2.4.12 shows the default Continuous Links screens for DASMC
continuous inputs.

Tag Descriptor
Addr =1A-2 Function DASMC Auto Sequence Motor Controller
A >*ENTRY Þ.00 Þ100.00 >.00 Þ
B >*ENTRY Þ.00 Þ100.00 >.00 Þ
C >*ENTRY Þ.00 Þ100.00 >.00 Þ
D >*ENTRY Þ.00 Þ100.00 >.00 Þ
E >*ENTRY Þ.00 Þ100.00 >.00 Þ
F >*TIMER Þ0. Þ1. Þ0.0 Þsecs
G >*TIMER Þ0. Þ1. Þ0.0 Þsecs
Q Þ.00 Þ100.00 >.00 Þ
Block Mode> LOCAL
CONFIG 1

Tag Descriptor
K >
L >
M >
N >
O >
Block Mode> LOCAL
CONFIG 1
Figure 2.4.12. Default Continuous Links Screens—DASMC

CB: 2-4-20
Discrete Links and Discrete Faceplate Screens for a DASMC
Figure 2.4.13 shows the default Discrete Links screen for a DASMC.
Some of the discrete links correspond to a line on the discrete
faceplate, where its status is displayed. Figure 2.4.14 shows the default
Discrete Faceplate screen for a DASMC.

Tag Descriptor
@a >*M ON Þ *2 > start @i >*OFF Þ *1 OFF
@d >*OFF Þ *12 enable @l >*OFF Þ *33 reset
@g >*OFF Þ *22 on cfrm @o >
Figure 2.4.13. Default Discrete Links Screen—DASMC

1 |OPERATOR|
Addr =1A-01 Function >DASMC Auto Sequence Motor Controller 2 > start |
3 > stop |
1>*38+ 2>@a 3>@b 4> 5>*39+ 4 | |
6 | enable |
7 |interlok|
6>@d 7>@k 8>@e 9> - 10>@g 8 | stop |
*OFF *OFF *OFF *OFF 9 |--------|
10 | on cfrm|
11 |off cfrm|
11>@h 12>j 13> 14>*88+ 15>a 12 | tripped|
14 |-OUTPUT-|
15 | run |
17 | failed |
FULL CONFIG 1
Figure 2.4.14. Default Discrete Faceplate Screen—DASMC

CB: 2-4-21
DASMC Input Functions and Output Conditions
Table 2.4.9 provides the discrete input functions and the discrete output
conditions for a DASMC. Table 2.4.10 provides the continuous input
functions for a DASMC. These tables provide the true state of the
DASMC inputs and outputs.
Table 2.4.9. Discrete Input Functions and Output Conditions--DASMC
@a Manual Start a Start
OK to start after preset time delay

@d d Ignore option(s) selected
when @k becomes true
One of f, g, h, j, or k outputs is true,

@e Automatic Stop e

is true
@g Confirm on g Failed to start within preset time limit
@h Confirm off h Failed to stop within preset time limit

OK to start after preset time delay if

@d is true, and to remain running

Releases security lockup (Required center power loss. Both confirms are off.
@l l

CB: 2-4-22
Table 2.4.10. Continuous Input Functions--DASMC
Input Function
A User-configurable
B User-configurable
C User-configurable
D User-configurable
E User-configurable
Start timer. Counts time between Start command

F
(step a) and Confirm On (@g).

G
Confirm Off (@h).
Delay On timer used with logic that guarantees a delay

H between a Start request (@d and @k true) and output of the
Start command (step a).
K User-configurable
L User-configurable
M User-configurable
N User-configurable
O User-configurable

CB: 2-4-23
Discrete Dual Speed Motor Controller (DDSMC) Configuration
The Discrete Dual Speed Motor Controller (DDSMC) function is a

preconfigured ControlBlock for use with a two-speed electric motor.
Figure 2.4.15 shows a control loop using a DDSMC function to operate
a motor.
Although the DDSMC function is preconfigured, you must configure

Contact
Output Block
High
Contact ControlBlock Output
Input Block DDSMC
Confirm High
Contact Two-speed
Stop Output Block Electric
Output Start, stop Motor
timers
Contact
Input Block
Confirm Low
Low
Output Contact
Output Block
Contact
Input Block
Confirm Off
Figure 2.4.15. Example of a Discrete Dual Speed Motor Controller Control Loop

CB: 2-4-24
Links Required for DDSMC Operation
Although the DDSMC is preconfigured, several discrete links are

required for a DDSMC to become operational. Configure these discrete
links on the Discrete Links screen. Table 2.4.11 summarizes the discrete
links that are required to make the block operational so that it can be
used to control a two-speed motor automatically or manually.
Figure 2.4.16 shows the preconfigured discrete faceplate that displays
the operation of the motor.
A DDSMC also has five preconfigured continuous inputs: F, G, H, I, and

J. You can configure the remaining continuous inputs A through E and K
through O as needed.
Table 2.4.11. Required Links for DDSMC Configuration
Link: To:
Source (high) Contact Output Block 1. High output (step a) of the DDSMC
Source (off) Contact Output Block 2. Stop output (step b) of the DDSMC
Source (low) Contact Output Block 3. Low output (step c) of the DDSMC
@g (Confirm High input) 4. Motor controller input from a ControlBlock
@i (Confirm Low input) 5. Motor controller input from a ControlBlock
@d and @f, if used 6. Automatic start signal (Auto mode only) of the DDSMC
@e, if used 7. Automatic stop signal (Auto mode only) of the DDSMC
@h (Confirm Off input), if used 8. Input from a Contact I/O block
1 OPERATOR
2 high
Manual control 3 >low
4 > stop
5 --AUTO--
Automatic control 6 high
7 low
8 stop
9 ---------
10 hi cfrm
Configuration options 11 low cfrm
12 tripped
13 -OUTPUT-
14 high
Motor response 15 low
16 STOP
17 failed
Figure 2.4.16. Discrete Faceplate for a DDSMC

CB: 2-4-25
Configuration Options for a DDSMC
After configuring the required discrete links to make the DDSMC

operational, you can choose from various options for the DDSMC.
Configure these links on the Discrete Links screen. You select
configuration options on the Continuous Faceplate screen and you can
change the preconfigured and unconfigured options.

DMC. The shaded box in Figure 2.4.17 shows the area where the
displays the DMC timer operation.
Table 2.4.12 lists the DDSMC options that appear on the Continuous
option.

Shed
Tag > Desc > Mode>
NONE >OUT>A>B>C>D
SC>N +--------+
Addr =1A-01 Function >DDSMC Dual Speed Motor Controller A | .00 |
A >.00 >.00 C | .00 |
B >.00 D | .00 |
C >.00 100- +--------+
D >.00 + |
75- + |
INPUTS F G H + |
50- + |
Target >5. >2. >2. + |
Value 0. 0. 0. 25- + |
Func STRT TMR STOP TMR STR2 TMR 0- +--------+
| .00 |
Interlock >no Intermediate Stop >no OUT || |
| |
FULL CONFIG 1
Figure 2.4.17. Default Continuous Faceplate Screen—DDSMC

CB: 2-4-26
Table 2.4.12. Configuration Options--DDSMC

following a STOP command (step b); otherwise an alarm (step h)


If “Yes“, @k must be true for the motor to start or to remain running,

Interlock Conf
Any change in speed attempted while running switches the block to

Intermediate Stop Conf the Stop state. It must remain in the Stop state for the setting of the
stop timer (G), even if stop is confirmed earlier.
If “Yes”, failure of any expected Confirm causes step l to go on. You

can configure step l to generate an appropriate alarm that indicates
MCC Alarm Conf motor control center power failure. (Requires “Confirm OffÞyes”.)



CB: 2-4-27
Continuous Links Screens for a DDSMC
Figure 2.4.18 shows the Continuous Links screen for DDSMC

continuous inputs.

Tag Descriptor
Addr =3D-2 Function DDSMC Dual Speed Motor Controller
A >*ENTRY Þ.00 Þ100.00 >.00 Þ
B >*ENTRY Þ.00 Þ100.00 >.00 Þ
C >*ENTRY Þ.00 Þ100.00 >.00 Þ
D >*ENTRY Þ.00 Þ100.00 >.00 Þ
E >*ENTRY Þ.00 Þ100.00 >.00 Þ
Q Þ.00 Þ100.00 >.00 Þ
Block Mode> LOCAL
CONFIG 1

Tag Descriptor
H >*TIMER Þ0 Þ1 >0. Þsecs
I >*COUNTER Þ0. Þ1 >0. Þtimes
J >*TIMER Þ0 Þ1 >0 Þmins
K >
L >
M >
N >
O >
Block Mode> LOCAL
CONFIG 1
Figure 2.4.18. Default Continuous Links Screens—DDSMC

CB: 2-4-28
Discrete Links and Discrete Faceplate Screens for a DDSMC
Figure 2.4.19 shows the default Discrete Links screen for DDSMC
discrete inputs. Some of the discrete links correspond to a line on the
discrete faceplate, where the status is displayed. Figure 2.4.20 shows
the default Discrete Faceplate screen.

Tag Þ Descriptor
@a >*M ON Þ *4 > high @i >*OFF Þ *23 lo cfrm
@c >*M ON Þ *3 > low @k >*OFF Þ *32 interlok
@d >*OFF Þ *4 high @l >*OFF Þ *33 reset
@f >*OFF Þ *3 low @n >
@g >*OFF Þ *24 hi cfrm @o >
Figure 2.4.19. Default Discrete Links Screen—DDSMC

1 |OPERATOR|
Addr =1A-01 Function >DDSMC Dual Speed Motor Controller 2 > high |
3 > low |
1>*38+ 2>@a 3>@c 4>@b 5>*39+ 4 > stop |
OPERATOR *M ON *M ON *M ON --AUTO-- 5 |--AUTO--|
6 | high |
7 | low |
6>@d 7>@f 8>@e 9> - 10>@g 8 | stop |
*OFF *OFF *OFF *OFF 9 |--------|
10 | hi cfrm|
11 | lo cfrm|
11>@i 12>j 13>*88+ 14>a 15>c 12 | tripped|
*OFF -OUTPUT- 13 |-OUTPUT-|
14 | high |
15 | low |
17 | failed |
FULL CONFIG 1
Figure 2.4.20. Default Discrete Faceplate Screen—DDSMC

CB: 2-4-29
DDSMC Input Functions and Output Conditions
Table 2.4.13 provides the discrete input functions and the discrete
output conditions for a DDSMC. Table 2.4.14 provides the continuous
input functions for a DDSMC. These tables provide the true state of the
DDSMC inputs and outputs.
Table 2.4.13. Discrete Input Functions and Output Conditions--DDSMC
@a Manual Start High a Start High Speed
@c Manual Start Low c Start Low Speed
@d Automatic Start High d Ignore option(s) selected
One of f to l outputs is true, indicating

@e Automatic Stop e
failure condition

@f Automatic Start Low f
is true
Failed to start at high speed within preset

@g Confirm High Speed g
time limit
Failed to start at low speed within preset

@i Confirm Low Speed i
time limit

OK to run (Required only if

“InterlockÞyes”)

Releases security lockup (Required center power loss. All confirms are off.
@l l

CB: 2-4-30
Table 2.4.14. Continuous Input Functions--DDSMC
Input Function
A User-configurable
B User-configurable
C User-configurable
D User-configurable
E User-configurable
Start timer. Counts time between High command (step a) and

F Confirm High (@g) or Low command (step c) and Confirm
Low (@i).

G
Confirm Off (@h).
Start timer for low speed. Counts between step c and confirm
H
(@i).
I Retry counter. Used with the Retry option.
K User-configurable
L User-configurable
M User-configurable
N User-configurable
O User-configurable

CB: 2-4-31
Discrete Dual Direction Motor Controller (DDDMC)

Configuration
The Discrete Dual Direction Motor Controller (DDDMC) function is a

preconfigured ControlBlock for use with a reversible electric motor.
Figure 2.4.21 shows a control loop using a DDDMC function to operate
a motor.
Although the DDDMC function is preconfigured, you must configure

Contact
Output Block
Contact ControlBlock Forward

Input Block DDDMC output
Confirm
Forward
Contact Start, Reversible

Output Block stop Electric
Stop Motor
output timers
Contact
Input Block
Confirm
Reverse
Reverse Contact
output Output Block
Contact
Input Block
(Optional)
Confirm
Stop
Figure 2.4.21. Example of a Discrete Dual Direction Motor Controller Control Loop

CB: 2-4-32
Links Required for DDDMC Operation
Although the DDDMC is preconfigured, several discrete links are

required for a DDDMC to become operational. Configure these discrete
links on the Discrete Links screen. Table 2.4.15 summarizes the
discrete links that are required to make the block operational so that it
can be used to control a reversible motor automatically or manually.
the operation of the motor.
A DDDMC also has five preconfigured continuous inputs: F, G, H, I, and

J. You can configure the remaining continuous inputs A through E and K
through O as you desire.
Table 2.4.15. Required Links for DDDMC Configuration
Link: To:
Source Contact Output Block 1. Forward output (step a) of the DDDMC
Source Contact Output Block 2. Stop output (step b) of the DDDMC
Source Contact Output Block 3. Reverse output (step c) of the DDDMC
@g (Confirm Forward or cancel Confirm On) 4. Motor controller input from a ControlBlock
@i (Confirm Reverse or cancel Confirm On) 5. Motor controller input from a ControlBlock
@d and @f 6. Automatic start signal (Auto mode only) of the DDDMC
@e 7. Automatic stop signal (Auto mode only) of the DDDMC
@h (Confirm Off input), if used 8. Input from a Contact I/O block
1 OPERATOR
Manual control 2 > forward
3 > stop
4 > reverse
5 --AUTO--
Automatic control 6 forward
7 stop
8 reverse
9 ---------
10 fwd cfrm
Configuration options 11 rev cfrm
12 tripped
13 -OUTPUT-
14 forward
Motor response 15 stop
16 reverse
17 failed
Figure 2.4.22. Discrete Faceplate for a DDDMC

CB: 2-4-33
Configuration Options for a DDDMC
After configuring the required discrete links to make the Dual Direction
Motor Controller operational, you can choose from various options for
the Dual Direction Motor Controller. You select configuration options on
the Continuous Faceplate screen and you can change the
preconfigured and unconfigured options.

DDDMC. The shaded box in Figure 2.4.23 shows the area where the
displays the DDDMC timer operation.
Table 2.4.16 lists the Dual Direction Motor Controller options that
appear on the Continuous Faceplate screen. The “Yes” selection
implements a desired option. The “No” selection cancels any undesired
option. If a selected entry requires a timer or counter entry, the entry
field appears when you select the option.

Shed
Tag > Desc > Mode>
NONE >OUT>A>B>C>D
SC>N +--------+
Addr =1A-01 Function >DDDMC Dual Direction Motor Controller A | .00 |
A >.00 >.00 C | .00 |
B >.00 D | .00 |
C >.00 100- +--------+
D >.00 + |
75- + |
INPUTS F G H + |
50- + |
Target >5. >2. >2. + |
Value 0. 2. 0. 25- + |
Func FWD TMR STOP TMR REV TMR 0- +--------+
| .00 |
Interlock >yes Ignore Interlock >no Intermediate Stop >yes OUT || |
| |
Confirm Off >yes Ignore Confirm Off >no Security Lockup >no +--------+
MCC Alarm >no Ignore Confirm On >no Trip Delay>no
Block Mode> LOCAL
FULL CONFIG 1
Figure 2.4.23. Default Continuous Faceplate Screen—DDDMC

CB: 2-4-34
Table 2.4.16. Configuration Options--DDDMC



If “Yes“, @k must be true for the motor to start or to remain running,

Interlock Conf
Any change in direction attempted while running switches the block to

Intermediate Stop Conf the Stop state. It must remain in the Stop state for the setting of the
stop timer (G), even if stop is confirmed earlier.
If “Yes”, failure of any expected Confirm causes step l to go on. Step l

can be configured to generate an appropriate alarm that indicates
MCC Alarm Conf motor control center power failure. (Requires “Confirm OffÞyes”).



CB: 2-4-35
Continuous Links Screens for a DDDMC
Figure 2.4.24 shows the Continuous Links screens for DDDMC

continuous inputs.

Tag Descriptor
Addr =3D-4 Function DDDMC Dual Direction Motor Controller
A >*ENTRY Þ.00 Þ100.00 >.00 Þ
B >*ENTRY Þ.00 Þ100.00 >.00 Þ
C >*ENTRY Þ.00 Þ100.00 >.00 Þ
D >*ENTRY Þ.00 Þ100.00 >.00 Þ
E >*ENTRY Þ.00 Þ100.00 >.00 Þ
Q Þ.00 Þ100.00 >.00 Þ
Block Mode> LOCAL
CONFIG 1

Tag Descriptor
Addr =3D-4 Function DDDMC Dual Direction Motor Controller
K >
L >
M >
N >
O >
Block Mode> LOCAL
CONFIG 1
Figure 2.4.24. Default Continuous Links Screens—DDDMC

CB: 2-4-36
Discrete Links and Discrete Faceplate Screens for a DDDMC
Figure 2.4.25 shows the default Discrete Links screen for DDDMC
discrete faceplate, where its status is displayed. Figure 2.4.26 shows
the default Discrete Faceplate screen for a DDDMC.

Tag Descriptor
Addr =3D-4 Function ÞDDDMC Dual Direction Motor Controller
@a >*M ON Þ *5 >forward @i >*OFF Þ *26 rev cfrm
@c >*M ON Þ *6 >reverse @k >*OFF Þ *32 interlok
@d >*OFF Þ *5 forward @l >*OFF Þ *33 reset
@f >*OFF Þ *6 reverse @n >
@g >*OFF Þ *25 fwd cfrm @o >
Figure 2.4.25. Default Discrete Links Screen—DDDMC

1 |OPERATOR|
Addr =1A-01 Function >DDSMC Dual Speed Motor Controller 2 >forward |
3 > stop |
1>*38+ 2>@a 3>@c 4>@b 5>*39+ 4 >reverse |
6 |forward |
7 | stop |
6>@d 7>@f 8>@e 9> - 10>@g 8 |reverse |
*OFF *OFF *OFF *OFF 9 |--------|
10 |fwd cfrm|
11 |rev cfrm|
11>@i 12>j 13>*88+ 14>a 15>c 12 | tripped|
*OFF -OUTPUT- 13 |-OUTPUT-|
14 |forward |
15 | STOP |
16>b 17>e Overview >17 Unit 1>15 2>15 3>17 16 |reverse |
17 |failed |
FULL CONFIG 1
Figure 2.4.26. Default Discrete Faceplate Screen—DDDMC

CB: 2-4-37
DDDMC Input Functions and Output Conditions
output conditions for a DDDMC. Table 2.4.18 provides the continuous
input functions for a DDDMC. These tables provide the true state of the
DDDMC inputs and outputs.
Table 2.4.17. Discrete Input Functions and Output Conditions--DDDMC
@a Manual Start Forward a Start Forward
@c Manual Start Reverse c Start Reverse
@d Automatic Start Forward d Ignore option(s) selected
One of f to l outputs is true, indicating

@e Automatic Stop e
failure condition

@f Automatic Start Reverse f
is true
Failed to start in forward within preset time

@g Confirm On Forward g
limit
Failed to start in reverse within preset time

@i Confirm On Reverse i
limit

OK to run (Required only if

“InterlockÞyes”)
D If “MCC Alarm” field is configured to

“yes,” output is true for motor
Releases security lockup (Required control center power loss.
@l l
D For all other configuration options,
the step is user-configurable.

CB: 2-4-38
Table 2.4.18. Continuous Input Functions--DDDMC
Input Function
A User-configurable
B User-configurable
C User-configurable
D User-configurable
E User-configurable
Forward timer. (Configured at STRT TMR field on Continuous

F Faceplate screen.) Counts time between Forward command
(step a) and Confirm Forward (@g).

G
Confirm Off (@h).
Reverse timer. (Configured at DELAY ON field on Continuous

H Faceplate screen.) Counts time between Reverse command
(step c) and Confirm Reverse (@i).
K User-configurable
L User-configurable
M User-configurable
N User-configurable
O User-configurable

CB: 2-4-39
Preconfigured Valve Controller Functions
The preconfigured valve control functions allow a valve to be actuated

automatically by a ControlBlock or manually from a discrete faceplate
on a group display. A function of this type becomes the major function of
the ControlBlock, using both the discrete and continuous portions of the
block. Table 2.4.19 lists and describes the valve controller functions.
The following features are common to all valve controllers:

D Provision for automatic or manual commands.
D Inputs for feedback of actual operating state (open/close).
D Alarming if the device does not respond to the command within a
preset time limit.
D Interlock and shutdown inputs that can override both automatic
and manual operations.
Table 2.4.19. Discrete Valve Controllers
Function
Mnemonic
Any valve, such as a solenoid valve, which

requires a contact closure to maintain the
DVC Discrete Valve Controller
open position, closed position, or both
positions.
Similar to DVC, except the valve is one of

Discrete Auto Sequence several that must be automatically opened in
DASVC
Valve Controller
a predetermined sequence.
Motorized valve operators, which require a

Discrete Motorized Valve contact closure to change position but not to
DMVC
Controller
maintain position.

CB: 2-4-40
Preconfigured Information for a Valve Controller
A preconfigured valve controller has the following information already

configured:
D The discrete steps required to perform logic.
D The discrete and continuous inputs required, with the appropriate
message pairs already chosen for display purposes. The inputs
are preconfigured on the Continuous Links and Discrete Links
screens.
D The Discrete Faceplate screen in order to display all commands
and feedback signals.
You can change any preconfigured information, but you cannot reduce
the number of analog inputs.
Unconfigured Information for a Valve Controller
You can use the unconfigured continuous inputs, A through E and J

through O, to monitor variables related to the valve, such as flow. Since
the ControlBlock continuous faceplate is not required for the major block
function, you can configure the continuous faceplate to display
information defined by the user. For more information about configuring
a continuous faceplate, see Section 1.

CB: 2-4-41
Effect of Block Mode on Valve Controller Operation
The operation of a valve controller function ControlBlock depends on

the block mode you configure. Table 2.4.20 describes the effect of each
block mode on the ControlBlock.
Table 2.4.20. Effect of Valve Controller Block Mode
Block Mode Description
Block responds only to auto commands (open, close, etc.), which are received
Auto
through inputs @d, @e, and @f. Block ignores commands from the keyboard.
Used with the Supervisory Computer Interface (SCI) or a MicroVAX to

PeerWay Interface. You must configure the block shed mode.
Computer Block output value responds to commands from an SCI or a MicroVAX to
(DDC) PeerWay Interface. If the SCI timer expires before an SCI write occurs, the
block responds as the configured shed mode. No commands are accepted.
NOTE: DDC is not a useful operating mode for a valve controller.
No commands are accepted but the output state is maintained and alarms and
Local interlocks function as configured.
NOTE: Local is not a useful operating mode for a valve controller.
Block responds only to keyboard commands (operator-entered), which are

Operator
received through inputs @a, @b, and @c. Block ignores auto commands.
Remote Cannot be selected for discrete valve controllers.

CB: 2-4-42
Discrete Valve Controller (DVC) Configuration
The Discrete Valve Controller (DVC) function is a preconfigured

ControlBlock for use with any valve that requires a contact closure to
maintain the open position, closed position, or both positions.
Figure 2.4.27 shows a control loop using a DVC function to operate a
valve.
Although the DVC function is preconfigured, you must configure several

discrete links and select any desired configuration options.
Contact ControlBlock Contact

Input Block DVC Output Block
Confirm Open
Open output
Valve
Contact Contact
Input Block Output Block
Confirm Close
output (Optional)
Open
Figure 2.4.27. Example of a Discrete Valve Controller Control Loop

CB: 2-4-43
Links Required for DVC Operation
Although the DVC is preconfigured, several discrete links allow a DVC

to become operational. Configure these discrete links on the Discrete
Links screen. Table 2.4.21 summarizes the discrete links that are
required to make the block operational so that it can be used to control
a valve automatically or manually. Figure 2.4.28 shows the
preconfigured discrete faceplate that displays the operation of the valve.
A DVC also has three preconfigured continuous inputs: F, G, and H. You

can configure the remaining continuous inputs A through E and I
Table 2.4.21. Required Links for DVC Configuration
Link: To:
Source Contact Output Block 1. Open output (step a) of the DVC
Source Contact Output Block

(as required, depending on the state of the 2. Close output (step b) of the DVC
valve when open is de-energized)
@g (Confirm Open), if used 3. Input from open limit switch on valve
@h (Confirm Close), if used 4. Input from closed limit switch on valve
@d 5. Automatic open signal (Auto mode only) of the DVC
@e 6. Automatic close signal (Auto mode only) of the DVC
1 OPERATOR
Manual control 2 > open
3 > close
4
5 --AUTO--
Automatic control 6 open
7 close
8
9 ---------
10 opn cfrm
Configuration options 11 travel
12 cls cfrm
13
14 -OUTPUT-
15 open
Valve response 16 close
17 failed
Figure 2.4.28. Discrete Faceplate for a DVC

CB: 2-4-44
Configuration Options for a DVC
After configuring the required discrete links to make the DVC

operational, you can choose from various options for the DVC. You
select configuration options on the Continuous Faceplate screen and
you can change the preconfigured and unconfigured options.

DVC. The shaded box in Figure 2.4.29 shows the area where the
displays the DVC timer operation.
Table 2.4.22 lists the Valve Controller options that appear on the
Continuous Faceplate screen. The “Yes” selection implements a desired
option. The “No” selection cancels any undesired option. If a selected
entry requires a timer or counter entry, the entry field appears when you
select the option.

Shed
SC>N +--------+
Addr =1A-01 Function >DVC Valve Controller A | .00 |
A >.00 >.00 C | .00 |
B >.00 D | .00 |
C >.00 100- +--------+
D >.00 + |
75- + |
INPUTS F G + |
50- + |
Target >30. >30. + |
Value 0. 30. 25- + |
Units secs secs + |
Func OPEN TMR CLS TMR 0- +--------+
| .00 |
Interlock >no OUT || |
| |
Confirm Close>yes Ignore Confirm Close>no Security Lockup >no +--------+
Confirm Open >yes Ignore Confirm Open >no Block Mode> LOCAL
FULL CONFIG 1
Figure 2.4.29. Default Continuous Faceplate Screen—DVC

CB: 2-4-45
Table 2.4.22. Configuration Options--DVC

following a close command (step b); otherwise an alarm (step h)
Confirm Close Conf occurs.
If “No”, the false state of @g (Confirm Open) constitutes a Confirm
Close.
If “Yes”, @g is expected to be true within a preset time period F

following an Open command (step a). If not, an alarm (step h) occurs.
Confirm Open Conf
If “No”, the false state of @h (Confirm Close) constitutes a Confirm
Open.
If “Yes”, no alarm occurs even though Confirm Close is not received

Ignore Confirm Close Supr when expected. Permits temporary bypass of @h. Field appears only
if “Confirm CloseÞyes”.
If “Yes”, no alarm occurs even though Confirm Open is not received

Ignore Confirm Open Supr when expected. Permits temporary bypass of @g. Field appears only
if “Confirm OpenÞyes”.
If “Yes”, the valve can open or remain open even though @k is false.
Ignore Interlock Supr Permits temporary bypass of @k. Field appears only if “Interlock
Þyes”.
If “Yes“, @k must be true for the valve to open or to remain open,

Interlock Conf
If “Yes”, recovery from a Failed state, regardless of block mode,


CB: 2-4-46
Continuous Links Screens for a DVC
Figure 2.4.30 shows the default Continuous Links screens for DVC
continuous inputs.

Tag Descriptor
Addr =3D-1 Function DVC Valve Controller
A >*ENTRY Þ.00 Þ100.00 >.00 Þ
B >*ENTRY Þ.00 Þ100.00 >.00 Þ
C >*ENTRY Þ.00 Þ100.00 >.00 Þ
D >*ENTRY Þ.00 Þ100.00 >.00 Þ
E >*ENTRY Þ.00 Þ100.00 >.00 Þ
Q Þ.00 Þ100.00 >.00 Þ
Block Mode> LOCAL
CONFIG 1

Tag Descriptor
I >
J >
K >
L >
M >
N >
O >
Block Mode> LOCAL
CONFIG 1
Figure 2.4.30. Default Continuous Links Screens—DVC

CB: 2-4-47
Discrete Links and Discrete Faceplate Screens for a DVC
Figure 2.4.31 shows the default Discrete Links screen for DVC discrete
inputs. Some of the discrete links correspond to a line on the discrete
faceplate, where the status is displayed. Figure 2.4.32 shows the
default Discrete Faceplate screen for a DVC.

Tag Þ Descriptor Þ
@a >*M ON Þ *8 > open @i >*OFF Þ *1 OFF
@b >*M ON Þ *9 > close @j >*OFF Þ *31 shutdown
@d >*OFF Þ *8 open @l >*OFF Þ *33 reset
@e >*OFF Þ *9 close @m >
@g >*OFF Þ *28 opn cfrm @o >
@h >*OFF cls cfrm Þ *29
Figure 2.4.31. Default Discrete Links Screen—DVC

1 |OPERATOR|
Addr =1A-01 Function >DVC Valve Controller 2 > open |
3 > close |
1>*38+ 2>@a 3>@b 4> 5>*39+ 4 > |
6 | open |
7 | close |
6>@d 7>@e 8> 9> - 10>@g 8 | |
*OFF *OFF *OFF 9 |--------|
10 |opn cfrm|
11 | travel |
11>@j 12>h 13> 14>*88+ 15>b 12 |cls cfrm|
14 |-OUTPUT-|
15 | open |
16>b 17>e Overview >17 Unit 1>15 2>16 3>17 16 | CLOSE |
17 | FAILED |
FULL CONFIG 1
Figure 2.4.32. Default Discrete Faceplate Screen—DVC

CB: 2-4-48
DVC Input Functions and Output Conditions
output conditions for a DVC. Table 2.4.24 provides the continuous input
functions for a DVC. These tables provide the true state of the DVC
inputs and outputs.
Table 2.4.23. Discrete Input Functions and Output Conditions--DVC
@a Manual Open a Open
@b Manual close b Close
@d Automatic Open d Ignore option(s) selected
One of f, g, h, or k outputs is true,

@e Automatic Close e

is true, suggesting a switch failure
Confirm open signal from limit switch

@g g Failed to open within preset time limit
on valve
Confirm close signal from limit switch

@h h Failed to close within preset time limit
on valve
Closes valve regardless of block One of the confirm timers is running,

@j j
mode indicating that the valve is traveling
Locked closed, waiting for @l (reset) =

OK to open and remain open true
@k k
(Required only if “InterlockÞyes”)
Releases security lockup (Required

@l l User-configurable

CB: 2-4-49
Table 2.4.24. Continuous Input Functions--DVC
Input Function
A User-configurable
B User-configurable
C User-configurable
D User-configurable
E User-configurable
Open timer. Counts time between output of an Open

F
command (step a) and Confirm Open input(@g).
Close timer. Counts time between output of a Close command

G
(step b) and Confirm Close input (@h).
Preconfigured as *Timer, but not used by DVC function.

H
Function should not be used.
I User-configurable
J User-configurable
K User-configurable
L User-configurable
M User-configurable
N User-configurable
O User-configurable

CB: 2-4-50
Discrete Auto Sequence Valve Controller (DASVC)

Configuration
The Discrete Auto Sequence Valve Controller (DASVC) function is a

preconfigured ControlBlock for use with a valve that is one of several
valves to be opened automatically in a predetermined sequence.
Figure 2.4.33 shows a control loop using an DASVC function to operate
a valve.
Although the DASVC function is preconfigured, you must configure

Contact
Input Block Confirm
Open
ControlBlock
DVC Contact
Output Block
Contact Open output Valve

Input Block Confirm
Close
Contact
Output Block
Close output
Contact
Input Block
Interlock
ControlBlock Contact
Previous Output Block
DVC or DMC Operate
in sequence
Confirm
Figure 2.4.33. Example of a Discrete Auto Sequence Valve Controller Control Loop

CB: 2-4-51
Links Required for DASVC Operation
Although the DASVC is preconfigured, you must configure several

discrete links for an DASVC to become operational. Configure these
discrete links on the Discrete Links screen. Table 2.4.25 summarizes
the discrete links that are required to make the block operational so that
it can be used to control a valve automatically or manually.
the operation of the valve.
A DASVC also has three preconfigured continuous inputs: F, G, and H.
You can configure the remaining continuous inputs A through E and I
through O as needed.
Table 2.4.25. Required Links for DASVC Configuration
Link: To:
Source Contact Output Block 1. Open output (step a) of the DASVC
Source Contact Output Block 2. Close output (step b) of the DASVC

(as required, depending on the state of the
valve when open is de-energized)
@g (Confirm Open), if used 3. Input from open limit switch on valve
@h (Confirm Close), if used 4. Input from closed limit switch on valve
@d (or configure it as a *Toggle or *On

5. Automatic enable signal of the DASVC
function)
@e 6. Automatic close signal of the DASVC
7. Confirm Open signal from the previous valve or device

@k (Interlock)
in the sequence
1 OPERATOR
3 > close
4
5 --AUTO--
6 enable
Automatic control 7 interlok
8 close
9 ----------
10 opn cfrm
Configuration options 11 TRAVEL
12 cls cfrm
13
14 -OUTPUT-
15 open
Valve response 16 CLOSE
17 failed
Figure 2.4.34. Discrete Faceplate for a DASVC

CB: 2-4-52
Configuration Options for a DASVC
After configuring the required discrete links to make the Auto Sequence
Valve Controller operational, you can choose from various options for
the DASVC. You select configuration options on the Continuous
Faceplate screen and you can change the preconfigured and
unconfigured options.

DASVC. The shaded box in Figure 2.4.35 shows the area where the
displays the DASVC timer operation.
Table 2.4.26 lists the DASVC options that appear on the Continuous
option.

Shed
Tag > Desc > Mode>
NONE >OUT>A>B>C>D
SC>N +--------+
Addr =1A-01 Function >DASVC Auto Sequence Valve Controller A | .00 |
A >.00 >.00 C | .00 |
B >.00 D | .00 |
C >.00 100-+--------+
D >.00 + |
75-+ |
INPUTS F G H + |
50-+ |
Target >30. >30. >10. + |
Value 0. 30. 0. 25-+ |
Func OPEN TMR CLS TMR DELAY ON 0-+--------+
| .00 |
Interlock >yes Ignore Interlock >no OUT|| |
| |
FULL CONFIG 1
Figure 2.4.35. Default Continuous Faceplate Screen—DASVC

CB: 2-4-53
Table 2.4.26. Configuration Options--DASVC
@h is expected to be true within a preset time period G following a

Close command (step b); otherwise an alarm (step h) occurs.
Confirm Close Conf
If “No”, the false state of @g (Confirm Open) constitutes a Confirm
Close.
If “Yes”, @g is expected to be true within a preset time period F

following an Open command (step a); otherwise an alarm (step h)
Confirm Open Conf occurs.
If “No”, the false state of @h (Confirm Close) constitutes a Confirm
Open.
If “Yes”, no alarm occurs even though Confirm Close is not received

Ignore Confirm Close Supr when expected. Permits temporary bypass of @h. Field appears only
if “Confirm CloseÞyes”.
If “Yes”, no alarm occurs even though Confirm Open is not received

Ignore Confirm Open Supr when expected. Permits temporary bypass of @g. Field appears only
if “Confirm OpenÞyes”.
If “Yes”, valve can open or remain open even though @k is false.

Ignore Interlock Supr Permits temporary bypass of @k. Field appears only if
“InterlockÞyes”.
@k must be true for the valve to open or to remain open, regardless

Interlock Conf
of the block mode. (Requires “InterlockÞyes”.)


CB: 2-4-54
Continuous Links Screens for a DASVC
Figure 2.4.36 shows the default Continuous Links screens for DASVC
continuous inputs.

Tag Descriptor
Addr =3D-6 Function DASVC Auto Sequence Valve Controller
A >*ENTRY Þ.00 Þ100.00 >.00 Þ
B >*ENTRY Þ.00 Þ100.00 >.00 Þ
C >*ENTRY Þ.00 Þ100.00 >.00 Þ
D >*ENTRY Þ.00 Þ100.00 >.00 Þ
E >*ENTRY Þ.00 Þ100.00 >.00 Þ
F >*TIMER Þ0. Þ1. Þ0.0 Þsecs
G >*TIMER Þ0. Þ1. Þ30.0 Þsecs
Q Þ.00 Þ100.00 >.00 Þ
CONFIG 1

Tag Descriptor
I >
J >
K >
L >
M >
N >
O >
Block Mode> LOCAL
CONFIG 1
Figure 2.4.36. Default Continuous Links Screens—DASVC

CB: 2-4-55
Discrete Links and Discrete Faceplate Screens for a DASVC
Figure 2.4.37 shows the default Discrete Links screen for DASVC
discrete faceplate, where its status is displayed. Figure 2.4.38 shows
the default Discrete Faceplate screen for a DASVC. The valve operation
of the DASVC is displayed on the Discrete Faceplate screen.

@d >*OFF Þ *12 enable @l >*OFF Þ *33 reset
@h >*OFF Þ *29 cls cfrm
Figure 2.4.37. Default Discrete Links Screen—DASVC

1 |OPERATOR|
Addr =1A-01 Function >DASVC Auto Sequence Valve Controller 2 > open |
3 > close |
1>*38+ 2>@a 3>@b 4> 5>*39+ 4 | |
6 | enable |
7 |interlok|
6>@d 7>@k 8>@e 9> - 10>@g 8 | close |
*OFF *OFF *OFF *OFF 9 |--------|
10 |opn cfrm|
11 | travel |
11>j 12>@h 13> 14>*88+ 15>a 12 |cls cfrm|
14 |-OUTPUT-|
15 | open |
17 | FAILED |
FULL CONFIG 1
Figure 2.4.38. Default Discrete Faceplate Screen—DASVC

CB: 2-4-56
DASVC Input Functions and Output Conditions
output conditions for a DASVC. Table 2.4.28 provides the continuous
input functions for a DASVC. These tables provide the true state of the
DASVC inputs and outputs.
Table 2.4.27. Discrete Input Functions and Output Conditions--DASVC
@b Manual Close b Close
OK to Open after preset time delay if

@d d Ignore option(s) selected
@k is also true

indicating a failure condition

Confirm Open signal from limit switch

on valve
Confirm Closed signal from limit

switch on valve

@j j
mode indicating the valve is traveling
OK to open after preset time delay if Locked Closed, waiting for @l (reset) =
@k @d is true, and remain open k true
thereafter as long as true


CB: 2-4-57
Table 2.4.28. Continuous Input Function--DASVC
Input Function
A User-configurable
B User-configurable
C User-configurable
D User-configurable
E User-configurable

F

G
(step b) and Confirm Open input (@h).
Delay On timer used with logic that guarantees a delay

H between an Open request (@d) and output of the Open
command (step a).
I User-configurable
J User-configurable
K User-configurable
L User-configurable
M User-configurable
N User-configurable
O User-configurable

CB: 2-4-58
Discrete Motorized Valve Controller (DMVC) Configuration
The Discrete Motorized Valve Controller (DMVC) function is a

preconfigured ControlBlock for use with a DMVC that requires a contact
closure to change position, but not to maintain position. Figure 2.4.39
shows a control loop using a DMVC function to operate a valve.
Although the DMVC function is preconfigured, you must configure

Contact ControlBlock Contact

Input Block DMVC Open Output Block
Confirm Output
Open
Motor Valve
Contact
Input Block Contact
Confirm Close Output Block
Close Output
Figure 2.4.39. Example of a Discrete Motorized Valve Controller Control Loop

CB: 2-4-59
Links Required for DMVC Operation
Although the DMVC is preconfigured, you must configure several

discrete links for a DMVC to become operational. Configure these
discrete links on the Discrete Links screen. Table 2.4.29 summarizes
the discrete links that are required to make the block operational so that
it can be used to control a valve automatically or manually.
the operation of the valve.
The DMVC maintains either the open or close output contact, based on
either a manual or automatic command, until:
D The related confirm is received,
or
D The related timer times out.
A DMVC also has two preconfigured continuous inputs: F and G. You

can configure the remaining continuous inputs A through E and I
Table 2.4.29. Required Links for DMVC Configuration
Link: To:
Source Contact Output Block 1. Open output (step a) of the MVC
Source Contact Output Block 2. Close output (step b) of the MVC
@g (Confirm Open) 3. Input from open limit switch on valve
@h (Confirm Close) 4. Input from close limit switch on valve
@d 5. Automatic open signal (Auto mode only) of the DMVC
@e 6. Automatic close signal (Auto mode only) of the DMVC
@f 7. Automatic stop signal (Auto mode only) of the DMVC

CB: 2-4-60
1 OPERATOR
3 > stop
4 > close
5 --AUTO--
Automatic control 6 open
7 close
8
9 ----------
10 opn cfrm
Configuration options 11 travel
12 cls cfrm
13
14 -OUTPUT-
15 open
Valve response 16 close
17 failed
Figure 2.4.40. Discrete Faceplate for a DMVC

CB: 2-4-61
Configuration Options for a DMVC
After configuring the required discrete links to make the DMVC

operational, you can choose from various options for the DMVC. You
select configuration options on the Continuous Faceplate screen and
you can change the preconfigured and unconfigured options.

DMVC. The shaded box in Figure 2.4.41 shows the area where the
displays the DMVC timer operation.
Table 2.4.30 lists the DMVC options that appear on the Continuous
option.

Shed
Tag > Desc > Mode>
NONE >OUT>A>B>C>D
SC>N +--------+
Addr =1A-01 Function >DMVC Motorized Valve Controller A | .00 |
A >.00 >.00 C | .00 |
B >.00 D | .00 |
C >.00 100-+--------+
D >.00 + |
75-+ |
INPUTS F G + |
50-+ |
Target >30. >30. + |
Value 0. 30. 25-+ |
Units secs secs + |
Func OPEN TMR CLS TMR 0-+--------+
| .00 |
Interlock >no OUT|| |
| |
FULL CONFIG 1
Figure 2.4.41. Default Continuous Faceplate Screen—DMVC

CB: 2-4-62
Table 2.4.30. Configuration Options--DMVC
@h is expected to be true within a preset time period G following a

Confirm Close Conf
Close command (step b); otherwise an alarm (step h) occurs.
@g is expected to be true within a preset time period F following an

Confirm Open Conf
Open command (step a); otherwise an alarm (step h) occurs.
If “Yes”, the motor runs for the close time, then a failed alarm occurs.
Ignore Confirm Close Supr
Field appears only if “Confirm CloseÞyes”.
If “Yes”, the motor runs for the open time, then a failed alarm occurs.
Ignore Confirm Open Supr
Field appears only if “Confirm OpenÞyes”.
If “Yes”, valve can open or remain open even though @k is false.

Ignore Interlock Supr Permits temporary bypass of @k. Field appears only if
“InterlockÞyes”.
If “Yes”, @k must be true for the valve to open or to remain open,

Interlock Conf
regardless of the block mode. (Requires “InterlockÞyes”.)


CB: 2-4-63
Continuous Links Screens for a DMVC
Figure 2.4.42 shows the default Continuous Links screens for DMVC
continuous inputs.

Tag Descriptor
Addr =3D-8 Function DMVC Motorized Valve Controller
A >*ENTRY Þ.00 Þ100.00 >.00 Þ
B >*ENTRY Þ.00 Þ100.00 >.00 Þ
C >*ENTRY Þ.00 Þ100.00 >.00 Þ
D >*ENTRY Þ.00 Þ100.00 >.00 Þ
E >*ENTRY Þ.00 Þ100.00 >.00 Þ
Q Þ.00 Þ100.00 >.00 Þ
Block Mode> LOCAL
CONFIG 1

Tag Descriptor
I >
J >
K >
L >
M >
N >
O >
Block Mode> LOCAL
CONFIG 1
Figure 2.4.42. Default Continuous Links Screens—DMVC

CB: 2-4-64
Discrete Links and Discrete Faceplate Screens for a DMVC
Figure 2.4.43 shows the default Discrete Links screen for DMVC
discrete faceplate, where the status is displayed. Figure 2.4.44 shows
the default Discrete Faceplate screen for a DMVC.
NOTE: Because the DMVC turns off the a and b outputs when the
valve is in position or failed, we recommend that you display “Opn Fail”
(g) and “Cls Fail” (h) on the discrete faceplate.

@c >*M ON Þ *83 > stop @k >*OFF Þ *32 interlok
@d >*OFF Þ *8 open @l >*OFF Þ *33 reset
@f >*OFF Þ *7 stop @n >
@h >*OFF cls cfrm Þ *29
Figure 2.4.43. Default Discrete Links Screen—DMVC

CB: 2-4-65

1 |OPERATOR|
Addr =1A-01 Function >DMVC Motorized Valve Controller 2 > open |
3 > stop |
1>*38+ 2>@a 3>@c 4>@b 5>*39+ 4 > close |
6 | open |
7 | close |
6>@d 7>@e 8> 9> - 10>@g 8 | |
*OFF *OFF *OFF 9 |--------|
10 |opn cfrm|
11 | travel |
11>j 12>@h 13> 14>*88+ 15>a 12 |cls cfrm|
14 |-OUTPUT-|
15 | open |
17 | FAILED |
FULL CONFIG1
Figure 2.4.44. Default Discrete Faceplate Screen—DMVC

CB: 2-4-66
DMVC Input Functions and Output Conditions
output conditions for a DMVC. Table 2.4.32 provides the continuous
input functions for a DMVC. These tables provide the true state of the
DMVC inputs and outputs.
Table 2.4.31. Discrete Input Functions and Output Conditions--DMVC
@b Manual Close b Close
@c Manual Stop c User-configurable
@d Automatic Open d Ignore option(s) selected

indicating a failure condition

@f Automatic Stop f
Confirm Open signal from limit switch

on valve
Confirm Closed signal from limit

switch on valve

@j j
mode indicating the valve is traveling
OK to open and remain open Locked closed, waiting for @l (reset) =

@k k
(Required only if “InterlockÞyes”) true


CB: 2-4-67
Table 2.4.32. Continuous Input Functions--DMVC
Input Function
A User-configurable
B User-configurable
C User-configurable
D User-configurable
E User-configurable

F

G
(step b) and Confirm Open input (@h).
Preconfigured as a *Timer, but not used by the DMVC. This

H
function should not be used.
I User-configurable
J User-configurable
K User-configurable
L User-configurable
M User-configurable
N User-configurable
O User-configurable

CB: 2-4-68

CB: 2-5-1
Section 5:
Hints for Configuring ControlBlock Functions
when configuring ControlBlock functions and some possible ways to
deal with them. This section also provides tips that are helpful when
configuring ControlBlock functions.
RS3: Configuring ControlBlock Functions Hints for Configuring ControlBlock Functions

CB: 2-5-2

ControlBlock functions and possible ways to handle them.
- How can I configure a continuous faceplate to display a
continuous input besides A--D?
Cursor to the “Out” arrow at the top of the continuous display and
type the letter of the register that you would like to display.
For more information, see Section 1.
- How can I ensure the bumpless transfer of a PID ControlBlock
when switching the ControlBlock from Manual mode to Auto mode?
Configure the “LS--PV Track” field as “Yes”.
- How can I ensure that the local setpoint tracks the process variable
when the PID ControlBlock is in Local or Manual mode?
Configure the “LS--PV Track” field as “Yes”.
- When I configure the equation for a Math ControlBlock, the
console screen beeps continuously.
You probably entered an equation with exactly 40 characters. As
soon as you call up another screen, the beeping will stop.
- When I view the ControlBlock configuration screens, the
“Block Mode”
field is blinking between the current block mode and Standby. Does
this mean that I should do something?
No. This is simply to alert you that the Controller Processor is in
Standby mode.
- I can’t adjust the ControlBlock output from the continuous
faceplate and, in fact, the output isn’t even displayed.
The faceplate is probably configured to display the input deviation
rather than the output. Cursor to the “Out/Dev” field and press
[NEXT OPTION] to change the configuration.
- The operator can’t control the ControlBlock output of a Manual
function ControlBlock.
Be sure that the ControlBlock is in Manual mode or Local mode, if
the operator needs to control the output.

CB: 2-5-3
- When I configure a DASMC ControlBlock or a DMC ControlBlock, it

doesn’t have an Off timer.
This happens when your motor doesn’t have a confirm off option. Try
this workaround:
1. Configure the “Confirm Off” field to Yes.
2. Configure a timer value in continuous input G.
3. Configure the “Confirm Off” field to No.
The timer retains its setting as long as you don’t change the block
function.
- The ControlBlock output is behaving erratically.
If the ControlBlock is a PID function ControlBlock with the Gap
option configured, the output has been known to behave erratically.
Try unconfiguring the Gap option.
- A rate-of-change alarm indicator is still displayed on a faceplate
even though the alarm condition has ended.
Don’t worry. It sometimes takes one or two seconds for the indicator
to disappear.

CB: 2-5-4
Configuration Tips
Listed below are hints to help you when configuring ControlBlock

functions.
- Using the SCI write function
Remember that to use the SCI write function, you need to configure
the “Shed Mode” field on the Continuous Faceplate screen.
- Reducing clutter in a tuning display
If a tuning display gets too cluttered, remember that you can delete
variables from the trend window. Cursor to the desired variable value
in the faceplate and press [SELECT] or [ENTER].
- Resetting a totalizer
For a TOT function, if you don’t want to configure a periodic reset
(using the “Next Reset” field), you can configure a treset logic
function to reset the totalizer.
- Configuring motor and valve controllers
D You can change any preconfigured information, but can’t reduce
the number of inputs.
D The local mode and DDC (Computer) mode are not useful
operating modes.
- Configuring a DMVC discrete faceplate
You might want to display the “Opn Fail” (g) and “Cls Fail” (h) on the
discrete faceplate, since the DMVC turns off the a and b outputs
when the valve is in position or failed.
- Configuring a negative lead time value
For a Lead/Lag function ControlBlock, if you want to configure a
negative lead time value you can’t do so using the “Lead Time” field.
Instead, scale the ControlBlock output from 0--1 and select one of
the user-configurable continuous inputs. Scale the input register
from 0--1 and enter the negative lead time in that register.

CB: 2-5-5
- Addressing ControlBlocks when redundant Controller

Processors are used
When you configure ControlBlocks and you are using redundant
Controller Processors, always configure using the addresses of the
left Controller Processor. Configurations using the right Controller
Processor addresses produce indeterminate results.
For example, if the Controller Processors are in slots A and B,
configure ControlBlocks with addresses for slot A.
For more information on redundant Controller Processors, see
OV: 3.

CB: 2-5-6

RS3t
Chapter 3:
Configuring Block Links
Section 1: Introduction to Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1-1

What is a Link? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1-1
Destination Block: ControlBlock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1-2
Destination Block: Output Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1-2
Block Link Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1-3
Block Links Within a Controller Processor Card . . . . . . . . . . . . . . . . . . . . . . . . . 3-1-3
Block Links Into and Out of Controller Processor Cards . . . . . . . . . . . . . . . . . . 3-1-4
Block Links Into and Out of ControlFiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1-5
Block Links Between PeerWays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1-6
Section 2: Continuous Links Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-1

Calling Up a Continuous Links Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-3
CB Continuous Links Screen Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-4
Invalid Link Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-4
Continuous Input Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-8
Scaling of Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-9
Types of Scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-9
Transmitter Scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-9
Internal or Normalized Scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-9
Display Scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-9
Scaling Sensitivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-11
Displaying Out-of-Range Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-12
Configuring Display Scaling to Match a Linked Source or a Register . . . . . . . 3-2-14
Matching the Scaling of Another Register . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-14
Scaling Dependent on Another Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-14
Converting Links to Engineering Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-16
Types of Conversions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-17
Configuring Conversion of Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-18
Reminders That Links Have Been Converted . . . . . . . . . . . . . . . . . . . . . . . . 3-2-20
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-22
Section 3: Discrete Links Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3-1

Calling Up a Discrete Links Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3-3
Discrete Links Screen Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3-4
Discrete Input Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3-6
Section 4: Configuration Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-1

Linking Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-1
RS3: Configuring Block Links Contents

CB: ii
Number of Controller Processor Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-2

Limit Within Controller Processors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-2
Limit Into and Out of Controller Processors . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-3
Number of ControlFile Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-5
Number of PeerWay Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-8
Limits for a PeerWay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-8
Limits for an HIA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-10
Viewing the Number of ControlFile Links Available . . . . . . . . . . . . . . . . . . . . . . 3-4-13
Viewing the Links of a ControlFile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-19
Tracing a Link to a Destination Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-21
Hints for Using Fewer Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-23
Use an Intermediate ControlBlock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-23
Use a ControlBlock Output Link Packet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-25
Free Space and Idle Time Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-27
Section 5: Hints for Configuring Block Links . . . . . . . . . . . . . . . . . . . . . . . . . 3-5-1


CB: iii
List of Figures
Figure Page
3.1.1 Examples of Linked Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1-1
3.1.2 Examples of Block Links Within a Controller Processor Card . . . . . . . 3-1-3
3.1.3 Examples of Block Links Between Controller Processor Cards . . . . . . 3-1-4
3.1.4 Examples of Block Links Between ControlFiles . . . . . . . . . . . . . . . . . . . 3-1-5
3.1.5 Examples of Block Links Between PeerWays . . . . . . . . . . . . . . . . . . . . . 3-1-6
3.2.1 Examples of Linked Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-1
3.2.2 Continuous Links Screens Among ControlBlock Screens . . . . . . . . . . . 3-2-2
3.2.3 Flowchart of Continuous Links Screens . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-3
3.2.4 Default Continuous Links Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-5
3.2.5 Continuous Input Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-8
3.2.6 Example of Control Loop Scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-10
3.2.7 Continuous Links Screen for Various Scaling Values . . . . . . . . . . . . . . . 3-2-12
3.2.8 Continuous Faceplate for Various Scaling Values . . . . . . . . . . . . . . . . . 3-2-13
3.2.9 Scaling a Typical PID Function ControlBlock . . . . . . . . . . . . . . . . . . . . . 3-2-15
3.2.10 Using “eu” and “nl” Conversions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-17
3.2.11 “Conv” Field for Converting Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-18
3.2.12 “Eng Zero” and “Eng Max” Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-20
3.2.13 Converted Links Marked on Discrete Diagram Screen . . . . . . . . . . . . . 3-2-21
3.3.1 Discrete Links Screens Among ControlBlock Screens . . . . . . . . . . . . . 3-3-2
3.3.2 Flowchart of Discrete Links Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3-3
3.3.3 Example of a Discrete Links Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3-4
3.3.4 Discrete Input Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3-6
3.4.1 Example of Links Within a Controller Processor . . . . . . . . . . . . . . . . . . . 3-4-2
3.4.2 Examples of Links Between Controller Processor Cards . . . . . . . . . . . 3-4-4
3.4.3 Examples of Links Between ControlFiles . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-6
3.4.4 Examples of Links Within a PeerWay . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-9
3.4.5 Examples of Links Between Controller Processor Cards . . . . . . . . . . . 3-4-11
3.4.6 HIA Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-12
3.4.7 Viewing the Number of Controller Processor and ControlFile
Available Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-13
3.4.8 Viewing the ControlFile Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-20
3.4.9 Block References Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-21
3.4.10 Example of Reducing Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-24

CB: iv
3.4.11 Linking the Block Output Packet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-25

3.4.12 Idle Time and Free Space Indicators on ControlFile Status Screen . . 3-4-27
3.5.1 Scrolling Message Pair Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5-4

CB: v
List of Tables
Table Page
3.2.1 Continuous Links Screen Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-6
3.2.2 Continuous Input Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-8
3.2.3 Example of Control Loop Scaling Relationships . . . . . . . . . . . . . . . . . . . 3-2-11
3.3.1 Discrete Links Screen Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3-5
3.3.2 Discrete Input Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3-7
3.4.1 Links Available for Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-1
3.4.2 Control File Status Screen Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-14
3.4.3 Block References Screen Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-22

CB: 3-1-1
Section 1:
Introduction to Links
This section defines a link and describes the types of block links.
What is a Link?
A link is the transfer path of information between two or more software

blocks.
Configure a block link at a destination block. A destination block

receives a link from a source block. You can link a source block to one
or more destination blocks. Figure 3.1.1 shows examples of linked
blocks.
Input Block ControlBlock ControlBlock ControlBlock
Input Block ControlBlock ControlBlock Output Block
ControlBlock ControlBlock Output Block
ControlBlock Output Block
Output Block
Source Block
Destination Block
Figure 3.1.1. Examples of Linked Blocks
RS3: Configuring Block Links Introduction to Links

CB: 3-1-2
Destination Block: ControlBlock
If the destination block is a ControlBlock, configure the link on either the

Continuous Links screen or the Discrete Links screen. Analog inputs,
which are also referred to as continuous inputs, are linked to one of 15
ControlBlock continuous registers, A through O, on the Continuous
Links screen. Both continuous and discrete inputs can be linked to one
of 15 discrete registers @a through @o in a ControlBlock on the
Discrete Links screen.
For more information about the Continuous Links screen, see Section 2.
For more information about the Discrete Links screen, see Section 3.
Destination Block: Output Block
If the destination block is an output block, configure the link on the I/O
Block Configuration screen. For information about configuring I/O
blocks, see the I/O Block Configuration Manual.

CB: 3-1-3
Block Link Paths
Block links can follow any of these paths between blocks:

D In a Controller Processor card
D In different Controller Processor cards in the same ControlFile
D In different ControlFiles
D On different PeerWays
For information about the number of links that can be used, see
Section 4.
Block Links Within a Controller Processor Card
You can link blocks residing in a Controller Processor card to other

blocks within the same card. Figure 3.1.2 shows examples of blocks
within Controller Processor card=15A that are linked to other blocks
within the same card.
=15A--8 =15A--14
Input Block ControlBlock

=15AB101 =15A--12

=15A--10 =15AC103
Output Block
=15AC203
Output Block
=15AC303
Figure 3.1.2. Examples of Block Links Within a Controller Processor Card

CB: 3-1-4
Block Links Into and Out of Controller Processor Cards
You can link blocks residing in a Controller Processor card to blocks

residing in another Controller Processor card in the same ControlFile.
Figure 3.1.3 shows examples of blocks residing in Controller Processor
card=15A that are linked to blocks residing in Controller Processor card
=15B.
=15A--8 =15B--10

=15AB101 =15B--12

=15A--10 =15BC103
Output Block
=15BC203
Output Block
=15BC303
Figure 3.1.3. Examples of Block Links Between Controller Processor Cards

CB: 3-1-5
Block Links Into and Out of ControlFiles
You can link blocks residing in a ControlFile to blocks residing in another

ControlFile. Figure 3.1.4 shows examples of blocks residing in
ControlFile =15 that are linked to blocks residing in ControlFile =17.
=15A--12 =17B--12

=15AB101 =17B--12

=15A--10 =17BAC103
Output Block
=17BC203
Output Block
=17bC303
Figure 3.1.4. Examples of Block Links Between ControlFiles

CB: 3-1-6
Block Links Between PeerWays
You can link blocks residing in a ControlFIle to blocks residing in

another ControlFile on a different PeerWay. Figure 3.1.5 shows
examples of blocks residing in ControlFile =15 on PeerWay 1 that are
linked to blocks residing in ControlFile =85 on PeerWay 3.
=15A--12 =85B--12
PeerWay 1 PeerWay 3

=15A--12 =85BC103
Output Block
=85BC203
Output Block
=85BC303
PeerWay 1 PeerWay 3
Figure 3.1.5. Examples of Block Links Between PeerWays

CB: 3-2-1
Section 2:
Continuous Links Screen
The Continuous Links screen is used to link continuous values to

ControlBlocks. This section describes the Continuous Links screen,
defines the continuous input sources, describes how to scale inputs,
and describes how to convert links to engineering units.
Use the Continuous Links screen to define the source of the continuous
links to the ControlBlock, the display scaling of the continuous values,
and the output tracking action in the event of a faulty input. The shaded
boxes in Figure 3.2.2 show the Continuous Links screens among the
ControlBlock configuration screens for ControlBlock =1A--4.
Input Block ControlBlock ControlBlock ControlBlock
Input Block ControlBlock ControlBlock Output Block
ControlBlock ControlBlock Output Block
Output Block
Source Block
Destination Block
Figure 3.2.1. Examples of Linked Blocks
RS3: Configuring Block Links Continuous Links Screen

CB: 3-2-2
ControlBlock =1A--4
CB CONTINUOUS [ EXCH ] CB DISCRETE

FACEPLATE FACEPLATE
CB CONTINUOUS
LINKS [ EXCH ]
H to O
[ PAGE ] CB DISCRETE LINKS
CB CONTINUOUS
LINKS [ EXCH ]
A to G
[ PAGE ] [ PAGE ]
CB DISCRETE
CB CONTINUOUS [ EXCH ] DIAGRAM
DIAGRAM
A
a
BLOCK REFERENCES
[ PAGE ] = [PAGE AHEAD] and [PAGE BACK]

buttons
Figure 3.2.2. Continuous Links Screens Among ControlBlock Screens

CB: 3-2-3
Calling Up a Continuous Links Screen

- To call up a Continuous Links screen:
D For a continuous function ControlBlock, press [BLOCK LINKS],
type the tag or address of the ControlBlock, and press [ENTER].
or
D For a discrete function ControlBlock, press [BLOCK LINKS], type
the tag or address of the ControlBlock, and press
[ENTER] [EXCH].
or
D From within a continuous function ControlBlock, press
[BLOCK LINKS] [ENTER].
Figure 3.2.3 shows how to navigate among Continuous Links screens.
CB CONTINUOUS
LINKS
(next address)
Inputs A to G
[PAGE AHEAD]
CB CONTINUOUS
LINKS
[ EXCH ]
Inputs H to O
CB DISCRETE
[PAGE AHEAD] LINKS
[PAGE BACK]
CB CONTINUOUS
LINKS
Inputs A to G [ EXCH]
[PAGE BACK]
CB CONTINUOUS
LINKS
(previous address)
Inputs A to G
Figure 3.2.3. Flowchart of Continuous Links Screens

CB: 3-2-4
CB Continuous Links Screen Fields
Use the Continuous Links screen to link the source of continuous data
values to the ControlBlock and to assign display scaling and units to
these values. Figure 3.2.4 shows the Continuous Links screen.
Table 3.2.1 describes the fields on the screen.
- To access inputs H through O:
D Press [PAGE AHEAD].
When the link is initially configured, the input is scaled the same as the
source to which the input is linked.
Invalid Link Alarm
When the link is initially configured, the control system immediately

searches for link information from the source block. If the link is from
another controller, this information is not available until the next block
evaluation cycle, so an Invalid Link alarm message appears. The
appearance of the Invalid Link alarm message is to be expected during
initial link configuration.

CB: 3-2-5
- To call up a Continuous Faceplate screen

for that block:
D Cursor to a source configured with a block
tag or address and press [SELECT].
CB CONTINUOUS LINKS 23-Feb-90 11:47:12

Tag Descriptor
PV >*ENTRY >.00 >100.00 >.00 >
LS >*ENTRY PV>.00 >100.00 >.00 >
RS >*ENTRY LS>.00 >100.00 >.00 >
FF >*ENTRY Q>.00 >100.00 >.00 >
E >
F >
G >
Q Þ.00 >100.00 >.00 >
Block Mode> LOCAL
Figure 3.2.4. Default Continuous Links Screen

CB: 3-2-6
Table 3.2.1. Continuous Links Screen Fields
Access
Level
Addr NA Address of the ControlBlock. Display only
LOCAL, MANUAL,
Block AUTO,
Oper Current block mode.
Mode COMPUTER,
REMOTE
Conv Conf Specifies whether the link should be converted to eu, nl

engineering units (eu) or normalized scaling (nl). For
more information, see “Converting Links to
Engineering Units” later in this section.
Desc NA User-defined block descriptor. Display only
User-defined value to represent the maximum scaling Max=1000000.

Eng Max Conf value. For more information, see “Scaling of Inputs” Min=--1000000.
later in this section. Default=100.00
User-defined value to represent the zero scaling value. Max=1000000

Eng Zero Conf For more information, see “Scaling of Inputs” later in Min=--1000000
this section. Default=.00
Function NA Major function of the ControlBlock. Display only
Specifies the output action if a bad signal is received

from the input source, by allowing the user to
configure whether or not a Hold Forward flag is acted
on by the ControlBlock.
If “No”, the ControlBlock output value is not held and
Hold Conf no, yes
the ControlBlock continues calculations. The default
condition is “no”.
If “Yes”, the ControlBlock output value is held if a Hold
Forward flag is received for that input and if the block
is in Auto mode.
Analog input register identification character A through

O. Continuous registers A, B, C, D may be displayed
INPUT NA Display only
as PV, LS, RS, and FF or other names, depending on
the function of the ControlBlock.
Q NA ControlBlock output (Q) variable Display only

CB: 3-2-7
Table 3.2.1. Continuous Links Screen Fields
Access
Level
Tag number, address, numeric value, or function of the

input. To select:
D A block input, enter the tag or address of the
block.
D A particular block register, use the format
tag or address/register character.
A particular flag from a block register, use the Block tag, address,
SOURCE Conf D
format or function
tag or address/register character/flag
D An input function, press [NEXT OPTION] to
select the desired function, and then press
[ENTER].
For examples of continuous input sources, see
Table 3.2.2.
Tag NA User-defined block tag. Display only
Maximum 8
Units Conf Engineering units you defined to display the input.
characters
Conf or Max=1000000
Value Current data value stored in the input register.
Oper* Min=--999949
* Conf for *Timer, *Counter, *Value, and *None values. Oper for an *Entry value.

CB: 3-2-8
Continuous Input Sources
Figure 3.2.5 shows that an input block, a ControlBlock, console entries,

or the ControlBlock logic can provide the continuous data value for a
ControlBlock. Table 3.2.2 provides the format for configuring each input
type in the “Source” field of the Continuous Links screen.
ControlBlock
Field Input Block
A--O, Q
ControlBlock
Operator Console
Logic
Figure 3.2.5. Continuous Input Sources
Table 3.2.2. Continuous Input Sources
Type of Input Corresponding Entry in “Source” Field
Address or Tag
Input Block
Example: =2AA101
Address or Tag
Output of another ControlBlock (Q)
Example: =3C--12
Address/Input
Input register value from another ControlBlock (A or Tag/Input
through O)
Example: FIC--100/B
Flag value from an input register of another Address/Input/Flag

ControlBlock or Tag/Input/Flag
Example: FIC--100/B/g
Input value that can be changed by the operator or

*ENTRY
configuror
Input value that can be changed by the configuror or

*TIMER, *COUNTER, *VALUE, *NONE
ControlBlock logic
Input value that can be changed by the supervisor

*SUPVSR
or configuror

CB: 3-2-9
Scaling of Inputs
Proper scaling of inputs is required for certain ControlBlock functions to

work properly and for performing ControlBlock logic or batch scaling.
Types of Scaling
Three types of scaling are used within a control loop: transmitter

scaling, internal scaling, and display scaling.
Transmitter Scaling
Transmitter scaling is the range of units of a device that is being used to

measure the value of a process variable. This range is determined by
and used by only the field device. An example of a transmitter scaling
range is 0--120 inches for the level of water in a tank.
Internal or Normalized Scaling
Internal scaling is fixed in the range from 0--1. This form, also known as
normalized scaling, is used by the RS3 control system to determine
internal block values for performing calculations and functions. For
example, with an Eng Zero of .00 and an Eng Max of 5000.00, the value
2500.00 is stored internally as .5 by the RS3 control system.
Display Scaling
Display scaling is a range that you configure for displaying internal

ControlBlock or I/O block values in terms of the plant scaling or
engineering units on faceplates and other console screens. For
example, an internal block value of .5 is displayed as 2500 gal on a
faceplate. Configure display block scaling using the “Eng Zero” and
“Eng Max” fields on a Continuous Links screen. Display scaling can be
different for each block. For more information about configuring display
scaling, see “Configuring Display Scaling of Continuous Inputs” later in
this section.
Figure 3.2.6 shows the input scaling for components of a typical control
loop.

CB: 3-2-10
Valve opens according

to the signal received
Device measures process variable

and outputs using a 4--20 mA signal
LT 0-5000 gal
(0-120 in. H2O)
4--20 mA
signal
4--20 mA
signal
FIC converts FIC converts

FIC 4--20 mA signal 0--1 value to a FIC
to a 0--1 value 4--20 mA signal
Internal scaling
value is sent
to the FIC
0--1 value 0--1 value

CONTROLBLOCK
INPUT BLOCK OUTPUT BLOCK
INPUT OUTPUT
Display Scaling Display Scaling Display Scaling

Display Scaling 0--100 0--100
0--5000 0--5000
PV
Internal PI Control Internal Internal Scaling
Internal Scaling Scaling Scaling 0--1
0--1 A Calculation
0--1 0--1
Linked input has

the same display Calculations are performed using
scaling and units internal scaling values
as the source
Level H20 Transmitter Internal Display

(inches) Out (mA) Scaling Scaling (gal)
25% 30 8 .25 1250
50% 60 12 .50 2500
75% 90 16 .75 3750
100% 120 20 1.0 5000
Figure 3.2.6. Example of Control Loop Scaling

CB: 3-2-11
Scaling Sensitivity
Display scaling values are not as sensitive as internal scaling values.

Internal scaling values can have up to nine decimal places. Engineering
units are not assigned to this value. Display scaling values can have up
to six decimal places.
Because a block can have an internal scaling value of up to nine digits

and a display scaling value of up to six digits, it is possible in certain
cases for the register to display a value such as 11.1, but to actually
contain 11.06, with 11.06 being rounded to 11.1. This is important to
consider when using block logic to test for absolute equality.
Table 3.2.3 provides sample scaling ranges and corresponding scaling

values for a control loop. You can determine the display block scaling
value using the following formula:
Display block scaling value =

(internal block scaling value) (Eng Max -- Eng Zero) +Eng Zero
For example, with a field device value of 12 mA and a plant scaling of

0--1000 gal, the display scaling is as follows:
Display block scaling value = (.5) (1000) = 500 gal
Table 3.2.3. Example of Control Loop Scaling Relationships
Plant Value Field Device Display Block Value

Internal
Value
Block Value
(Scaled (Scaled (Scaled (Scaled (Scaled
0--1000 gal) 0--100 ft) (Scaled 0--1) 0--1000 gal) 0--100 ft)
4--20 mA)
1000 gal 100 ft 20 mA 1.0 1000 gal 100 ft
500 gal 50 ft 12 mA .5 500 gal 50 ft
0 gal 0 ft 4 mA .00 0 gal 0 ft

CB: 3-2-12
Displaying Out-of-Range Values
ControlBlock continuous inputs are scaled according to the “Eng Zero”

and “Eng Max” values on the Continuous Links screen. The “Eng Zero”
and “Eng Max” values do not limit the value of the continuous input, but
simply determine how the value is displayed. Values outside of the Eng
Zero-Eng Max range are represented nonlinearly on the faceplate.
Figure 3.2.7 shows the Continuous Links screen for a sample
ControlBlock, with the Eng Zero-Eng Max range highlighted.
Figure 3.2.8 shows how the continuous inputs are represented on the
continuous faceplate.

Tag Descriptor
Addr Function
A >*ENTRY Þ.00 Þ100.00 >50.00 Þ
B >*ENTRY Þ50.00 Þ100.00 >75.00 Þ
C >*ENTRY Þ50.00 Þ100.00 >25.00 Þ
D >*ENTRY Þ150.00 Þ250.00 >295.00 Þ
Figure 3.2.7. Continuous Links Screen for Various Scaling Values

CB: 3-2-13
A 50.00
Values above the “Eng Max” are
B 75.00 represented by a bar above the 100
C 25.00 height
D 295.00
Eng Max value
100--
75--
Vertical bar graph 50--

is scaled 0--100
25--
0--
32.47 Eng Min value
OUT
Horizontal bar graph
(for Q) is scaled 0--100 Values below the “Eng Zero” are
represented by a bar below the 0
height
Figure 3.2.8. Continuous Faceplate for Various Scaling Values

CB: 3-2-14
Configuring Display Scaling to Match a Linked Source or a

Register
When a destination block is linked to a source block, the destination

block is assigned the same display scaling (“Eng Zero” and “Eng Max”)
as the source block. An asterisk appears in front of the “Eng Zero” field
to indicate that the scaling is derived from the source block. For
information on scaling an input the same as a source block, see
Figure 3.2.9.
If you change the assigned scaling at the destination block, the asterisk
disappears and changes to the source block scaling will not affect the
destination block scaling. To reconfigure the destination block to be
scaled as its source block, you must press [ENTER] in the scaling field
to indicate that the input is scaled to match its source block.
Figure 3.2.9 shows that the PV input is scaled the same as its source
block TT101.
You can change the assigned display scaling to a user-defined value.

Figure 3.2.9 shows a Continuous Links screen with the scaling of input
E defined by the user.
Matching the Scaling of Another Register
You can change the assigned display scaling to match the scaling of
another continuous input or output. Enter an input or output register
letter (A--O, Q, or a--o) in the “Eng Zero” value, to indicate that the link
has the same display scaling values as the input or output register.
Figure 3.2.9 shows that the LS, RS, and FF inputs each are scaled to
match the scaling of another input.
Scaling Dependent on Another Value
If the display scaling of a linked source is used for the display scaling of
a block, the scaling values of the destination depend on the source, but
not vice versa. Scaling inputs that are dependent upon one another, like
the example in Figure 3.2.9, are helpful if the scaling of one of the
primary components, such as a transmitter, is changed. If the scaling of
a transmitter is changed and that transmitter provides an input to a
block, the scaling of all links for that block are changed accordingly.

CB: 3-2-15
- To configure the input with the same

scaling as the source block:
Input PV is scaled as configured D Place the cursor above the “Eng
on block TT101, from 0--1000.00 Zero” or “Eng Max” field (to the right
of the Þ) and press [ENTER]. An
Input LS is scaled the same asterisk appears.
as PV, from 0--100

Tag Descriptor
PV >TT101 Þno *Þ.00 Þ1000.00 .00 ÞDEG C
LS >*ENTRY PVÞ.00 Þ1000.00 >.00 ÞDEG C
RS >*NONE LSÞ.00 Þ1000.00 Þ.00 ÞDEG C
FF >*NONE QÞ.00 Þ100.00 Þ.00 Þ
E >*ENTRY Þ50.00 Þ100.00 >.00 ÞDEG C
F >TT102 Þ.00 Þ100.00 .00 ÞDEG C
G >
Q Þ.00 Þ100.00 >.00 Þ
CONFIG 1
Input RS is scaled the same Input FF is scaled the same Input E is scaled as you defined
as LS, from 0--100 as Q, from 0--100
- To configure the input with the same scaling - To configure the input with a
as another register: user-defined value:
D Place the cursor above the “Eng Zero” or D Place the cursor above the “Eng Zero”
“Eng Max” field (to the right of the Þ), type or “Eng Max” field, type the
the register letter with the appropriate appropriate value including a decimal
scaling, then press [ENTER]. The register point, then press [ENTER].
letter appears to the left of the arrow.
Figure 3.2.9. Scaling a Typical PID Function ControlBlock

CB: 3-2-16
Converting Links to Engineering Units
The purpose of converting links to engineering units is so that you can

write equations in Math blocks and logic steps in a form you would
normally use. Before the conversion function was available, you would
have been required to take the specific scale range of the link into
consideration when writing the equation.
As an example of how converting links simplifies your equations,

suppose you want to take the average of three temperatures with
different ranges.
Input ranges A 0 to 150 °F

B --50 to 200 °F
C 0 to 200 °F
If you could not convert the link scaling, your equation for the
temperature average and the block output might look like this:
Q = ( A´150 + B´250 -- 50 + C´200 ) / 3
However, when you convert links A, B, and C to engineering units using

the “eu” conversion, your equation is much simpler:
Q = ( A+B+C ) / 3
If required, Q can be linked to another destination and changed back to

normalized scaling using the “nl” conversion.

CB: 3-2-17
Types of Conversions
You convert links by designating the type of conversion in the “Conv”

field on the Continuous Links screen. Two types of conversion are
possible:
D eu Converts the link to engineering units by performing a
scaling calculation based on the Eng Zero and Eng Max
values obtained from the source of the link.
D nl Converts the link to normalized scaling by performing a
calculation based on the Eng Zero and Eng Max values of
the register with the “nl”.
In a given loop, you typically configure both a conversion to engineering

units (eu) and a conversion back to normalized (nl) scaling. The
following example shows how the two types of conversions might be
used.
Example: Assume you want to add two flows together and multiply the
sum of the two flows by an operator-adjustable ratio from .1 to 1.0. You
then want to control a third flow based on this ratio to the total wild flow.
Figure 3.2.10 shows the simplified math using the two types of scaling
conversions.
Flow controller calculation is

performed in Math block directly
0 -- 900 GPM in engineering units. The configuror selects “nl”, then
either specifies “same as PV,” or
AIB enters the SP scaling locally.
PID CB
PV AOB
0 -- 200 GPM Q
nl
SP
AIB MATH CB
eu
A Q
Q = (A+B) ´ C Q = 0 to 1.0 GPM To control
eu valve
AIB B
0 -- 1000 GPM C
Could be any I/O block; Operator adjustable The configuror must enter 0 -- 1.0 GPM scaling
AIB given as example. ratio (0 to 1.0) on the output in order to get the correct
function in the Math block.
Figure 3.2.10. Using “eu” and “nl” Conversions

CB: 3-2-18
Configuring Conversion of Links
You configure conversion of input links to ControlBlocks on the

Continuous Links screen. Figure 3.2.11 shows the “Conv” field, which
you use to configure the conversion.
- To convert a link to engineering units (eu):
1. Cursor to the “Conv” field for the link.
2. Press [NEXT OPTION] to select “eu”, then press [ENTER].
If you previously entered Eng Zero and Eng Max values for this
link on this page, the system prevents you from entering “eu”.
You must first remove the local scaling by cursoring to the “Eng
Zero” or “Eng Max” fields and pressing [ENTER].
3. To make the output scaling match the link scaling, enter 0 in the
output “Eng Zero” field and 1. in the output “Eng Max” field. Use
as many zeros to the right of the decimal point as is required for
any displays.
CB CONTINUOUS LINKS 16-Mar-93 14:55:39

Tag FLOW-MATH Descriptor Ratio for Flow Control
A >FLOW1 >eu >no .0 1.0 .0 GPM
B >FLOW2 >eu >no .0 1.0 .0 GPM
C >*ENTRY >.0 >1.0 >.0 >RATIO
D >
E >
F >
G >
Q >.0 >1.0 .0 >GPM
Block Mode> AUTO
CONFIG 2
Figure 3.2.11. “Conv” Field for Converting Links

CB: 3-2-19
- To convert a link to normalized scaling (nl):

2. Press [NEXT OPTION] to select “nl”, then press [ENTER].
3. Enter Eng Zero and Eng Max values for the link. You can either
— Enter the register letter that has the appropriate scaling.
or
— Enter Eng Zero and Eng Max in the fields for this link.
- To remove scaling conversion from a link:
2. Type “none”, and press [ENTER].
NOTE: When you change a scaling conversion for a link, you are
changing a mathematical computation that was previously performed.
This change will noticeably affect the values produced by your
equations in Math blocks or logic steps.

CB: 3-2-20
Reminders That Links Have Been Converted
When you configure scaling conversion to engineering units, you

receive visual cues to remind you that the link has been converted. This
section explains those cues.
“Eng Zero” and “Eng Max” Fields
After conversion to engineering units, the scaling fields display 0 and 1

for Eng Zero and Eng Max. These scaling values are used for
displaying the converted value only. The values used for performing the
actual conversion (in the controller) are those obtained from the source
of the link.
The “Þ” prompt in front of the Eng Zero and Eng Max fields disappears
after you configure an “eu” conversion. You cannot change the values in
the scaling fields because, after conversion to engineering units, the
number in the “Value” field is already in engineering units and does not
need to be scaled.
Figure 3.2.12 shows what the fields look like after conversion to
engineering units. The number of zeros to the right of the decimal point
and the name of the units will be the same as the source scaling.
CB CONTINUOUS LINKS 16-Mar-93 14:55:39

Tag FLOW-MATH Descriptor Ratio for Flow Control
A >FLOW1 >eu >no .0 1.0 .0 GPM
B >FLOW2 >eu >no .0 1.0 .0 GPM
C >*ENTRY >.0 >1.0 >.0 >RATIO
D >
E >
F >
G >
Q >.0 >1.0 .0 >GPM
Block Mode> AUTO
CONFIG 2
Figure 3.2.12. “Eng Zero” and “Eng Max” Fields

CB: 3-2-21
Discrete Diagram Screen
The Discrete Diagram screen shows which values have been converted
to engineering units. Next to each converted link, “eu” appears to
remind you that equations using these links must also use values
compatible with engineering units.
Example: Suppose you have a level indicator linked to input A with the
link converted to engineering units. The indicator shows the level in a
water column from 0 to 333 inches. You configured a logic step to turn
on when the level nears the top of the range. Figure 3.2.13 shows the
Discrete Diagram screen with the converted link marked.
CB DISCRETE DIAGRAM 16-Mar-93 14:56:54

Tag LEVEL-MATH Descriptor High Level Indicator
Addr =129A-80 Function MATH User-Defined Function Plnt>0
Free Space: Stat = 93 % Dyn = 91 % Priority>0
+------------------CONDITIONS-----------------------+Step>a
>LEVEL-AIB |A * |
301.00 (eu) | * a= >A>300 |Mode>Auto
| * |MsgPr
| * Set > |>*4
| * |On
| *Clear> |
| * |> HIGH
|--*----------------ACTIONS-------------------------|
| * |
| * Rise> |
| * |
| * ON > |Rpt>None
| * |
| * Fall> |
| * |
| * OFF > |
+---------------------------------------------------+
CONFIG 2
Figure 3.2.13. Converted Links Marked on Discrete Diagram Screen

CB: 3-2-22
Restrictions
When you configure scaling conversion for links, keep these restrictions
in mind:
D You cannot enter a conversion before you enter a link.
D You cannot configure scaling conversion on Q, nor on inputs that
are not linked (for example, *VALUE).
D The PID function with all its variations prevents “eu” conversion
on PV, LS, RS, FF, and, if the ratio or bias option is selected, RA
and BI. However, “eu” conversion of these links (A, B, C, D, E,
and F) is possible on other block types. Do not change another
block type with converted links to a PID block: the conversion will
remain on the links, but the scaling will be wrong.
D Conversion to “eu” only works on links within the same controller.
For example:
To convert a link between . . .
=75A--1 and =75A--20 Is possible using “eu”
=75A--1 and =75E--10 Is not possible using “eu”
D Conversion to “nl” does work on links between controllers. For
example:
To convert a link between . . .
=75A--1 and =75E--20 Is possible using “nl”
D When you configure scaling conversion on a link, the ultimate
source of the eu or nl scaling cannot be more than 3 links away.
This would not typically be a limitation for most configurations.
D Tracking and scaling conversion will not work together correctly.
Do not configure scaling conversion on the tracking input. The
tracking value sent back to the source will not be converted.

CB: 3-3-1
Section 3:
Discrete Links Screen
The Discrete Links screen is used to link discrete values to

ControlBlocks. This section describes the Discrete Links screen and the
discrete input sources.
Use the Discrete Links screen to configure the discrete links to the
ControlBlock and the message pairs that correspond to the input state.
The shaded box in Figure 3.3.1 shows the Discrete Links screen among
ControlBlock screens for ControlBlock =1A--4.
RS3: Configuring Block Links Discrete Links Screen

CB: 3-3-2
ControlBlock =1A--4

FACEPLATE FACEPLATE
CB CONTINUOUS
LINKS [ EXCH ]
H to O
CB CONTINUOUS
LINKS [ EXCH ]
A to G
[ PAGE ] [ PAGE ]

DIAGRAM DIAGRAM
A a
BLOCK REFERENCES

buttons
Figure 3.3.1. Discrete Links Screens Among ControlBlock Screens

CB: 3-3-3
Calling Up a Discrete Links Screen

- To call up a Discrete Links screen:
D For a discrete function ControlBlock, press [BLOCK LINKS], type
the tag or address of the ControlBlock, and press [ENTER] to call
up the Discrete Links screen.
or
D For a continuous function ControlBlock, press [BLOCK LINKS],
type the tag or address of the ControlBlock, and press [ENTER]
[EXCH] to call up the Discrete Links screen.
or
D From within a discrete function ControlBlock, press
[BLOCK LINKS] [ENTER].
Figure 3.3.2 shows how to navigate among Discrete Links screens.

Press [PAGE AHEAD] to call up the Discrete Links screen for the next
ControlBlock address. Press [PAGE BACK] to call up the Discrete Links
screen for the previous ControlBlock address.
CB DISCRETE
LINKS
(next address)
[PAGE AHEAD]
CB CONTINUOUS
[ EXCH] LINKS
H to O
CB DISCRETE
LINKS
CB CONTINUOUS
[PAGE BACK] [ EXCH] LINKS
A to G
CB DISCRETE
LINKS
(previous address)
Figure 3.3.2. Flowchart of Discrete Links Screens

CB: 3-3-4
Discrete Links Screen Fields
Use the Discrete Links screen to link discrete data values to the
ControlBlock and to assign message pairs to these values. Figure 3.3.3
shows a sample Discrete Links screen. Table 3.3.1 describes the fields
on the screen.
- To move to the source block:

D Cursor to a source and press [SELECT].
CB DISCRETE LINKS 23-Feb-92 11:47:12

Tag Descriptor
Addr =1C-80 Function DISC Discrete Block
@a >*M ON Þ*2 >start @i >
@b >*M ON Þ*7 >stop @j >
@c >MCC-1V Þ*1 >OFF @k >
@d >Vopen4X Þ144 OpenSgnl @l >
@e >Vclose4X Þ145 ClosSgnl @m >
@f >FIC-100/B Þ*2 >start @n >
@g > @o >
@h >
Block Mode> AUTO
CONFIG 1
Figure 3.3.3. Example of a Discrete Links Screen

CB: 3-3-5
Table 3.3.1. Discrete Links Screen Fields
Access
Level
LOCAL, OPERATOR,
Block Mode Oper Current block mode.
AUTO
Descriptor NA User-defined block descriptor. Display only
Discrete input register identification character

INPUT NA Display only
(@a through @p).
Standard message pair:

Number of the message pair assigned to the *1 -- * 100
Msg Conf
input. User message pair:
1--155
Tag number, address, or function of the input.

To select a block input, enter the tag or address
of the block.
To select a particular block register, use the
Block tag, address, or
SOURCE Conf format (tag or address/register character).
function
To select an input function, press [NEXT
OPTION] until the desired function appears, and
then press [ENTER].
For the discrete input sources, see Table 3.3.2.
State NA Current state of the input. Display only

CB: 3-3-6
Discrete Input Sources
Figure 3.3.4 shows that a Discrete or Contact input block, ControlBlock,

block register, or input function can provide the discrete data value for a
ControlBlock. Table 3.3.2 provides the format of each input type for
configuration in the “Source” field of the Discrete Links screen.
ControlBlock
Discrete or
Field Contact
Input Block
a--p
ControlBlock
Operator Console
Batch
Program
Figure 3.3.4. Discrete Input Sources

CB: 3-3-7
Table 3.3.2. Discrete Input Sources
Corresponding Function or Example

Type of Input Entry in “Source”
Field
Discrete or Contact Input Block Address or Tag Example: =2AA101
Output of another ControlBlock (a Address/input or

Example: =3D--15/c
through p) Tag/input
Input value that can be changed *M ON Remains OFF until turned ON. Remains ON
from the console keyboard or by (momentary ON) for one evaluation cycle.
a Batch program.
*M OFF Remains ON until turned OFF. Remains OFF
(momentary OFF) for one evaluation cycle.
*TOGGLE Changes state each time that the input is
actuated with [ENTER].
*SELECT
*VALUE Denotes input as part of a group. When one
of the inputs in a group is ON, all others in the
group are OFF. Use [ENTER] to turn on one
input in a group.
Denotes a value that can be changed from
another source (such as Batch). Cannot be
changed from the faceplate.
Fixed state input value that must *ON Remains ON at all times. Cannot be changed
be reconfigured to be changed. from faceplate.
*OFF
Remains OFF at all times. Cannot be
changed from the faceplate.

CB: 3-3-8

CB: 3-4-1
Section 4:
Configuration Constraints
The RS3 control system has constraints on the amount of information

that can be processed. You must consider these constraints when
configuring the control system. This section discusses linking and
capacity considerations.
Linking Considerations
Inputs and outputs of ControlBlocks are linked together to provide the

information necessary to perform process control. Table 3.4.1
summarizes the number of links available for each Controller Processor
card, each ControlFile, and each PeerWay. A description of the link
limits for each component follows.
Table 3.4.1. Links Available for Components
Number of
Component
Available Links
MPC Controller Processor:

Within Controller Processor Unlimited
Into and out of Controller Processor 40
MPCII Controller Processor:

MPC5 Controller Processor:

ControlFile:
Into and out of ControlFiles 40
PeerWay:
Within PeerWays 300
Between PeerWays (HIA) 40
RS3: Configuring Block Links Configuration Constraints

CB: 3-4-2
Number of Controller Processor Links
The number of links available for Controller Processors depends on

whether you link ControlBlocks that reside on the same Controller
Processor or ControlBlocks that reside on different Controller
Processors.
Limit Within Controller Processors
You can make an unlimited number of links between ControlBlocks

within the same Controller Processor. See Figure 3.4.1.
PeerWay Q
=16A--14 =16A--6
PeerWay Costs Controller Processor=16A 0 link

Buffer Costs ControlFile=16 0 link
Card Costs PeerWay 0 link
ControlFile
Coordinator Q
Processor =16A--12 =16A--2
Card
Controller Controller =16A--4

Processor Processor
Card Card
=16A =16B
Costs Controller Processor=16A 0 link
Costs ControlFile=16 0 link
CONTROLFILE =16
Costs PeerWay 0 link
Figure 3.4.1. Example of Links Within a Controller Processor

CB: 3-4-3
Limit Into and Out of Controller Processors
Forty links are available for each MPC Controller Processor. Eighty links
are available into and out of each MPCII or MPC5 Controller Processor.
The ControlFile Status screen displays the number of remaining links
for Controller Processors. For information about the ControlFile Status
screen, see “Viewing the Number of ControlFile Links Available” later in
this section.
D An input or output sent from a Controller Processor costs the
Controller Processor one link, regardless of how many Controller
Processors you link it to. See Figure 3.4.2.
D An input or output received by a Controller Processor costs the
Controller Processor one link, regardless of how many blocks in
the Controller Processor you link it to. See Figure 3.4.2.

CB: 3-4-4
PeerWay
Q
=16A--14 =16B--22
PeerWay
Buffer
Card
=16B--46
ControlFile
Coordinator
Processor Costs Controller Processor=16A 1 link
Card Costs Controller Processor=16B 1 link
Controller Controller
Processor Processor
Card Card
=16A =16B
ControlFile =16
PeerWay
Q
=16A--14 =16B--22
PeerWay
Buffer
Card
=16G--12
ControlFile Costs Controller Processor=16A 1 link

Coordinator Costs Controller Processor=16B 1 link
Processor Costs Controller Processor=16G 1 link
Card Costs ControlFile=16 0 link
Controller Controller Controller

Processor Processor Processor
Card Card Card
=16A =16B =16G
ControlFile =16
Figure 3.4.2. Examples of Links Between Controller Processor Cards

CB: 3-4-5
Number of ControlFile Links
Forty links are available for each ControlFile. The ControlFile Status
screen displays the number of remaining links for Controller Processors.
For information about the ControlFile Status screen, see “Viewing the
Number of ControlFile Links Available” later in this section.
D An input or output sent from a ControlFile costs the ControlFile
one link, regardless of how many ControlFiles you link it to. See
Figure 3.4.3.
D An input or output received by a ControlFile costs the ControlFile
one link, regardless of how many blocks in the ControlFile you
link it to. See Figure 3.4.3.

CB: 3-4-6
Q
=16A--14 =18B--22

Costs Controller Processor=18B 1 link
PeerWay
PeerWay PeerWay
Buffer Buffer
Card Card
ControlFile ControlFile
Coordinator Coordinator
Processor Processor
Card Card
Controller Controller Controller Controller

Processor Processor Processor Processor
Card Card Card Card
=16A =16B =18A =18B
ControlFile =16 ControlFile =18
Figure 3.4.3. Examples of Links Between ControlFiles

CB: 3-4-7
Q
=16A--14 =18A--22
=18B--46

PeerWay
PeerWay PeerWay
Buffer Buffer
Card Card
Processor Processor
Card Card

Card Card Card Card
=16A =16B =18A =18B
Figure 3.4.3. Examples of Links Between ControlFiles (continued)

CB: 3-4-8
Number of PeerWay Links
The number of links available for PeerWays depends on whether you

link ControlBlocks that reside on the same PeerWay or ControlBlocks
that reside on different PeerWays.
Limits for a PeerWay
Three hundred links are available for each PeerWay. You cannot view
the number of PeerWay links available so you should keep track of the
number of PeerWay links used.
D An input or output received by a PeerWay costs the PeerWay
one link, regardless of how many blocks in the PeerWay you link
it to. See Figure 3.4.4.

CB: 3-4-9
Q
=16A--14 =16B--22
=16B--46

Costs PeerWay 1 0 link
PeerWay 1 HIA HIA PeerWay 3
PeerWay PeerWay
Buffer Buffer
Card Card
Processor Processor
Card Card

Card Card Card Card
=16A =16B =20A =20B
Figure 3.4.4. Examples of Links Within a PeerWay

CB: 3-4-10
Limits for an HIA
Forty links are available for each Highway Interface Adapter (HIA)
connecting two PeerWays. See Figure 3.4.5.
Figure 3.4.6 shows a sample HIA configuration with three PeerWays

connected together. HIA connections have been made so that if
communication fails between a pair of HIAs, information can still be
shared among all PeerWays.
An HIA is used to connect two different PeerWays when the PeerWay

has more than 32 nodes. Links between ControlBlocks on different
PeerWays are seldom required. Take care if you are defining links over
HIAs. Define links so that no more than 40 links can be made over an
HIA under any condition.
For example, a link between PeerWay 1 and PeerWay 2 in Figure 3.4.6

can be established between HIA =18 and HIA =50, or along HIA =20,
HIA =82, HIA =84, and HIA =52. Therefore, count a link between
PeerWay 1 and PeerWay 2 as a link for all HIAs. In fact, when
configuring HIAs in a ring, count a link over any HIA as a link for all
HIAs.

CB: 3-4-11
Q
=16A--14 =85A--22
=85B--46

PeerWay 1 HIA HIA PeerWay 3
PeerWay PeerWay
Buffer Buffer
Card Card
Processor Processor
Card Card

Card Card Card Card
=16A =16B =85A =85B
Figure 3.4.5. Examples of Links Between Controller Processor Cards

CB: 3-4-12
HIA HIA
=20 =82
PeerWay 1 PeerWay 3
HIA HIA
=18 =84
HIA HIA
=50 =52
PeerWay 2
Figure 3.4.6. HIA Links

CB: 3-4-13
Viewing the Number of ControlFile Links Available
Since there is a limit to the number of links you can configure, it is

helpful to know how many available links remain. The ControlFile Status
screen contains fields that indicate the number of ControlFile links and
Controller Processor links that are available for configuration.
Figure 3.4.7 shows a sample ControlFile Status screen for node 2.
Table 3.4.2 describes the screen fields.
- To call up a ControlFile Status screen:
D From the command line, type:

CFS node number of the ControlFile [ENTER]
or
D From the ControlFile Links screen, press [EXCH].
ControlFile
Controller Processor (Coordinator Processor)
available links available links
CONTROL FILE STATUS 04-Nov-90 09:40:05

Node Address >2 File Status ®Norm Batch CP Batch Config NVM 56 K
Left CP: Boot 2.70 Prgm 14.08 Avail Links 40 Idle Time 62. %
Right CP: Boot 2.70
Left Program NVM Free 50 % BRAM V1.10 Soft Count 0
Additional Images: 1. MPCA
Config NVM Free 200 K
A B C D E F G H
Control Type MPCA MPCA MPCA
Boot Rev 5.23 5.23 5.23
Prgm Rev 14.12 14.12 14.12
Idle Time 92. % 92. % 100 %
Free Space 88 % 90. % 94. %
Avail Links 36 36 38
Avl Trnd Spc 1666 1712 1680
Primary
Status ®Norm ®Norm ®Norm
Alarm Inhib ®no ®no ®no
LOCAL Inhib ®no ®no ®no
Start Cal
Jumper Code 1_7_7 1_7_7 1_7_7
SC Timeout ÞNone ÞNone ÞNone
Scan Time Þ.5 S Þ.5 S Þ.5 S
NV Mem Used 8 K 8 K 8 K
Figure 3.4.7. Viewing the Number of Controller Processor and ControlFile Available Links

CB: 3-4-14
Table 3.4.2. Control File Status Screen Fields
Access
Level
Additional Lists (in order as loaded) all additional images

NA Display Only
Images loaded on the ControlFile.
Selects the alarm functioning of each Controller

Processor.
If “No” is selected, all alarms and events for the
Alarm Inhib Supr no, yes
Controller Processor function.
If “Yes” is selected, all alarms and events for the
Controller Processor are inhibited.
Avail Links Indicates the number of ControlFile links remaining

NA Display Only
(header) for configuration.
Avail Links Indicates the number of links remaining for

NA Display Only
(column) configuration for each Controller Processor.
Indicates the amount of trend space remaining for

Avl Trnd Spc NA Display Only
each Controller Processor.
Indicates the revision level of the Controller

Boot Rev NA Display Only
Processor boot software.
Control Type NA Indicates the type of the Controller Processor card. Display Only
Indicates the status of the Coordinator Processor.

“Norm” indicates that the Coordinator Processor
and all controller Processors are in normal
Supr/ operating mode.
File Status Norm, Stdby
Oper(1) “Stdby” indicates that the Coordinator Processor or
one of the Controller Processors is in standby
mode.
Use [NEXT OPTION] to select file status.
Indicates the amount of space available for each

Free Space NA Controller Processor to configure blocks, and block Display Only
components such as logic steps and links.
Indicates the amount of idle time of the CP

Idle Time Processor. It is normal for the idle time to drop to
(Coordinator NA zero at some times. If there is a running batch Display Only
Processor) operation on the CP, idle time may always be zero,
which is normal.
(1) Supervisors can access this field for non-Batch Coordinator Processors. Operators can access this field
for batch Coordinator Processors.
(2) Supervisors can change from Norm to Stdby status. Operators can change from Stdby to Norm status.

CB: 3-4-15
Table 3.4.2. Control File Status Screen Fields (continued)
Access
Level
Indicates the amount of idle time remaining during

Idle Time an evaluation cycle for each Controller Processor.
(Controller NA In final configuration, controller idle time should be Display Only
Processor) no lower than 18% under normal operation to allow
for process upset handling.
Indicates the MPC functionality and the image

selection for which the jumpers are configured when
using an MPCII.
Displayed in the format x_y_z, where:
x = 0 for 12 MHz MPC functionality, or
Display only
Jumper Code Conf 1 for 16 MHz MPC functionality
y = 0--7 for the Image Select jumpers
(HD6 -- HD8)
z = 0--7 for the MPC2 or MPC5 Sub-image
Select jumpers (HD4, HD5, and HD9)
For more information about jumpers, see SV: 4.
Displays the revision level of the Coordinator

Processor boot software. Use this field to switch
between redundant CPs.
If “Primry” appears, the primary CP is inhibited from
switching to the redundant CP. “Primry” appears if:
1. The CP has exceeded 2 automatic CP switches.
“Primry” is removed after 5.5 minutes.
2. The CP was manually switched by an operator.
Left CP: Boot “Primry” is removed after 11 minutes.
Supr/
[ENTER]
Right CP: Boot Oper(1) 3. The redundant communication area in the Bubble
or RAMBO dual port RAM is either not initialized or
is corrupt. “Primry” is removed when the error is
corrected.
4. The redundant CP has a data integrity error.
“Primry” is removed when the condition is no longer
present.
5. The CP is currently executing a program
download. “Primry” is removed when the download
is complete.

CB: 3-4-16
Access
Level
Indicates the amount of space available in

nonvolatile memory. Also indicates the type and
revision level of the nonvolatile memory (Bubble for
Left Program bubble nonvolatile memory or BRAM for
NA battery-backed RAM nonvolatile memory). Display Only
NVM Free
If the correct number of additional images have
been loaded into the CP, nonvolatile memory free
space should not be a limiting factor.
Left Program Indicates counting that occurs during the

NA Display Only
NVM Soft Count background diagnostics check.

CB: 3-4-17
Access
Level
Indicates whether or not any ControlBlocks can be

set to Local mode.
If “No”, ControlBlocks can be switched to Local
LOCAL Inhib Supr no, yes
mode.
If “Yes”, ControlBlocks cannot be switched to Local
mode.
Node Address Oper User-assigned node number. 1--992
Indicates the amount of nonvolatile memory that is

NV Mem Used NA reserved for the Controller Processor. The memory Display Only
is allocated in 8K chunks.
Indicates the revision level of the Coordinator

Processor software. The name of the software
Prgm NA Display Only
program appears to the right of the “File Status”
field.
Indicates the revision level of the Controller

Prgm Rev NA Display Only
Processor Program.
Indicates the primary Controller Processor for a

redundant Controller Processor. Use this field to
switch between redundant Controllers.
If “Primry” appears, the primary controller is
inhibited from switching to the redundant controller.
“Primry” appears if:
1. The controller has exceeded 2 automatic
controller switches. “Primry” is removed after 5.5
Primary Supr minutes. [ENTER]
2. The controller was manually switched by an
operator. “Primry” is removed after 11 minutes.
3. The same alarm on the same block which
caused the previous controller switch occurs again
within 10 seconds of the previous switch. “Primry” is
removed when the condition is no longer present.
After any controller switch, a manual switch is not
allowed for 8 seconds.

CB: 3-4-18
Access
Level

(SCI) or the MicroVAX to PeerWay Interface.
Indicates the time frame during which the SCI or
MicroVAX to PeerWay Interface must send at least
one write message to a ControlBlock residing within
SC Time out Conf 0 (None) --1800 S
the Controller Processor. The ControlBlock must
have a configured shed mode.
If a message is not sent within the configured time
frame, the SCI timer expires and the ControlBlock
switches to the configured shed mode.
Indicates the evaluation time for each Controller

Processor. Use [NEXT OPTION] to select scan .125 S, .25 S, .50 S,
Scan Time Conf
1.00 S
time.
Field is functional for Multi-Loop and

Single-Strategy Controller Processors only.
Calibrates all analog-to-digital (A/D) converters on
the Controller Processor. An alarm is generated if
an A/D converter has drifted out of the desired
Start Cal Oper no, act
range.
To calibrate the Controller Processor, cursor to the
desired Controller Processor and press [ENTER].
Field displays “act” for up to one minute, then
displays “no”.
Indicates status of each Controller Processor.

“Norm” indicates that the Controller Processor is in
Supr/ normal operating mode.
Status Norm, Stdby
Oper(2)
“Stdby” indicates that the Controller Processor is in
standby mode.

CB: 3-4-19
Viewing the Links of a ControlFile
The ControlFile Links screen displays the block addresses of links in

and out of a ControlFile and its Controller Processors. When too many
links are configured, knowing the ControlFile links that exist helps you to
determine whether you can rearrange blocks to eliminate some of those
links.
The ControlFile Links screen has a page for the Coordinator Processor
(displayed as PeerWay on the ControlFile Links screen) and one page
for each of its Controller Processors. Figure 3.4.8 shows a sample
ControlFile Links screen for the ControlFiles on node 2. Screens for
both the PeerWay links and the Controller Processor links are shown.
- To call up a ControlFile Links screen:
CFL node number of the ControlFile [ENTER]
or
D From the ControlFile Status screen, press [EXCH].
or
D From a ControlFile Links page for a Controller Processor, press
[PAGE AHEAD] to view the desired ControlFile Links page for a
ControlFile.

CB: 3-4-20
CONTROLFILE LINKS 27-Nov-91 09:59:31

Controller 2C Links
0 In Links (Values Requested)
Controller 2B Links

Controller 2A Links
=2B101
=2B104
=2D-7
3 Out Links (Values Supplied)
=2A-21
=2A-2
=2A-35
- To call up a Block References screen for that

block:
[PAGE AHEAD] D Cursor to a ControlBlock and press [SELECT].

Peerway Links for Node 1

=1B-03
=3A-22
3 Out Links (Values Supplied)
=2C-45
=2A-02
=2C-03
CONFIG 1
Figure 3.4.8. Viewing the ControlFile Links

CB: 3-4-21
Tracing a Link to a Destination Block
The Block References screen lists the ControlBlock variables that you
have linked to other blocks. This screen displays the tag and address of
the destination block to which you linked the block input. This
information can help you determine the effect of a change in block logic
on the block. This screen is for display purposes only. Figure 3.4.9
shows a sample Block References screen for ControlBlock =78A--08.
Table 3.4.3 describes the fields on the screen.
- To call up a Block References screen:
D Press [BLOCK REFERENCES], type the tag or address of the
block, and press [ENTER].
or
BR tag or address of the block [ENTER]
or
D From another screen in the same block, press
[BLOCK REFERENCES] or type
BR, then press [ENTER].
Use [PAGE AHEAD] and [PAGE BACK] to call up the Block References
screen for other ControlBlocks for a Controller Processor. More than
one page of block references may exist for a ControlBlock.
- To call up a Discrete Faceplate screen for the block:

D Cursor to a destination and press [SELECT].
BLOCK REFERENCES 27-May-92 10:21:07

Tag > Address >=78A-08
Source Destination Destination Source Destination Destination
Link Tag Address Link Tag Address
n -> LCC-103 =2A-71/@a |
o -> LCC-103 =2A-71/@b |
n -> FCC-110 =2A-73/@a |
0 -> FCC-110 =2A-73/@b |
|
|
|
|
|
|
|
|
|
*end*
Figure 3.4.9. Block References Screen

CB: 3-4-22
Table 3.4.3. Block References Screen Fields
Access
Field Description
Level
Addr Oper Address of the ControlBlock.
Destination Address NA Address of the block to which the ControlBlock register value is linked.
Tag of the block to which the ControlBlock register value is linked.

Destination Tag NA NOTE: If you have any controller image running on MPCI controller
hardware, the full 16-character tag is not displayed. The first 8
characters appear followed by “********”.
Source Link NA Letter of the ControlBlock register value that is linked to another block.
Tag Oper User-defined block tag.

CB: 3-4-23
Hints for Using Fewer Links
Advanced planning can significantly reduce linking bottlenecks. The

best way to avoid linking problems is to design the control system so
that the minimum number of inputs and outputs are linked between
Controller Processors and ControlFiles.
Use an Intermediate ControlBlock
As an example, Figure 3.4.10 shows two ways to achieve the same

results. Four continuous inputs are brought into Controller Processor
=1A. A calculation based on their values is used by ControlBlock
=1B--1. The first method links the four inputs directly to ControlBlock
=1B--1. This method costs Controller Processors =1A and =1B each
four links.
In contrast, the second method brings the four inputs to an intermediate

ControlBlock in Controller Processor =1A, where the calculation is
performed. One value is then linked to ControlBlock =1B--1. This
method costs Controller Processors =1A and =1B only 1 link each.

CB: 3-4-24
METHOD 1
=1A Costs =1A and =1B each 4 links. =1B
=1B--1
=1AA101
=1AA102
Calculation
=1AA103
=1AA104
METHOD 2
=1A Costs =1A and =1B each 1 link. =1B
=1A--4 =1B--1
=1AA101
=1AA102
Calculation
=1AA103
=1AA104
Figure 3.4.10. Example of Reducing Links

CB: 3-4-25
Use a ControlBlock Output Link Packet
Another feature that reduces linking problems is the ControlBlock output

link packet. All outputs of a block are sent as a packet. This packet
includes the continuous output (Q) and all the discrete outputs (a, b, c,
d, e, f, g, h, i, j, k, l, m, n, o, and p). The cost of sending the entire
packet is only one link. For more information about the data contained
in this packet, see Chapter 7.
Figure 3.4.11 shows an example using the ControlBlock output packet

feature. ControlBlock =1A--1 sends the continuous output Q and
discrete outputs a and b to ControlBlock =1B--4. Sending these outputs
costs Controller Processors =1A and =1B only 1 link each.
Costs Controller Processors

=1A and =1B
1 link.
=1A--1 Q =1B--4
Figure 3.4.11. Linking the Block Output Packet

CB: 3-4-26
You can group discrete links into an intermediate ControlBlock when

you use the output link packet.
However, because ControlBlocks are evaluated in numerical order, you

must address the intermediate ControlBlock properly in order to avoid
inducing an additional evaluation delay. The link data of a Controller
Processor is transferred to the Coordinator Processor after each
Controller Processor evaluation cycle. You must ensure that the
intermediate ControlBlock is always the last block evaluated in the
Controller Processor, or “old” link data may be transmitted (from the
ControlBlocks that have not been evaluated yet).
You only need to create an intermediate ControlBlock in the link sending

controller and not in the link receiving controller. You will win neither
links, nor evaluation time in the second case.

CB: 3-4-27
Free Space and Idle Time Considerations
ControlFile components have a finite amount of space in which to

contain control system information. The ControlFile Status screen
contains indicators of how much space is left, as shown in
Figure 3.4.12. For a description of the screen fields, see “Viewing the
Number of ControlFile Links Available” earlier in this section.
Controller Processor
Free Space
Controller Processor Nonvolatile Memory Coordinator Processor

Idle Time Free Space Idle Time
CONTROL FILE STATUS 04-Nov-90 09:40:05

Node Address >2 File Status ®Norm Batch CP Batch Config NVM 56 K
Left CP: Boot 2.70 Prgm 14.08 Avail Links 40 Idle Time 62. %
Right CP: Boot 2.70
Left Program NVM Free 50 % BRAM V1.10 Soft Count 0
Additional Images: 1. MPCA
Config NVM Free 200 K
A B C D E F G H
Control Type MPCA MPCA MPCA
Boot Rev 5.23 5.23 5.23
Prgm Rev 14.12 14.12 14.12
Idle Time 92. % 92. % 100 %
Free Space 88 % 90. % 94. %
Avail Links 36 36 38
Avl Trnd Spc 1666 1712 1680
Primary
Status ®Norm ®Norm ®Norm
Alarm Inhib ®no ®no ®no
LOCAL Inhib ®no ®no ®no
Start Cal
Jumper Code 1_7_7 1_7_7 1_7_7
SC Timeout ÞNone ÞNone ÞNone
Scan Time Þ.5 S Þ.5 S Þ.5 S
NV Mem Used 8 K 8 K 8 K
Figure 3.4.12. Idle Time and Free Space Indicators on ControlFile Status Screen

CB: 3-4-28
The following issues are some of the factors that affect the amount of
free space and idle time remaining in a Controller Processor. To
increase the amount of free space and idle time remaining in a
Controller Processor, make these kinds of changes in your
configuration:
D Fewer ControlBlocks
D Fewer I/O blocks
D Fewer links
D Fewer logic steps
D Fewer logic step comments
D Fewer descriptors
D Shorter descriptors
D Slower scan time
D Fewer ControlBlocks, more functions in each block
D Fewer ControlBlocks, more I/O blocks
NOTE: The Controller Processor idle time should be at least 18% or

higher.

CB: 3-5-1
Section 5:
Hints for Configuring Block Links
when configuring ControlBlock links and some possible ways to deal
with them. This section also provides tips that are helpful when
configuring ControlBlock links.

ControlBlock links and possible ways to handle them.
- The Continuous Links screen only displays inputs A through G.
How can I view inputs H through O?
Simply press [PAGE AHEAD] to view continuous inputs H through O.
- Every time that I try to configure a block link, an Invalid Link alarm
is displayed.
Don’t worry about this alarm. It’s normal for this message to appear
whenever you initially configure a link.
- The block input value is displayed as a value of 11.1, but the step
output for the following logic statement shows false:
aÞB==11.1
Display scaling values are not as sensitive as internal scaling values.
The actual input value has probably been rounded off to 11.1.
- Originally, I configured a ControlBlock input with the same scaling
as its source block. Then I changed the input scaling to match
another register. Now, I want to reconfigure the block so that it’s
scaled the same as the source block again, but I can’t get the
reconfiguration to work.
On the Continuous Links screen, cursor to the “Eng Zero” field for
the input that you want to scale and press [ENTER]. The * indicates
that the input is now scaled the same as its source block.
RS3: Configuring Block Links Hints for Configuring Block Links

CB: 3-5-2
- How can I increase the amount of Controller Processor free

space?
Try reducing the number of blocks, links, logic steps, logic step
comments, or descriptors that are configured to increase the amount
of Controller Processor free space. Reducing the scan time will
increase the Controller Processor idle time.
- The RS3 is running slowly.
You may need to reduce the number of links that are configured.
Check the ControlFile Status screen to see how many links are
configured:
D The “Avail Links” field at the top of the screen displays the
number of ControlFile (Coordinator Processor) links.
D The “Avail Links” field in the body of the screen displays the
number of Controller Processor links.
Reducing the number of blocks, links, logic steps, logic step
comments, or descriptors that are configured increases the
Controller Processor free space and idle time, speeding up the
system. Increasing the scan time (which reduces the scan
frequency) also helps speed up the system.

CB: 3-5-3
Configuration Tips
Listed below are hints to help you when configuring ControlBlock links.
- Using Eng Max and Eng Min
Remember that continuous input values A through O (on the
Continuous Links screen) aren’t limited to the range specified in the
“Eng Zero” and “Eng Max” fields. Any values outside of this range
are nonlinearly represented on the continuous faceplate.
- Using HIAs and links
When using HIAs, a link over any HIA is a link for all HIAs. This is
important to remember when determining the number of links that
are configured.
- Use caution when entering a tag or address
For situations like the one described below, be sure to enter a valid
hardware address or tag (one that has been referenced previously
on another Controller Processor card) for a source link. Otherwise,
an Invalid Link Input message will not be generated to warn you of
the improper configuration, and as a result, the source block will not
be updated.
If you are:
D configuring the “Source” field on a Continuous Links screen or
the Discrete Links screen, and
D using redundant Controller Processors, and
D planning to enter the hardware address of the block
Then:
D be sure to enter the hardware address of the block using the
left-hand Controller Processor, that is, A for Controller
Processors A and B, etc., as the Controller Processor part of the
address. For example, use the address =13AA101 rather than
the address =13BA101.

CB: 3-5-4
- Scrolling message pairs to save configuration time

For quicker configuration, you can scroll labels when assigning a
message pair number to a ControlBlock input, as shown in
Figure 3.5.1.
- To scroll message pair labels:

1. Cursor to the “Msg” field and enter the first letter
(or letters) of the desired label.
2. Press [NEXT OPTION] to scroll

through the labels that begin with
that letter (or letters).
3. When the label of your choice
appears, press [ENTER].

Tag Descriptor
l LOW
@a Þ*M ON Þ*2 >start @i >
low
@b Þ*M ON Þ*7 >stop @j >
@c ÞMCC-1V Þ*1 >OFF @k >
@d ÞVopen4X Þ144 OpenSgnl @l >
@e ÞVclose4X Þ145 ClosSgnl @m >
@f ÞFIC-100/B Þ*2 >start @n >
@g > @o >
@h >
Block Mode> AUTO
Figure 3.5.1. Scrolling Message Pair Labels

RS3t
Chapter 4:
Configuring a Continuous Diagram Screen
Section 1: Configuring ControlBlock Alarm Points . . . . . . . . . . . . . . . . . . . . 4-1-1

Types of Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1-1
Setting ControlBlock Alarm Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1-2
Alarms for Continuous Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1-2
Deviation Alarms for Continuous Input A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1-4
Deadbands for Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1-6
Alarms for the Continuous Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1-8
Configuring Alarm Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1-10
Section 2: Configuring a Continuous Diagram Screen . . . . . . . . . . . . . . . . . 4-2-1

Calling Up a Continuous Diagram Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2-3
Continuous Diagram Screen Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2-4
Section 3: Hints for Configuring a Continuous Diagram Screen . . . . . . . . 4-3-1

RS3: Configuring a Continuous Diagram Screen Contents

CB: ii
List of Figures
Figure Page
4.1.1 Configuring ControlBlock Alarm Points . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1-3
4.1.2 Deviation Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1-5
4.1.3 Alarm Generation with a Deadband . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1-6
4.1.4 Alarm Deadband . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1-7
4.1.5 Continuous Diagram Screen-Q Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1-9
4.1.6 Configuring Alarm Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1-11
4.2.1 Continuous Diagram Screen Among ControlBlock Screens . . . . . . . . . 4-2-2
4.2.2 Flowchart of Continuous Diagram Screens . . . . . . . . . . . . . . . . . . . . . . . 4-2-3
4.2.3 Continuous Diagram Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2-4

CB: iii
List of Tables
Table Page
4.2.1 Continuous Diagram Screen Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2-5
4.3.1 Alarm Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3-2

CB: 4-1-1
Section 1:
Configuring ControlBlock Alarm Points
This section describes the ControlBlock alarms and alarm priority for
continuous inputs and outputs.
Types of Alarms
You can set the following types of alarms:

D Critical alarms are used to indicate a critical situation that should
be handled immediately.
D Advisory alarms are used to indicate less critical problems.
D rate-of-change alarms are used to indicate that the input is
changing faster than the desired rate. A rate-of-change alarm is
in the format of x/second, with x being the rate expressed in
scaled units. Rate-of-change alarms are automatically
categorized as advisory with regard to priority and color.
RS3: Configuring a Continuous Diagram Screen Configuring ControlBlock Alarm Points

CB: 4-1-2
Setting ControlBlock Alarm Points
Set ControlBlock alarm points on the Continuous Diagram screen. The

shaded boxes in Figure 4.1.1 show the areas on the Continuous
Diagram screens that you can use to set alarms for each continuous
input and the output.
There is a Continuous Diagram screen for each continuous input (A

through O) that is configured on the Continuous Links screen. There is
also a Continuous Diagram for continuous output Q. The input register
character identified in the “Alarms” field indicates the input screen that is
displayed. Use [PAGE AHEAD] and [PAGE BACK] to access the next or
previous input screens. Figure 4.1.1 shows a sample Continuous
Diagram screen for the A (PV) input. For a description of the fields on
the screen, see Section 2.
Alarms for Continuous Inputs
You can set critical, advisory, and rate-of-change alarms for each
continuous input, A through O, on the corresponding Continuous
Diagram screen.
Figure 4.1.1 shows a faceplate with a high critical alarm of 100, a low
critical alarm of 0, and a rate-of-change alarm of 2 units/second
configured for input A (PV).

CB: 4-1-3
Continuous input alarms
CB CONTINUOUS DIAGRAM 27-Nov-91 09:57:18

Tag FCC-103 Descriptor
Addr =1A-01 Function PID Controller
Sample Time>.25 S Alarm Priority>0
+------------------------+
>FT-101 -------------->PV | | OPR Alarm Entry
.00 GPM | >PV ALARMS: | Crit >no
| PV Hi Crit >100.00 | Adv >no
>*ENTRY -------------->LS | |
.00 GPM | PV Hi Adv >None |
| | Output
>*NONE -------------->RS | PV Lo Adv >None |
.00 | |-----> 9.79
| PV Lo Crit >0.00 |
>*NONE -------------->FF | |
.00 | PV Rate >2.00/S |
| | Plant Unit >0
| PV DdBand >10.00 |
| | Auto Lock >no
| Dev Adv >40.00 |
| |
| Dev Crit >40.00 |
+------------------------+ Block Mode>AUTO
FULL CONFIG 1
Alarm deadband |SP--PV| Deviation alarms
Figure 4.1.1. Configuring ControlBlock Alarm Points

CB: 4-1-4
Deviation Alarms for Continuous Input A
You can set advisory and critical deviation alarms on the Continuous
Diagram screen for continuous input A of a PID function ControlBlock.
Only one advisory and one critical alarm are allowed per ControlBlock,
and these appear on each page of the Continuous Diagram screen after
they are set.
Deviation alarms are used to indicate a deviation of input A (the process

variable) from input B while in Auto, Manual, or Local mode, or to
indicate a deviation of input A from input C (the remote setpoint) while in
Remote mode. A deviation alarm is entered as a positive number, x,
which represents a deviation of x or --x. Deviation alarms can be a
combination of critical and advisory alarms.
NOTE: If you have configured an alarm deadband for the continuous

output Q, that deadband is applied to deviation alarms. The continuous
output alarm deadband is configured on the Q page of the Continuous
Diagram screen.
Figure 4.1.2 shows a sample continuous faceplate for inputs A and B

with a deviation alarm represented. The input PV has a critical deviation
alarm of ±40 configured as shown in the Continuous Diagram screen of
Figure 4.1.1

CB: 4-1-5
Units FLOW GPM

P V - A 195.06
LSP - B 195.00
RSP- C
FF - D
100 Safe zone
75
50
Alarm zone
25
0
50.18
OUT
% VALVE
AUTO
Figure 4.1.2. Deviation Alarm

CB: 4-1-6
Deadbands for Alarms
The deadband defines a range that extends below a high alarm point,
above a low alarm point, and within deviation alarm points for each
continuous input and the ControlBlock output. This range is to prevent
repeated tripping of alarms by a variable drifting in and out of the alarm
limit.
An alarm is generated when the value of a variable equals the alarm

point. The alarm indication remains as long as the value of the variable
is within the deadband or beyond the alarm point. Use of the alarm
deadband reduces the occurrence of multiple alarms for a variable
operating close to an alarm point. Figure 4.1.3 shows an example of an
alarm point with a deadband, and shows when alarms are generated.
Alarm indication
Another alarm indication

High alarm point
100 --
High alarm deadband
75
50
25
Figure 4.1.3. Alarm Generation with a Deadband

CB: 4-1-7
Configure the input deadband for each continuous input on the

corresponding page of the Continuous Diagram screen. Configure the
ControlBlock output deadband on the Q page of the Continuous
Diagram screen.
When configuring alarm deadbands, be aware that the size of the

deadband is important.
D Too small a deadband can result in the persistent generation of
an alarm, even though the variable may be within an acceptable
operating range.
D Too large a deadband can result in unusual fluctuations within the
deadband going unnoticed since only the initial occurrence of an
unacceptable value generates an alarm.
In other words, the alarm deadband should ideally be equal to the

magnitude of the “noise” component, no larger, no smaller.
Figure 4.1.4 shows a sample continuous faceplate with alarm

deadbands represented. The input PV has an input deadband of 10
engineering units configured as shown on the Continuous Diagram
screen in Figure 4.1.1.
Units FLOW GPM
PV-- A 195.0
High alarm point
LS-- B 195.1
RSP--C
High alarm deadband
FF-- D
100 -- High deviation alarm point
75
Deviation deadband
50
Low deviation alarm point

25
0 Low alarm deadband

50.1
OUT
Low alarm point
%
Figure 4.1.4. Alarm Deadband

CB: 4-1-8
Alarms for the Continuous Output
You can configure critical and advisory alarms for the continuous output
Q on the Q page of the Continuous Diagram screen.
Figure 4.1.5 shows a faceplate with a high advisory alarm of 100 and a
low advisory alarm of 0 configured for the output Q. Alarm entries are
expressed in scaled units as defined on the Continuous Links screen,
except for the deadband, which is entered as a percent of range.
To reach the Q page, use [PAGE AHEAD] and [PAGE BACK] from the
continuous input pages.

CB: 4-1-9
Continuous output alarms

+------------------------+
| | OPR Alarm Entry
| >Q ALARMS: | Crit >no
| Q Hi Crit >None | Adv >no
| |
| Q Hi Adv >100 |
| | Output
| Q Lo Adv >0 |
| |-----> 9.79
| Q Lo Crit >None |
| |
| |
| | Plant Unit >0
| Q DdBand >1.00 |
| | Auto Lock >no
| Dev Adv >None |
| |
| Dev Crit >None |
+------------------------+ Block Mode>AUTO
CONFIG 1
Alarm Deadband
Figure 4.1.5. Continuous Diagram Screen-Q Page

CB: 4-1-10
Configuring Alarm Priority
RS3 control system alarms are annunciated with a colored banner,

referred to as an alarm line, at the bottom of the console screen. The
“Alarm Priority” field affects only the alarm displayed in the alarm line.
For information about alarm annunciation and operator response to
alarms, see OP: 2.
If more than one unacknowledged alarm of the same type exists at one
time, a set of priorities determines which alarm banner is shown in the
alarm line. A list of the process alarm priorities follows:
1. Active unacknowledged alarms have priority over cleared
unacknowledged alarms.
2. Critical alarms have priority over advisory alarms.
3. Alarms are assigned priority by a number from 0-15. Alarms with
a lower alarm priority number assigned have priority over alarms
with a higher alarm priority number and replace the alarm
displayed in the alarm line.
When configuring ControlBlock priority, it may be desirable to
configure a priority of 7 or 8 to allow for later manipulation of the
priority without having to change the priority of all ControlBlocks.
4. When two alarms have the same priority, the first alarm
generated has priority over alarms generated later.
You can configure the default value for the “Alarm Priority” field on the
Alarm Configuration screen.
Figure 4.1.6 shows the area on the Continuous Diagram screen for
configuring the alarm priority.

CB: 4-1-11

+------------------------+
>*ENTRY -------------->PV | | OPR Alarm Entry
| PV Hi Crit >100 | Adv >no
>*NONE -------------->LS | |
| | Output
.00 | |-----> 9.79
| PV Lo Crit >0 |
>*NONE -------------->FF | |
.00 | PV Rate >2/S |
| | Plant Unit >0
| PV DdBand >10.00 |
| | Auto Lock >no
| Dev Adv >40.00 |
| |
| Dev Crit >40.00 |
+------------------------+ Block Mode> AUTO
FULL CONFIG 1
Figure 4.1.6. Configuring Alarm Priority

CB: 4-1-12

CB: 4-2-1
Section 2:
Configuring a Continuous Diagram Screen
This section describes the Continuous Diagram screen and the screen
fields.
Use the Continuous Diagram screen to configure continuous alarms,

plant units, and other features for the continuous input. The shaded box
in Figure 4.2.1 shows the Continuous Diagram screen among the
configuration screens for ControlBlock =1A--4.
RS3: Configuring a Continuous Diagram Screen Configuring a Continuous Diagram Screen

CB: 4-2-2
ControlBlock =1A--4

FACEPLATE FACEPLATE
CB CONTINUOUS
LINKS
H to O
[ EXCH ]
[ PAGE ]
CB DISCRETE LINKS
CB CONTINUOUS
LINKS
[ EXCH ]
A to G
[ PAGE ] [ PAGE ]

DIAGRAM DIAGRAM
A a
BLOCK REFERENCES
Figure 4.2.1. Continuous Diagram Screen Among ControlBlock Screens

CB: 4-2-3
Calling Up a Continuous Diagram Screen

- To call up a Continuous Diagram screen:
D Press [BLOCK DIAGRAM], type the tag or address of the
ControlBlock, and type / x [ENTER]
where x is the specified continuous input A--O.
or
D From another screen in the same ControlBlock, type
[BLOCK DIAGRAM] / x [ENTER]
where x is the specified continuous input A--O.
or
D From a ControlBlock Discrete Diagram screen, press [EXCH].
Figure 4.2.2 shows a flowchart of the Block Diagram screens that can
be called up from ControlBlock input A. Use [PAGE AHEAD] and [PAGE
BACK] keys to access the screens for the continuous inputs
A to O and continuous output Q.
CB CONTINUOUS
DIAGRAM
CB CONTINUOUS CB CONTINUOUS
DIAGRAM DIAGRAM
Input A
DIAGRAM Input Q Input BDIAGRAM
CB CONTINUOUS
Input O
DIAGRAM Input C
CB CONTINUOUS
Input N
CB CONTINUOUS Input D
DIAGRAM
DIAGRAM
CB CONTINUOUS
Input E
Input M
DIAGRAM
Input L DIAGRAM
CB CONTINUOUS CB CONTINUOUSDIAGRAMInput F
DIAGRAM DIAGRAM
CB CONTINUOUS
Input K DIAGRAM Input G
Input J Input H
Input I
[PAGE BACK] [PAGE AHEAD]
Figure 4.2.2. Flowchart of Continuous Diagram Screens

CB: 4-2-4
Continuous Diagram Screen Fields
The Continuous Diagram screens are primarily used to assign alarm

points to specific ControlBlock continuous values. A Continuous
Diagram exists for each continuous input (A through O) that is
configured on the Continuous Links screen. There is also a Continuous
Diagram for continuous output Q. Figure 4.2.3 shows the Continuous
Diagram screen for the A, or PV, input. Table 4.2.1 describes the screen
field areas.
For information about configuring alarm points, see Section 1.
Continuous Diagram screen

for input A (PV)
Information about
continuous links

+------------------------+
>*ENTRY -------------->PV | | OPR Alarm Entry
| PV Hi Crit >None | Adv >no
>*NONE -------------->LS | |
| | Output
.00 | |-----> 9.79
| PV Lo Crit >None |
>*NONE -------------->FF | |
.00 | PV Rate >None |
| | Plant Unit >0
| PV DdBand >1.00 |
| | Auto Lock >no
| Dev Adv >None |
| |
| Dev Crit >None |
+------------------------+ Block Mode> AUTO
FULL CONFIG 1
Figure 4.2.3. Continuous Diagram Screen

CB: 4-2-5
Table 4.2.1. Continuous Diagram Screen Fields
Access
Level
Assigns an alarm priority to critical and advisory

process alarms. 0 indicates highest priority, 15
Alarm Priority Conf indicates lowest priority. 0--15
For more information about alarm priorities, see
Section 1.
Indicates the input values at which alarms are to

be generated. If the input is equal to or greater
than the “Hi” alarm point or, equal to or less than
the “Lo” alarm point, an alarm is generated.
Fields appear only if an input is configured.
Supr The“Crit” fields are used to configure critical
alarms. The “Adv” fields are used to configure None, A--O,
ALARMS: or
advisory alarms. --999999. to 999999.
Oper
The “Rate” field specifies the maximum rate
(engineering units per second) that the input may
change before an alarm is generated.
For information about configuring input alarms,
see Section 1.
Indicates the range within which a variable can Input Deadband:

remain without tripping repeated alarms. An None, A--O,
alarm is generated only when the value of a 0. to 999999.
variable equals the configured alarm point. Default = 1.00
DdBand Conf The “DdBand” field selects the input alarm range. (engineering units)
The “Out DdBand” field selects the output alarm Output Deadband:
deadband range. 0. to 999999.
For more information about deadbands, see Default = 1.00
Section 1. (engineering units)
Indicates the PV--SP deviation range (expressed

as ± a number of engineering units) in which
input A can drift from input B or input C before an
alarm is generated. Must be a PID type
ControlBlock.
The “Dev Crit” field is used to configure the
Dev Crit generation of a critical alarm if input A exceeds None, A--O,
Supr*
Dev Adv the configured range. 0. to 999999.
The “Dev Adv” field is used to configure the
generation of an advisory alarm if input A
exceeds the configured range.
For more information about deviation alarms, see
Section 1.
* Operators can access the field if the “OPR Alarm Entry” field is configured as “Yes”.

CB: 4-2-6
Table 4.2.1. Continuous Diagram Screen Fields (continued)
Access
Level
Indicates whether or not the ControlBlock is

locked in Auto mode.
If “Yes”, the ControlBlock is locked in Auto mode
Auto Lock Conf no, yes
and cannot be changed to other modes.
If “No”, the ControlBlock can be switched to other
modes.
LOCAL, MANUAL,
Block Mode Oper Current block mode. AUTO, REMOTE,
DDC, COMP SP
Descriptor NA User--defined block descriptor. Display only
“Crit” field determines whether the operator can

enter critical alarm points. “Adv” field determines
whether the operator can enter advisory alarm
OPR Alarm points. To change the operator alarm entry
Entry selection, cursor to “Crit” or “Adv” and press
Conf [ENTER]. no, yes
Crit
Adv If “No”, the operator cannot change the input or
output alarm points. The default is “No”.
If “Yes”, the operator can change the input or
output alarm points.
Value of the ControlBlock output.

Output Oper The output value can be modified if the “Block .00 to 100.00
Mode” is Local or Manual.
Indicates a user--defined group to which the

ControlBlock is assigned. Write authority and
alarm annunciation for ControlBlocks with a plant
unit other than zero is restricted to consoles that
specify the same number on their Plant Unit
Plant Unit Conf Configuration screen. 0--255
Your console must first own the plant unit on the
Plant Unit Configuration screen, or you will not be
able to make an entry in this field.
For more information on the Plant Unit
Configuration screen, see CC: 1.

CB: 4-2-7
Table 4.2.1. Continuous Diagram Screen Fields (continued)
Access
Level
Indicates the output values (Q) at which alarms

are to be generated. If the output value is equal
to or greater than the “Hi” alarm point or, equal to
or less than the “Lo” alarm point, an alarm is
generated. None, A--O,
Q ALARMS: Supr* The “Crit” fields are used to configure critical --999999. to 999999.
alarms. The “Adv” fields are used to configure
advisory alarms.
These fields only appear on the Q page of the
Continuous Diagram screen. For information
about configuring output alarms, see Section 1.
Indicates the time interval between ControlBlock

output updates. The ControlBlock scans inputs
and performs calculations at the Controller
Processor scan time interval, regardless of the 0--99999.
“Sample Time” value. Hours (H), minutes
Sample Time Conf
The “Sample Time” may be longer, but not (M), seconds (S)
shorter, than the Controller Processor scan time. Default=1.S
If the ControlBlock “Sample Time” value is the
same as the Controller Processor scan time, the
value is backlighted.

CB: 4-2-8

CB: 4-3-1
Section 3:
Hints for Configuring a Continuous Diagram
Screen
when configuring a Continuous Diagram screen and some possible
ways to deal with them. This section also provides tips that are helpful
when configuring a Continuous Diagram screen.
Listed below are typical problems that occur when configuring a

Continuous Diagram screen and possible ways to handle them.
- The ControlBlock continuous input or output keeps alarming.
You might need to modify the deadband. The deadband allows a
value to move up and down freely within a band surrounding the
alarm point without repeatedly generating a new alarm each time it
crosses the alarm point. The purpose of this is to filter out the effect
of “noise”—fluctuations that are not of interest.
- Sometimes I can’t enter certain values in the “Sample Time”
field.
You’re probably trying to enter a sample time that’s less than the
Controller Processor scan time. If so, the value is defaulting to the
Controller Processor scan time.
You’ll have to enter a sample time that’s equal to or greater than the
scan time, or else change the scan time.
RS3: Configuring a Continuous Diagram Screen Hints for Configuring a Continuous Diagram Screen
CB: 4-3-2
Configuration Tips
Listed below are hints to help you when configuring a Continuous

Diagram screen.
- Determining the size of a deadband
Be careful when configuring the size of an alarm deadband:
D If the deadband is too small, an alarm could be generated
repeatedly even though the variable is within an acceptable
operating range.
D If the deadband is too large, you might not notice unusual
fluctuations within the deadband since an unacceptable value
only generates an alarm the first time it occurs.
- Configuring a process alarm
Remember that if you configure a process alarm for a ControlBlock,
you should configure an alarm priority too.
- Configuring Alarm priority
D Remember that when configuring the alarm priority, you might
want to configure a priority of 7 or 8 so that in the future you can
adjust the priority level without having to change the priority of all
other ControlBlocks.
D The alarm priority for unacknowledged alarms of the same type
is shown in Table 4.3.1.
Table 4.3.1. Alarm Priority
Priority
These alarms... have priority over...
No.
1 Active unacknowledged alarms Cleared unacknowledged alarms
2 Critical alarms Advisory alarms
3 Alarms with a smaller alarm priority number Alarms with a larger alarm priority number
The older alarm of two alarms with the same

4 The more recent alarm
priority
RS3: Configuring a Continuous Diagram Screen Hints for Configuring a Continuous Diagram Screen
RS3t
Chapter 5:
Configuring a Discrete Faceplate Screen
Section 1: Discrete Faceplate Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1-1

Calling Up a Discrete Faceplate Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1-3
Discrete Faceplate Screen Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1-4
Section 2: Configuring a Discrete Faceplate . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2-1

Discrete Faceplate Positions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2-2
Displaying a Discrete Variable State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2-4
Displaying a Continuous Variable Value or Units . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2-7
Displaying a System or User Flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2-9
Displaying a Message Pair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2-11
Displaying Static Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2-13
Section 3: Hints for Configuring Discrete Faceplates . . . . . . . . . . . . . . . . . . 5-3-1

RS3: Configuring a Discrete Faceplate Screen Contents

CB: ii
List of Figures
Figure Page
5.1.1 Discrete Faceplate Screen Among ControlBlock Screens . . . . . . . . . . 5-1-2
5.1.2 CB Discrete Faceplate Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1-4
5.2.1 Configuring a Discrete Faceplate Screen . . . . . . . . . . . . . . . . . . . . . . . . . 5-2-3
5.2.2 Displaying a Discrete Variable State Faceplate . . . . . . . . . . . . . . . . . . . 5-2-5
5.2.3 Sample Discrete Links Screen for Assigning a Message Pair . . . . . . . 5-2-6
5.2.4 Sample Discrete Diagram Screen for Assigning a Message Pair . . . . 5-2-6
5.2.5 Displaying Continuous Variable Information on a Faceplate . . . . . . . . . 5-2-8
5.2.6 Displaying a System Flag on a Faceplate . . . . . . . . . . . . . . . . . . . . . . . . 5-2-10
5.2.7 Displaying a Message Pair on a Faceplate . . . . . . . . . . . . . . . . . . . . . . . 5-2-11
5.2.8 Sample Discrete Faceplate and a Standard Message Pair Screen . . . 5-2-12
5.2.9 Displaying Static Information on a Faceplate . . . . . . . . . . . . . . . . . . . . . 5-2-13
5.3.1 Operator--Enterable Continuous Variable . . . . . . . . . . . . . . . . . . . . . . . . . 5-3-2

CB: iii
List of Tables
Table Page
5.1.1 Discrete Faceplate Common Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1-5
5.2.1 Continuous Variable Information for a Faceplate . . . . . . . . . . . . . . . . . . 5-2-8

CB: 5-1-1
Section 1:
Discrete Faceplate Screen
This section describes the Discrete Faceplate screen and the screen
fields.
You use the Discrete Faceplate screen to configure a discrete faceplate.

A discrete faceplate provides a display of the ControlBlock input and
output information. You can configure a discrete faceplate for each
ControlBlock to display up to 17 lines of information, including
continuous variable values or engineering units, discrete variable states,
message pair labels, and certain alphanumeric characters. The shaded
box in Figure 5.1.1 shows the Discrete Faceplate screen among the
other ControlBlock configuration screens.
RS3: Configuring a Discrete Faceplate Screen Discrete Faceplate Screen

CB: 5-1-2

FACEPLATE FACEPLATE
CB CONTINUOUS LINKS [ EXCH ]
H to O
[ EXCH ]
CB CONTINUOUS LINKS
A to G
[ PAGE ] [ PAGE ]
A a
BLOCK REFERENCES
Figure 5.1.1. Discrete Faceplate Screen Among ControlBlock Screens

CB: 5-1-3
Calling Up a Discrete Faceplate Screen

- To call up a Discrete Faceplate screen:
D For a discrete function ControlBlock (such as a DISC, DMC,
DVC, or others), at the command line press [BLOCK
FACEPLATE], type the tag or address of the ControlBlock, and
press [ENTER].
or
D For a continuous function ControlBlock, (such as a PID, MATH,
or others), at the command line press [BLOCK FACEPLATE],
type the tag or address of the ControlBlock, press [ENTER], and
then press [EXCH].
or
D From a group display or a Process Graphic display of a discrete
function ControlBlock, cursor to a faceplate and press [SELECT].
or
D From a group display or a Process Graphic display of a
continuous function ControlBlock, cursor to a faceplate, press
[SELECT], and then press [EXCH].
Figure 5.1.1 shows the Discrete Faceplate screen among the other
ControlBlock configuration screens.

CB: 5-1-4
Discrete Faceplate Screen Fields
Configure a discrete faceplate on the Discrete Faceplate screen.

Figure 5.1.2 shows an unconfigured Discrete Faceplate screen.
Table 5.1.1 describes the screen fields.
CB DISCRETE FACEPLATE 27-Nov-91 09:55:51

1 | |
Addr Function 2 | |
3 | |
1> 2> 3> 4> 5> 4 | |
5 | |
6 | |
7 | |
6> 7> 8> 9> 10> 8 | |
9 | |
10 | |
11 | |
11> 12> 13> 14> 15> 12 | |
13 | |
14 | |
15 | |
16> 17> Overview > Unit 1> 2> 3> 16 | |
17 | |
FULL CONFIG 1
Figure 5.1.2. CB Discrete Faceplate Screen

CB: 5-1-5
Table 5.1.1. Discrete Faceplate Common Fields
Access
Level
Assigns an alarm priority to critical and advisory

process alarms. 0 indicates highest priority, 15
Alarm Priority Conf indicates lowest priority. 0 (default) --15
Chapter 4, Section 1.
LOCAL (default), MANUAL,

Block Mode Oper Current block mode. AUTO, COMPUTER,
REMOTE
Descriptor Conf User-defined block descriptor.
characters
NONE (Unconfigured),
MAN Manual Block,
P Controller,
I Controller,
D Controller,
PI Controller,
ID Controller,
PD Controller,
PID Controller,
IB Controller,
LL Lead/Lag,
DT Dead Time,
TOT Stack Totalizer,
TOTSP Setpoint Totalizer,
RB Ratio/Bias, SS Signal
Selector, VLIM Velocity
Function Conf Major function of the ControlBlock. Limiter, POLY Polynomial
Function, PLI Piecewise
Linear Interpolator, MATH
User-Defined Function, ATP
Auto Tuning, ATPI Auto
Tuning, ATPD Auto Tuning,
ATPID Auto Tuning, DISC
Discrete Block, DMC Motor
Controller, DASMC Auto
Sequence Motor Controller,
DDSMC Dual Speed Motor
Controller, DDDMC Dual
Direction Motor Controller,
DVC Valve Controller,
DASVC Auto Sequence
Valve Controller, DMVC
Motorized Valve Controller

CB: 5-1-6
Table 5.1.1. Discrete Faceplate Common Fields (continued)
Access
Level
Fields that correspond to the numbered rows of

the discrete faceplate at the right of the screen.
Each field has an upper line to accept your entry
and a lower line for display.
You can enter one of the following on the upper
line of each field:
D A discrete variable (@a--@o, a--p). The
faceplate displays the corresponding on/off Discrete variables:
state. @a--@o, a--p
D A continuous variable (A--O, Q). The Continuous variables:
faceplate displays the corresponding value A--O, Q
or engineering units. Continuous variable eng
(Numbered
Conf A message pair number (standard units:
Fields) D
messages *1--*100 or user messages %A--%O, %Q
1--155). The faceplate displays one of the Message pairs:
two states specified in the message pair. (Standard) *1--*100,
D A symbol (*, --, =, +). The faceplate (User) 1--155
displays a line filled with the symbol you Symbols: *, --, =, +
type.
The lower line displays the tag or function that
corresponds to the register you entered on the
upper line or the information that will appear on
the faceplate.
For information about configuring the faceplate
display, see Section 2.
Identifies the number of the one line of the

discrete faceplate that will appear on an overview
display.
Overview Conf 1--17
An overview display shows one line of each
faceplate from up to two unit displays. The
overview display faceplates are for display only.
Indicates a user-defined group to which the

ControlBlock is assigned. Write authority and
alarm annunciation for ControlBlocks with a plant
unit other than zero are restricted to consoles that
specify the same number on their Plant Unit
Plant Unit Conf Configuration screen. 0 (default) -255
Your console must first own the plant unit on the
Plant Unit Configuration screen, or you will not be
able to make an entry in this field.
For more information on the Plant Unit
Configuration screen, see CC: 1.
Displays the register letter (a through p) of all of

Steps in
NA the ControlBlock logic steps that are currently in Display only
MANUAL
Manual mode.

CB: 5-1-7
Table 5.1.1. Discrete Faceplate Common Fields (continued)
Access
Level
characters, at least one of
Tag Conf User-defined block tag.
which must be an
alphabetical character
Identifies the number of the line of the discrete

faceplate that will appear on a unit display. Up to
three lines from the faceplate can be designated
Unit 1, 2, 3 Conf to appear on a unit display. 1--17
A unit display shows up to three lines of a
discrete faceplate from a group display. The
faceplates on the unit display are for display only.

CB: 5-1-8

CB: 5-2-1
Section 2:
Configuring a Discrete Faceplate
This section describes how to configure a discrete faceplate using the

Discrete Faceplate screen. It describes the relationship between the
numbered fields on the screen and the faceplate. It also describes how
to display these types of information on a discrete faceplate:
D A discrete variable state
D A continuous variable value or units
D A system or user flag
D A message pair
D Static information
RS3: Configuring a Discrete Faceplate Screen Configuring a Discrete Faceplate

CB: 5-2-2
Discrete Faceplate Positions
You configure a discrete faceplate for a ControlBlock on the Discrete

Faceplate screen. You can configure each discrete faceplate to display
up to 17 lines of information, including continuous variable values or
engineering units, discrete variable states, message pair labels, and
certain alphanumeric characters.
Configure a discrete faceplate from the 17 numbered fields on the

Discrete Faceplate screen. These fields correspond to the numbered
rows of the faceplate display at the right of the screen. Each field has an
upper line to accept your entry and a lower line for display. The upper
line is for faceplate configuration. The lower line displays the tag or
function that corresponds to the register you entered on the upper line
or the information that will appear on the faceplate. Figure 5.2.1 shows
how field number 5 corresponds to row number 5 on the discrete
faceplate.

CB: 5-2-3
Faceplate configuration field Faceplate display field

Tag >STK1-Valve BB4 Descriptor > +--------+
1 | pump |
Addr =1A-01 Function PID Controller 2 | ON |
3 > OFF |
1>25+ 2>@b 3>@g 4>- 5>A 4 |--------|
STK1-1A *TOGGLE =1A-7 5 | 5 |
Sensor 2 6 | GPM |
7 | FILL 1 |
6>%A-3 7>*13- 8>= 9>g 10> 8 |========|
=1A-7 9 |RUN CFRM|
10 | |
11 |********|
11>* 12>Q 13>%Q 14>*21- 15> 12 | 24.16 |
13 | GPM |
14 |confirm |
15 | |
16>#B 17>C.u.d Overview > Unit 1> 2> 3> 16 > 28.60 |
17 | ON |
FULL CONFIG 1
Figure 5.2.1. Configuring a Discrete Faceplate Screen

CB: 5-2-4
Displaying a Discrete Variable State
The state of a discrete input, @a through @o, or a discrete step output,

a through p, can be displayed on a discrete faceplate. The discrete
variable state is displayed as described by a message pair. Unless you
configure a descriptive message pair to describe the variable state, the
state is displayed as on or off. Figure 5.2.2 shows a discrete faceplate
configured to display the state of inputs @b and @g and the state of
step output g. Figure 5.2.2 also describes how to configure a faceplate
to display a discrete variable state.
Message pairs are assigned to discrete inputs on the Discrete Links

screen and to discrete outputs on the Discrete Diagram screen.
Figure 5.2.3 shows the Discrete Links screen for input @g with standard
message pair number 1 configured to describe its output state.
Figure 5.2.4 shows the Discrete Diagram screen for output g with
standard message pair number 30 configured to describe its output
state.
For information about configuring a Discrete Links screen, see

Chapter 3. For information about configuring a Discrete Diagram
screen, see Chapter 6.
More descriptive message pairs can be configured on the Standard

Message Pairs screen and the User Message Pairs screen. For
information about configuring message pairs, see CC: 1.

CB: 5-2-5
- To display a discrete variable state:

D Cursor to the appropriate numbered field, ente
r the appropriate register letter, and press [EN The second line displays the tag or
TER]. function of the variable.

1 | pump |
3 > OFF |
1>25+ 2>@b 3>@g 4>- 5>A 4 |--------|
STK1-1A *TOGGLE =1A-7 5 | 5 |
Sensor 2 6 | GPM |
7 | FILL 1 |
6>%A-3 7>*13- 8>= 9>g 10> 8 |========|
=1A-7 9 |RUN CFRM|
10 | |
11 |********|
11>* 12>Q 13>%Q 14>*21- 15> 12 | 24.16 |
13 | GPM |
14 |confirm |
15 | |
17 | ON |
FULL CONFIG 1
Figure 5.2.2. Displaying a Discrete Variable State Faceplate

CB: 5-2-6
Tag Descriptor
INPUT SOURCE State Msg INPUT SOURCE State Msg

@a Þ*M ON >start Þ*2 @i >
@b ÞTank-1 >ON Þ*1 @j >
@c ÞMCC-1V >OFF Þ*1 @k >
@d ÞVopen4X OpenSgnlÞ144 @l >

@e ÞVclose4X ClosSgnlÞ145 @m >
@f ÞFIC-100/b >start Þ*2 @n >
@g Þ*Toggle >OFF Þ*1 @o >

@h >
Block Mode> AUTO

CONFIG 1
Figure 5.2.3. Sample Discrete Links Screen for Assigning a Message Pair
CB DISCRETE DIAGRAM 27-Nov-91 09:54:31

Tag STK1-Valve AB2 Descriptor
Addr =1A-01 Function DISC Discrete Block Plnt>0
+-------------------CONDITIONS--------------------+Step>g
| * |
| * g= > |Mode>Auto
| * |
| * Set > |MsgP>*30
| * |On
| *Clear> |
| * |->RUN CFRM
|---*----------------ACTIONS----------------------|
| * |
| * Rise> |
| * |
| * ON > |Rpt>None
| * |
| * Fall> |
| * |
| * OFF > |
+-------------------------------------------------+
FULL CONFIG 1
Figure 5.2.4. Sample Discrete Diagram Screen for Assigning a Message Pair

CB: 5-2-7
Displaying a Continuous Variable Value or Units
You can display the value or engineering units corresponding to a

continuous input A through O or output Q on a discrete faceplate.
When you configure the first line of one of the 17 numbered fields, the
second line displays the corresponding tag or function of the variable.
The value of a continuous input that is displayed uses the scaling
configured on the Continuous Links screen.
Figure 5.2.5 shows a discrete faceplate configured to display the value

and units for continuous input A and continuous output Q. Table 5.2.1
describes the continuous variable information that can be displayed on
a discrete faceplate and provides examples of each.

CB: 5-2-8

1 | pump |
3 > OFF |
1>25+ 2>@b 3>@g 4>- 5>A 4 |--------|
STK1-1A *TOGGLE =1A-7 5 | 5 |
Sensor 2 6 | GPM |
7 | FILL 1 |
6>%A-3 7>*13- 8>= 9>g 10> 8 |========|
=1A-7 9 |RUN CFRM|
10 | |
11 |********|
11>* 12>Q 13>%Q 14>*21- 15> 12 | 24.16 |
13 | GPM |
14 |confirm |
15 | |
17 | ON |
FULL CONFIG 1
Figure 5.2.5. Displaying Continuous Variable Information on a Faceplate
Table 5.2.1. Continuous Variable Information for a Faceplate
To display this information Example (from

Enter this information on the first line . . .
on the faceplate . . . Figure 5.2.5 above)
Continuous variable value Continuous variable name A (field 5)
Engineering units of the

% and the continuous variable name %Q (field 13)
continuous variable
Continuous variable %, the continuous variable name, a dash, and the

engineering units, message pair color. For information about color %A--3 (field 6)
with message pair color number selection, see CC: 1.
Continuous variable value, # and the continuous variable name

#B (fields 15 and 16)
operator enterable (The preceding position must be empty)

CB: 5-2-9
Displaying a System or User Flag
A system or user flag for a ControlBlock can be displayed on a discrete

faceplate. One or all flags can be displayed. The format for configuring
the flag for display depends on the number of flags to be displayed as
shown by the following examples.
- To display one flag on a discrete faceplate, type:
X.z.y where
X is the register A--O or Q, containing the flag
z is a “u” to indicate a user flag or an “s” or “t” to indicate a
system flag
y is a particular flag, a--p
- To display all flags on a discrete faceplate, type:
X.z where
X is the register A--O or Q, containing the flag
z is a “u” to indicate the user flags or an “s” or “v” to
indicate the system flags
If all flags are displayed, 16 positions of the faceplate are occupied. No

other entries are allowed in those 16 fields.
Figure 5.2.6 shows a discrete faceplate configured to display user flag d

of input C and describes how to configure a faceplate to display a user
or system flag.
For more information about flags, see Chapter 7.

CB: 5-2-10

1 | pump |
3 > OFF |
1>25+ 2>@b 3>@g 4>- 5>A 4 |--------|
STK1-1A *TOGGLE =1A-7 5 | 5 |
Sensor 2 6 | GPM |
7 | FILL 1 |
6>%A-3 7>*13- 8>= 9>g 10> 8 |========|
=1A-7 9 |RUN CFRM|
10 | |
11 |********|
11>* 12>Q 13>%Q 14>*21- 15> 12 | 24.16 |
13 | GPM |
14 |confirm |
15 | |
17 | ON |
FULL CONFIG 1
- To display a flag: The status of the particular flag is

D Cursor to the appropriate numbered field; enter displayed. In this example, user
the flag to be displayed, using the format flag d of the C input, the valid
described on the facing page; and press [ENTER]. data flag, is active.
Figure 5.2.6. Displaying a System Flag on a Faceplate

CB: 5-2-11
Displaying a Message Pair
A message pair can be displayed on a faceplate. Message pairs help to

identify the information that is being displayed in a faceplate.
Figure 5.2.7 shows a discrete faceplate configured to display message

pair labels in positions 1, 7, and 14 and describes how to configure
message labels to appear in a faceplate. Figure 5.2.8 shows that the
false message for message pair number 21 is “confirm”.
Message pair labels are messages from the Standard Message Pair
screen and the User Message Pair screen. Messages on the faceplate
appear in the color in which the message is configured on the Standard
Message Pair screen or the User Message Pair screen. For information
about standard and user message pairs, see CC: 1.
- To display a message pair:

D Cursor to the appropriate numbered field; enter the desire
d message pair number, including a + for the true messag
e or a -- for the false message; and press [ENTER].
If the + or -- message is not assigned, the +message is th
e default.

1 | pump |
3 > OFF |
1>25+ 2>@b 3>@g 4>- 5>A 4 |--------|
STK1-1A *TOGGLE =1A-7 5 | 5 |
Sensor 2 6 | GPM |
7 | FILL 1 |
6>%A-3 7>*13- 8>= 9>g 10> 8 |========|
=1A-7 9 |RUN CFRM|
10 | |
11 |********|
11>* 12>Q 13>%Q 14>*21- 15> 12 | 24.16 |
13 | GPM |
14 |confirm |
15 | |
17 | ON |
FULL CONFIG 1
Figure 5.2.7. Displaying a Message Pair on a Faceplate

CB: 5-2-12
1 pump STD MESSAGE PAIRS

2 ON
3 > OFF Pair True Atr False Atr Pair
4 ---------
5- 5 *21 %CONFIRM %C4 %confirm %C1 *31
6 GPM
7 FILL 1 *22 %ON CFRM %C4 %on cfrm %C1 *32
8 ========
9 RUN CFRM *23 %LO CFRM %C4 %lo cfrm %C1 *33
10
11 ********* *24 %HI CFRM %C4 %hi cfrm %C1 *34
12 24.16
13 GPM *25 %FWD CFRM %C4 %fwd cfrm %C1 *35
14 confirm
15 *26 %REV CFRM %C4 %rev cfrm %C1 *36
16 > 28.60
17 *27 %OFF CFRM %C4 %off cfrm %C1 *37
*28 %OPN CFRM %C4 %opn cfrm %C1 *38
*29 %CLS CFRM %C4 %cls cfrm %C1 *39
*30 %RUN CFRM %C4 %run cfrm %C1 *40
Figure 5.2.8. Sample Discrete Faceplate and a Standard Message Pair Screen

CB: 5-2-13
Displaying Static Information
Static characters can be displayed on a faceplate. Static characters

help format the information displayed in a faceplate.
When configured for faceplate display, static characters such as =, --, *,

and + fill the faceplate line. Any characters not associated with a block
variable can be displayed as static characters. Figure 5.2.9 shows a
discrete faceplate configured to display static characters in positions 4,
8, and 11 for faceplate dividing lines, and it describes how to configure
static characters to appear in a faceplate.
- To display static information:

D Cursor to the appropriate numbered field, enter the d
esired character, and press [ENTER].

1 | pump |
3 > OFF |
1>25+ 2>@b 3>@g 4>- 5>A 4 |--------|
STK1-1A *TOGGLE =1A-7 5 | 5 |
Sensor 2 6 | GPM |
7 | FILL 1 |
6>%A-3 7>*13- 8>= 9>g 10> 8 |========|
=1A-7 9 |RUN CFRM|
10 | |
11 |********|
11>* 12>Q 13>%Q 14>*21- 15> 12 | 24.16 |
13 | GPM |
14 |confirm |
15 | |
17 | ON |
FULL CONFIG 1
Figure 5.2.9. Displaying Static Information on a Faceplate

CB: 5-2-14

CB: 5-3-1
Section 3:
Hints for Configuring Discrete Faceplates
when configuring a ControlBlock discrete faceplate and some possible
ways to deal with them. This section also provides tips that are helpful
when configuring a discrete faceplate.
Listed below are typical problems that occur when configuring a

ControlBlock discrete faceplate and possible ways to handle them.
- The discrete faceplate does not allow an operator to enter a
discrete variable value.
Be sure that the variable function is configured as *Toggle.
- When the ControlBlock is evaluated, the outputs are not as I
expected.
Check the “Steps in Manual” field to see if any steps are in Manual
mode. If so, change them to Auto mode. Only steps in Auto mode
are evaluated when the ControlBlock is evaluated.
- The discrete faceplate screen does not allow me to enter “#B” so
that I can configure an operator-enterable continuous variable
value.
This is a common problem. You are configuring the variable position
correctly by entering “#B” in position 16, but you may have forgotten
that the previous position, in this case position 15, must be empty.
Check that the previous numbered field in the faceplate is empty, as
shown in Figure 5.3.1.
RS3: Configuring a Discrete Faceplate Screen Hints for Configuring Discrete Faceplates
CB: 5-3-2

1 | pump |
3 > OFF |
1>25+ 2>@b 3>@g 4>- 5>A 4 |--------|
FCC-103 *TOGGLE =1A-7 5 | 5 |
6 | GPM |
7 | FILL 1 |
6>%A-3 7>*13- 8>= 9>g 10> 8 |========|
=1A-7 9 |RUN CFRM|
10 | |
11 |********|
11>* 12>Q 13>%Q 14>*21- 15> 12 | 24.16 |
13 | GPM |
14 |confirm |
15 | |
17 | ON |
FULL CONFIG 1
Field 15 must be empty to allow operator entry in line 16.
Figure 5.3.1. Operator--Enterable Continuous Variable
CB: 5-3-3
Configuration Tips
Listed below are hints to help you when configuring a ControlBlock

discrete faceplate.
- Configuring descriptive message pairs
D Remember that you can configure descriptive messages for
display on a discrete faceplate by assigning them on the User
Message Pair screen or the Standard Message Pair screen.
D When specifying a message pair on a discrete faceplate you can
also enter a + (for true condition) or a -- (for false condition) to
specify the label to be displayed. If no label is specified, the +
message is the default.
CB: 5-3-4
RS3t
Chapter 6:
Configuring Logic Steps
Section 1: Introduction to Logic Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1-1

Screens for Configuring ControlBlock Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1-2
Logic Step Evaluation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1-4
Order of Logic Steps is Important . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1-4
Input Changes on the Following Cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1-5
Scaling and Logic Step Evaluation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1-6
Section 2: Configuring a Discrete Diagram Screen . . . . . . . . . . . . . . . . . . . . 6-2-1

Calling Up a Discrete Diagram Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2-2
Discrete Diagram Screen Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2-4
Configuring a Logic Step to Generate an Alarm or Event Message . . . . . . . . . . . 6-2-7
Section 3: Configuring Logic Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-1

Configuring Conditions Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-2
Configuring an Emulation Logic Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-4
Configuring a Set/Clear Logic Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-6
Configuring Action Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-8
Configuring an On Logic Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-10
Configuring an Off Logic Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-12
Configuring a Rise Logic Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-14
Configuring a Fall Logic Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-16
How to Write Logic Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-18
Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-18
Continuous Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-18
Discrete Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-19
Mathematical and Logical Operators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-20
Logic Statement Order of Precedence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-23
Using Variables and Operators in Combined Expressions . . . . . . . . . . . . . 6-3-23
Logic Statement Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-24
Comments in Logic Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-25
Applications for Logic Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-26
Using a Set/Clear Statement to Detect a Change in State . . . . . . . . . . . . . . . . 6-3-26
Using an Action Statement to Override a Block Action . . . . . . . . . . . . . . . . . . . 6-3-28
Block Actions Affecting the Output, Q . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-28
Block Actions Affecting the Linked Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-30
Section 4: Logic Statement Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4-1

Count Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4-3
RS3: Configuring Logic Steps Contents

CB: ii
Delay Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4-5

Duty and Period Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4-7
Timer Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4-12
Wait Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4-14
Ramping a Variable (ramp function) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4-16
Using the Clock Time or Date (time function) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4-18
Changing the Logic Step Mode (setuauto and setuman functions) . . . . . . . . . . . . 6-4-20
Changing or Testing the ControlBlock Operating Mode . . . . . . . . . . . . . . . . . . . . . 6-4-22
(setmode n function) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4-22
Testing for Block Mode (mode n function) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4-24
Testing the Block Mode of the Block Being Configured . . . . . . . . . . . . . . . . 6-4-24
Testing the Block Mode of Another Block . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4-25
Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4-26
Testing the Controller Processor Mode (ifstand function) . . . . . . . . . . . . . . . . . 6-4-26
Setting the Controller Processor Card Mode (sstand and snorm functions) . 6-4-28
Inhibiting ControlBlock Alarms (inhibit function) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4-30
Inhibiting and Enabling the Controller Processor Alarms
and Events (inha and enba functions) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4-32
(if?then:else function) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4-34
Resetting a Stack Totalizer (treset function) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4-37
Section 5: Hints for Configuring Logic Steps . . . . . . . . . . . . . . . . . . . . . . . . . 6-5-1


CB: iii
List of Figures
Figure Page
6.1.1 ControlBlock Logic Step . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1-1
6.1.2 Screens Used to Configure a Logic Step . . . . . . . . . . . . . . . . . . . . . . . . . 6-1-3
6.1.3 Inputs Change One Cycle Later . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1-5
6.2.1 Discrete Diagram Screen Among ControlBlock Screens . . . . . . . . . . . . 6-2-1
6.2.2 Flowchart of Discrete Diagram Screens . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2-3
6.2.3 Discrete Diagram Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2-4
6.2.4 Configuring a Logic Step to Generate an Alarm or Event Message . . 6-2-7
6.2.5 Configuring a Logic Step to Generate an Event Message . . . . . . . . . . 6-2-9
6.3.1 Discrete Diagram—Area for Configuring Condition Logic
Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-3
6.3.2 Simple Emulation Logic Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-4
6.3.3 Emulation Logic Statement Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-5
6.3.4 Sample Set/Clear Logic Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-7
6.3.5 Set/Clear Logic Statement Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-7
6.3.6 Discrete Diagram—Area for Configuring Action Logic Statements . . . 6-3-9
6.3.7 Setting and Locking a Setpoint Using an On Statement . . . . . . . . . . . . 6-3-11
6.3.8 On Logic Statement Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-11
6.3.9 Setting and Locking a Setpoint Using an Off Statement . . . . . . . . . . . . 6-3-13
6.3.10 Off Logic Statement Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-13
6.3.11 Adjusting a Setpoint Using a Rise Statement . . . . . . . . . . . . . . . . . . . . . 6-3-15
6.3.12 Rise Logic Statement Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-15
6.3.13 Adjusting a Setpoint Using a Fall Statement . . . . . . . . . . . . . . . . . . . . . . 6-3-17
6.3.14 Fall Logic Statement Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-17
6.3.15 Using Set and Clear Statements to Detect a Change in State . . . . . . . 6-3-26
6.3.16 Using the Rise Operator in a Set Logic Statement . . . . . . . . . . . . . . . . . 6-3-27
6.3.17 Replacing a Linked Value with a Constant . . . . . . . . . . . . . . . . . . . . . . . . 6-3-31
6.3.18 Replacing a Linked Value with Another Linked Value . . . . . . . . . . . . . . . 6-3-31
6.4.1 Sample Logic Statement Using the Count Function . . . . . . . . . . . . . . . . 6-4-4
6.4.2 Behavior of the Count Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4-4
6.4.3 Sample Logic Statement Using the Delay Function . . . . . . . . . . . . . . . . 6-4-6
6.4.4 Behavior of the Delay Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4-6
6.4.5 Sample Logic Statement Using the Duty and Period Functions . . . . . . 6-4-9
6.4.6 Behavior of the Period and Duty Functions . . . . . . . . . . . . . . . . . . . . . . . 6-4-11

CB: iv
6.4.7 Sample Logic Statement Using the Timer Function . . . . . . . . . . . . . . . . 6-4-13

6.4.8 Behavior of the Timer Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4-13
6.4.9 Sample Logic Statement Using the Wait Function . . . . . . . . . . . . . . . . . 6-4-15
6.4.10 Behavior of the Wait Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4-15
6.4.11 Sample Ramp Logic Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4-17
6.4.12 Ramp Function Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4-17
6.4.13 Setting the Clock Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4-19
6.4.14 Setting the Logic Step Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4-21
6.4.15 Setting the ControlBlock Operating Mode . . . . . . . . . . . . . . . . . . . . . . . . 6-4-23
6.4.16 Testing the Operating Mode of the Block Being Configured . . . . . . . . . 6-4-24
6.4.17 Testing the Operating Mode of Another Block . . . . . . . . . . . . . . . . . . . . . 6-4-25
6.4.18 Testing the Controller Processor Mode . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4-27
6.4.19 Setting the Block Mode of the Controller Processor Card . . . . . . . . . . . 6-4-29
6.4.20 Inhibiting Alarms on a ControlBlock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4-31
6.4.21 Inhibiting Alarms and Events on the Controller Processor . . . . . . . . . . 6-4-33
6.4.22 Format of an if?then:else Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4-34
6.4.23 Sample if?then:else Logic Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4-36
6.4.24 Resetting a Stack Totalizer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4-37
6.5.1 Scrolling Message Pair Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5-4

CB: v
List of Tables
Table Page
6.2.1 Discrete Diagram Screen Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2-5
6.2.2 Alarm or Event Message Field Descriptions . . . . . . . . . . . . . . . . . . . . . . 6-2-10
6.3.1 Unlinked Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-19
6.3.2 Mathematical and Logical Operators . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-20
6.3.3 Examples of Continuous Variables in Logic Statements . . . . . . . . . . . . 6-3-24
6.3.4 Examples of Discrete Variables in Logic Statements . . . . . . . . . . . . . . . 6-3-24
6.3.5 Effects of Logic Actions Applied to Q . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3-29
6.4.1 Logic Statement Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4-1
6.4.2 Time Function Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4-18
6.4.3 Control Block Operating Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4-22

CB: 6-1-1
Section 1:
Introduction to Logic Steps
This section presents the screens used to configure ControlBlock logic

and explains how logic steps are evaluated. This section also provides
a glossary of ControlBlock logic terms.
Each ControlBlock has 16 discrete outputs (a through p). Each discrete

output is also called a logic step because it can be used to configure a
step of a logic sequence. Figure 6.1.1 shows the portion of a Discrete
Diagram screen used to configure the ControlBlock logic for step a.
Each logic step a--p has a

separate Discrete Diagram
screen.
CB DISCRETE DIAGRAM
StepÞa
CONDITIONS
a Þ
Set Þ
ClearÞ
ACTIONS
Rise Þ
ON Þ
Fall Þ
OFF Þ
Figure 6.1.1. ControlBlock Logic Step
RS3: Configuring Logic Steps Introduction to Logic Steps

CB: 6-1-2
Screens for Configuring ControlBlock Logic
You use a number of screens to configure a logic step:

D Continuous Links/ Identifies input sources for use in the logic
Discrete Links steps.
For information about configuring the
Continuous Links screen or the Discrete
Links screen, see Chapter 3.
D Discrete Diagram Defines the conditions required to control
the step output or defines the action to be
taken on the continuous portion of the
ControlBlock.
Discrete Diagram screen, see Section 2.
D Discrete Faceplate Allows configuration of a faceplate to
display ControlBlock inputs/outputs.
Discrete Faceplate screen, see Chapter 5.
Figure 6.1.2 shows the ControlBlock screens used to configure logic

steps and briefly describes the purpose of each screen.

CB: 6-1-3
CB CONTINUOUS LINKS
Tag Descriptor
Addr=01A-01 Function
CB DISCRETE LINKS
INPUTTagSOURCE
Descriptor Hold Eng Zero
Eng Addr=1A-1
Max Function
Value Units
PV Þ
LS Þ INPUT SOURCE INPUT SOURCE
RS Þ @a Þ @i Þ
ÞÞ
FF Þ @b @l @j Þ Identifies input sources for
E Þ @c @mÞÞ @k Þ use in the logic steps.
FÞ @d @n ÞÞ @l Þ
G Þ @e @oÞÞ @m Þ
H Þ @f Þ @n Þ
@g Þ @o Þ
@h Þ
CB DISCRETE DIAGRAM
Step Þ d
CONDITIONS
d Þ Defines the conditions required to
Set Þ control the step output or defines the
ClearÞ action to be taken on continuous
ACTIONS
portion of the ControlBlock.
Rise Þ
ON Þ
Fall Þ
OFF Þ
CB DISCRETE FACEPLATE
Tag DescriptorÞ
Addr=1A-1 Function
1Þ 2Þ 3Þ 4Þ 5Þ
6Þ 7Þ 8Þ 9Þ 10Þ Allows configuration of a

faceplate to display
ControlBlock inputs/outputs.
11Þ 12Þ 13Þ 14Þ 15Þ
16Þ 17Þ
Figure 6.1.2. Screens Used to Configure a Logic Step

CB: 6-1-4
Logic Step Evaluation Process
Logic steps are evaluated once each evaluation cycle. You determine
the time for an evaluation cycle when you specify the scan time of the
ControlBlock. Evaluation takes place in this order:
1. The Controller Processor determines all of the input values that
are linked to the ControlBlock. All ControlBlock input values are
updated.
2. Each logic step, a through p, is evaluated separately beginning
with step a. The conditions statements of logic step a are
evaluated to determine whether the step is to be set to on or off.
— The first time the logic step is turned on, the Rise logic
statement is evaluated.
— Each time the logic step is on, the ON logic statement is
evaluated.
— The first time the logic step is turned off, the Fall logic
statement is evaluated.
— Each time the logic step is off, the OFF logic statement is
evaluated.
This same evaluation process continues for each logic step until
all logic steps of a ControlBlock have been evaluated.
3. The main function of the ControlBlock (such as DMC) is
evaluated.
4. Each ControlBlock outputs the continuous value Q and the
discrete values a through p.
The ControlBlock evaluation cycle is repeated at the next scan time

interval.
Order of Logic Steps is Important
Keep the logic step evaluation process in mind when you use logic step
outputs as variables in logic statements. If you use a logic step output
as a variable in another logic step, the value of the output depends on
whether the other logic step precedes or follows it.
For example, a logic statement in step c that uses the output of logic in
step a gets the current calculated value of a. A logic statement in step a
that uses the output of logic in step c gets the value of c that was
calculated during the last evaluation cycle.
For a description of each type of logic statement, see Section 3.

CB: 6-1-5
Input Changes on the Following Cycle
It is important to realize that although you change an input value in a

logic step, the new value is not seen until the following evaluation cycle.
For one cycle, the old value of a variable is still the one used by the
step. In many cases, this delay is not significant. However, in some
cases, even a delay of one cycle is undesirable.
Figure 6.1.3 shows a case in which the delay exists, but is not readily
apparent. Three actions are configured in the On logic statement.
Because all three actions appear on one line, it appears that all three
will take place at the same time. What actually happens is that the
mode changes immediately, but the old input values remain in effect
until the next cycle.
CONDITIONS
A
It appears that inputs A and B
B are updated at the same time that
the mode is changed. Actually,
the old values are in effect until
ACTIONS the next cycle.
Rise Þ
ON Þ setmode 2;A=1;B=0
Fall Þ
OFF Þ A=0; B=1
Figure 6.1.3. Inputs Change One Cycle Later
In this example, if it is necessary to have the mode change and the

input change occur on the same cycle, the solution is to delay the mode
change for one cycle so that the inputs can be updated first.
For more information on configuring On logic statements, see Section 3:

Configuring Logic Statements. For more information on configuring
mode, see Section 4

CB: 6-1-6
Scaling and Logic Step Evaluation
All numbers appearing in logic statements are displayed as actual

unscaled or “absolute” values, whereas the block register values to
which they may relate are displayed in scaled form. This will usually
result in an apparent discrepancy between the two forms of display.
For example, with input A scaled 120.0 to 360.0 gal, the logic statement
“A=.5” results in A being assigned an absolute value of .5. However, this
will be displayed as 240.0 gal.
For more information on display scaling, see Chapter 3, Section 2.

CB: 6-2-1
Section 2:
Configuring a Discrete Diagram Screen
This section describes the Discrete Diagram screen and the fields that
are used to configure logic steps. The shaded box in Figure 6.2.1 shows
the Discrete Diagram screen among the ControlBlock configuration
screens for a ControlBlock.

FACEPLATE FACEPLATE
CB CONTINUOUS [ EXCH ]
LINKS
CB CONTINUOUS [ PAGE ] CB DISCRETE LINKS

A to G
LINKS
[ EXCH ]
H to O
[ PAGE ] [ PAGE ]
A a
BLOCK
REFERENCES
[PAGE ] = [PAGE AHEAD] and [PAGE BACK] keys
Figure 6.2.1. Discrete Diagram Screen Among ControlBlock Screens
RS3: Configuring Logic Steps Configuring a Discrete Diagram Screen

CB: 6-2-2
Calling Up a Discrete Diagram Screen

- To call up a Discrete Diagram screen:
D Press [BLOCK DIAGRAM], type the tag or address of the
ControlBlock, and press / x [ENTER], where x is the letter of the
logic step a--p.
or
D From another screen in the same ControlBlock, press
[BLOCK DIAGRAM] / x [ENTER], where x is the letter of the
logic step a--p.
or
D From a ControlBlock Continuous Diagram screen,
press [EXCH].
Figure 6.2.2 shows the Block Diagram screens for the logic steps. Use
the [PAGE AHEAD] and [PAGE BACK] keys to access the screens for
the discrete outputs a through p of a ControlBlock.

CB: 6-2-3
CB DISCRETE
DIAGRAM
CB DISCRETE CB DISCRETE
DIAGRAM DIAGRAM
CB DISCRETE Output a CB DISCRETE

DIAGRAM
Output p DIAGRAM
Output b
DIAGRAM
Output o DIAGRAM
Output c
Output n
DIAGRAM Output d
DIAGRAM
OutputDIAGRAM
m Output e
DIAGRAM
CB DISCRETE
DIAGRAM CB DISCRETE
Output l DIAGRAM
Output f
Output k
DIAGRAM DIAGRAM
Output g
CB DISCRETE
DIAGRAM
Output j Output h
[PAGE BACK] Output i [PAGE AHEAD]
Figure 6.2.2. Flowchart of Discrete Diagram Screens

CB: 6-2-4
Discrete Diagram Screen Fields
To configure ControlBlock logic steps, use the Discrete Diagram

screens. A Discrete Diagram exists for each ControlBlock discrete
output, a through p. Figure 6.2.3 shows the Discrete Diagram screen for
the output of step a. The shaded areas show some of the key
configuration areas of the screen. Table 6.2.1 describes the fields on the
screen.
Displays tags of the linked inputs used in the

logic statements. Also shows message pairs The logic step
or values. Configure the linked inputs on the (discrete output)
The logic state—on/off
Discrete Links and Continuous Links screens.
Logic step mode
Displays linked inputs used in
logic statements—@c, @e, @b

1Tag Agitator 155 Descriptor
+-------------------CONDITIONS--------------------+Step>a
>Level 1 |@c * |
Off OFF | * a= > |Mode>Aut
o | * |
>Level 2/c |@e * Set >@c & @e |MsgP>*14
Off OFF | * |Off
| *Clear>@b |
>Tank 4 |@b * |-> agitat
on off |---*----------------ACTIONS----------------------|
| * |
>Tank 25 |B * Rise> |
.65 gal | * |
| * ON >B=.65 |Rpt>None
| * |
| * Fall> |
| * |
| * OFF >B=0 |
+-------------------------------------------------+
Message pair description

describing the state of the ControlBlock
logic step—on or off mode
Figure 6.2.3. Discrete Diagram Screen

CB: 6-2-5
Table 6.2.1. Discrete Diagram Screen Fields
Access
Level
Area for configuring condition logic statements to control

the state of the step output.
Rise Equation evaluated on the cycle when the step
value changes from OFF to ON.
ON Equation evaluated on each cycle when the step is
ON. Logic statements
ACTIONS Conf
Fall Equation evaluated on the cycle when the step as required
value changes from ON to OFF.
OFF Equation evaluated on each cycle when the step is
OFF.
For more information about configuring condition logic
statements, see Section 3.
Local, Manual,
Block Mode Oper Current ControlBlock mode.
Auto
Area for configuring action logic statements to perform

various functions, such as acting on the continuous
portion of the ControlBlock. These functions depend on
the state of the step.
x= Expression whose value determines the value of
step x. Logic statements
CONDITIONS Conf
set Expression whose value determines whether step as required
x is set.
clear Expression whose value determines whether step
x is cleared.
For more information about configuring action logic
statements, see Section 3.
Descriptor NA User-defined block descriptor. Display only
Amount of space remaining in the ControlBlock before it

Free Space: reaches its maximum size.
Stat NA “Stat” indicates the amount of space available for static Display only
information that is entered by the user. “Dyn” indicates
Dyn the amount of space available for dynamic information
that is generated by the control system.

CB: 6-2-6
Table 6.2.1. Discrete Diagram Screen Fields (continued)
Access
Level
Current logic step mode. The step mode is independent

of the block mode.
“Auto” indicates that the logic steps are evaluated when
Mode Conf Auto, Man
the ControlBlock is evaluated. The user cannot change
the step output in Auto mode.
“Man” indicates that the user can change the step output.
Message pair assigned to describe the discrete output User message

state. You can configure message pair descriptions on pair: 1--155
MsgP Conf
the STD Message Pairs screen or the User Message Standard message
Pairs screen. pair: *1--*100
Indicates a user-defined group to which the ControlBlock

is assigned. Write authority and alarm annunciation for
ControlBlocks with a plant unit other than zero are
restricted to consoles that specify the same number on
their Plant Unit Configuration screen.
Plnt Conf 0-255
Your console must first own the plant unit on the Plant
Unit Configuration screen, or you will not be able to make
an entry in this field.
For more information on the Plant Unit Configuration
screen, see CC: 1.
Assigns an alarm priority to critical and advisory process

alarms. 0 indicates highest priority, 15 indicates lowest
Priority Conf priority. 0-15
Chapter 4, Section 1.
Allows selection of the type of event or alarm to be

generated on the on, off, rise, fall, or change of a logic
step. Fields appear for entering the type of logic step
change that is to generate the report and the name of the None, Evt, Adv,
Rpt Conf variable to be logged. Crit, Hard, Batch
For information about configuring the “Report” field, see
“Configuring a Logic Step to Generate an Alarm or Event
Message” in this section.
Step NA Logic step. a--p
Displays any steps that are currently in manual mode.

Steps in
NA The Conditions portion of a step in Manual mode is not Display only
Manual
evaluated when the ControlBlock is evaluated.

CB: 6-2-7
Configuring a Logic Step to Generate an Alarm or

Event Message
You can configure an alarm or event to be generated by changes in the

logic step output. Figure 6.2.4 shows the area on the Discrete Diagram
screen where the alarm or event can be configured. Additional fields
appear, depending on which option you select in the “Rpt” field.
NOTE: For restrictions on using the “Rpt” field with preconfigured steps
for discrete motor controllers and valve controllers, see Table 6.2.2.
For information about configuring alarm and event list screens, see
CC:6.

Tag Agitator 155 Descriptor
>Level 1 |@c * |
Off OFF | * a= > |Mode>Auto
| * |
Off OFF | * |Off
| *Clear>@b |
on off |---*----------------ACTIONS----------------------|
| * |
.65 gal | * |
| * |
| * Fall> |
| * |
| * OFF >B=0 |
+-------------------------------------------------+
FULL CONFIG 1
Figure 6.2.4. Configuring a Logic Step to Generate an Alarm or Event Message

CB: 6-2-8
- To configure a logic step to generate an alarm or event

message:
1. Cursor to the “Report” field and press [NEXT OPTION] until the
appropriate type of message appears. Press [ENTER]. The
“When” and “Log” fields appear. If you selected “Evt” as the type,
the “Event Type” field also appears.
2. Cursor to the “When” field and press [NEXT OPTION] until the
appropriate logic step action appears.
CAUTION
If you configure an event using “On” or “Off”, an event is
generated with every Controller Processor scan cycle. If
you want an event to be generated only once, configure the
event using “Rise”, “Fall”, or “Chng”.
Be aware that preconfigured discrete ControlBlocks for motor and
valve controllers do not generate an alarm or an event on rise,
fall, or change conditions.
3. Cursor to the “Log” and “Event Type” fields, and type in the
desired information. (For more information on the fields, see
Table 6.2.2.)
4. If you want to initiate a printout using event types 241-255, the
event type must be assigned to an event list (1-10) on the Event
Configuration screen. Any values to be logged (“Log” field) are
then sent to the event list to which the printout event has been
assigned. (For more information on the Event List Configuration
screen, see CC:6.)

CB: 6-2-9
Figure 6.2.5 shows a sample Discrete Diagram screen configured to

print out the Disk Event List when the logic step a output is on. The
value and units of continuous input B will be logged on the event list
configured for the event type (244) on the Event List Configuration
screen. Note that the printout only includes disk events generated since
the last printout.
Table 6.2.2 describes the alarm or event message fields.

>Level 1 |@c * |
| * |
Off OFF | * |Off
| *Clear>@b |
on off |---*----------------ACTIONS----------------------|
| * |Event
>Tank 25 |B * Rise> |Type>244
.65 gal | * |
| * ON >B=.65 |Rpt>Evt
| * |
| * Fall> |When>Rise
| * |
| * OFF >B=0 |Log >B
+-------------------------------------------------+
FULL CONFIG 1
Figure 6.2.5. Configuring a Logic Step to Generate an Event Message

CB: 6-2-10
Table 6.2.2. Alarm or Event Message Field Descriptions
Access
Level
Allows you to specify a number for the event, which can

then be entered on the Event List Configuration screen.
Field appears only when “Evt” is configured in the “Report”
field.
1--240 = Events defined by the user in these 4 fields.
You can enter these events on only one list on the Event
List Configuration screen. 1--255
241 = Initiates printout of hardware alarm lists. (241--254 are
Event Type Conf
special event
242 = Initiates printout of process alarm lists. types)
243 = Initiates printout of the system status list.
244 = Initiates printout of the disk event list.
245--254 = Initiates printout of the specified event list
(1--10).
255 = Initiates printout of the Operator Change Log.
Specifies the ControlBlock variable for which the value is to A--O, a--p,
Log Conf
be displayed with the event message. @a--@o
* Not for use with preconfigured steps for discrete motor controllers and valve controllers. If this is a
problem, use the following workaround to configure a report trigger on the rise, fall, or change of a
preconfigured step.
WORKAROUND:
Select a user-configurable step and configure x = y (where x is a user-configurable step and y is a
preconfigured step) and then configure the “Rpt” field of x as needed.

CB: 6-2-11
Table 6.2.2. Alarm or Event Message Field Descriptions (continued)
Access
Level
Selects the type of alarm or event message to be

generated if the “When” condition occurs.
NOTE: This field should be configured first.
“None” = no message is generated.
“Evt” = an event message is generated.* None, Evt, Adv,
Report Conf
Crit, Hard, Batch
“Adv” = an advisory process alarm is generated.
“Crit” = a critical process alarm is generated.
“Hard” = a hardware alarm is generated.
“Batch” = a batch alarm is generated.
Specifies the logic step action that generates the alarm or

event message.
“Rise” = a message is generated when the logic step
changes from off to on.*
“On” = For alarms: a message is generated when the
logic step is on.
For events: a message is generated every
evaluation cycle the logic step is on. Rise, On, Fall, Off,
When Conf
“Fall” = a message is generated when the logic step Chng
changes from on to off.*
“Off” = For alarms: a message is generated when the
logic step is off.
For events: a message is generated every
evaluation cycle the logic step is off.
“Chng” = a message is generated when the logic step
changes.*
* Not for use with preconfigured steps for discrete motor controllers and valve controllers. If this is a
problem, use the following workaround to configure a report trigger on the rise, fall, or change of a
preconfigured step.
WORKAROUND:
Select a user-configurable step and configure x = y (where x is a user-configurable step and y is a
preconfigured step) and then configure the “Rpt” field of x as needed.

CB: 6-2-12

CB: 6-3-1
Section 3:
Configuring Logic Statements
This section describes how to configure condition logic statements and

action logic statements. This section also explains how to write logic
statements.
Conditions Logic Statements
Conditions logic statements control the state of the step output using
one or more of the following statements:
D Emulation statement
D Set statement
D Clear statement
Condition logic statements are executed unconditionally on each block

evaluation.
Actions Logic Statements
Actions logic statements act on the continuous inputs and output of the
ControlBlock using one or more of the following statements:
D Rise statement
D On statement
D Fall statement
D Off statement
Action logic statements are only executed for certain states of the step
output.
RS3: Configuring Logic Steps Configuring Logic Statements

CB: 6-3-2
Configuring Conditions Statements
You can configure ControlBlock logic statements to control the state of

the step output. These types of logic statements are called condition
statements. Condition statements are configured in the Conditions
portion of the Discrete Diagram screen for the logic step, shown in the
shaded box in Figure 6.3.1.
One or more condition logic statements can be configured for a discrete

output. During a ControlBlock evaluation, the Emulation statement is
evaluated first, followed by the Set statement, and then the Clear
statement.

CB: 6-3-3
Emulation statement—
If the emulation statement is true, the step output is turned on.
If this statement is false, the step output is turned off.
Set statement—
If the Set statement is true, the step output is
turned on. The Set statement cannot turn the step
output off.
>Level 1 |@c * |
| * |
Off OFF | * |Off
| *Clear>@b |
>Tank 4 |@b * |-> ON
On ON |---*----------------ACTIONS----------------------|
| * |
.65 gal | * |
| * |
| * Fall> |
| * |
| * OFF >B=0 |
+-------------------------------------------------+
FULL CONFIG 1
Clear statement—
If the Clear statement is true, the step output is turned off.
The Clear statement cannot turn the step output on.
Figure 6.3.1. Discrete Diagram—Area for Configuring Condition Logic Statements

CB: 6-3-4
Configuring an Emulation Logic Statement
An Emulation logic statement causes the logic step output to emulate, or

copy, the true/false condition of the statement. Thus, when the
Emulation statement is true, the step output is true or on. When the
Emulation statement is false, the step output is false or off.
Example
Figure 6.3.2 shows a sample Emulation condition statement for logic

step a. Whenever both inputs @c and @e are on, logic step a is on. If
one or both of these inputs is off, logic step a is off. Figure 6.3.3 shows
the behavior of the emulating conditions statement in Figure 6.3.2.
Emulation logic statement is true. Step output state turns on.

>Level 1 |@c * |
On ON | * a= >@c & @e |Mode>Auto
| * |
>Level 2/c |@e * Set > |MsgP>*1
On ON | * |Off
| *Clear> |
| * |-> ON
|---*----------------ACTIONS----------------------|
| * |
| * Rise> |
| * |
| * ON > |Rpt>None
| * |
| * Fall> |
| * |
| * OFF > |
+-------------------------------------------------+
FULL CONFIG 1
Figure 6.3.2. Simple Emulation Logic Statement

CB: 6-3-5
True
(@c & @e) False
On
Step a output
Off
Figure 6.3.3. Emulation Logic Statement Behavior

CB: 6-3-6
Configuring a Set/Clear Logic Statement
You can configure Set and Clear logic statements to configure the step
output.
D If the Set statement is true, the step output is turned on. The Set
statement cannot turn the step output off.
D If the Clear statement is true, the step output is turned off. The
Clear statement cannot turn the step output on.
You can configure both a Set and a Clear statement, so that the step
can be turned on and turned off.
Because the ControlBlock is evaluated from top to bottom, Set and

Clear statements are evaluated after the emulation statement, so Set
and Clear statements override the emulation statement. Also, Clear
statements are evaluated after Set statements, so Clear statements
override Set statements. If both the Set and Clear statements are true
during an evaluation, the step output is off since the Clear statement is
performed last.
Example
Figure 6.3.4 shows sample set and clear logic statements that set the
output of step a to on and off, depending on the state of the linked
variables @c, @e, and @b. Logic step a is on when both @c & @e are
true and @b is false. Logic step a is off if @b is true, regardless of the
state of @c and @e. Figure 6.3.5 shows the effect of the Set and Clear
statements on the step output.

CB: 6-3-7
Clear statement is true. Step output turns off.

>Level 1 |@c * |
| * |
Off OFF | * |Off
| *Clear>@b |
>Tank 4 |@b * |-> OFF
On ON |---*----------------ACTIONS----------------------|
| * |
| * Rise> |
| * |
| * ON > |Rpt>None
| * |
| * Fall> |
| * |
| * OFF > |
+-------------------------------------------------+
FULL CONFIG 1
Figure 6.3.4. Sample Set/Clear Logic Statements
True
(@c & @e) False
True
@b False
On
Step a output Off
Figure 6.3.5. Set/Clear Logic Statement Behavior

CB: 6-3-8
Configuring Action Statements
You can configure ControlBlock action logic statements that act on the
continuous inputs and output of the ControlBlock as well as its mode.
You configure action statements in the Actions portion of the Discrete
Diagram screen, as shown in the shaded box in Figure 6.3.6.
Types of Action Statements

Rise = Action is executed when the logic step goes from off to on.
On = Action is executed each evaluation cycle that the logic
step is on.
Fall = Action is executed when the logic step goes from on to off.
Off = Action is executed each evaluation cycle that the logic
step is off.
You can configure any or all action statements for a logic step.

CB: 6-3-9

>Level 1 |@c * |
| * |
Off OFF | * |Off
| *Clear>@b |
>Tank 4 |@b * |-> ON
On ON |---*----------------ACTIONS----------------------|
| * |
.65 gal | * |
| * |
| * Fall> |
| * |
| * OFF >B=0 |
+-------------------------------------------------+
FULL CONFIG 1
Figure 6.3.6. Discrete Diagram—Area for Configuring Action Logic Statements

CB: 6-3-10
Configuring an On Logic Statement
The On logic statement expression is executed whenever the logic step

output is true.
The On logic function is repeated each time the block is evaluated.
Examples of Situations for Use
Configure an On logic statement:

D To set a variable equal to a predetermined constant value when
the step output is on.
D Whenever the operator is not required to change the value of the
variable when the step output is on. (If the operator needs to be
able to manipulate the variable during this time, configure a Rise
statement rather than an On statement.)
Example
Figure 6.3.7 shows a sample On logic statement that is configured to set

analog input B to a value different from the current B input value and to
lock input B at that value while logic step a is on. Inputs @c, @e, @b,
and B are linked to logic step a. This sample logic statement is
configured to set the analog input B (local setpoint) to 65% of its range
when the output of Step a is on. Step a is set on when both @c and @e
are true. While the output of Step a remains on, the local setpoint is
locked at the value 65% and cannot be changed from the console
keyboard.
If @b becomes true, the output of Step a turns off and the local setpoint
remains at 65%, but may be changed using the keyboard. Figure 6.3.8
shows the behavior of an On statement.

CB: 6-3-11

>Level 1 |@c * |
| * |
Off OFF | * |Off
| *Clear>@b |
>Tank 4 |@b * |-> ON
On ON |---*----------------ACTIONS----------------------|
| * |
>*ENTRY |B * Rise> |
.65 gal | * |
| * |
| * Fall> |
| * |
| * OFF > |
+---------------------------------------------------+
FULL CONFIG 1
Step a turned on. Local setpoint set to 65%.
Figure 6.3.7. Setting and Locking a Setpoint Using an On Statement
True
(@c & @e) False
True
@b False
On
Step a Output
Off
True
On Output Action False
Figure 6.3.8. On Logic Statement Behavior

CB: 6-3-12
Configuring an Off Logic Statement
The Off logic statement expression is executed whenever the logic step
output is off.
The Off function is repeated each time the block is evaluated.
Configure an Off logic statement:

D To set a variable at a particular value when the step is off.
D Whenever the operator is not required to change the value of the
variable when the step is off. (If the operator needs to be able to
manipulate the variable during this time, configure a Fall
statement rather than an Off statement.)
Example
Figure 6.3.9 shows a sample Off logic statement that is configured to set
analog input B to a value different from the current B input value and
lock input B at that value, while logic step a is off. Inputs @c, @e, @b,
and B are linked to logic step a. This sample logic statement is to set the
analog input B to 65% of its range when the output of Step a is off. Step
a is off when @b is true. While Step a remains off, the local setpoint is
locked at the value 65% and cannot be changed from the console
keyboard.
If @b becomes false and @a and @e become true, the output of Step a

turns on and the local setpoint remains at 65%, but it may be changed
by using the keyboard. Figure 6.3.10 shows the behavior of an Off
statement.

CB: 6-3-13

>Level 1 |@c * |
Off OFF | * a= > | Mode>Auto
| * |
>Level 2/c | @e * Set >@c & @e | MsgP>*1
Off OFF | * | Off
| *Clear>@b |
>Tank 4 | @b * | -> OFF
On ON |---*----------------ACTIONS----------------------|
| * |
>*ENTRY | B * Rise> |
.65 gal | * |
| * ON > | Rpt>None
| * |
| * Fall> |
| * |
| * OFF >B=.65 |
+-------------------------------------------------+
FULL CONFIG 1
Step a turned off. Local setpoint set to 65%.
Figure 6.3.9. Setting and Locking a Setpoint Using an Off Statement
True
@b False
True
(@c & @e)
False
On
Step Output Off
True
Off Output Action False
Figure 6.3.10. Off Logic Statement Behavior

CB: 6-3-14
Configuring a Rise Logic Statement
The Rise expression is executed whenever the logic step output

changes from false to true.
The Rise function is only activated during the evaluation cycle that the
logic step output changes from off to on.
Configure a Rise logic statement:

D To initialize a variable to a value when a step turns on, but then to
allow the operator to modify the variable. (To set a variable at a
particular value when the step is on and to prevent operator
adjustments, configure an On action statement rather than a Rise
statement.)
Example
Figure 6.3.11 shows a sample Rise logic statement that is configured to

change the value of analog input B to a value different from the current
value, and to allow changes to that value while logic step a is on. Inputs
@c, @e, @b, and B are linked to Step a. This logic statement sets the
analog input B value to 65% when the output of Step a turns on, and it
allows changes even though the output of Step a remains on. Step a is
on when both @c and @e are true and @b is off. Figure 6.3.12 shows
the behavior of a Rise statement.

CB: 6-3-15

+-------------------CONDITIONS-------------------+Step>a
>Level 1 |@c * |
On ON | * a= > | Mode>Auto
| * |
>Level 2/c | @e * Set >@c & @e | MsgP>*1
On ON | * | Off
| *Clear>@b |
>Tank 4 | @b * | -> ON
Off OFF |---*----------------ACTIONS----------------------|
| * |
>*ENTRY | B * Rise>B=.65 |
.65 gal | * |
| * ON > | Rpt>None
| * |
| * Fall> |
| * |
| * OFF > |
+-------------------------------------------------+
FULL CONFIG 1
Step output changed to on. May manually alter setpoint.
Figure 6.3.11. Adjusting a Setpoint Using a Rise Statement
True
(@c & @e)
False
True
@b
False
On
Step Output Off
True
Rise Output Action False
Figure 6.3.12. Rise Logic Statement Behavior

CB: 6-3-16
Configuring a Fall Logic Statement
The Fall expression is executed whenever the logic statement changes

from true to false.
The Fall function is only activated during the evaluation cycle that the
logic step output changes from on to off.
Example of Situations for Use
Configure a Fall logic statement:

D To initialize a variable to a value when a step turns off, but then to
allow the operator to modify the variable. (To set a variable at a
particular value when the step is off and to prevent operator
adjustments, configure an Off action statement rather than a Fall
statement.)
Example
Figure 6.3.13 shows a sample Fall logic statement that is configured to

change the value of analog input B to a value different from the current
value, and to allow changes to that value, while logic Step a is off.
Inputs @c, @e, @b, and B are linked to Step a. This logic statement
sets the analog input B value to 65% when the output of Step a turns off
and allows changes even though the output of Step a remains off. Step
a is off when @b is true.
If the value of B needs to be changed to a value other than 65% (for

example 57%) when Step a turns off, you must configure an additional
action statement. Figure 6.3.14 shows the behavior of a Fall statement.

CB: 6-3-17

>Level 1 |@c * |
| * |
Off OFF | * |Off
| *Clear>@b |
>Tank 4 |@b * |-> OFF
On ON |---*----------------ACTIONS----------------------|
| * |
.65 gal | * |
| * ON > |Rpt>None
| * |
| * Fall>B=.65 |
| * |
| * OFF > |
+-------------------------------------------------+
FULL CONFIG 1
Step output changed to off. May manually alter local setpoint.
Figure 6.3.13. Adjusting a Setpoint Using a Fall Statement
True
@b False
True
(@c & @e)
False
On
Step Output Off
True
Fall Output Action False
Figure 6.3.14. Fall Logic Statement Behavior

CB: 6-3-18
How to Write Logic Statements
A logic statement is composed of one or more variables, values, and

operators that perform a calculation. This section explains the variables
and operators used in logic statements and provides notes for
configuring logic statements. Section 4 discusses the logic functions
available to perform specific logic operations.
Logic Statement Examples
Logic statements are written in the Conditions or Actions portion of a

logic step. The following are several logic statement examples:
D delay(30,H,@c)
D ramp(.5,C,.00005)
D setmode 2
D B=@c?.67:.75
Variables
You must list all variables used in the logic statements of a ControlBlock
on the Continuous Links or Discrete Links screens for that ControlBlock.
Continuous Variables
Continuous variables consist of the continuous inputs A through O and

the continuous output Q.
Continuous variables are typically used in logic statements to compare

the variable or expression as less than, equal to, or greater than a
predetermined target. The target may be a constant value, another
variable, or another expression. The comparison gives a true or false
value as a result. Numerical constants are written as a decimal fraction
of the span of the variable and are called internal scaling values.

CB: 6-3-19
Discrete Variables
Discrete variables include discrete inputs @a through @o and discrete

outputs a through p.
Discrete inputs can have discrete values linked from other blocks.
Discrete variables have a value of 0.0 if false, and a value of 1.0 if true.
Unlinked discrete inputs entered from the keyboard can be assigned the
block functions described in Table 6.3.1.
Table 6.3.1. Unlinked Inputs
Function Description
*Off Always off, logical constant. State cannot be changed from the discrete faceplate.
*On Always on, logical constant. State cannot be changed from the discrete faceplate.
*M Off Normally on, momentarily off when entered. Off for one evaluation cycle, then on.
*M On Normally off, momentarily on when entered. On for one evaluation cycle, then off.
*Toggle Maintains previous state, changes when entered.
*Select Maintained when one is turned On by entry, all other *Selects in the block turn off.

CB: 6-3-20
Mathematical and Logical Operators
Mathematical and logical operators are used in logic statements to

perform calculations. Table 6.3.2 lists and describes the operators for
use in logic expressions.
NOTE: Mathematical and logical operators consider a value less than

or equal to 0.0 as false and a value greater than 0.0 as true.
Table 6.3.2. Mathematical and Logical Operators
Operator Description Format Explanation
relational equality—is one variable or If x is equal to y,

== x==y
expression equal to another? the expression is true
assignment—sets one expression

= equal to the value of another x=y x equals y
expression
order evaluation—operations within

() (x+y) *z (2+10)*4 is 48
parentheses are performed first
If x is true, v equals y
x?y:z if-else selection v=x?y:z
If x is false, v equals z
rounding function—variable or
round 2.2 is 2
round expression is rounded to nearest round x
round 2.6 is 3
integer
integer function—truncates a number int 4.73 is 4

int int x
to an integer int --4.2 is --5
fraction function—returns the fractional

fract fract x fract 3.2 is .2
part of a number
abs 5 is 5
abs absolute value function abs x
abs --5 is 5
signum (sign) function

sign sign x sign --4 is --1
Returns +1, 0, or --1
square root function—returns the sqrt 16 is 4

sqrt sqrt x
square root of a number sqrt .0001 is .01
square root limited gain function—

sqrl 16=4
sqrl returns the square root of x if x>.01 of sqrl x
sqrl .0001=.001
scale; otherwise returns 10*x
sin sine trigonometric function (radians) sin x sin 1 is .841471
asin inverse sine trigonometric function asin x asin 1 is 1.57080
NOTE: x, y, and z may be single discrete variables (@a--@o, a--p), single continuous variables (A--O, Q), or
expressions.

CB: 6-3-21
Table 6.3.2. Mathematical and Logical Operators (continued)
cos cosine trigonometric function (radians) cos x cos 0 is 1.000
acos inverse cosine trigonometric function acos x acos .5 is 1.04720
tan tangent trigonometric function (radians) tan x tan .90 is 1.26016
atan inverse tangent trigonometric function atan x atan .5 is .463648
log2 base 2 log function log2 x log2 600 is 9.23
exp2 exponent of 2 function exp2 x exp2 6 is 26 is 64
exp10 exponent of 10 function exp10 x exp10 3 is 103 is 1000
log base 10 log function log x log 52,400 is 4.72
ln base e log function (natural log) ln x ln 15 is 2.71
exponent of e function (natural

exp exp x exp 1 is 2.72
exponent)
** exponentiation x**y 2**3 is 23 is 8
* multiply x*y 4*3 is 12
/ divide x/y 12/4 is 3
% divide modulo (remainder) x%y 5%2 is 1
max maximum value function x max y 10 max 1 is 10
min minimum value function x min y 10 min 1 is 1
+ add x+y 7+2 is 9
-- subtract x--y 9--7 is 2
~= relational inequality ~=x 3~=6 is true
>= relational greater than or equal to x>=y 8>=6 is true
> relational greater x>y 12>4 is true
<= relational less than or equal to x<=y 2<=2 is true
< relational less than x<y 5<8 is true
~ unary logical negation ~ x is negated
conditional and—true if both returns true (1) if x and y are >0; else,
& x&y
expressions are true; false otherwise returns false (0)
expressions.

CB: 6-3-22
Table 6.3.2. Mathematical and Logical Operators (continued)
conditional inclusive or—true if either

one expression or another is true, or returns true (1) if x>0 or y>0, or both;
| x|y
both expressions are true; false else, returns false (0)
otherwise
conditional exclusive or—true if either

returns true (1) if x>0 or y>0, but not
one expression or another is true; false xy
both; else, returns false (0)
otherwise
returns true for only one evaluation

The condition is true if the variable
rise risex cycle after x changes, even though x
following just became true.
itself may remain true
returns true for only one evaluation

The condition is true if the variable
fall fallx cycle after x changes, even though x
following just became false.
itself may remain false
expressions.

CB: 6-3-23
Logic Statement Order of Precedence
Following is the order of precedence in which logic statement

components are evaluated:
1. Parentheses
2. Single arithmetic components (abs, round, int)
3. Root and trigonometric functions (sqrt, sqrl, sin, cos, atan)
4. Binary arithmetic (**, *, /, %, max, min, +, --)
5. Logic (rise—the variable following just became true; fall—the
variable following just became false, ~, &, |, )
6. Relational (==, ~=, >=, >, <=, <)
7. if?then:else
8. Assignment (=)
Example
D @a l(@b&@c) = If @a is true or @b and @c are true, then the
expression is true.
D (@a l@b)&@c = If @a or @b is true and @c is true, then the
statement is true.
Using Variables and Operators in Combined Expressions
You can combine expressions in an action logic statement so that

several actions are imposed simultaneously by the logic step.
When writing an actions statement containing several expressions,

separate the expressions by a semicolon. Any number of expressions
can be combined into a single action statement. The only limitation is
that the total number of characters, including semicolons, cannot
exceed 36.
Example
A logic step can change its PI Controller to Auto and set its remote
setpoint at 65% with one action statement:
RiseÞ C=.65;setmode 2

CB: 6-3-24
Logic Statement Examples
Table 6.3.3 provides examples of logic statements using continuous

variables with relational operators. Table 6.3.4 provides examples of
logic statements using discrete variables with logic (or Boolean)
operators.
Table 6.3.3. Examples of Continuous Variables in Logic Statements
Sample
Condition is true if:
Expression
Continuous input A is less than 60% of span A<.6
Continuous input C is greater than 75% of span C>.75
Continuous input H is equal to 46% of span H==.46
Continuous input B is less than or equal to 60% of span B<=.6
Continuous input G is greater than or equal to 27% of span G>=.27
Continuous input B is greater than or equal to analog input B>=D

D See note
B--A>0
Controller error signal is positive
See note
NOTE: Each variable is treated as a percentage of its span, regardless of the

display scaling assigned. For further explanation of how analog values are treated in
block computations, see Chapter 2 of this manual.
Table 6.3.4. Examples of Discrete Variables in Logic Statements
Sample
Condition is true if:
Expression
Discrete input a is true @a
Discrete inputs a and c are both true @a&@c
Either discrete input d or g is true @d l@g
Discrete inputs, a, b, and c, and step b (of this block) are all
@a&@b&@c&b
on
One or more of the discrete inputs, f, g, or h, are true @f l@g l@h
Any one, but only one, of the discrete inputs, f, or g, is true @f@g
Discrete input a is false ~@a
Discrete input b is true and step d (of this block) is off @b&~d

CB: 6-3-25
Comments in Logic Statements
You can write comments in the Actions portion of a logic statement to

leave notes for yourself or others who may have to use or troubleshoot
your configuration. Comments are written inside delimiters. The
delimiters prevent the material inside from being evaluated as part of a
logic statement. Three types of delimiters can be used:
D Double quotation marks (“ ”)
D Single quotation marks (‘ ’)
D The expression “rem” to start the comment, with a semicolon (;)
to end the comment. If a comment started with “rem” is the last
thing on the line, the semicolon is not needed to end the
comment.
A comment can appear on the same line as a logic statement or on a

line by itself. The comment, or the comment plus logic statement, can
be only 39 characters long (the length of the line), including delimiters.
Examples
B=.65; “setpoint”
‘Drain vessel’
rem Input to Tank 37;B=.65
B=.65;rem Input to Tank 37
If you need quotation marks to clarify the text of your comment, you can
nest single quotation marks inside double quotation marks, or vice
versa.

CB: 6-3-26
Applications for Logic Statements
This section provides the following sample applications of logic

statements:
D Detecting a change in the state of a variable
D Overriding a block action
Using a Set/Clear Statement to Detect a Change in State
You can combine Set and Clear statements with rise or fall logical
operators to identify a change in the state of a variable. A statement
using rise as the operator is true for only one evaluation cycle after the
condition changes from false to true, even if the condition remains true.
A statement using fall as the operator is true for only one evaluation
cycle after the condition changes from true to false. Figure 6.3.15 shows
a sample statement that combines rise with Set and Clear statements to
turn on the step output only once, when @a changes during an
evaluation cycle.
Figure 6.3.16 shows that the sample expression rise@a is true for one
evaluation cycle after @a changes from false to true even though @a
remains true. When @b is true, the step output is cleared, or turned off.

>Level 1 |@a * |
| * |
>Level 2/c |@b * Set >rise @a |MsgP>*1
Off OFF | * |Off
| *Clear>@b |
| * |-> OFF
|---*----------------ACTIONS----------------------|
| * |
| * Rise> |
| * |
| * ON > |Rpt>None
| * |
| * Fall> |
| * |
| * OFF > |
+-------------------------------------------------+
FULL CONFIG 1
Figure 6.3.15. Using Set and Clear Statements to Detect a Change in State

CB: 6-3-27
Set Þ @a True
Clear Þ @b
@a False
True
Turns on the step output
as often as necessary @b False
On
Step output Off
Set Þ rise@a True

Clear Þ @b
@a False
True
Turns on the step
output only once each rise @a False
evaluation cycle
True
@b False
On
Step output Off
Figure 6.3.16. Using the Rise Operator in a Set Logic Statement

CB: 6-3-28
Using an Action Statement to Override a Block Action
In some cases the action imposed by the logic step is in direct conflict
with the normal behavior of the continuous ControlBlock function. This
occurs when the logic action affects the output, Q, or when a linked
input is replaced by an alternate value. In most of these cases, the logic
action takes priority.
Block Actions Affecting the Output, Q
The action statement Q=0.0, when imposed on a P+I controller with the
block in either the Auto or Remote mode, probably conflicts with the
value of Q that is calculated by the controller algorithm. In most cases,
the logic action overrides the block function. A logic action affecting Q
also overrides manual operation if the block is in Manual or Computer
mode. If the block is in Local mode, the logic action does not take
control of the output, Q.
When the logic action affecting Q is turned off, the output, Q, responds
as if the block had just been changed from Manual mode to Auto mode.
In the case of a controller, integral action begins to act in order to
reduce the error to zero. Table 6.3.5 lists all continuous functions and
how they are affected by a Q=X action statement when the block is in
Auto or Remote mode. For a detailed description of each function, see
Chapter 2. Logic actions do not affect Q when the block is in Local
mode.

CB: 6-3-29
Table 6.3.5. Effects of Logic Actions Applied to Q
Block Function
Q=X Action Statement
in Auto or Remote
While Imposed When Relaxed
Equations include an integrating

Integral term begins normal
term. When the output is
PI, PID, I, or ID Controller calculations and the output adjusts
constrained for any reason, the
to reduce any existing error to zero.
integrating term is back-calculated to
The output changes as permitted by
make the calculated output agree
the controller tuning.
with the imposed output value.
New output, Q, is calculated using

the current value of Q as a starting
Lead/Lag Function resumes normal operation
point. Each time the block is
by adding an increment to or
Setpoint Totalizer evaluated, the function computes an
subtracting an increment from the
Stack Totalizer increment that it attempts to add to
current value of Q.
or subtract from the imposed Q, but
it is blocked from doing so.
P, PD, or D Controller
Dead Time
Polynomial Calculated block value is replaced Output immediately changes to the
by the value imposed by the action value calculated by the block
Piecewise Linear Interpolator statement. function.
Signal Selector
Ratio/Bias
Manual Output assumes the imposed value. Output remains the same.

CB: 6-3-30
Block Actions Affecting the Linked Input
You can configure a logic action statement to override a linked input

value. An action logic statement can provide the value that is to override
the linked value. This new value is considered an imposed value. The
imposed value can be a constant, another continuous variable, or a
mathematical expression. When such a logic action is imposed (on), the
imposed value is displayed and acted on, as viewed either on the
Continuous Links page or the faceplate.
Figure 6.3.17 shows a sample logic statement that is to override a

variable input value with a constant. Continuous input A is linked to this
logic step and has a value of .66. This logic statement sends a value of
50% to register A, which overrides the linked value of 66%.
Figure 6.3.18 shows a sample logic statement that is to override a

variable input value with the value of another continuous variable.
Continuous inputs A and B are linked to this logic step. The value of A is
.66. The value of B is .39. This sample logic statement sets the register
A equal to register B so that the B register value of 39% overrides the A
register value of 66%.
When the logic action is relaxed (off), the function immediately resumes
using the linked value of 66%. If a numerical constant rather than a link
address was entered, the function resumes using the numerical
constant.
CAUTION
Logic action statements may cause abrupt changes in the
variable that could adversely affect process operations.

CB: 6-3-31
CONDITIONS When the logic step is on,

the imposed value of .50
overrides the linked value of .66.
ON
ACTIONS
Fill--1 A Rise Þ
.50 GAL ON Þ A=.5
Fall Þ
OFF Þ
CONDITIONS When the logic step is off,

the linked value of .66
remains in the register.
OFF
ACTIONS
Fill--1 A Rise Þ
.66 GAL ON Þ A=.5
Fall Þ
OFF Þ
Figure 6.3.17. Replacing a Linked Value with a Constant
CONDITIONS When the logic step is on,

the imposed value of .39 from
input B overrides the linked value
of .66 from input A
ON
ACTIONS
Fill--1 A Rise Þ
.39 GAL ON Þ A=B
Fall Þ
Fill--2 B OFF Þ
.39 GAL
CONDITIONS
When the logic step is off,
the linked value of .66
remains in the register
ACTIONS OFF
Fill--1 A Rise Þ
.66 GAL ON Þ A=B
Fall Þ
Fill--2 B OFF Þ
.39 GAL
Figure 6.3.18. Replacing a Linked Value with Another Linked Value

CB: 6-3-32

CB: 6-4-1
Section 4:
Logic Statement Functions
This section describes the functions that can be configured in a logic

step. Table 6.4.1 summarizes these logic statement functions.
Functions listed without an asterisk are described in this section in the
order in which they appear in the table.
Table 6.4.1. Logic Statement Functions
Counts the occurrences of a specified event and becomes true after a preset number of
count
counts.
Turns on a logic step after a condition has been true for an uninterrupted length of time,
delay and then turns off the logic step after the condition has been false for the same
uninterrupted length of time.
duty Converts a controller output to a variable period pulse train.
period Generates pulses at a preset interval as long as a specified condition remains true.
timer Turns on a logic step after a condition has been true for a cumulative length of time.
wait Turns on a logic step after a condition has been true for an uninterrupted length of time.
ramp Increases or decreases a variable (Y) toward a target value (X) at a rate (Z).
time Provides a true/false value that depends on the current clock time or date.
setuauto Sets the logic step mode to Auto.
setuman Sets the logic step mode to Manual.
setmode Sets the operating mode of the ControlBlock being configured.
mode Tests the mode of a ControlBlock.
sstand Sets the Controller Processor card to Standby mode.
snorm Sets the Controller Processor card to Normal mode.
ifstand Tests if the Controller Processor is in Standby mode.
inhibit Inhibits all alarms from a ControlBlock
inha Inhibits all alarms and events on the Controller Processor.
enba Enables all alarms and events on the Controller Processor.
* These functions are not described in detail and are listed here for reference only.
RS3: Configuring Logic Steps Logic Statement Functions

CB: 6-4-2
Table 6.4.1. Logic Statement Functions (continued)
Specifies a condition, an action that occurs if the condition is true, and another action that
if?then:else
occurs if the condition is false.
treset Resets a stack totalizer to zero and shifts inputs B, C, and D.
fhf* Forces hold forward action. Expressed as fhf.
track* All blocks continue to operate if the output is not linked to anything. Expressed as track.
Invalidates any numbers currently in the Dead Time stack and sets the hold forward flag.
The Dead Time stack can then be filled with numbers and can contain a combination of
fill*
valid and invalid numbers. Expressed as fill. For information about using the fill function
with a Dead Time function ControlBlock, see Chapter 2.
Fills the Dead Time stack with a user-specified value. The output goes to the
vfill x* user-specified value until new information is received. Expressed as vfill x. For information
about using the vfill function with a Dead Time function ControlBlock, see Chapter 2.
Forces an evaluation of the block function. When “fnow” is on, a new value is put in the
fnow*
dead time stack. When “fnow” is off, the stack and display freeze. Expressed as fnow.
norate* Disables all operator entry rate limits. Expressed as norate.
Forces a block to ignore received backtracking by clearing all four track action flags. Has
notrack*
no effect on Hold Forward. Expressed as notrack.
Sets the value of a PID integration term. The siterm function should be used carefully
siterm x* because the tracking system depends on being able to adjust to the integral term.
Expressed as siterm x.
ssm is the number of seconds since midnight. The ssm function allows you to schedule an
ssm*
event between midnight and 1 a.m.
ssm is the number of seconds since Sunday midnight. The ssm function allows you to
sss*
schedule an event.
V is the output tracking value in a tracking scheme. Using V in a logic statement allows
V*
you to test for the tracking value coming back to the primary block.
* These functions are not described in detail and are listed here for reference only.

CB: 6-4-3
Count Function
Definition
A count function is an event timer that counts the number of evaluation

cycles that the condition is true. The logic step becomes true when the
count reaches a target value.
You must configure a separate logic statement to reset the event

counter.
Expression
count(X,Y,Z) Where X is the target count. When Y=X, the logic step
turns on.
Y is the counter register (*Counter), which
tracks the evaluation cycles that the condition
is true. You must configure the register as a
*Counter function.
Z is a condition. For each evaluation that the
condition is true, the counter is incremented
by 1.
Sample Logic Statement
Figure 6.4.1 shows a sample logic statement for performing a count

function and a sample logic statement for resetting the counter to 0.
Example
Figure 6.4.2 shows the behavior of the count statement in Figure 6.4.1
using a target count of 4.0. Note that Z remains true for three evaluation
cycles from t6 to t9, which usually results in the accumulation of three
counts. In most applications, the objective is to count the number of
times a condition becomes true without regard to how long it remains
true each time. To accomplish this, a rise statement can be used for Z.
For information about using a Rise statement, see Section 3.

CB: 6-4-4
K is the counter register—Input K is used to

track the number of evaluation cycles that
@d or @j changes from off to on.
12 is the target—
When @d or @j changes from off
to on for 12 evaluation cycles, @d and @j are the condition—When @d
the step is turned on. or @j turns from off to on, the counter is
incremented by 1.
CONDITIONS
c Þ count(12,K,rise @d |rise @j)

Set Þ CONDITIONS
ClearÞ e Þ c&@a
ACTIONS Set Þ
Rise Þ ClearÞ
ON Þ ACTIONS
Fall Þ RiseÞ
OFF Þ ONÞ K=0.0

FallÞ
Resets the counter to 0 and turns this logic
step off by turning step c off. OFFÞ
Figure 6.4.1. Sample Logic Statement Using the Count Function
The step output is true when Y³X. ( At t4 and t10.)

Counter Y increments by one during each evaluation cycle while z is true.
Y must be reset to zero manually or by another logic function (t5 and t13).
Y continues to accumulate counts until reset, even when the function is already TRUE (t11 and t12).
4 (X)
3
2 Counts
1
Counter (Y) 0
Step Output
One Evaluation Cycle

t1 t2 t3 t4 t5 t6 t7 t8 t9 t10 t11 t12 t13
Figure 6.4.2. Behavior of the Count Function

CB: 6-4-5
Delay Function
Definition
A delay function is a dual, sequential, elapsed-time timer that turns on a

logic step after a condition has been true for an uninterrupted length of
time and then turns off the logic step after the condition has been false
for the same uninterrupted length of time.
Expression
delay(X,Y,Z) Where X is the uninterrupted number of seconds that
Z must be true in order to turn on the step, and
it is also the number of seconds that Z must be
false in order to turn off the step.
Y is the timer register (*Timer) that tracks the
amount of time that the condition is true and
the amount of time that the condition is false.
You must configure the register as a *Timer
function.
Z is a condition. Each evaluation that the
condition changes from true to false or from
false to true, the timer begins counting.
Figure 6.4.3 shows a sample configuration of a delay statement to

perform a delay function.
Example
Figure 6.4.4 shows the behavior of the delay statement in Figure 6.4.3.
When Z goes true at t1, the timer starts timing from --30 seconds toward
zero. At t2, after 30 seconds have elapsed and Y equals zero, the step
output turns on. At this point, Y is set equal to +30 seconds. At t3, Z
goes false. The timer therefore starts timing down from 30 toward zero.
At t4, after 30 seconds have elapsed and Y equals zero, the step output
turns off. Although Z goes true again at t5, it goes false at t6 before it
has been true long enough for Y to time to 30, so the step output does
not turn on. This has the effect of filtering out pulses on Z shorter than
30 seconds in duration.

CB: 6-4-6
H is the timer register—Input H is

30 is the target—When @c used to track the number of
uninterrupted seconds that @c is @c is the condition—When @c
is true for 30 uninterrupted changes state the timer begins
seconds, the step is turned true or false. When @c changes
state, H is reset. counting. Each evaluation
on. When @c is false for 30 cycle that the target count is
uninterrupted seconds, the reached, the step output state
step is turned off. changes.
CONDITIONS
b Þ delay(30,H,@c)
Set Þ
ClearÞ
ACTIONS
Rise Þ
ON Þ
Fall Þ
OFF Þ
Figure 6.4.3. Sample Logic Statement Using the Delay Function
The step output changes state when Y=0.

Timer Y is reset to +X when the step output is true.
Y is reset to --X when the step output is false.
Z
30
.00 (X)
Seconds
Timer (Y) --30
ON
Step Output
30 OFF
sec
t1 t2 t3 t4 t5 t6
Figure 6.4.4. Behavior of the Delay Function

CB: 6-4-7
Duty and Period Functions
Definition
A period function is a pulse generator that operates as long as a

specified condition is true. Often a period function is combined with an
action statement that is configured to perform a duty function. The
period function can be used independently or with other functions.
A duty function is a counter that can be used to convert a controller

output to a variable period pulse train. The duty function, when
combined with a period function, serves to set the evaluation time of the
period, rather than having the controller set the evaluation time. The
duty function is typically used with a period function.
Duty Function Expression
The duty function is expressed as:

duty(X,Y,Z) Where X is a controller output. X must be between 0
and 1.
Y is the counter register (*Counter), which
tracks the evaluation cycles that the condition
is true. You must configure the register as a
*Counter function.
Z is a condition. Each evaluation that the
condition is true, the counter is incremented by
the controller output.
For each evaluation cycle that Z is on, Y=Y+X. When Y³1.0, Y is set to
Y--1.0 and the value of the duty function becomes true for one
evaluation cycle.

CB: 6-4-8
Period Function Expression
The period function is expressed as:

period(X,Y,Z) Where X is the number of seconds between pulses.
Y is the timer register (*Timer), which tracks
the time that the condition is true. Y is reset to
zero whenever the condition is true. Y is reset
to zero whenever Y=X or when Z becomes
false. You must configure the register as a
*Timer function.
Z is a condition. Each evaluation cycle that the
condition is true, pulses are generated.
The period expression stays on for a single evaluation cycle, the length
of which may be 1/4second, 1/2 second, or 1 second, as selected for
the controller. When used with a duty function, the period expression is
on while the duty function is activated, which extends the on time of the
ControlBlock output.

CB: 6-4-9
Figure 6.4.5 shows a sample configuration of a period statement and a

duty statement that are to generate a pulse for an extended evaluation
cycle, when a is true.
G is the timer register—Input G is used to

10 is the target time— track the number of uninterrupted seconds
When @a is true for 10 that @a is true or false. When @a changes
uninterrupted seconds, the step is state, input G is reset.
turned on and the timer resets to
zero. When @a is false, the step
is turned off and the timer resets @a is the condition—When @a is
to zero. true, pulses are generated.
CONDITIONS
c Þ period(10,G,@a)
Set Þ
ClearÞ
ACTIONS
Rise Þ
ON Þ e=duty(A,H,1)
Fall Þ
OFF Þ
A is the controller output 1 is the condition—Each evaluation

cycle that the period statement is true,
H is the counter register—Input H is used the counter is incremented by A.
to track the number of evaluation cycles
that the period statement is true. The
counter is reset when it reaches a value
greater than or equal to 1 and @a is false.
Figure 6.4.5. Sample Logic Statement Using the Duty and Period Functions

CB: 6-4-10
Example Using Duty and Period Functions
The top part of Figure 6.4.6 shows the behavior of the period statement
in Figure 6.4.5. At t1, Z goes true. The timer starts timing from zero
toward 10 seconds. At t2, after 10 seconds have elapsed, Y equals 10,
so the step output turns on. In addition, the timer is automatically reset
and resumes timing from zero toward 10 seconds. As long as Z remains
true, the period expression cycles on and off once every 10 seconds.
However, Z goes false at t4, before another 10 seconds expire, so at t4
the timer is reset to zero and the period expression becomes false. The
timer remains at zero and the step output remains off until Z again goes
true and stays true for at least 10 seconds.
The bottom part of Figure 6.4.6 shows the behavior of the duty
statement with a controller output of .25. Z remains true for a number of
evaluation cycles, but the duty function is true only when Y is ³1 and Z
is true. Y resets to 0 when Y is £1 and Z is false.

CB: 6-4-11
period(X,Y,Z) Expression is true for one evaluation cycle when Y=X.

Timer Y is reset to zero when the expression returns to false
or when Z becomes false.
Z
10
On Delay
(X) seconds
Timer (Y) 0
On
Period Off
Step Output
t1 t2 t3 t4 t5
10
sec
duty(X,Y,Z)
Z
1.0
.75
.50 Counts
.25
Counter (Y) 0
X .25 seconds
On
Duty
Step Output Off
The expression is true when Y³1.0 and Z is true

Counter Y increments by X during each evaluation cycle while Z is true.
Y is reset to zero when Y£1 and Z turns false
When Y³1.0 and Z is true, Y=Y--1.0
Figure 6.4.6. Behavior of the Period and Duty Functions

CB: 6-4-12
Timer Function
Definition
A timer function is a timer that turns on a logic step after a condition has
been true for a cumulative length of time.
To reset the timer, configure a separate logic action.
Expression
timer(X,Y,Z) Where X is the cumulative number of seconds that Z
must be true in order to turn on the step. This
may be the length of a single, uninterrupted
period or the sum of the length of two or more
separate periods.
the amount of time that the condition is true.
function.
condition is true, the timer is counting (without
being reset).
Figure 6.4.7 shows a sample configuration of a logic statement that

performs a timing function and a logic statement that resets the timer to
zero.
Example
Figure 6.4.8 shows that when Z goes true at t1, the timer begins timing
toward 300 seconds. When Y reaches 300 at t2, the step output turns
on. Notice that between t2 and t3, Z goes false; the step output remains
on, however, because Y is reset by another logic step at t3. At t4, Z
goes true. Y therefore starts timing toward 300 seconds. At t5, after an
elapsed time of less than 300 seconds, Z goes false again. Y remains at
the elapsed time it accumulated up to that point. At t6, Z goes true
again. The timer resumes timing toward 300 seconds. At t7, when the
timer reaches 300 seconds, the step output turns on. The timer
expression stays on, regardless of whether Z is true or false, until Y is
reset to zero by a logic action statement.

CB: 6-4-13
H is the timer register—Input H is used to track the

cumulative number of seconds that @d and @e are
300 is the target—When @d and @e are true.
true for one or more evaluation cycles for a @d and @e are the condition—When @d
cumulative time of 300 seconds, the step is and @e are on, the timer begins counting.
turned on.
CONDITIONS
CONDITIONS
b Þ timer(300,H,(@d&@e)) c Þ @g
Set Þ Set Þ
ClearÞ ClearÞ
ACTIONS
ACTIONS
Rise Þ
Rise Þ
ON Þ
ON Þ H=0.0
Fall Þ
Fall Þ
OFF Þ
OFF Þ
Resets the time to 0 when @g is true and turns off logic step b.
Figure 6.4.7. Sample Logic Statement Using the Timer Function
Step output is true when Y=X.

Timer Y is not reset to zero when Z goes false, but must be
reset either manually or by another logic function.
Z
300
(X)
Seconds
Timer (Y) .00
Step Output
300
sec
t1 t2 t3 t4 t5 t6 t7
Figure 6.4.8. Behavior of the Timer Function

CB: 6-4-14
Wait Function
Definition
A wait function is an elapsed-time timer that turns on a logic step after a

condition has been true for an uninterrupted length of time. The logic
step becomes false when the condition goes false.
Expression
wait(X,Y,Z) Where X is the uninterrupted number of seconds that
Z must be true to turn on the step.
the amount of time that the condition is true.
function.
condition is true, the timer begins counting.
Figure 6.4.9 shows a sample configuration of a wait statement to turn on

a logic step after a condition has been true for an uninterrupted length of
time.
Example
Figure 6.4.10 shows the behavior of the wait statement. When Z goes
true at t1, the timer, Y, begins timing toward 60 seconds. When Y
reaches 60 at t2, the step output turns on. When z goes false at t3, the
step output turns off and the timer is reset. Although Z goes true again
at t4, it goes false at t5 before it has been true long enough for Y to time
to 60, so the step output does not turn on.

CB: 6-4-15
F is the timer register—Input F is used to

track the number of seconds that @a is
true. When @a changes state, F is reset.
60 is the target time—When @a is @a is the condition—When @a is true,

true for 60 uninterrupted seconds, the timer begins counting. Each
the step is turned on. When @a is evaluation cycle that the target is
false, the step is turned off. reached, the step output state turns on.
CONDITIONS
b Þ wait(60,F,@a)
Set Þ
ClearÞ
ACTIONS
Rise Þ
ON Þ
Fall Þ
OFF Þ
Figure 6.4.9. Sample Logic Statement Using the Wait Function
Step output is true when Y=X.

Timer Y is reset to zero when Z goes false.
Z
60
(X)
Seconds
Timer (Y) .00
Step Output
60
sec
t1 t2 t3 t4 t5
Figure 6.4.10. Behavior of the Wait Function

CB: 6-4-16
Ramping a Variable (ramp function)
Definition
The ramp function increases or decreases a variable toward a specified

target value at a predetermined rate.
Expression
ramp(X,Y,Z) Where X is the target value, which is a constant,
another variable, or an expression. X must be
a value between 0 and 1.
Y is the variable (usually a setpoint) that is to
be ramped.
Z is the ramp rate in units per second, which
may be a positive (+) or negative (~) value and
can be a constant, another variable, or an
expression.
Figure 6.4.11 shows a sample configuration of a ramp statement for a

fixed target and rate.
Example
Figure 6.4.12 shows the behavior of the sample ramp statement in

Figure 6.4.11. The ramp function activated at t1, with Y incrementing
toward 500 °F from the temperature prevailing at the time. During the
one-second interval between t2 and t3, Y rises 0.05 °F, which
corresponds to a rate of 3 °F/minute. Y reaches the target value of 500
°F at t4, at which time Y ceases to increment further.

CB: 6-4-17
CONDITIONS
@a g= Þ@a
Set Þ
ClearÞ
ACTIONS
C Rise Þ
ON Þramp(.5,B,.00005)
Fall Þ
OFF Þ
Ramp rate of .05 °F/sec

500 is the target temperature— (with a range of 0--1000 °F)
500 °F (with a range of 0--1000 °F)
Reactor vessel temperature ramped at 3

degrees/minute to the target of 500 °F
Figure 6.4.11. Sample Ramp Logic Statement
500 F (X)
0.05 F (Z)
1 sec
t1 t2 t3 t4
Figure 6.4.12. Ramp Function Behavior

CB: 6-4-18
Using the Clock Time or Date (time function)
Definition
The time function provides a value for a logic statement that depends on
the current clock time or date. Clock time refers to the system clock time
displayed on the upper right hand corner of all console screens.
Expression
time X Where X is a number that represents the desired time
or date. See Table 6.4.2 for a list of the time
function options.
Table 6.4.2. Time Function Options
Time Example
Description Time or Date
Operator Format
time 0 Number of minutes since January 1 1441 1441
time 1 Current number of seconds on the system clock 54 seconds 54
time 2 Current number of minutes on the system clock 30 minutes 30
time 3 Current number of hours on the system clock Twelve hours 12
time 4 Day of the month The tenth 10
time 5 Month of the year January 1
time 6 Year AD, written as a four-digit number 1989 1989
time 7 Day of the week Sunday 1
time 15 Number of days in the current month June 10 30
time 16 Number of days in the current year October 6, 1992 366

December 25, 1993 365
time 21 Clock time (hour:minute:second) 9:45:20 AM 94520

in the form hhmmss
15:30:00 (3:30:00 153000
PM)
time 22 Clock time in the form yymmdd June 23, 1990 900623
time 23 Clock time in the form mmddyy June 23, 1990 062390
time 24 Clock time in the form ddmmyy June 23, 1990 230690

CB: 6-4-19
Expression Examples
The following are some examples of clock time and date statements:
D The expression “time 3<8” is true when the hour is less than 8.
D The expression “time 7==1” is true all day Sunday every week.
D The expression “time 7>1” is true Monday through Saturday of
each week, but false all day Sunday.
D The expression time 2==30 is true for one minute each hour until
31 minutes past the hour.
D An expression that is to be true for a given span of clock time
must be written with an and (&) function. The expression
(time 21>=90000) & (time 21<=113000) is true for the time span
between 9:00 am and 11:30 am each day. A statement written in
the form 90000<=time 21<=113000 is accepted as an entry, but
does not function.
Example
Figure 6.4.13 shows a sample condition logic statement that sets the
step on when the clock time is 8:45:50.
Clock time is set to 8:45:50
CB DISCRETE DIAGRAM 27-Jun-92 08:45:50

| * |
| * a= > | Mode>Auto
| * |
| * Set >time 21==084550 | MsgP>*1
| * | On
| *Clear> |
| * | -> ON
|---*----------------ACTIONS----------------------|
| * |
| * Rise> |
| * |
| * ON > | Rpt>None
| * |
| * Fall> |
| * |
| * OFF > |
+-------------------------------------------------+
FULL CONFIG 1
Figure 6.4.13. Setting the Clock Time

CB: 6-4-20
Changing the Logic Step Mode (setuauto and setuman

functions)
Definition
The following functions set the logic step mode to Auto or Manual mode.
D setuauto Sets the logic step to Auto mode.
D setuman Sets the logic step to Manual mode.
Expression
The setuauto function is expressed as:

setuauto x Where x is the number corresponding to the particular
logic step. For example, the number assigned
to logic step a is 1, and logic step p is 16.
The setuman function is expressed as:

setuman x Where x is the number corresponding to the particular
logic step. For example, the number assigned
to logic step a is 1, and logic step p is 16.

CB: 6-4-21
Example
Figure 6.4.14 shows a sample logic statement that sets the logic step
mode to Auto when the step is on and sets the logic step mode to
Manual when the step is off.
Step a is on, setting the logic step mode of

step f (6) to Auto.

>Level 1 |@c * |
On ON | * a= >@c |Mode>Auto
| * |
| * Set > |MsgP>*1
| * |Off
| *Clear> |
| * |-> ON
|---*----------------ACTIONS----------------------|
| * |
| * Rise> |
| * |
| * ON >setuauto 6 |Rpt>None
| * |
| * Fall> |
| * |
| * OFF >setuman 6 |
+-------------------------------------------------+
FULL CONFIG 1
Figure 6.4.14. Setting the Logic Step Mode

CB: 6-4-22
Changing or Testing the ControlBlock Operating Mode
You can change or test the ControlBlock operating mode with logic
functions:
D setmode n function Changes the operating mode of the block
being configured
D mode function Tests the operating mode
Numerical values are used to represent the ControlBlock operating

modes. Table 6.4.3 lists the operating modes and the numerical values.
Table 6.4.3. Control Block Operating Modes
Operating Numerical
Mode Value (n)
Local 0
Manual 1
Auto 2
Remote 3
DDC 4
COMP SP 5

(setmode n function)
The setmode n function sets the operating mode of the ControlBlock

being configured. Configure a setmode expression in the Actions portion
of a logic step.
Expression
setmode n Where n is an integer from Table 6.4.3. For
information on the effect of mode on block
behavior, see Chapter 2.

CB: 6-4-23
Configure a setmode n function statement:

D To set the operating mode each time that the block is evaluated
and also to prevent an operator from changing the mode,
configure the expression in the On or Off statement.
D To set the operating mode when the step changes state and to
also allow an operator to change the mode, configure the
expression in the Rise or Fall statement.
Example
Figure 6.4.15 shows a sample logic statement that sets the block mode
to Auto.
Step a is on, setting the block mode to Auto.

+-------------------CONDITIONS---------------+Step>a
>Level 1 |@a * |
On ON | * a= >@a |Mode>Auto
| * |
| * Set > |MsgP>*1
| * |Off
| *Clear> |
| * |-> ON
|---*----------------ACTIONS------------------ |
| * |
| * Rise> |
| * |
| * ON >setmode 2 |Rpt>None
| * |
| * Fall> |
| * |
| * OFF > |
+----------------------------------------------+
FULL CONFIG 1
Figure 6.4.15. Setting the ControlBlock Operating Mode

CB: 6-4-24
Testing for Block Mode (mode n function)
Use the mode function to test the operating mode of a block. You can
use the mode function to test the mode of its own block or another
block.
Testing the Block Mode of the Block Being Configured
Expression
To test the operating mode of a block that is being configured, use the
mode function expression:
mode==n Where n is an integer from Table 6.4.3 that
corresponds to the block mode.
Example
Figure 6.4.16 shows a sample logic statement that tests the

ControlBlock mode.

+-------------------CONDITIONS------------------+Step>c
| * |
| * c= >mode==2 |Mode>Auto
| * |
| * Set > |MsgP>*1
| * |On
| *Clear> |
| * |-> ON
|---*----------------ACTIONS----------------------|
| * |
| * Rise> |
| * |
| * ON > |Rpt>None
| * |
| * Fall> |
| * |
| * OFF > |
+-------------------------------------------------+
FULL CONFIG 1
Step c is on, indicating that

ControlBlock =1A--01 is in Auto mode.
Figure 6.4.16. Testing the Operating Mode of the Block Being Configured

CB: 6-4-25
Testing the Block Mode of Another Block
To test the operating mode of another block, the ControlBlock must test
for the mode block status bit. To do this, configure the other block being
tested as a continuous link to the source block. The block tag or address
is followed by “/MD” in the “Source” field on the Continuous Links
screen. Configure the test expression in a logic step.
Expression
To test the block mode of another block, use the expression:
x==y Where x is a continuous variable.
y is an integer from Table 6.4.3 that
corresponds to the block mode.
Example
Figure 6.4.17 shows a sample logic statement that tests the current
mode of a ControlBlock linked to this ControlBlock. The ControlBlock in
the example is linked to blocks =1A--9, =1A--13, and =1A--14. Notice
that “/MD” is entered following the address of the block =1A--14 on the
Continuous Links screen. This indicates that the sample logic statement
is testing the mode of block 1A--14. The logic statement is testing for
Auto mode.
Logic step in block 1A--1 configured to

turn on when block 1A--14 is in Auto.

ControlBlock 1A--14 Tag DescriptorÞ
is linked to CB 1A--1 Addr=1A-1 FunctionÞ MATH
and is in Auto mode. INPUT SOURCE Hold Eng Zero Eng Max Value Units
AÞ 1A-9 Þ.00 Þ100.00 >48.00 Þ
BÞ 1A-13 Þ.00 Þ100.00 >39.00 Þ
CÞ 1A-14/MD Þ0. Þ1. >2 Þ
DÞ
EÞ
CONDITIONS
a=Þ C==2 Þ.00 Þ100.00 >.00Þ
SetÞ Block Mode>AUTO
ClearÞ CONFIG 1
ON
ACTIONS
Figure 6.4.17. Testing the Operating Mode of Another Block

CB: 6-4-26

Mode
You can test the Controller Processor operating mode with logic
functions:
D ifstand function Testing the Controller Processor mode
D sstand, snorm Setting the Controller Processor card mode
functions
Testing the Controller Processor Mode (ifstand function)
Definition
Use the ifstand function to test if a Controller Processor is in Standby

mode. If the Controller Processor is in Standby mode, a value of 1 is
returned, otherwise a 0 is returned.
Expression
To test the Controller Processor for Standby mode, use the ifstand
expression:
ifstand
Configure an ifstand expression in the Conditions portion of a logic

statement.
NOTE: To make troubleshooting easier, we recommend that you

configure an ifstand function in a single ControlBlock with an appropriate
tag and descriptor.

CB: 6-4-27
Example
Figure 6.4.18 shows a sample logic statement to determine whether the

Controller Processor is in Standby mode.
Step c is on, indicating that the Controller

Processor is in Standby mode.

Tag Standby Test Descriptor Tests cntrlr for standby
+-------------------CONDITIONS--------------------+Step>c
| * |
| * c= >ifstand |Mode>Auto
| * |
| * Set > |MsgP>*1
| * |On
| *Clear> |
| * |-> ON
|---*----------------ACTIONS----------------------|
| * |
| * Rise> |
| * |
| * ON > |Rpt>None
| * |
| * Fall> |
| * |
| * OFF > |
+-------------------------------------------------+
FULL CONFIG 1
Figure 6.4.18. Testing the Controller Processor Mode

CB: 6-4-28
Setting the Controller Processor Card Mode (sstand and snorm

functions)
Definition
The following functions set the Controller Processor card to Standby or

Normal mode.
D sstand function Sets the Controller Processor card to
Standby mode.
D snorm function Sets the Controller Processor card to
Normal mode.
Expression
The sstand function is expressed as: sstand
The snorm function is expressed as: snorm
Configure sstand and snorm expressions in the Actions portion of a

logic statement.

configure sstand and snorm functions in a single ControlBlock with an
appropriate tag and descriptor.
While in Standby mode, a Controller Processor can read inputs and

tracking signals but cannot generate a link value or set outputs to any
other Controller Processor or to the field. The Controller Processor also
ignores all ControlBlock rate limits.

CB: 6-4-29
Example
Figure 6.4.19 shows a sample logic statement to set the mode of the
Controller Processor.
Step c is on, setting the Controller

Processor to Normal mode.

Tag Set Normal Descriptor Sets controller to normal
*TOGGLE |@a * |
>On ON | * c= >@a |Mode>Auto
| * |
| * Set > |MsgP>*1
| * |Off
| *Clear> |
| * |-> ON
|---*----------------ACTIONS----------------------|
| * |
| * Rise> |
| * |
| * ON >snorm |Rpt>None
| * |
| * Fall> |
| * |
| * OFF > |
+-------------------------------------------------+
FULL CONFIG 1
Figure 6.4.19. Setting the Block Mode of the Controller Processor Card

CB: 6-4-30
Inhibiting ControlBlock Alarms (inhibit function)
Definition
The inhibit function inhibits all of the alarms from a ControlBlock from
generating and being sent on the PeerWay.
NOTE: The inhibit function does not work on MPCI controllers.
When the inhibit function is executed, the following tasks occur:

D The block sends a clear message on the PeerWay for each
uncleared alarm in the block.
D All alarms from the block are inhibited from generating and are
not sent on the PeerWay.
Expression
The inhibit function is expressed as:
inhibit
Configure an inhibit expression in the Actions portion of a logic

statement.
NOTE: The alarms are inhibited only as long as the inhibit function is
executed. That is, alarms are inhibited only for those evaluation cycles
in which the inhibit function is executed.

CB: 6-4-31
Example
Figure 6.4.20 shows a sample logic statement that inhibits all alarms on
ControlBlock =1A--10.
When Step c is on, alarms from =1A--01 are inhibited.

*TOGGLE |@a * |
| * |
| * Set > |MsgP>*1
| * |Off
| *Clear> |
| * |-> ON
|---*----------------ACTIONS----------------------|
| * |
| * Rise> |
| * |
| * ON >inhibit |Rpt>None
| * |
| * Fall> |
| * |
| * OFF > |
+-------------------------------------------------+
FULL CONFIG 1
Figure 6.4.20. Inhibiting Alarms on a ControlBlock

CB: 6-4-32
Inhibiting and Enabling the Controller Processor Alarms

and Events (inha and enba functions)
Definition
The following functions inhibit or enable the Controller Processor card

alarms and events.
inha function Inhibits all alarms (including block alarms) and events
on the Controller Processor card from generating and
being sent on the PeerWay. When executed, the
following tasks occur:
D The Controller Processor sends a clear message
on the PeerWay for each uncleared alarm.
D All alarms from the Controller Processor are

inhibited from generating and are not sent on the
PeerWay.
enba function Enables all alarms and events on the Controller
Processor card to generate and be sent on the
PeerWay.
- To inhibit alarms from a Controller Processor, use:
D The inha function in ControlBlock logic,
or
D The “Alarm Inhib” field on the ControlFile Status screen
(“Alarm InhibÞyes”).
- To uninhibit alarms from a Controller Processor, use:
D The enba function in ControlBlock logic,
or
D The “Alarm Inhib” field on the ControlFile Status screen
(“Alarm InhibÞno”).

CB: 6-4-33
Expression
The inha function is expressed as: inha
The enba function is expressed as: enba
Configure inha and enba expressions in the Actions portion of a logic

statement.
NOTE: Once alarms from a ControlFile are inhibited, they stay inhibited
until the opposite function is executed. That is, once a function is
executed, that condition remains in effect until the opposite condition is
executed.

configure inha and enba functions in a single ControlBlock with an
appropriate tag and descriptor.
Example
Figure 6.4.21 shows a sample logic statement that inhibits all alarms
and events on the Controller Processor.
When Step c is on, alarms and events from this ControlFile are inhibited.
The alarms and events remain inhibited until they are enabled.

Tag Enable Alarms Descriptor Enable alarms and events
*TOGGLE |@a * |
| * |
| * Set > |MsgP>*1
| * |Off
| *Clear> |
| * |-> ON
|---*----------------ACTIONS----------------------|
| * |
| * Rise> |
| * |
| * ON >enba |Rpt>None
| * |
| * Fall> |
| * |
| * OFF > |
+-------------------------------------------------+
FULL CONFIG 1
Figure 6.4.21. Inhibiting Alarms and Events on the Controller Processor

CB: 6-4-34

(if?then:else function)
Definition
The if?then:else function specifies a condition, an action that occurs if

the condition is true, and another action that occurs if the condition is
false.
Notation of an if?then:else Statement
Figure 6.4.22 provides an example of the format of an if?then:else logic

statement. Configure an if?then:else statement in the Actions portion of
a logic statement. Any equation in the Conditions area must be true
before the true part of an action statement is executed.
if?then:else
X ? Y : Z
Indicates the condition Result if the condition

is false (off)
Result if the condition

is true (on)
X can be a single discrete variable or an expression.

Y and Z can be fixed values, variables, or expressions.
Figure 6.4.22. Format of an if?then:else Statement

CB: 6-4-35
Expression Examples
D F=@a?E+.2:E--.2 If @a is true, then F=E+.2.
If @a is false, then F=E--.2.
D @c?(B=.67):(A=.75) If @c is true, then B=.67

If @c is false, then A=.75
D D=@a & @b?D+.1:D If @a and @b are true, then

D=D+.1.
If @a or @b is false, then D
remains unchanged.
D A<.15?setmode 1:setmode 2 If the PV value is:

D Less than 15%, then the
block mode is set to
manual.
D Greater than 15%, then the
block mode is set to auto.
Example
To understand how an if?then:else statement works and the types of

situations in which it may be used, consider the logic used in the
example in Figure 6.4.23.
D If both @a and @c are true (on), set B equal to .67.
D If @a is true (on) and @c is false (off), set B equal to .75.
D If @a is false, leave the value of B as it is regardless of the
condition of @c.
Figure 6.4.23 shows two ways to perform the same operation. The
upper portion of Figure 6.4.23 shows the if?then:else function for
performing the logic. Note that only one logic step is required. The lower
portion of Figure 6.4.23 shows multiple logic steps that are configured to
perform the same function.

CB: 6-4-36
Using one logic step and the if?then:else function
CONDITIONS
a Þ @a
Set Þ
If @a is true:
ClearÞ
D and @c is true, then B is set to .67.
ACTIONS
D and @c is false, then B is set to .75.
Rise Þ
If @a is false, then the step is off and the
value of B remains as is. ON Þ B=@c?.67:.75
Fall Þ
OFF Þ
Using multiple logic steps
CONDITIONS
a Þ @a & @c
CONDITIONS
Set Þ
b Þ @a & ~@c
ClearÞ
Set Þ
ACTIONS
ClearÞ
Rise Þ
ACTIONS
ON Þ B=.67
Rise Þ
Fall Þ
ON Þ B=.75
OFF Þ
Fall Þ
OFF Þ
Figure 6.4.23. Sample if?then:else Logic Statement

CB: 6-4-37
Resetting a Stack Totalizer (treset function)
Definition
You can configure an action logic statement to reset a stack totalizer

and shift inputs B, C, and D, bypassing the “Periodic Reset” fields on the
Continuous Faceplate screen for the TOT function ControlBlock. For
information about configuring the stack totalizer, see Chapter 2.
Expression
The treset function is expressed as: treset
Example
Figure 6.4.24 shows a sample logic step that is configured to reset a

stack totalizer.
Step c is on, so the stack totalizer

has been reset to zero and the inputs are shifted.
NOTE: If the totalizer underflows or overflows, the
inputs are not shifted.
*ON |@a * |
| * |
| * Set > |MsgP>*1
| * |On
| *Clear> |
| * |-> ON
|---*----------------ACTIONS----------------------|
| * |
| * Rise> |
| * |
| * ON >treset |Rpt>None
| * |
| * Fall> |
| * |
| * OFF > |
+-------------------------------------------------+
FULL CONFIG 1
Figure 6.4.24. Resetting a Stack Totalizer

CB: 6-4-38

CB: 6-5-1
Section 5:
Hints for Configuring Logic Steps
when configuring ControlBlock logic steps and some possible ways to
deal with them. This section also provides tips that are helpful when
configuring logic steps.
Listed below are typical problems that occur when configuring logic
steps and possible ways to handle them.
- I want to change the output of a logic step manually, but the
system will not let me change the output field.
Check the “Mode” field to be sure that the logic step is in Manual
mode.
- Some ControlBlock evaluations do not seem to be working. The
ControlBlock is in Auto mode.
Although the ControlBlock is in Auto mode, some of the logic
steps may be in Manual mode. Such steps are not evaluated by
the ControlBlock. Check the “Steps in Manual” field to see if any
steps are in Manual mode. If they are, change the steps to Auto
mode.
- A logic step that isn’t even configured is on.
At one time this logic step was probably configured. Before it was
deleted, it was not turned off. You will need to turn off the logic
step.
To turn off the logic step:
1. Configure the “Function” as any function type, except a
preconfigured function.
2. On the Discrete Diagram screen for the logic step, turn the step
off.
3. Configure the “Function” as None to delete the ControlBlock.
or
Another logic step’s action statements are setting this step by
assignment.
RS3: Configuring Logic Steps Hints for Configuring Logic Steps

CB: 6-5-2
- I want to configure a trigger for a DMC to generate an alarm on a

rise for step a (when step a changes from off to on), but I can’t put
Rise in the “When” field.
Step a for a DMC is a preconfigured step. The Rise, Fall, and
Change Report options cannot be configured.
Workaround:
To configure an alarm trigger on the rise, fall, or change of a
preconfigured step, select a user-configured step and configure
x=>y (where x is a user-configured step and y is the
preconfigured step) and then configure the “Report” field of x as
needed.
- I have a trigger for a DMC configured to generate an event
whenever step a is on. Instead of triggering an event to generate
one time, the event is generated continuously while the step is on.
The Event Report options On and Off generate an event
message for every evaluation cycle that the step is true. To
generate a single event, you must use Rise, Fall, or Change.
Configuration Tips
Listed below are hints to help you when configuring logic steps.
- Writing logic statements
D When combining variables and operators in logic statements, be
sure to use parentheses to group statements, so that the
evaluation order is clear. If there are no parentheses in the logic
statement, and conditions are tested for first, then or conditions.
D When writing action logic statements that contain several
expressions, be sure to use a semicolon to separate the
expressions.
- Using logic statement operators
When using operators in a logic statement, remember that a value
less than or equal to 0.0 is considered false, and a value greater
than 0.0 is considered true.

CB: 6-5-3
- Remembering the difference between “Mode” and “Block

Mode” fields
The logic step mode is different from the block mode.
D “Mode” field displays the current logic step mode:
If Auto, the logic steps are evaluated when the ControlBlock is
evaluated. You cannot change the step output.
If Manual, you can change the step output. Note that even when
a logic step is in Manual, the conditions and actions sxtatements
are still evaluated and all their effects still occur, with the
exception that the step output remains unchanged.
D “Block Mode” field displays the current ControlBlock mode.
- Changing an input value from a linked block
When an input value originates at one block and is linked to another
block, you can temporarily change the linked value. Configure an On
logic statement to replace the linked value with a constant or another
linked value when the logic statement is true.
- Troubleshooting ControlBlocks
For easier troubleshooting, you might want to configure each of the
following functions in a single ControlBlock with an appropriate tag
and descriptor:
D inha and enba functions
D sstand and snorm functions
D ifstand function
- Unconfiguring a discrete variable
Remember that if you want to unconfigure a discrete variable, be
sure to turn off the logic step first. This will prevent the current step
state from being maintained.
- Changing the initial logic step state
When initially configured, the state of a variable is off. If you like, you
can configure a constant in the step to override the initial off state.

CB: 6-5-4
- Using logic step outputs in logic statements

Although logic step outputs can be used as variables in logic
statements, remember that the value of the variable depends on
whether the logic step precedes or follows the logic step that it is
providing the value for.
D If the logic step precedes it, the value calculated at the last
evaluation cycle is used. For example, a logic statement in step a
that uses the output of logic in step c gets the value of c that was
calculated the last evaluation cycle.
D If the logic step follows it, the current calculated value for the
logic step is used. For example, a logic statement in step c that
uses the output of logic in step a gets the current calculated value
of step a.
- Scrolling message pairs to save configuration time
For quicker configuration, you can scroll labels when assigning a
message pair number to a Discrete Diagram screen, as shown in
Figure 6.5.1.
- To scroll message pair labels:

1. Cursor to the “Msg Pr” field and 2. Press [NEXT OPTION] to scroll
enter the first letter (or letters) of through the labels that begin with
the appropriate label. that letter (or letters).
3. When the appropriate label
appears, press [ENTER].

>Level 1 |@c * |
| * | L
Off OFF | * |Off
| *Clear>@b | LOCKOUT
>Tank 4 |@b * |-> OFF
on ON |---*----------------ACTIONS----------------------| lockout
| * |
.65 | * |
| * |
| * Fall> |
| * |
| * OFF > |
+-------------------------------------------------+
FULL CONFIG 1
Figure 6.5.1. Scrolling Message Pair Labels

RS3t
Chapter 7:
Using System Flags and User Flags
Section 1: Introduction to Flags and Flag Logic . . . . . . . . . . . . . . . . . . . . . . . 7-1-1

What is a Flag? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1-1
Transfer of Data Between Linked Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1-2
Flag Notation for Logic Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1-4
Example of a Logic Step for Testing an Individual Flag . . . . . . . . . . . . . . . . . . . 7-1-5
Testing the Rise and Fall of an Individual Flag . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1-6
Binary and Hexadecimal Notation of Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1-7
Binary Notation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1-7
Hexadecimal Notation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1-7
Example of a Logic Step for Testing All Flags at Once . . . . . . . . . . . . . . . . . . . 7-1-9
Section 2: Input and Output Block Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2-1

Transfer of Flags: I/O Block Linked to a ControlBlock . . . . . . . . . . . . . . . . . . . . . . 7-2-2
I/O Block Flag Bit Representations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2-3
Testing for I/O Block Flag Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2-9
Section 3: ControlBlock Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-1

Transfer of Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-2
ControlBlock Linked to a ControlBlock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-2
System Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-2
User Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-4
Within a ControlBlock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-6
System Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-6
ControlBlock Flag Bit Representations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-7
Testing for ControlBlock Flag Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-10
Testing for ControlBlock Flags from a Continuous Input . . . . . . . . . . . . . . . . . . 7-3-11
Testing for System Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-11
Testing for User Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-12
Testing for ControlBlock Discrete Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-13
Testing for ControlBlock Flags Within a Block . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-15
Testing for ControlBlock Discrete Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-16
Testing All Discrete Inputs Using the Discrete Output User Flags . . . . . . . . . . 7-3-17
Manipulating ControlBlock Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-18
Section 4: Console Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4-1

Transfer of Flags: Console Node Linked to a ControlBlock . . . . . . . . . . . . . . . . . . 7-4-1
RS3: Using System Flags and User Flags Contents

CB: ii
Console Flag Bit Representations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4-3

Testing for Console Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4-4
Section 5: Testing Block Status Bits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5-1

What are Status Bits? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5-1
Block Status Bit Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5-2
Testing Block Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5-5
Section 6: Hints for Configuring Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6-1


CB: iii
List of Figures
Figure Page
7.1.1 Link Packet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1-1
7.1.2 Transfer of Data Between an I/O Block and a ControlBlock . . . . . . . . . 7-1-2
7.1.3 Transfer of Data Between ControlBlocks . . . . . . . . . . . . . . . . . . . . . . . . . 7-1-3
7.1.4 Transfer of Data Between a Console and a ControlBlock . . . . . . . . . . . 7-1-3
7.1.5 Flag Notation for Testing an Individual Flag . . . . . . . . . . . . . . . . . . . . . . . 7-1-4
7.1.6 Flag Notation for Testing All Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1-4
7.1.7 Testing an Individual Flag for a Critical High Alarm . . . . . . . . . . . . . . . . 7-1-5
7.1.8 Testing the Rise in an Individual Flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1-6
7.1.9 Using Binary or Hexadecimal Notation to Test All Flags . . . . . . . . . . . . 7-1-8
7.1.10 Testing the On/Off Status of All Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1-9
7.2.1 Transfer of Flags with an I/O Block Linked to a ControlBlock . . . . . . . . 7-2-2
7.2.2 Testing a System Flag for a Particular Value . . . . . . . . . . . . . . . . . . . . . . 7-2-10
7.3.1 Transfer of Flags Between Two Linked ControlBlocks . . . . . . . . . . . . . . 7-3-3
7.3.2 Example of Continuous Output Flags Between Two Linked
ControlBlocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-4
7.3.3 Example of Continuous Input Flags Between Two Linked
ControlBlocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-5
7.3.4 Flags Within a ControlBlock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-6
7.3.5 Testing the Status of System Flag g for Hold Forward Status . . . . . . . 7-3-11
7.3.6 Testing a User Flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-12
7.3.7 Testing for a Discrete Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-13
7.3.8 Testing for All Discrete Outputs (Except Step a) . . . . . . . . . . . . . . . . . . . 7-3-14
7.3.9 Testing for an Output System Flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-15
7.3.10 Testing a User Flag for a Discrete Input State . . . . . . . . . . . . . . . . . . . . 7-3-16
7.3.11 Testing All Discrete Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-17
7.4.1 Transfer of Flags Between a Console and a ControlBlock . . . . . . . . . . 7-4-1
7.4.2 Linking a Console Node to a ControlBlock . . . . . . . . . . . . . . . . . . . . . . . . 7-4-2
7.4.3 Acknowledging an Active Hardware Alarm . . . . . . . . . . . . . . . . . . . . . . . 7-4-4
7.5.1 Testing the Status of a Hardware High Alarm . . . . . . . . . . . . . . . . . . . . . 7-5-5

CB: iv
List of Tables
Table Page
7.2.1 I/O Block System Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2-3
7.2.2 Analog Input Block (AIB) User Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2-4
7.2.3 Analog Output Block (AOB) User Flags . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2-4
7.2.4 Contact Input Block (CIB) and Discrete Input Block (DIB) User
Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2-5
7.2.5 Contact Output Block (COB) and Discrete Output Block (DOB)
User Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2-5
7.2.6 Multiplexer Input Block (MIB) User Flags . . . . . . . . . . . . . . . . . . . . . . . . . 7-2-6
7.2.7 Pulse Input/Output Block (PIOB) User Flags . . . . . . . . . . . . . . . . . . . . . 7-2-6
7.2.8 Smart Transmitter Input Block (SIB) User Flags . . . . . . . . . . . . . . . . . . . 7-2-7
7.2.9 HART Output Block (HOB) User Flags . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2-7
7.2.10 Temperature Input Block (TIB) User Flags . . . . . . . . . . . . . . . . . . . . . . . 7-2-8
7.3.1 ControlBlock System Flags for Continuous Inputs
A through O (Z.s and Z.s.x) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-7
7.3.2 ControlBlock System Flags for Continuous Output Q (Q.t.x)* . . . . . . . 7-3-8
7.3.3 ControlBlock System Flags for Continuous Output Q (Q.v)* . . . . . . . . 7-3-9
7.3.4 ControlBlock Flags for Which You Can Test . . . . . . . . . . . . . . . . . . . . . . 7-3-10
7.3.5 Operators to Use with Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3-18
7.4.1 Console System Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4-3
7.4.2 Console User Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4-3
7.5.1 I/O Block Status Bit Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5-2
7.5.2 Programmable Logic Controller Block (PLCB) Status Bit Codes . . . . . 7-5-3
7.5.3 ControlBlock Status Bit Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5-4

CB: 7-1-1
Section 1:
Introduction to Flags and Flag Logic
This section describes flags and flag notation for writing logic to test the
status of flags.
What is a Flag?
When a block or console is linked to a ControlBlock, an information

packet is continually passed to the ControlBlock. This packet contains
64-bit representations of block and status information consisting of:
D System flags
D User flags
D An analog value or variable
The system flags generally contain information that can include:

D Block alarm status
D Hold forward status
D Valid data status
D Current mode
User flags generally contain alarm information.
The analog value or variable is composed of continuous inputs A--O or

the continuous output Q.
Figure 7.1.1 shows the components of a link packet. Figure 7.1.1 also
shows the letters, a--p, used to refer to the flag position.
LINK PACKET
· System Flags: xxxx xxxx xxxx xxxx; where x is a 0 or 1
· User Flags: xxxx xxxx xxxx xxxx; where x is a 0 or 1
· Value or variable: A--O, Q
p m i e a
xxxx xxxx xxxx xxxx
Figure 7.1.1. Link Packet
RS3: Using System Flags and User Flags Introduction to Flags and Flag Logic
CB: 7-1-2
Transfer of Data Between Linked Blocks
System flags and user flags exist for the following components:
D I/O Blocks
D ControlBlocks
D Console nodes
All of the linked information, including the system flags and user flags, is
stored in the destination ControlBlock input registers. You can test one
or all system flags and user flags in the destination ControlBlock logic
steps to provide information about the source block or the destination
ControlBlock input registers. In some cases, you can test for a flag, but
the flag value may not be accurate. Therefore, this chapter discusses
only the valid flags for which you can test.
Figure 7.1.2 shows the transfer of data between an I/O block and a
linked ControlBlock. Figure 7.1.3 shows the transfer of data between
two linked ControlBlocks. Figure 7.1.4 shows the transfer of data
between a console and a linked ControlBlock.
Linked Information
I/O Block ControlBlock
System Flags
I/O Block: (Valid data, Hold forward)
ControlBlock Link: (Alarm information, block mode)
User Flags for the I/O Block

(Alarm information, block mode)
Block Value (for the I/O Block)
Figure 7.1.2. Transfer of Data Between an I/O Block and a ControlBlock
CB: 7-1-3
Linked Information
System Flags
Source ControlBlock: (Valid data, Hold forward)
Destination ControlBlock Link: (Alarm information)
User Flags
Source ControlBlock: (User flags for A--O)
Destination ControlBlock: (Discrete outputs)
Variable (for the source ControlBlock)
Figure 7.1.3. Transfer of Data Between ControlBlocks
Linked Information
Console ControlBlock
System Flags
(Valid data)
User Flags
(Alarm information)
Figure 7.1.4. Transfer of Data Between a Console and a ControlBlock
CB: 7-1-4
Flag Notation for Logic Steps
When you use flags in logic steps, a special notation is required. Flags
can be tested individually or all at once. Figure 7.1.5 shows the flag
notation for writing logic to test an individual flag. Figure 7.1.6 shows the
flag notation for writing logic to test all flags at one time.
You can configure and test logic statements on the Discrete Diagram
screen. For information about configuring logic steps, see Chapter 6.
X.z.y Examples:
A.s.a Tests system flag a of
register A
C.u.p Tests user flag p of
register C
Q.t.e Tests system flag e of
A--O, Q a--p the continuous output Q
Designates the continuous Designates the flag that is
register that contains the flag being tested
s, t or u
Designates the type of flag—
s or t = system flag;
u = user flag
Figure 7.1.5. Flag Notation for Testing an Individual Flag
Examples:
X.z A.s Tests the system flags
of register A
C.u Tests the user flags of
register C
Q.v Tests the system flags
of the continuous
A--O, Q s, v or u output Q
Designates the continuous Designates the type of flag—
register that contains the flag s or v = system flag; u =user flag
Figure 7.1.6. Flag Notation for Testing All Flags
CB: 7-1-5
Example of a Logic Step for Testing an Individual Flag
Figure 7.1.7 shows a sample logic statement that tests a single flag that
indicates whether or not an AIB has a critical high alarm. The AIB value
is linked to register A. Flag p is tested for the status of the critical high
alarm for the AIB. If the AIB has a critical high alarm, flag p of the user
flags is on, and the logic step is on.
Displays the status of the flag to which

the logic step pertains:
· SF indicates a system flag
· UF indicates a user flag
Evaluating user flag p to determine
· .x identifies a specific flag whether the critical high alarm is on

Tag Descriptor
Addr =1F-98 Function PI Controller Plnt>0
>OIL |PV * |
UF.p=ON | * a= >A.u.p==1 |Mode>Auto
| * |
| * Set > |MsgP>*1
| * |Off
| *Clear> |
| * |-> ON
|---*----------------ACTIONS---------------------|
| * |
| * Rise> |
| * |
| * ON > |Rpt>None
| * |
| * Fall> |
| * |
| * OFF > |
+------------------------------------------------+
FULL CONFIG 1
User flag p of the source block is on; therefore, logic step a is on.
Figure 7.1.7. Testing an Individual Flag for a Critical High Alarm
CB: 7-1-6
Testing the Rise and Fall of an Individual Flag
Figure 7.1.8 shows a sample logic statement that tests the rise of a
single flag. This example tests user flag p in register A. To test the fall of
an individual flag, enter “fall” instead of “rise”. Registers A--O and Q are
tested in this manner.
Displays the status of the flag to which

the logic step pertains:
· SF indicates a system flag
· .x identifies a specific flag

Tag Descriptor
>OIL |PV * |
UF.p=ON | * a= >rise(A.u.p) |Mode>Auto
| * |
| * Set > |MsgP>*1
| * |Off
| *Clear> |
| * |-> ON
|---*----------------ACTIONS---------------------|
| * |
| * Rise> |
| * |
| * ON > |Rpt>None
| * |
| * Fall> |
| * |
| * OFF > |
+------------------------------------------------+
FULL CONFIG 1
User flag p of the source block is turned on; therefore, logic step a is on.
Figure 7.1.8. Testing the Rise in an Individual Flag
CB: 7-1-7
Binary and Hexadecimal Notation of Flags
Logic statements for testing all flags at one time may use binary or
hexadecimal notation to represent the flag bit value. Both the binary
notation and the hexadecimal notation in Figure 7.1.9 represent the
same value. Either type of notation can be used.
Binary Notation
When you use binary notation, a # symbol must precede the 16-bit
binary value and an underline must separate each group of four digits.
The upper screen in Figure 7.1.9 shows a logic statement using binary
notation. If the value of a particular bit is not required, you can use an x
to represent a bit value of either 0 or 1.
Hexadecimal Notation
When using hexadecimal notation, a $ symbol must precede the 4-bit

hexadecimal value. The lower screen in Figure 7.1.9 shows a logic
statement using hexadecimal notation.
CB: 7-1-8

Tag Descriptor
>OIL |PV * |
UF=0000 | * a= >A.u==#0010_0110_1001_0001 |Mode>Auto
| * |
| * Set > |MsgP>*1
| * |Off
| *Clear> |
| * |-> OFF
|---*----------------ACTIONS---------------------|
| * |
| * Rise> |
| * |
| * ON > |Rpt>None
| * |
| * Fall> |
| * |
| * OFF > |
+------------------------------------------------+
FULL CONFIG 1
Binary notation
Displayed as hexadecimal
Hexadecimal notation

Tag Descriptor
>OIL |PV * |
UF=0000 | * a= >A.u==$2691 |Mode>Auto
| * |
| * Set > |MsgP>*1
| * |Off
| *Clear> |
| * |-> OFF
|---*----------------ACTIONS---------------------|
| * |
| * Rise> |
| * |
| * ON > |Rpt>None
| * |
| * Fall> |
| * |
| * OFF > |
+------------------------------------------------+
FULL CONFIG 1
Figure 7.1.9. Using Binary or Hexadecimal Notation to Test All Flags
CB: 7-1-9
Example of a Logic Step for Testing All Flags at Once
Figure 7.1.10 shows a sample logic statement for testing all of the user
flags of register A to determine whether the block flags are on or off.
Displays the status of the flags to which

the logic step pertains: Evaluating all user flags, a-p, for
· SF indicates a system flag equality to zero (off).

Tag Descriptor
>OIL |PV * |
UF=0000 | * a= >A.u==$0000 |Mode>Auto
| * |
| * Set > |MsgP>*1
| * |Off
| *Clear> |
| * |-> ON
|---*----------------ACTIONS---------------------|
| * |
| * Rise> |
| * |
| * ON > |Rpt>None
| * |
| * Fall> |
| * |
| * OFF > |
+------------------------------------------------+
FULL CONFIG 1
User flags of the source block are off; therefore, logic step a is on.
Figure 7.1.10. Testing the On/Off Status of All Flags
CB: 7-1-10
CB: 7-2-1
Section 2:
Input and Output Block Flags
This section describes the input/output (I/O) flags, provides the I/O flag
bit representations, and explains how to test for I/O block flag values.
RS3: Using System Flags and User Flags Input and Output Block Flags
CB: 7-2-2
Transfer of Flags: I/O Block Linked to a ControlBlock
When an I/O block is linked to a ControlBlock, information about the I/O

block alarms, hold forward status, valid data status, and block mode is
continually passed to the ControlBlock. Figure 7.2.1 shows the transfer
of information between an I/O block and a ControlBlock. The transferred
information includes:
D System flags
D User flags
D An I/O block output value
All of the linked information, including the system flags and user flags,
resides in the destination ControlBlock register.
You test I/O block system flags and user flags in the destination
ControlBlock logic steps to provide information about the I/O block.
However, flags d (valid data) and g (hold forward) can only be tested as
system flags of the destination ControlBlock. For all I/O block types
except PLCBs, all flags other than d and g must be tested as user flags
of the destination ControlBlock for I/O block alarm information and block
mode. For PLCBs, user flags cannot be tested. (For more information,
see Section 5.)
You test the user flags for output blocks by linking the output block to a
ControlBlock variable and testing it in the same manner as an input
block.
The ControlBlock also contains alarm information for the linked input.
Test the ControlBlock system flags a--c, e--f, and h--p for alarm
information about the linked input.
Linked information
I/O Block ControlBlock
System Flags
I/O Block: X.s.d, X.s.g from source I/O block
ControlBlock: All other system flags developed
in receiving ControlBlock
User Flags
X.u.a -- X.u.p (for the I/O block)
Block Value
Figure 7.2.1. Transfer of Flags with an I/O Block Linked to a ControlBlock
CB: 7-2-3
I/O Block Flag Bit Representations
Table 7.2.1 lists the bit representations and descriptions of I/O block
system flags. Table 7.2.2 through Table 7.2.10 list the bit
representations and descriptions of I/O block user flags.
NOTE: Each evaluation cycle, the ControlBlock clears the valid data
flag for all registers expecting information from linked blocks.
Table 7.2.1. I/O Block System Flags
Letter Bit Representation Description
p 1xxx xxxx xxxx xxxx Critical high alarm

o x1xx xxxx xxxx xxxx Critical low alarm
n xx1x xxxx xxxx xxxx Advisory high alarm
m xxx1 xxxx xxxx xxxx Advisory low alarm
l xxxx 1xxx xxxx xxxx Rate of change alarm

k xxxx x1xx xxxx xxxx Critical high message
j xxxx xx1x xxxx xxxx Critical low message
i xxxx xxx1 xxxx xxxx Advisory high message
h xxxx xxxx 1xxx xxxx Advisory low message

g xxxx xxxx x1xx xxxx Hold forward
f xxxx xxxx xx1x xxxx Logic active
e xxxx xxxx xxx1 xxxx Tracking active
d* xxxx xxxx xxxx 1xxx Valid data

c xxxx xxxx xxxx x1xx Rate of change message
xxxx xxxx xxxx xx11 Unconfigured block
* When redundant controllers switch, valid data flag resets for one scan.
CB: 7-2-4
Table 7.2.2. Analog Input Block (AIB) User Flags
p 1xxx xxxx xxxx xxxx Critical high alarm active

o x1xx xxxx xxxx xxxx Critical low alarm active
xx1x xxxx xxxx xxxx Not assigned
m xxx1 xxxx xxxx xxxx Advisory high alarm active
l xxxx 1xxx xxxx xxxx Advisory low alarm active

k xxxx x1xx xxxx xxxx Default calibration alarm active
j xxxx xx1x xxxx xxxx Hardware high alarm active
i xxxx xxx1 xxxx xxxx Hardware low alarm active
h xxxx xxxx 1xxx xxxx Hardware misc alarm active

g xxxx xxxx x1xx xxxx Not usable
xxxx xxxx xx00 xxxx I/O Type FIC
xxxx xxxx xx01 xxxx I/O Type FIM
d xxxx xxxx xxxx 1xxx Not usable

xxxx xxxx xxxx x000 Manual mode
xxxx xxxx xxxx x001 Auto mode
Table 7.2.3. Analog Output Block (AOB) User Flags
111x xxxx xxxx xxxx Not assigned

m xxx1 xxxx xxxx xxxx Input configuration alarm
xxxx 1xxx xxxx xxxx Not assigned

k xxxx x1xx xxxx xxxx Default calibration alarm
j xxxx xx1x xxxx xxxx Invalid input alarm
xxxx xxx1 xxxx xxxx Not assigned
h xxxx xxxx 1xxx xxxx Hardware misc alarm


xxxx xxxx xxxx x010 Override mode
CB: 7-2-5
Table 7.2.4. Contact Input Block (CIB) and

Discrete Input Block (DIB) User Flags
p 1xxx xxxx xxxx xxxx Critical on alarm active

o x1xx xxxx xxxx xxxx Critical off alarm active
xx1x xxxx xxxx xxxx Not assigned
m xxx1 xxxx xxxx xxxx Advisory on alarm active
l xxxx 1xxx xxxx xxxx Advisory off alarm active

k xxxx x1xx xxxx xxxx Raw state
j xxxx xx1x xxxx xxxx Hardware on alarm active
i xxxx xxx1 xxxx xxxx Hardware off alarm active

f xxxx xxxx xx1x xxxx Output state
e xxxx xxxx xxx1 xxxx Filtered value

Table 7.2.5. Contact Output Block (COB) and Discrete Output

Block (DOB) User Flags
111x xxxx xxxx xxxx Not assigned

xxxx 11xx xxxx xxxx Not assigned

j xxxx xx1x xxxx xxxx Invalid input link
i xxxx xxx1 xxxx xxxx Value from input link

f xxxx xxxx xx1x xxxx Field value
e xxxx xxxx xxx1 xxxx Last field value

CB: 7-2-6
Table 7.2.6. Multiplexer Input Block (MIB) User Flags

n xx1x xxxx xxxx xxxx Critical rate alarm active

k xxxx x1xx xxxx xxxx Advisory rate alarm active

f xxxx xxxx xx1x xxxx Critical deviation alarm active
e xxxx xxxx xxx1 xxxx Advisory deviation alarm active

Table 7.2.7. Pulse Input/Output Block (PIOB) User Flags
p 1xxx xxxx xxxx xxxx Illegal PIO configuration

o x1xx xxxx xxxx xxxx Not assigned
n xx1x xxxx xxxx xxxx Not assigned
l xxxx 1xxx xxxx xxxx Invalid input alarm

k xxxx x1xx xxxx xxxx Counter is at or above target
j xxxx xx1x xxxx xxxx Counter is disabled
i xxxx xxx1 xxxx xxxx Input cutoff active

f xxxx xxxx xx1x xxxx Copy of input state
e xxxx xxxx xxx1 xxxx Not assigned

CB: 7-2-7
Table 7.2.8. Smart Transmitter Input Block (SIB) User Flags

p 1xxx xxxx xxxx xxxx FIC/Transmitter comm error

o x1xx xxxx xxxx xxxx Transmitter status failure
n xx1x xxxx xxxx xxxx Transmitter status warning
xxx1 xxxx xxxx xxxx Not assigned

k xxxx x1xx xxxx xxxx Default calibration alarm active


xxxx xxxx xxxx x010 Simulate mode
Table 7.2.9. HART Output Block (HOB) User Flags

p 1xxx xxxx xxxx xxxx Deviation alarm

o x1xx xxxx xxxx xxxx Field device status failure
n xx1x xxxx xxxx xxxx Field device status warning

k xxxx x1xx xxxx xxxx Default calibration alarm
j xxxx xx1x xxxx xxxx Invalid input alarm
xxxx xxx1 xxxx xxxx Not assigned


CB: 7-2-8
Table 7.2.10. Temperature Input Block (TIB) User Flags

xx1x xxxx xxxx xxxx Input configuration alarm

k xxxx x1xx xxxx xxxx Default calibration active for at
least 1 of the 8 calibration
ranges

xxxx xxxx xx11 xxxx Not assigned

CB: 7-2-9
Testing for I/O Block Flag Values
You can test for both the I/O block system flag values and user flag
values. The ControlBlock contains the I/O block system flags
d (valid data) and g (hold forward) and the ControlBlock link system
flags a--c, e--f, and h--p. The user flags contain the alarm status
information of the I/O block. Use the following sample expressions to
test for flags:
D X.s.d, Tests the status of I/O block system flags.
X.s.g
D X.s.z Where z=a--c, e--f, or h--p. Tests the status of a particular
ControlBlock linked input system flag. (For information on
I/O block system flags, see Table 7.2.1.)
D X.u Tests the status of all I/O block user flags.
D X.u.y Tests the status of a particular I/O block user flag.
NOTE: Do not test flags d and g as user flags; instead

test them as system flags. If you test d or g as user flags
from another controller and that controller disappears,
the test at the destination will incorrectly show the results
at the time the controller went down.
NOTE: You cannot test PLCB user flags. For information about testing
for the PLCB alarm information, see Section 5.
Figure 7.2.2 shows a sample logic statement that tests whether the I/O
block hold forward flag (system flag g) is set. The I/O block is linked to
register C. If the hold forward flag is set, logic step a is on.
CB: 7-2-10
Logic step a is on, indicating the hold

System flag g for forward flag is set and the output value
variable C is on. will hold if communication fails.

Tag Descriptor
>OIL |RS * |
SF.g=ON | * a= >C.s.g==1 |Mode>Auto
| * |
| * Set > |MsgP>*1
| * |Off
| *Clear> |
| * |-> ON
|---*----------------ACTIONS---------------------|
| * |
| * Rise> |
| * |
| * ON > |Rpt>None
| * |
| * Fall> |
| * |
| * OFF > |
+------------------------------------------------+
FULL CONFIG 1
Figure 7.2.2. Testing a System Flag for a Particular Value
CB: 7-3-1
Section 3:
ControlBlock Flags
This section describes the ControlBlock flags, explains how to test

ControlBlock flag values, provides some sample applications for flags,
and explains how to manipulate flags.
RS3: Using System Flags and User Flags ControlBlock Flags

CB: 7-3-2
Transfer of Flags
Flags provide information about a ControlBlock. This information varies,

depending on whether or not the ControlBlock is linked to another
ControlBlock.
ControlBlock Linked to a ControlBlock
When a ControlBlock is linked to another ControlBlock, information is

continually passed to the destination ControlBlock. Figure 7.3.1 shows
the transfer of information between two ControlBlocks. The information
includes system flags, user flags, and variable data. All of the linked
information, including the system flags and user flags, is stored in the
destination ControlBlock registers. Figure 7.3.2 shows an example of
some of the specific continuous output flag values passed between two
linked ControlBlocks. Figure 7.3.3 shows an example of some of the
specific continuous input flag values passed between two linked
ControlBlocks.
You can test ControlBlock system flags and user flags in the destination
ControlBlock logic steps to provide information about the source
ControlBlock or the linked input of the destination ControlBlock.
You can also set ControlBlock user flags in the destination ControlBlock
logic steps to particular values, overwriting the information about the
source ControlBlock.
System Flags
When two ControlBlocks are linked together, system flags of the source
ControlBlock contain alarm information for the source register. System
flags of the destination ControlBlock contain alarm information for the
destination register, and valid data and hold forward information from
the source register.

CB: 7-3-3
Linked Linked
I/O Block Information Source Information Destination
System Flags System Flags
I/O Block: Source CB:
Z.s.d, Z.s.g Z.s.d, Z.s.g
CB Link: Destination CB:
All others All others
User Flags
User Flags
Z.u.a -- Z.u.p Z.u.a -- Z.u.p
Block Value Variable
Figure 7.3.1. Transfer of Flags Between Two Linked ControlBlocks

CB: 7-3-4
User Flags
When two ControlBlocks are linked together, the information in the user
flags depends on how the blocks are linked.
D If you link the registers of a destination ControlBlock (B.u) to the
continuous output of a source ControlBlock (Q.u), the user flags
at the destination ControlBlock contain the discrete output states
for Q. See Figure 7.3.2.
If the source ControlBlock has logic configured, this is the
information that is passed to the destination ControlBlock. If no
logic is configured, there may be no information contained in the
source ControlBlock user flags that can be passed on to the
destination ControlBlock.
D If you link the registers of a destination ControlBlock (B.u) to the
continuous input of a source ControlBlock (A.u), the user flags at
the destination ControlBlock contain the same information as the
user flags of the source ControlBlock input. See Figure 7.3.3.
Note that if the source ControlBlock is linked to an I/O block, the
source ControlBlock user flags contain alarm information from
the I/O block user flags.
=1A--2 =1A--2
=1AB102
Linked Source Linked Destination
CIB Block Information
Information ControlBlock ControlBlock
B Q B
System Flags System Flags
I/O Block: Q.u=$0000 Source CB: Register B
Z.s.d, Z.s.g (discrete output Z.s.d, Z.s.g
states) B.u=$0000
Q=50.00% All others B=50.00%
All others
User Flags User Flags

Z.u.a -- Z.u.p Z.u.a -- Z.u.p
Figure 7.3.2. Example of Continuous Output Flags Between Two Linked ControlBlocks

CB: 7-3-5
=1AB101 =1A--1 =1A--6
AIB Block Linked Source Linked Destination

Information ControlBlock Information ControlBlock
A A B
System Flags Register A Register B
System Flags
A.u.p=1 B.u.p=1
I/O Block: A=60.00% Source CB: B=60.00%
Z.s.d, Z.s.g Z.s.d, Z.s.g
All others All others
User Flags User Flags

Z.u.a -- Z.u.p A.u.p=1

60.00% A=60.00%
Figure 7.3.3. Example of Continuous Input Flags Between Two Linked ControlBlocks

CB: 7-3-6
Within a ControlBlock
Even when a ControlBlock is not linked to another ControlBlock,

information is continually available from within the ControlBlock.
Figure 7.3.4 shows the information available within the system flags of a
ControlBlock.
You can test ControlBlock continuous output system flags individually or

as a group to provide information about a ControlBlock that is not linked
to any other ControlBlocks.
System Flags
D When tested individually using Q.t.x, the system flags of the

ControlBlock continuous output contain rate limit, output limit,
tracking, and ControlBlock mode information.
D When tested as a group using Q.v, the ControlBlock continuous
output system flags contain alarm, and ControlBlock mode
information.
=1A--8
ControlBlock
Continuous Output
System Flags
Q.t.a -- Q.t.p:
Rate limit, mode, tracking
Continuous Output
System Flags
Q.v:
Alarm, mode
Figure 7.3.4. Flags Within a ControlBlock

CB: 7-3-7
ControlBlock Flag Bit Representations
Table 7.3.1 lists the bit representations and descriptions of ControlBlock

system flags for continuous inputs A through O. Table 7.3.2 and
Table 7.3.3 list the bit representations and descriptions of ControlBlock
system flags for continuous output Q.
Table 7.3.1. ControlBlock System Flags for Continuous Inputs

A through O (Z.s and Z.s.x)
p 1xxx xxxx xxxx xxxx Critical high alarm

o x1xx xxxx xxxx xxxx Critical low alarm
n xx1x xxxx xxxx xxxx Advisory high alarm
m xxx1 xxxx xxxx xxxx Advisory low alarm
l xxxx 1xxx xxxx xxxx Rate-of-change alarm

k xxxx x1xx xxxx xxxx Critical high message
j xxxx xx1x xxxx xxxx Critical low message
i xxxx xxx1 xxxx xxxx Advisory high message
h xxxx xxxx 1xxx xxxx Advisory low message

g* xxxx xxxx x1xx xxxx Hold forward
f xxxx xxxx xx1x xxxx Logic active
d*(1) xxxx xxxx xxxx 1xxx Valid data

c xxxx xxxx xxxx x1xx Rate of change message
xxxx xxxx xxxx xx11 Unconfigured block
* These flags contain information about the source ControlBlock. All other
flags are developed in the destination ControlBlock based on events,
such as alarms or logic, that occur in the destination block.
(1) When redundant controllers switch, valid data flag resets for one scan.

CB: 7-3-8
Table 7.3.2. ControlBlock System Flags for Continuous Output Q (Q.t.x)*
p 1xxx xxxx xxxx xxxx Output high limit

o x1xx xxxx xxxx xxxx Output low limit
n xx1x xxxx xxxx xxxx Manual output change rate limit
m xxx1 xxxx xxxx xxxx Rate limit inhibit
l xxxx 1xxx xxxx xxxx Tracking flag VH (value is high lim for the output)
k xxxx x1xx xxxx xxxx Tracking flag VL (value is low lim for the output)
j xxxx xx1x xxxx xxxx Tracking flag QH (output must not go any higher)
i xxxx xxx1 xxxx xxxx Tracking flag QL (output must not go any lower)
h xxxx xxxx 1xxx xxxx Now—the block is evaluating this evaluation cycle
g xxxx xxxx x1xx xxxx Hold forward
f xxxx xxxx xx1x xxxx Logic active on the output
d xxxx xxxx xxxx 1xxx Not used

xxxx xxxx xxxx x101 Comp SP mode
xxxx xxxx xxxx x100 DDC mode
xxxx xxxx xxxx x011 Remote mode
xxxx xxxx xxxx x000 Local mode
* There is no Q.t function.

CB: 7-3-9
Table 7.3.3. ControlBlock System Flags for Continuous Output Q (Q.v)*
1xxx xxxx xxxx xxxx Critical high

x1xx xxxx xxxx xxxx Critical low
xx1x xxxx xxxx xxxx Alarm inhibit
xxx1 xxxx xxxx xxxx Advisory high
xxxx 1xxx xxxx xxxx Advisory low

xxxx x1xx xxxx xxxx Invalid function
xxxx xx1x xxxx xxxx Critical deviation
xxxx xxx1 xxxx xxxx Advisory deviation
xxxx xxxx 1xxx xxxx Insufficient inputs

xxxx xxxx x1xx xxxx Wrong input type
xxxx xxxx xx1x xxxx Logic problem
xxxx xxxx xxx1 xxxx Invalid track count
xxxx xxxx xxxx 1xxx Input configuration error

xxxx xxxx xxxx x101 Comp SP mode requested
xxxx xxxx xxxx x100 DDC mode requested
xxxx xxxx xxxx x011 Remote mode requested
xxxx xxxx xxxx x010 Auto mode requested
xxxx xxxx xxxx x001 Manual mode requested
xxxx xxxx xxxx x000 Local mode requested
* There is no Q.v.x function.

CB: 7-3-10
Testing for ControlBlock Flag Values
You can test for both the ControlBlock system flag values and user flag
values. Table 7.3.4 lists the ControlBlock flags for which you can test.
Table 7.3.4. ControlBlock Flags for Which You Can Test
Flag Type Flag Value Represents: You Can Test as:
Input value alarms, logic, and tracking System flags, using Z.s, Z.s.x
ControlBlock flags from a information
continuous input
Source block discrete output values User flags, using Z.u, Z.u.x
ControlBlock
Discrete output values (logic steps) User flags, using Q.u
discrete outputs
Alarm block mode requests System flags, using Q.v

ControlBlock output flags
within a block
Rate limit, block mode, and tracking System flags, using Q.t.x

CB: 7-3-11
Testing for ControlBlock Flags from a Continuous Input
When a ControlBlock is linked to another ControlBlock, you can test the

destination ControlBlock for the source continuous input ControlBlock
system and user flags.
Testing for System Flags
You can test for the source ControlBlock system flags d (valid data) and
g (hold forward) or the destination ControlBlock input system flags a--c,
e--f, or h--p for alarm information. Use either of the following expressions
to test for system flags:
D Z.s Tests the status of all ControlBlock system flags
D Z.s.y Tests the status of a particular ControlBlock system flag
Figure 7.3.5 shows a sample logic statement that tests whether the
ControlBlock hold forward flag (system flag g) is on. The ControlBlock of
register A is tested for equality to 1, to determine whether hold forward
is active.
System flag g is on and the logic step is on,

indicating that hold forward is active.

Tag Descriptor
>OIL |PV * |
SF.g=ON | * a= >A.s.g==1 |Mode>Auto
| * |
| * Set > |MsgP>*1
| * |Off
| *Clear> |
| * |-> ON
|---*----------------ACTIONS---------------------|
| * |
| * Rise> |
| * |
| * ON > |Rpt>None
| * |
| * Fall> |
| * |
| * OFF > |
+------------------------------------------------+
FULL CONFIG 1
Figure 7.3.5. Testing the Status of System Flag g for Hold Forward Status

CB: 7-3-12
Testing for User Flags
If the source ControlBlock continuous output Q is linked to the

destination ControlBlock, you can test for discrete outputs a through p.
When the source ControlBlock continuous inputs are linked to the
destination ControlBlock, you can test for the user flag states of the
source ControlBlock continuous input. You can test for one user flag or
all user flags. Use either of the following sample expressions to test for
user flags:
D Z.u Tests all ControlBlock user flags a--p
D Z.u.z Tests a particular ControlBlock user flag
NOTE: Do not test flags d and g as user flags; instead

test them as system flags. If you test d or g as user flags
from another controller and that controller disappears,
the test at the destination will incorrectly show the
results at the time the controller went down.
Figure 7.3.6 shows a sample logic statement that tests whether discrete
output e of the source ControlBlock is on. Logic step a tests for equality
to 1, to determine if user flag e of register A is on.
NOTE: If necessary, you can write logic to overwrite these flag values.
User flag e is on and the logic step is on,

indicating that discrete output e is on.

Tag Descriptor
>OIL |PV * |
UF.e=ON | * a= >A.u.e==1 |Mode>Auto
| * |
| * Set > |MsgP>*1
| * |Off
| *Clear> |
| * |-> ON
|---*----------------ACTIONS---------------------|
| * |
| * Rise> |
| * |
| * ON > |Rpt>None
| * |
| * Fall> |
| * |
| * OFF > |
+------------------------------------------------+
FULL CONFIG 1
Figure 7.3.6. Testing a User Flag

CB: 7-3-13
Testing for ControlBlock Discrete Outputs
You can test a ControlBlock for its discrete outputs using user flags:
D Q.u Tests all of the user flags of all ControlBlock logic steps
a--p
D Q.u.x Tests the user flags of a particular ControlBlock logic
step
Figure 7.3.7 shows a sample logic statement that tests the output state
of output a (logic step a), turning the step on as configured.
Figure 7.3.8 shows a sample logic statement that tests the output state
of all outputs (except step a), turning the step on as configured.
NOTE: If desired, you can write logic to overwrite these flag values.
The logic step is on,

indicating that discrete output a is on.

Tag Descriptor
+-------------------CONDITIONS-------------------+Step>p
|Q * |
UF.a=ON | * p= >Q.u.a==1 |Mode>Auto
| * |
| * Set > |MsgP>*1
| * |Off
| *Clear> |
| * |-> ON
|---*----------------ACTIONS---------------------|
| * |
| * Rise> |
| * |
| * ON > |Rpt>None
| * |
| * Fall> |
| * |
| * OFF > |
+------------------------------------------------+
FULL CONFIG 1
Figure 7.3.7. Testing for a Discrete Output

CB: 7-3-14
The logic step is on, indicating that all

discrete outputs except a are off.

Tag Descriptor
|Q * |
UF=0001 | * a= >Q.u==#0000_0000_0000_000x |Mode>Auto
| * |
| * Set > |MsgP>*1
| * |Off
| *Clear> |
| * |-> ON
|---*----------------ACTIONS---------------------|
| * |
| * Rise> |
| * |
| * ON > |Rpt>None
| * |
| * Fall> |
| * |
| * OFF > |
+------------------------------------------------+
FULL CONFIG 1
Figure 7.3.8. Testing for All Discrete Outputs (Except Step a)

CB: 7-3-15
Testing for ControlBlock Flags Within a Block
You can configure the ControlBlock system flags to test for the flags
within the ControlBlock:
D Q.v Tests all of the system flags of a ControlBlock (see
Table 7.3.3)
D Q.t.z Tests a particular system flag of a ControlBlock (see
Table 7.3.2)
Figure 7.3.9 shows a sample logic statement that tests the output
system flag a, manual mode, turning the step on as configured.
The logic step is on,

indicating that the ControlBlock mode is manual.

Tag Descriptor
|Q * |
SF.a=ON | * a= >Q.t.a==1 |Mode>Auto
| * |
| * Set > |MsgP>*1
| * |Off
| *Clear> |
| * |-> ON
|---*----------------ACTIONS---------------------|
| * |
| * Rise> |
| * |
| * ON > |Rpt>None
| * |
| * Fall> |
| * |
| * OFF > |
+------------------------------------------------+
Steps in Manual Block Mode> MANUAL
FULL CONFIG 1
Figure 7.3.9. Testing for an Output System Flag

CB: 7-3-16
Testing for ControlBlock Discrete Inputs
You can test, but not set, the ControlBlock discrete inputs @a through
@o, whether they are linked or not. Use the following sample
expression to test for discrete inputs:
D R.u Tests the discrete input state of all ControlBlock discrete
inputs @a--@o
R.u.x is not supported. To test an individual discrete input, you must

mask first. For example, to test for @b, use
R.u&$0002==$0002
Figure 7.3.10 shows sample logic statements that test the state of the
discrete inputs of a ControlBlock.
User flags are off; therefore, the logic step is off,

indicating that discrete inputs @a through @p are all off.

Tag Descriptor
In Register |R * |
UF=0000 | * a= >R.u==$0000 |Mode>Auto
| * |
| * Set > |MsgP>*1
| * |Off
| *Clear> |
| * |-> OFF
|---*----------------ACTIONS---------------------|
| * |
| * Rise> |
| * |
| * ON > |Rpt>None
| * |
| * Fall> |
| * |
| * OFF > |
+------------------------------------------------+
FULL CONFIG 1
Figure 7.3.10. Testing a User Flag for a Discrete Input State

CB: 7-3-17
Testing All Discrete Inputs Using the Discrete Output User

Flags
You can configure the ControlBlock discrete inputs to be copied to the

output user flags. This allows you to test the discrete inputs @a through
@o without configuring logic in each step.
Figure 7.3.11 shows the sample logic statements that test the state of
the discrete inputs.
NOTE: If this logic is configured in logic step a, the logic statements in

other logic steps can change the result. To prevent this, we recommend
that you configure the logic statement in step o and leave a comment in
step a referring to step o.
All of the R user flags are off;

therefore, the discrete outputs a through o are off.

Tag Descriptor
+-------------------CONDITIONS-------------------+Step>p
|Q * |
UF=0000 | * p= > |Mode>Auto
| * |
In Register |R * Set > |MsgP>*1
UF=0000 | * |Off
| *Clear> |
| * |-> OFF
|---*----------------ACTIONS---------------------|
| * |
| * Rise> |
| * |
| * ON >Q.u=R.u |Rpt>None
| * |
| * Fall> |
| * |
| * OFF >Q.u=R.u |
+------------------------------------------------+
FULL CONFIG 1
Figure 7.3.11. Testing All Discrete Inputs

CB: 7-3-18
Manipulating ControlBlock Flags
You can write logic steps including operators to manipulate ControlBlock

flags. Table 7.3.5 shows the operators you can use.
Table 7.3.5. Operators to Use with Flags
Operator Description Format Result
Sets each flag in the first register equal

to the value of the corresponding flag in
the second register.
Result: all flags are changed using only
one statement:
Assignment—sets one A.u.a=B.u.a
expression equal to the
= A.u=B.u A.u.b=B.u.b
value of another
expression A.u.c=B.u.c
.
.
.
A.u.p=B.u.p
Result:
A.u.a=B.u.a&C.u.a
Conditional and—true if A.u.b=B.u.b&C.u.b
& both expressions are true; A.u=B.u&C.u .
false otherwise .
.
A.u.p=B.u.p&C.u.p
Result:
A.u.a=B.u.a|C.u.a
Conditional inclusive or—
true if either one A.u.b=B.u.b|C.u.b
| expression or another is A.u=B.u|C.u .
true, or both expressions .
are true; false otherwise
.
A.u.p=B.u.p|C.u.p
Sets each flag in the first register equal

to the negative value of the
~ Unary logical negation A.u=~B.u
corresponding flag in the second
register, using only one statement.
Shifts each flag in the register to the

B.u=A.u>>positive right the number of places specified by
>> Right shift operator
integer the positive integer. The spaces to the
left are padded with zeros.

CB: 7-4-1
Section 4:
Console Flags
This section describes the console flags, provides the console flag bit
representations, and explains how to test for console flag values.
Transfer of Flags: Console Node Linked to a

ControlBlock
You can link a console node to a ControlBlock to test for console valid
data or alarm status information. Figure 7.4.1 shows the transfer of
system flag and user flag information when you link a console node to a
ControlBlock. All of the linked information resides in the ControlBlock
register.
Test system flags and user flags in the ControlBlock logic steps to
provide information about the console node. Flag d (valid data) can be
tested as a system flag. All other flags can be tested as user flags for
alarm status information.
CONSOLE NODE Linked Information CONTROLBLOCK

=28 =28A001
System Flags
X.s.d
User Flags
X.u.a -- X.u.p
Figure 7.4.1. Transfer of Flags Between a Console and a ControlBlock
RS3: Using System Flags and User Flags Console Flags

CB: 7-4-2
- To link a console node to a ControlBlock:

D On the Continuous Links screen, enter the node address as
=xA001, where x is the console node number.
Figure 7.4.2 shows that console node =28 is linked to ControlBlock
MCC--1.

Tag MCC-1 Descriptor
PV >
LS >
RS >
FF >
E > =28A001 Þno *Þ?.00 Þ?1.00 ?.00 Þ????????
F >
G >
Q Þ
Block Mode> LOCAL
CONFIG 1
Figure 7.4.2. Linking a Console Node to a ControlBlock

CB: 7-4-3
Console Flag Bit Representations
Table 7.4.1 lists and describes the console system flags and bit
representations. Table 7.4.2 lists the console user flags and bit
representations.
Table 7.4.1. Console System Flags
Valid data (Always set to 1 in the link

d xxxx xxxx xxxx 1xxx
message reply from the console)*
* By testing this flag, the ControlBlock can determine whether a console is

present.
Table 7.4.2. Console User Flags
p 1xxx xxxx xxxx xxxx Reserved

o x1xx xxxx xxxx xxxx Acknowledge button pressed
n xx1x xxxx xxxx xxxx Unacknowledged, cleared Batch alarm
m xxx1 xxxx xxxx xxxx Unacknowledged, active Batch alarm
l xxxx 1xxx xxxx xxxx Acknowledged, active hardware alarm

k xxxx x1xx xxxx xxxx Acknowledged, active critical alarm
j xxxx xx1x xxxx xxxx Acknowledged, active advisory alarm
i xxxx xxx1 xxxx xxxx Acknowledged, active system alarm
h xxxx xxxx 1xxx xxxx Unacknowledged, cleared hardware alarm

g xxxx xxxx x1xx xxxx Unacknowledged, cleared critical alarm
f xxxx xxxx xx1x xxxx Unacknowledged, cleared advisory alarm
e xxxx xxxx xxx1 xxxx Unacknowledged, cleared system alarm
d xxxx xxxx xxxx 1xxx Unacknowledged, active hardware alarm

c xxxx xxxx xxxx x1xx Unacknowledged, active critical alarm
b xxxx xxxx xxxx xx1x Unacknowledged, active advisory alarm
a xxxx xxxx xxxx xxx1 Unacknowledged, active system alarm

CB: 7-4-4
Testing for Console Flags
You can test for either the console node system flag d (valid data) or
any of the user flags, which contain alarm status information. Use any of
the following sample expressions to test for flags:
D X.s.d Tests the status of console system flag d for valid data
D X.u Tests the alarm status of all console user flags
D X.u.y Tests the alarm status of a particular console user flag
Figure 7.4.3 shows a sample logic statement that tests user flag l of
register E for equality to 1, to indicate whether an active hardware alarm
has been acknowledged.
User flag l is ON and the logic step is ON, indicating

that an active hardware alarm has been acknowledged.

Tag Descriptor
>=28A001 |E * |
UF.l=ON | * a= >E.u.l==1 |Mode>Auto
| * |
| * Set > |MsgP>*1
| * |Off
| *Clear> |
| * |-> ON
|---*----------------ACTIONS---------------------|
| * |
| * Rise> |
| * |
| * ON > |Rpt>None
| * |
| * Fall> |
| * |
| * OFF > |
+------------------------------------------------+
FULL CONFIG 1
Figure 7.4.3. Acknowledging an Active Hardware Alarm

CB: 7-5-1
Section 5:
Testing Block Status Bits
This section describes status bits, provides the system codes for testing
block status bits, and explains how status bits are used to test for block
conditions.
What are Status Bits?
Status bits represent binary pieces of information that are individually

linked to a ControlBlock input. Just as you can test system flags and
user flags for block status information, you can also use status bits to
test for status information of a block.
Because block status bits contain some of the same information as the
system flags, testing the status bits is an easy way to access these
system flags. The status bits for I/O blocks contain alarm information
and some of the system flags. The status bits for ControlBlocks contain
information such as the ControlBlock mode, output limits, and some of
the system flags.
You use a code, which contains two alphabetical letters or a question

mark followed by a number, to test block status bits. Configure the block
status bits on the Discrete Links screen. You can then use discrete
inputs in logic statements to test the block status bits.
RS3: Using System Flags and User Flags Testing Block Status Bits
CB: 7-5-2
Block Status Bit Codes
Table 7.5.1 provides a list of the system codes for testing status bits of
all I/O Blocks, except PLCBs. Table 7.5.2 provides a list of the system
codes for testing status bits of PLCBs. Table 7.5.3 provides a list of the
system codes for testing status bits of ControlBlocks.
Table 7.5.1. I/O Block Status Bit Codes
Code Description
AH Advisory high alarm
AL Advisory low alarm
CH Critical high alarm
CL Critical low alarm
HF Hold forward (value is not good)
HH Hardware high alarm
HL Hardware low alarm
Hardware miscellaneous alarm

HM
(faulty I/O hardware)
?1 System flag b*
?2 System flag c*
?3 System flag d—valid data*
?4 System flag e*
?6 System flag f*
?A System flag k*
?D System flag n*
* See Table 7.2.1 for a definition of the system flag.
CB: 7-5-3
Table 7.5.2. Programmable Logic Controller Block (PLCB)

Status Bit Codes
Code Description
AH System flag m—Input configuration alarm
AL System flag l—PLC write exception error
CH Wrong PLC port in redundant mode
CL System flag o—Too many PLCs configured
HF System flag g—Hold forward
HH System flag j—Invalid input alarm
HL Not assigned
HM System flag h—Hardware misc alarm active
System flag b—Mode ON=auto, fail

?1
OFF=simulate
System flag c—Mode ON=auto, fail

?2
OFF=simulate
?3 System flag d—Output valid
?4 System flag e—PLC read exception error
?6 System flag f—PLC address error
?A System flag k—Trying to write to a read only address
?D System flag n—First time block has been evaluated
CB: 7-5-4
Table 7.5.3. ControlBlock Status Bit Codes
Code Code Description
HF Hold forward
LA Logic active on the output
Block mode
must be linked to a continuous input
0=Local
MD 1=Manual
2=Auto
3=Remote
4=Computer
Now (this evaluation cycle)—the block is

NW
evaluating
OH Output high limited
OL Output low limited
RL Manual output change rate limit
System flag c—ControlBlock mode

?2 0=Local
1=DDC, Comp SP, Manual, Auto, or Remote
?3 System flag d—Valid data
?4 System flag e—Tracking active
System flag i—Tracking flag QL

?8
(output must not go any lower)
System flag j—Tracking flag QH

?9
(output must not go any higher)
System flag k—Tracking flag VL

?A
(value is a low limit for the output)
System flag l—Tracking flag VH

?B
(value is a high limit for the output)
?C System flag m—Rate limit inhibit
CB: 7-5-5
Testing Block Status
Write the logic to test a block status bit on the Discrete Links screen.
- To test the block status, type:
block tag / XX , where XX is the status bit code
For the system codes for testing block status bits, see the “Block Status
Bit Codes” earlier in this section.
Figure 7.5.1 shows a Discrete Links screen with the “Source” field
configured as TT101/HH. The figure shows that I/O block TT101 is
being tested to determine whether a hardware high alarm is currently
active in the block.
Figure 7.5.1 also shows the Discrete Diagram screen with a sample
logic statement for determining the status of the alarm. If @a=0, the
step is Off to indicate that the alarm is not active. If @a=1, the step is on
to indicate that the alarm is active.
CB DISCRETE LINKS 27-Nov-91 09:54:31

Tag Descriptor
@a> TT101/HH OFF @i>
@b> CB DISCRETE DIAGRAM 27-Nov-91 09:54:31

Tag Descriptor
@c> Addr =1A-01 Function DISC Discrete Block Plnt>0
@d> +-------------------CONDITIONS-------------------+Step>a
>TT101/HH | * |
@e> OFF Off | * a= >@a |Mode>Auto
| * |
@f> | * Set > |MsgP>*1
| * |Off
@g> | *Clear> |
| * |-> OFF
@h> |---*----------------ACTIONS---------------------|
| * |
| * Rise> |
FULL | * CONFIG
| 1
| * ON > |Rpt>None
| * |
| * Fall> |
| * |
| * OFF > |
+------------------------------------------------+
FULL CONFIG 1
@a is off, so the hardware high alarm is not active.
Figure 7.5.1. Testing the Status of a Hardware High Alarm
CB: 7-5-6
CB: 7-6-1
Section 6:
Hints for Configuring Flags
This section provides tips that are helpful when configuring flags.
Configuration Tips
Listed below are hints to help you when configuring flags.

- I/O block valid data and hold forward flags
These are some of the conditions that set an I/O block valid data or
hold forward flag to 1 or 0.
D I/O block valid data
The valid data flag is set to 1:
— If data is successfully being passed between Controller
Processors
— If the source Controller Processor is in Standby mode
— If the Coordinator Processor fails
— If the source Controller Processor is failing
D I/O block hold forward
The hold forward flag for an I/O block is set to 1:
— If the I/O block is in Manual mode
— If block configuration problems exist
— If block evaluation problems exist
— If hardware errors are present
— If hardware configuration problems exist
— If FIC hardware errors are present
— If A/D conversion errors are present
— If communication errors are present
— If the Controller Processor is in Standby mode
— If Multiplexer Controller Processor problems exist
RS3: Using System Flags and User Flags Hints for Configuring Flags
CB: 7-6-2
- ControlBlock valid data and hold forward flags

These are some of the conditions that set a ControlBlock valid data
or hold forward flag to 1 or 0.
D ControlBlock valid data
— If data is successfully being passed between Controller
Processors
— If the source Controller Processor is in Standby mode
— If the Coordinator Processor fails
— If the source Controller Processor is failing
D ControlBlock hold forward
The hold forward flag is set to 1:
— If the ControlBlock is in a non-normal mode, such as Local or
Manual
— If the ControlBlock is a default manual (MAN) function or
default discrete (DISC) function ControlBlock
RS3: Using System Flags and User Flags Hints for Configuring Flags
RS3t
Chapter 8:
Configuring Autotuning ControlBlocks
Section 1: Autotuning Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1-1

Guidelines for Autotuning ControlBlocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1-2
Using Autotuning ControlBlocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1-3
Special Autotuning Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1-4
Section 2: Configuring Autotuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2-1

Configuring the ATC Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2-3
Configuring General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2-4
Open Loop Stable Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2-7
Configuring Detailed Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2-8
Loop Damping Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2-12
Minimum Period Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2-13
Using an ATPID Block to Tune Another Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2-14
Section 3: Operating an Autotuning ControlBlock . . . . . . . . . . . . . . . . . . . . . 8-3-1

1. Begin Autotuning Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3-2
2. Enable Autotuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3-3
3. Create a Setpoint Disturbance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3-4
4. Wait for the Evaluation to Finish . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3-6
5. Enter New PID Values into the Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3-8
6. Repeat Disturbances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3-10
7a. Enter New PID Values into Nonvolatile Memory . . . . . . . . . . . . . . . . . . . . . . . . 8-3-11
7b. Disconnect ATPID Block and Resume Normal Operations . . . . . . . . . . . . . . . 8-3-12
Section 4: Autotune Event Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4-1
Section 5: Reference Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5-1

Message Pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5-1
Autotuning Evaluation States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5-2
Discrete Faceplate Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5-3
Continuous Links Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5-4
Discrete Links Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5-5
RS3: Configuring Autotuning ControlBlocks Contents

CB: ii
List of Figures
Figure Page
8.1.1 Autotuning ControlBlock as Part of a Control Loop . . . . . . . . . . . . . . . . 8-1-3
8.1.2 Autotuning ControlBlock Providing PID Parameters for Another
Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1-3
8.1.3 Accessing ATPID Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1-4
8.2.1 Autotuning ControlBlock Continuous Faceplate Screen . . . . . . . . . . . . 8-2-2
8.2.2 ATC Configuration Screen with General Configuration Information . . . 8-2-4
8.2.3 Example of How to Categorize a Process as Open Loop Stable
or Open Loop Unstable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2-7
8.2.4 ATC Configuration Screen with Detailed Configuration Information . . 8-2-8
8.2.5 “Loop Damping” Field Values and Various Loop Responses . . . . . . . . 8-2-12
8.2.6 Relationship Between “Loop Damping” and “Min Period” Fields . . . . . 8-2-13
8.2.7 Links Between an ATPID Block and a PID Block . . . . . . . . . . . . . . . . . . 8-2-14
8.3.1 Enabling Autotuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3-3
8.3.2 Creating a Setpoint Disturbance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3-5
8.3.3 Waiting for the Evaluation to Finish . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3-7
8.3.4 Discrete Faceplate PID Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3-8
8.3.5 Entering New PID Values into the ATPID Block from the Discrete
Faceplate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3-9
8.3.6 Entering all PID Values into the Block at Once . . . . . . . . . . . . . . . . . . . . 8-3-9
8.3.7 Entering PID Values into Nonvolatile Memory . . . . . . . . . . . . . . . . . . . . . 8-3-11
8.5.1 ATPID Block Default Discrete Faceplate Screen . . . . . . . . . . . . . . . . . . 8-5-3
8.5.2 ATPID Block Default Continuous Links Screens . . . . . . . . . . . . . . . . . . . 8-5-4
8.5.3 ATPID Block Default Discrete Links Screen . . . . . . . . . . . . . . . . . . . . . . 8-5-5

CB: iii
List of Tables
Table Page
8.2.1 ATC Configuration Screen General Configuration Information Fields 8-2-5
8.2.2 ATC Configuration Screen Detailed Configuration Information Fields 8-2-9
8.4.1 ATPID Event Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4-1
8.5.1 Autotuning ControlBlock Evaluation States . . . . . . . . . . . . . . . . . . . . . . . 8-5-2
8.5.2 Special ATPID Discrete Faceplate Screen Entries . . . . . . . . . . . . . . . . . 8-5-3

CB: 8-1-1
Section 1:
Autotuning Overview
The Autotuning ControlBlock (ATPID) is designed to emulate the

feedback procedure that a process control engineer uses to tune a
control loop. The user creates a setpoint change or a load disturbance
in the process. The Autotuning ControlBlock then observes the closed
loop response and determines new tuning parameters. This iterative
process is repeated until the desired response is obtained.
RS3: Configuring Autotuning ControlBlocks Autotuning Overview

CB: 8-1-2
Guidelines for Autotuning ControlBlocks
General guidelines apply to the use of the Autotuning ControlBlock:

D The Autotuning ControlBlock can be used with processes with
minor dead times and minor lags.
D The Autotuning ControlBlock can be used with non-minimum
phase processes, such as boiler level control.
D The Autotuning ControlBlock can only be used with 4--20 mA
devices.
D Since it typically takes a number of autotuning calculations to
tune a loop, the Autotuning ControlBlock does not perform well
for a loop with constantly changing dynamics.
D The Autotuning ControlBlock should not be used with processes
that have severe nonlinearization.
D The Autotuning ControlBlock should not be used with processes
that have severe valve hysteresis.
D Derivative control should not be used for first-order processes.
D If you want to use derivative control for a second- or higher-order
process, first tune the loop with derivative control disabled (PI
control). Then enable derivative control and tune the loop again.
D If you use the Autotuning ControlBlock to tune an open loop
unstable process to a load disturbance, and then you introduce a
setpoint disturbance, the ATPID block may produce an oscillatory
response. As a result, configure the ATPID block very
conservatively for this type of application.

CB: 8-1-3
Using Autotuning ControlBlocks
An Autotuning ControlBlock (ATPID) is a PID controller with autotuning

capabilities. You can use an Autotuning ControlBlock to control a loop
directly, as shown in Figure 8.1.1.
However, an Autotuning ControlBlock takes up many times more space

than a regular PID block. As a result, you may want to use an
Autotuning ControlBlock to provide PID parameters to other
ControlBlocks only when autotuning is needed, as shown in
Figure 8.1.2.
The ATPID block is part of the

control loop. In addition to being
a PID controller, it can also
calculate new PID parameters.
Autotuning
Field Field
Input Block ControlBlock Output Block
Device Device
(ATPID)
Figure 8.1.1. Autotuning ControlBlock as Part of a Control Loop
The ATPID block

Autotuning calculates new PID
ControlBlock parameters for the PID
(ATPID) block that is controlling
the process.
Field ControlBlock Field

Input Block Output Block
Device (PID) Device
Figure 8.1.2. Autotuning ControlBlock Providing PID Parameters for Another Block

CB: 8-1-4
Special Autotuning Screens
The ControlBlock screens for an Autotuning ControlBlock are very

similar to the screens for a PID block. An Autotuning ControlBlock
contains two additional screens:
D The ATC Configuration screen, which you use to configure
special autotuning parameters.
D The ATC Diagnostics screen, which Fisher-Rosemount personnel
use to evaluate the operation of the Autotuning ControlBlock.
Figure 8.1.3 shows how to access the special Autotuning ControlBlock

screens.
[PAGE BACK]
[PAGE BACK] [PAGE BACK]
ATPID Block ATPID Block ATC ATPID Block ATC Next Block
Continuous Configuration Diagnostics Continuous
Faceplate Screen Screen Screen Faceplate Screen
[PAGE AHEAD] [PAGE AHEAD] [PAGE AHEAD]
Figure 8.1.3. Accessing ATPID Screens

CB: 8-2-1
Section 2:
Configuring Autotuning
The Autotuning ControlBlock is a PID controller with autotuning

capabilities. This section describes configuration of an ATPID block to
perform autotuning.
RS3: Configuring Autotuning ControlBlocks Configuring Autotuning

CB: 8-2-2
Configuring the Continuous Faceplate Screen
Figure 8.2.1 shows the Continuous Faceplate screen for the ATPID
ControlBlock. The ATPID block is the same as the PID block except for
the following items:
D The block function type is ATPID.
D There is no “Opt” field (and no PID options such as gap, ratio, or
bias).
D The “PI Act” and “D Act” fields are not enterable.
D The “Prop Band”, “Integ Time”, and “Deriv Time” values appear
differently. The use of these values is explained in Section 3.
D The controller action (Reverse or Direct) must match the loop to
be tuned.
D The block mode must be set to AUTO.
- To call up initially: - To access other screens:

D [TAG] (tag or address) [ENTER] D [PAGE AHEAD] to see ATC
D [PAGE AHEAD] from previous block Configuration.
number Continuous Faceplate. D [PAGE BACK] to see Continuous
D [PAGE BACK] from next block Faceplate for previous block.
number Continuous Faceplate.
Function type is ATPID.

Shed
Tag > Desc > Mode>
NONE >OUT>A>B>C>D
SC>N +--------+
Addr Function >ATPID Auto Tuning PI Act>Err D Act>PV PV | .00 |
PV >.00 >.00 >Reverse RS | .00 |
LS >.00 Action FF | .00 |
RS >.00 100-+--------+
FF >.00 + |
Prop Band Integ Time Deriv Time 75-+ |
100. >100. 1. M >1. M 0. S >None + |
50-+ |
FF Gain >0. + |
25-+ |
OUT|| |
High Lim >100.00 High Lim >100.00 | |
+--------+
Block Mode>
AUTO
FULL CONFIG 1
Figure 8.2.1. Autotuning ControlBlock Continuous Faceplate Screen

CB: 8-2-3
Configuring the ATC Configuration Screen
You configure autotuning parameters on the ATC Configuration screen.

The ATC Configuration screen contains general and detailed
configuration information, and initially appears with only the general
configuration information. To see the detailed configuration information,
set the “Details Disp” field value to “yes”.

CB: 8-2-4
Configuring General Information
Figure 8.2.2 shows the ATC Configuration screen with only general
information. The highlighted field (“Open Loop Stable”) should be
configured before using the Autotuning ControlBlock. This field blinks
until configured.
The block mode must be set to AUTO.
Table 8.2.1 describes the general information fields.
- To call up: - To access other screens:

D [PAGE AHEAD] from Continuous Faceplate. D [PAGE AHEAD] to see ATC Diagnostics.
D [PAGE BACK] from ATC Diagnostics. D [PAGE BACK] to see Continuous Faceplate.
D [EXCH] to see Tuning Display number in
“Tuning Display” field.
ATC CONFIGURATION 27-Nov-91 10:27:30

Tag >atc-1 ATune Opt >SP
Enter All >Constants +--------+
TUNING LIMITS: >AutoTune|
Addr =22E-01 Event Type >0 Maximum | |
Gain >1000. >adj.gain|
INPUTS Value Units Tag Minimum |1. |
PV .00 Integ Tm >.5 S |= Gain |
FV .00 Maximum |0. |
+--------------------------------------------+ Deriv Tm >5. H |=NewGain|
| EVALUATION: | Max Change >adj. Ti |
+--------------------------------------------+ Mult >1200. |1. M |
Tuning Display >0 |= Ti Sec|
Details Disp >no |0. S |
Open Loop Stable >no |= New Ti|
Deriv Act >no >adj. Td |
| None |
|= Td Sec|
|0. S |
|= New Td|
+--------+
AUTO
FULL CONFIG 1
Figure 8.2.2. ATC Configuration Screen with General Configuration Information

CB: 8-2-5
Table 8.2.1. ATC Configuration Screen General Configuration Information Fields
Field Description Entries
Addr Address of the Autotuning block. Display Only
Specifies the type of disturbances that trigger an autotuning

evaluation.
SP — triggered by setpoint changes only. To produce a
setpoint disturbance with this option selected, you make direct
numeric entries on the faceplate. SP
ATune Opt
Load — triggered by load changes only. To produce a setpoint Load
disturbance with this option selected, you use the slewing SP+Load
buttons.
SP+Load — triggered by setpoint changes and by load
changes.
Specifies whether or not the derivative parameter is active on

Deriv Act yes, no
this controller.
Determines whether or not the detailed configuration

Details Disp yes, no
information is displayed on this screen.
To enter all newly calculated PID parameters into the block,

Enter All [ENTER]
press [ENTER] here. For more information, see Section 3.
Displays a summary of the autotuning evaluation. For more

Evaluation Display only
information, see Section 3.
Assigns an event type number to events generated by the

ATPID block.
Event Type 0—255
An entry of 0 indicates that events appear in event list 1.
For more information about event lists, see CC: 7.
Shows the values and units of the PV input and FV input

(filtered PV). The FV input is used for the autotuning
Inputs Display only
calculations. The FV input is also the ATPID block E input.
The tag indicates the tag of the PV source.
Specifies an advisory limit for the maximum change to the PID

parameters. If the limit is exceeded during an evaluation, an 1.—999999.
Max Change Mult event message is generated. A to O
The proportional parameter is always evaluated in terms of Default=1200
controller gain.
Specifies an advisory limit to the maximum value of the 0.—999999.

Maximum Deriv derivative time. If the limit is exceeded during an evaluation, A to O
Time
an event message is generated. Default=5.0 H
Specifies an advisory limit to the maximum value of the 0.—999999.

Maximum Gain proportional band parameter. This field is always specified in A to O
terms of controller gain. Default=1000.
NOTE: Bold entries indicate default values

CB: 8-2-6
Table 8.2.1. ATC Configuration Screen General Configuration Information Fields (continued)
Specifies an advisory limit to the minimum value of the integral 0.—999999.

Minimum Integ time. If the limit is exceeded during an evaluation, an event A to O
Tm
message is generated. Default=0.5 S
Categorizes the process as open loop stable or open loop

unstable. The ATPID block uses different algorithms,
depending on whether the process is configured as open loop
stable or open loop unstable.
yes, no
Open Loop Stable Enter yes if the process is open loop stable.
Enter no if the process is open loop unstable.
For more information about this field, see the “Open Loop
Stable Field” heading in this section.
Up to 16
alphanumeric
Specifies the block tag. This field is the same as the “Tag” characters, at least
Tag
field on the Continuous Faceplate screen. one of which must be
an alphabetical
character.
Specifies the number of a tuning display. If [EXCH] is pressed

Tuning Display from this screen, the specified tuning display is called up. 0—10
0 specifies that no tuning display is called up.

CB: 8-2-7
Open Loop Stable Field
You use the “Open Loop Stable” field to categorize the process as open
loop stable or open loop unstable. The ATPID block uses different
algorithms, depending on whether the process is configured as open
loop stable or open loop unstable. Figure 8.2.3 shows an example of a
way to categorize the process.
D If the loop is open loop stable, select “Open Loop StableÞyes”.
D If the loop is open loop unstable, select “Open Loop StableÞno”.
FIC-100 FIC-100
GPM GPM
72.04 72.04
72.00 72.00
1. As an example, a
PID controller for a
loop is put into
MANUAL mode. 60.00
50.00
2. The output is raised
to introduce a
%DEMAND disturbance to the %DEMAND
process. MANUAL
MANUAL
3. If the process does not stabilize,

it is open loop unstable.
If the process does stabilize,

it is open loop stable.
Figure 8.2.3. Example of How to Categorize a Process as Open Loop Stable or Open Loop Unstable

CB: 8-2-8
Configuring Detailed Information
Figure 8.2.4 shows the ATC Configuration screen with detailed

information. You should configure the shaded fields (“Loop Damping”
and “Minimum Period”) before using the Autotuning ControlBlock.
Table 8.2.2 describes the detailed information fields.
- To call up the ATC Configuration screen:

D [PAGE AHEAD] from Continuous faceplate.
D [PAGE BACK] from ATC Diagnostics.
- To access other screens:

D [PAGE AHEAD] to see ATC Diagnostics.
D [PAGE BACK] to see Continuous Faceplate.
D [EXCH] to see Tuning Display number in
“Tuning Display” field.
- To display detailed configuration information:

D Cursor to the “Details Disp” field and press
[ENTER]. The field displays “yes” and the
additional fields appear.

TUNING LIMITS: >AutoTune|
+--------------------------------------------+ Mult >1200. |1. M |
INITIAL PROCESS INPUTS: Tuning Display >0 |= Ti Sec|
PV Filter Process >0. S Details Disp >yes |0. S |
Constant >3.92699 Deadtime 0. S Open Loop Stable >no |= New Ti|
ATUNE TARGET RESPONSE CURVE: | None |
Loop Tuning Minimum Tuning |= Td Sec|
Damping >.25 Toler >18.0181 Period >5. S Sens >1. |0. S |
|= New Td|
ATUNE TRIGGER ADJUSTMENT: +--------+
Set Point Load Oscill Noise WAITING
Trig Mag >5.00 Trig Mag >5.00 Deadband >20.00 Mag >1.00
FULL CONFIG 1
Figure 8.2.4. ATC Configuration Screen with Detailed Configuration Information

CB: 8-2-9
Table 8.2.2. ATC Configuration Screen Detailed Configuration Information Fields
Specifies the load trigger magnitude, which is the minimum

FV deviation from the setpoint that triggers an autotuning
evaluation. This value must be larger than the “Noise Mag”
field entry and the actual process noise.
The “Load Trig Mag” value is in the same engineering units
0—999999
Load Trig Mag as the PV input.
A to O
The default value is 5.00% of the PV engineering units
range.
As an example, if the “Load Trig Mag” value is 5, then a
deviation of FV from the setpoint of 5 units or greater must
occur for an autotuning evaluation to begin.
Specifies the desired response curve of the loop to a

disturbance. When the ATPID block performs an
autotuning evaluation, it attempts to calculate PID .000001 — 1.0
Loop Damping parameters so that the loop response to a disturbance A to O
matches the value entered in this field. Default=0.25
For more information, see the “Loop Damping Field”
heading in this section.
Limits the speed of the loop response to a disturbance.

When the ATPID block calculates new PID values, it 8. S — 999999. H
attempts to match the response curve specified in the A to O
“Loop Damping” field. However, the calculated PID values
Minimum Period will not provide a response curve with peaks that occur any
faster than the “Minimum Period” field. Default=Varies
depending on Controller
For more information, see the “Minimum Period Field” Processor scan time.
heading in this section.
Specifies the amplitude of the loop noise (noise

magnitude). The ATPID block assumes that any amplitude
change less than or equal to the noise magnitude is a
result of the noise inherent to the loop and is ignored by
the autotuning calculations.
The “Noise Mag” value is in the same engineering units as 0—999999
Noise Mag the PV input. A to O
The default value is 1.00% of PV engineering units range.
As an example, if the “Noise Mag” value is 1, then any
deviation of FV from the setpoint of 1 unit or less is
assumed by the autotuning evaluation to be caused by
process noise.

CB: 8-2-10
Table 8.2.2. ATC Configuration Screen Detailed Configuration Information Fields (continued)
Specifies an oscillation deadband that is used by the

ATPID oscillation deadband watchdog. The oscillation
watchdog algorithm is active during an autotuning
evaluation. The oscillation watchdog monitors the PV value
(not the FV value) for oscillations.
If the PV value has a peak-to-peak oscillation greater than
the oscillation deadband, the oscillation watchdog acts to
reduce the oscillations by overdamping the loop response.
The action it takes is a reduction of the PID values of the
ATPID. The reduced values may or may not actually
reduce the oscillation, depending on whether: 0—999999
Oscill Deadband
D The ATPID is being used as part of the control loop A to O
(as in Figure 8.1.1)..
or
D The continuous inputs L,M, and N from the ATPID
are linked to the PID block (as in Figure 8.1.2 and
Figure 8.2.7)..
The “Oscillation Deadband” value is in the same
engineering units as the PV value.
Specifies the process deadtime used by the ATPID

calculations. The ATPID block automatically calculates a
deadtime for the process whenever a setpoint change
triggers an autotuning evaluation. The “Process Deadtime“
field is typically used when initially applying the ATPID
block to a process with a known deadtime to improve the
performance of the initial autotune evaluations.
The ATPID block only calculates a deadtime on setpoint 0. S—999999. H
Process triggers. If a deadtime exists for the process, the initial
Deadtime
evaluation should be triggered by a setpoint change, or the Default=0. S
user should initially enter an accurate value in this field.
There are two values for the “Process Deadtime” field: the
top number is the current value being used by the block,
and the bottom number is the value stored in nonvolatile
memory for the block. To enter the current value into
nonvolatile memory, cursor to the top field and press
[ENTER].

CB: 8-2-11
Table 8.2.2. ATC Configuration Screen Detailed Configuration Information Fields (continued)
Defines a filter for the PV input value. The filter is used to

minimize the effects of process noise. The filtered PV
value (FV) is the value used by the ATPID block during
autotuning evaluations. The lower the “PV Filter Constant”
value, the more the PV value is filtered.
--999999.—999999.
During the initial autotuning evaluation, this field is left (radians/s)
open to a large default value. When the ATPID block
PV Filter successfully completes an evaluation, a new “PV Filter
Constant Default=Varies
Constant” value is calculated. The user does not ordinarily
need to enter a value in this field. depending on Controller
Processor scan time.
However, if the initial autotuning evaluation does not
complete because of process noise, the user may want to
enter a small value in this field to start the evaluation with a
large amount of filtering. A value that is too small, however,
will mask closed loop effects.
Specifies the setpoint trigger magnitude, which is the

minimum setpoint change that triggers an autotuning
evaluation. The value must be larger than the “Noise Mag”
field entry and the actual process noise.
Set Point Trig The “Setpoint Trig Mag” value is in the same engineering 0—999999
Mag units as the PV input. A to O
As an example, if the “Setpoint Trig Mag” value is 5, then a
setpoint change of 5 units of the FV value or greater must
occur for an autotuning evaluation to begin.
Specifies a value that can be used to change the relative

conservative/aggressive response of the autotuning
evaluation. As the “Tuning Sens” value increases, the PID 0—2
changes are greater and the convergence to the target A to O
Tuning Sens performance is faster. As the “Tuning Sens” value
decreases, the PID changes are smaller and the
convergence to the target performance is slower. Default=1.0
The default value is 1.0, which is a neutral value.
Specifies a value that is an approximate tuning deadband. 0.000001—100

For example, a value of 20 specifies an approximate tuning A to O
Tuning Toler deadband of 20%; that is, when the response to a setpoint
disturbance is within about 20% of the target response,
then the target response has been achieved. Default=18.0181

CB: 8-2-12
Loop Damping Field
You use the “Loop Damping” field to specify the desired response curve
of the loop to a disturbance. When the ATPID block performs an
autotuning evaluation, it attempts to calculate PID parameters so that
the loop response to a disturbance matches the value entered in the
“Loop Damping” field. It may take several evaluations to obtain the
desired response.
The value entered in the “Loop Damping” field can range from 0 to 1. A
value of 0 represents sustained oscillation. A value of 1 represents
overdamping. Figure 8.2.5 shows response curves for varying “Loop
Damping” field values.
Loop DampingÞ0.0
Loop DampingÞ0.2
Loop DampingÞ0.4
Loop DampingÞ0.6
Loop DampingÞ1.0
NOTE: If an overdamped process with a fast
response time is desired, configure Loop
DampingÞ0.0 and use the “Minimum Period” field to
tune the loop.
Figure 8.2.5. “Loop Damping” Field Values and Various Loop Responses

CB: 8-2-13
Minimum Period Field
You use the “Minimum Period” field to limit the speed of the loop
response to a disturbance. The “Minimum Period” field can also be used
to limit wear on the loop output device. Figure 8.2.6 shows an example
of how the “Loop Damping” and “Minimum Period” fields are used by
the ATPID block.
Loop Damping field Minimum Period field

specifies response represents minimum period
curve between response curve peaks
When the ATPID block calculates new PID values, it tries to

match the response curve specified in the “Loop Damping”
field.
However, the calculated PID values will not provide a
response curve with peaks that occur any faster than the
“Minimum Period” field.
Figure 8.2.6. Relationship Between “Loop Damping” and “Min Period” Fields

CB: 8-2-14
Using an ATPID Block to Tune Another Block
If you use the ATPID ControlBlock to provide PID parameters for

another ControlBlock, then you must configure certain links between the
blocks. Figure 8.2.7 shows these links.
ATPID Mandatory Links

block
The continuous inputs A and B from the PID block
are linked to inputs A and B of the ATPID block.
CB CONTINUOUS LINKS
Function ATPID
INPUT SOURCE
PV PID/A
LS PID/B
RS
FF
E
F
G
PID Optional Links

block
The continuous inputs L (controller gain), M
(integral time), and N (derivative time) from the
ATPID block are linked to user-specified inputs
of the PID block.
CB CONTINUOUS LINKS
Function PID The ATPID parameters are
then used for the PID block.
INPUT SOURCE
H
I CB CONTINUOUS FACEPLATE
J
K Function PID
L ATPID/L
M ATPID/M
N ATPID/N Cont Gain®L Integ Time®M Deriv Time®N
O
Figure 8.2.7. Links Between an ATPID Block and a PID Block

CB: 8-3-1
Section 3:
Operating an Autotuning ControlBlock
This section describes a typical operating sequence for using an

Autotuning ControlBlock to tune a PID loop. The operating sequence
steps are listed below.
1. Begin autotuning session.
2. Enable autotuning.
3. Create a setpoint disturbance.
4. Wait for the evaluation to finish.
5. Enter new PID values into the block.
6. Repeat disturbances.
7. Do one of the following:
a. (If ATPID block is part of control loop)
Enter final PID values into nonvolatile memory.
or
b. (If ATPID block is being used to tune another block)
Disconnect ATPID block and resume normal operations.
RS3: Configuring Autotuning ControlBlocks Operating an Autotuning ControlBlock

CB: 8-3-2
1. Begin Autotuning Session
Before you enable autotuning, complete these steps:

1. Enter the appropriate option that should appear in the “Open
Loop Stable” field.
2. Ensure the PV-SP error is less than 1/2 of the smaller of the “Set
Point Trig Mag” and “Load Trig Mag” field values. If the default
values for these fields are used, then the PV-SP error must be
less than 2.5% of the PV value.
3. Specify “Deriv Act®no” on the ATC Configuration screen for the
first evaluation. If you want to use derivative control for a second-
or higher-order process, first tune the loop with derivative control
disabled (PI control). Then, enable derivative control and tune the
loop again.
4. Specify “ATune Opt®SP” on the ATC Configuration screen for at
least the first evaluation. The ATPID block only calculates a
deadtime on setpoint triggers. If a deadtime exists for the
process, the initial evaluation should be triggered by a setpoint
change, or the user should initially enter an accurate value in the
“Process Deadtime” field.
5. Assign autotune event messages to an event list with the “Event
Type” field. The default value of “Event TypeÞ0” indicates that
autotune messages appear in event list 1. For more information
about configuring event lists, see CC: 7.
6. Set up a method of monitoring the process using trending, tuning
displays, or some other means.
7. Enter the appropriate loop damping and minimum period on the
ATC Configuration screen. (See Figure 8.3.1.)
If you are using an ATPID block to tune another block (as in
Figure 8.1.2), complete these additional steps before enabling
autotuning:
1. Link PV and LS of the PID block to be tuned to the ATPID.
2. Record present PID values for future reference. Enter the values
into the ATPID block for the first evaluation.
3. (Optional) Link the ATPID L, M, and N registers to the PID block
links and faceplate. See “Oscillation Deadband” in Table 8.2.2 for
more information on the effects of links L, M, and N.
4. Observe the action of the block to be tuned (either direct or
reverse). Use the same action for the ATPID.
5. Ensure both ATPID and PID blocks are in AUTO mode.
6. On the block to be tuned, ensure the local setpoint is operator
enterable. If another link is configured, remove the link
temporarily while using autotuning. Record the link and reconnect
it after the tuning session is complete.

CB: 8-3-3
2. Enable Autotuning
After completing all preliminary steps, enable autotuning as shown in

Figure 8.3.1.
- To enable autotuning:
D Cursor to the top line of the discrete faceplate and press [ENTER].
The line changes from “>AutoTune” to “>AUTOTUNE”
to show that autotuning is enabled.

TUNING LIMITS: >AUTOTUNE|
+--------------------------------------------+ Mult >1200. |1. M |
PV Filter Process >0. S Details Disp >yes |0. S |
ATUNE TARGET RESPONSE CURVE: | None |
Damping >.25 Toler >18.0181 Period >5. S Sens >1. |0. S |
|= New Td|
FULL CONFIG 1
Figure 8.3.1. Enabling Autotuning

CB: 8-3-4
3. Create a Setpoint Disturbance
After you have enabled autotuning, you need to create a setpoint

disturbance. The Autotuning ControlBlock uses the response of the loop
to the disturbance to calculate new PID parameters and determine
deadtime. The new PID parameters attempt to provide a loop response
that meets the requirements of the “Loop Damping” and “Minimum
Period” fields.
The setpoint disturbance must be introduced from the Continuous

Faceplate screen or with the [LSP/B] button, as shown in Figure 8.3.2.
The slewing buttons cannot be used.
NOTE: Producing a setpoint disturbance with the slewing buttons will

only be successful when you have selected “Load” as the option in the
“ATune Opt” field. If you selected the “SP” option, only the direct
numeric entry may be used, since slewing will cause the the evaluation
to abort with a “setpoint retrigger” message.

CB: 8-3-5

Shed
Tag > atc-1 Desc > Mode> NONE >OUT>A>B>C>D
SC>N +--------+
PV >60.54 >.00 >Reverse RS | .00 |
LS >50.00 Action FF | .00 |
RS >.00 100-+--------+
FF >.00 + |
100. >100. 1. M >1. M 0. S >None + |
50-+ |
You can change the setpoint from the

Continuous Faceplate screen.
CONTINUOUS
SUPERVISORY
COMPUTER
>50.00
You can also change the
setpoint by pressing the
DEMAND [LSP/B] button,
60.54 LSP R
60.00 typing a new setpoint at the B E
top of the continuous M
faceplate, and pressing RATIO O
[ENTER]. BIAS T
E
AUTO
19.20
OUTPUT
%OPEN
OPERATOR
AUTO
Figure 8.3.2. Creating a Setpoint Disturbance

CB: 8-3-6
4. Wait for the Evaluation to Finish
After you have created a setpoint disturbance, an autotuning evaluation

begins. The autotuning evaluation status is displayed on the ATC
Configuration and ATC Detail screens directly below the faceplate
(where the block mode is usually displayed), as shown in Figure 8.3.3.
For more information about autotuning evaluation status, see Section 5.
The Evaluation box on the ATC Configuration screen displays a short

description of the result of the autotuning evaluation.
Also, any event messages that occur as a result of the autotuning

evaluation are listed in the event list specified in the “Event Type” field
on the ATC Configuration screen (“Event TypeÞ0” puts messages into
event list 1). Call up the associated event list to view the autotuning
messages. For more information about autotuning messages, see
Section 4.
NOTE: You can manually abort an evaluation by toggling off autotuning

on the discrete faceplate.

CB: 8-3-7
Displays a short description of the results of the autotuning evaluation. If more than one
message is active for an evaluation, the highest priority message is displayed. The
messages are listed in priority order.
Aborted= The evaluation was aborted.
Oscillation Detected= Oscillations in the process triggered the ATPID oscillation
watchdog. The PID parameters may have been changed in
response to the oscillation.
Param Limit Exceeded= The evaluation was successful and new PID parameters
may have been calculated. However, one or more of the
parameters may exceed the specified tuning limits.
Successful= The evaluation was successful and new PID parameters
may have been calculated.
No New PID Changes= The evaluation was successful and the process response
was within user-specified parameters. No new PID values
have been calculated.
Tag >atc-1 ATune Opt >SP Enter All >Constants +--------+

INPUTS Value Units Tag Minimum |xxxxxx |
FV .00 Maximum |xxxxxx |
+--------------------------------------------+ Mult >1200. |xxxxxx |
PV Filter Process >0. S Details Disp >yes |xxxxxx |
ATUNE TARGET RESPONSE CURVE: |xxxxxx |
Damping >.25 Toler >18.0181 Period >5. S Sens >1. |xxxxxx |
|= New Td|
FULL CONFIG 1
Autotuning evaluation status

1. When an autotuning evaluation begins, the status changes from
Waiting to Pause.
2. As the evaluation continues, different status messages are
displayed.
3. When the evaluation is complete, the Waiting status appears again,
and a message appears in the Evaluation field.
4. You can call up the appropriate event list to view autotuning event
messages.
Figure 8.3.3. Waiting for the Evaluation to Finish

CB: 8-3-8
5. Enter New PID Values into the Block
If the autotuning evaluation was successful, then it may be desirable to

enter the newly calculated PID values into the ATPID block. The current
and newly calculated PID values are displayed on the discrete
faceplate, as shown in Figure 8.3.4.
You can enter new PID values on the ATC Configuration screen with the
discrete faceplate (as shown in Figure 8.3.5) or with the “Enter All
Constants” field (as shown in Figure 8.3.6).
If the ATPID is part of the control loop (as in Figure 8.1.1), the new
values will be used for subsequent evaluation.
If the ATPID is tuning another block (as in Figure 8.1.2), the new values
will be automatically entered into the PID block if L, M, and N are linked.
You must enter the new values into the PID block if L, M, and N are not
linked.
>AUTOTUNE
>adj.gain
Current controller gain value xx
Gain
New controller gain value xx
NewGain
>adj. Ti
xx Current integral time value
Ti Sec
xx New integral time value
New Ti
>adj. Td
Current derivative time value xx
Td Sec
New derivative time value xx
New Td
Figure 8.3.4. Discrete Faceplate PID Values

CB: 8-3-9
>AUTOTUNE
To enter the new controller gain value, >adj.gain
cursor to this line and press [ENTER]. xxxxxx
Gain
xxxxxx
New Gain
To enter the new integral time value, >adj. Ti
Ti Sec
xxxxxx
New Ti
To enter the new derivative time value, >adj. Td
Td Sec
xxxxxx
New Td
Figure 8.3.5. Entering New PID Values into the ATPID Block from the Discrete Faceplate
To enter all new PID values at once, cursor to

this field and press [ENTER].

INPUTS Value Units Tag Minimum |xxxxxx |
FV .00 Maximum |xxxxxx |
+--------------------------------------------+ Mult >1200. |xxxxxx |
PV Filter Process >0. S Details Disp >yes |xxxxxx |
ATUNE TARGET RESPONSE CURVE: |xxxxxx |
Damping >.25 Toler >18.0181 Period >5. S Sens >1. |xxxxxx |
|= New Td|
FULL CONFIG 1
Figure 8.3.6. Entering all PID Values into the Block at Once

CB: 8-3-10
6. Repeat Disturbances
You can trigger autotuning evaluations by repeating steps 3, 4, and 5

(create a disturbance, wait for the evaluation to complete, and enter
new PID values) as often as needed to achieve the desired loop
response.
You may want to enable derivative control for subsequent evaluations.

You may also want to change your autotune option to “Load” changes or
“Sp + Load” changes to trigger subsequent evaluations.

CB: 8-3-11
7a. Enter New PID Values into Nonvolatile Memory
If the ATPID block is part of the control loop, follow these steps. If you
are using the ATPID block to tune another block, follow the steps in
section “7b. Disconnect ATPID Block and Resume Normal Operations”.
In a PID ControlBlock, the PID values are always stored in nonvolatile
memory. In an ATPID ControlBlock, however, the newly calculated PID
values are not stored in nonvolatile memory, even after entering the new
values into the block (step 5). The ATPID block requires you to enter
new PID values into nonvolatile memory manually.
This ATPID characteristic affects you in the following instances:
D If disk and tape operations are performed (for example, saving a
configuration), the PID values in nonvolatile memory are used for
the block.
D If the Controller Processor is restarted, the block is restarted with
the PID values that were stored in nonvolatile memory. The other
PID values in the ATPID block are lost.
Figure 8.3.7 shows how to enter PID values into nonvolatile memory.
The left number is the The right number is the To enter a PID value into
value stored in nonvolatile value currently being used nonvolatile memory, cursor
memory. by the block. to the value and press
[ENTER].

Shed
Tag > atc-1 Desc > Mode>
NONE >OUT>A>B>C>D
SC>N +--------+
PV >.00 >.00 >Reverse RS | .00 |
LS >.00 Action FF | .00 |
RS >.00 100-+--------+
FF >.00 + |
100. >100. 1. M >1.5 M 0. S >None + |
50-+ |
FF Gain >0. + |
25-+ |
OUT|| |
High Lim >100.00 High Lim >100.00 | |
+--------+
Block Mode> LOCAL
FULL CONFIG 1
Figure 8.3.7. Entering PID Values into Nonvolatile Memory

CB: 8-3-12
7b. Disconnect ATPID Block and Resume Normal

Operations
If you are using the ATPID block to tune another block, follow these
steps. If the ATPID block is part of the control loop, follow the steps in
section “7a. Enter Final PID Values into Nonvolatile Memory”.
When you are satisfied with the response used for the last evaluation,
follow these steps:
1. If you used L, M, and N to bring PID values to the tuned block,
enter the gain, integral time, and derivative time on the tuned
block faceplate. This will replace links L, M, and N.
2. If you used L, M, and N to bring PID values to the tuned block,
delete the ATPID L, M, and N links from the Block Links screen of
the tuned block.
3. If you previously changed the local setpoint to operator entry,
re-establish the local setpoint link to the tuned block.
4. Delete the PV and LS of the tuned block from the ATPID.

CB: 8-4-1
Section 4:
Autotune Event Messages
This section lists the event messages that can appear as a result of
autotuning evaluations. You assign autotune event messages to an
event type with the “Event Type” field on the ATC Configuration screen.
You assign event types to event lists on the Event List Configuration
screen. For more information about event lists, see CC: 7.
Table 8.4.1 lists the ATPID messages.
Table 8.4.1. ATPID Event Messages
Event Message Meaning
Evaluation Aborted: the evaluation aborted because the

ABORT Deviation Large at
FV-SP deviation was too large. Another disturbance may have
End Loc1
occurred during the evaluation.

ABORT Faulty Peak Time
process response to the disturbance did not meet the ATPID
Combination
requirements.

ABORT Illegal Combination
integral time value was not greater than 4 times the derivative
Ti & Td
time value.

ABORT Kalman Slope Large process response to the disturbance was too fast for the
ATPID requirements.
Evaluation Aborted: the evaluation aborted because the initial

ABORT Kalman Slope
Negative
requirements.
Evaluation Aborted: the evaluation aborted because the initial

ABORT Kalman State
Unknown
requirements.

ABORT Kalmn Crossed Zero
process response to the disturbance was too fast for the
Cnt <6
ATPID requirements.

ABORT Newton Raphson ATPID evaluation was unable to predict the closed loop
Failure bandwidth of the loop. Another disturbance may have
occurred during the evaluation.
RS3: Configuring Autotuning ControlBlocks Autotune Event Messages

CB: 8-4-2

ABORT OmegaN1 Out
Range Kalman Slope
requirements.

ABORT Period Out Range
Kalman Slope
requirements.
Evaluation Aborted: the evaluation aborted because another

ABORT Setpoint Retrigger
setpoint or load trigger occurred during the evaluation.

ABORT Third Peak Larger
First Peak
requirements.
Evaluation Finished—Successful—No New PID Changes:

the evaluation finished and the process response was within
Bypass
the user-specified parameters. No new PID values have been
calculated.

BYPASS: Phase Margin the evaluation finished and the process response was within
Within Deadband the user-specified parameters. No new PID values have been
calculated.

BYPASS: Unstable D_Active the evaluation finished and the process response was within
cpm>.90 the user-specified parameters. No new PID values have been
calculated.

BYPASS: Unstable cpm>.75, the evaluation finished and the process response was within
pmerr Neg the user-specified parameters. No new PID values have been
calculated.

BYPASS: Unstable, Ovrdmp, the evaluation finished and the process response was within
Ldeval the user-specified parameters. No new PID values have been
calculated.
Computed Derivative Time The ATPID calculated a new derivative time parameter.
Computed Gain The ATPID calculated a new controller gain parameter.
Computed Integral Time The ATPID calculated a new integral time parameter.
Evaluation Finished—Param Limit Exceeded: the evaluation

finished, but the process response was not within the
Derivative Time Delta Limit user-specified parameters because the “Max Change Mult”
field value was reached for the derivative time parameter. New
PID values may have been calculated.

CB: 8-4-3

Derivative Time Limit user-specified parameters because the “Max Deriv Tm” field
value was reached. New PID values may have been
calculated.

Gain Delta Limit user-specified parameters because the “Max Change Mult”
field value was reached for the controller gain parameter. New

Gain Limit
user-specified parameters because the “Max Gain” field value
was reached. New PID values may have been calculated.

Integral Time Delta Limit user-specified parameters because the “Max Change Mult”
field value was reached for the integral time parameter. New

Integral Time Limit user-specified parameters because the “Max Integ Tm” field
value was reached. New PID values may have been
calculated.
Evaluation Finished—Successful: the evaluation finished, but

OmegaN2 Low the process response was not as fast as desired. New PID
values may have been calculated.
Oscillations in the process triggered the ATPID oscillation

watchdog. The PID parameters may have been changed in
OSCILLATION DETECTED
response to the oscillation. Subsequent messages will appear
that list the new PID parameters.

Oscillation Detected: Actual
watchdog. The oscillation watchdog has changed the
Derivative
derivative time to the value shown in this message.

watchdog. The oscillation watchdog has changed the
Gain
controller gain to the value shown in this message.

watchdog. The oscillation watchdog has changed the integral
Integral
time to the value shown in this message.

CB: 8-4-4

CB: 8-5-1
Section 5:
Reference Information
This section provides reference information about the ATPID block,

including preconfigured message pairs, evaluation states, and some
default screens.
Message Pairs
User message pairs 151 through 155 are preconfigured to be used by

ATPID blocks.
RS3: Configuring Autotuning ControlBlocks Reference Information

CB: 8-5-2
Autotuning Evaluation States
When an autotuning evaluation is triggered, the evaluation state is

displayed below the faceplate instead of the block mode. Table 8.5.1
lists the autotune evaluation states in the order that they typically occur.
Table 8.5.1. Autotuning ControlBlock Evaluation States
Phase ATPID Action
Waiting Waiting for an autotune evaluation trigger.
Locate 0 Determining size of load disturbance (if present).
Locate 1 Determining first peak magnitude and time.
Locate 2 Determining second peak magnitude and time.
Locate 3 Determining third peak magnitude and time.
Locate 4 Determining fourth peak magnitude and time.
Calc 1 If overdamped, performing intermediate computations.
Calc 2 Performing intermediate computations.
Calc 3 Performing intermediate computations.
Calc 4 Computing new Ti, gain and Td.
Pause Waiting for evaluation cycle time to expire and for deviation to
be near zero.
Waiting Waiting for an autotune evaluation trigger.

CB: 8-5-3
Discrete Faceplate Screen
Figure 8.5.1 shows the ATPID block default Discrete Faceplate screen.
Table 8.5.2 lists special ATPID entries for the screen.

1 >AutoTune|
Addr =1A-01 Function PID Controller 2 | |
3 >adj.gain|
1>@a 2> 3>@c 4>/ag 5>/%ag 4 |1. |
*TOGGLE *M ON 5 |= Gain |
6 |0. |
7 |=NewGain|
6>/cg 7>/%cg 8>@d 9>/ati 10>/%ati 8 >adj. Ti |
*M ON 9 |1. M |
10 |= Ti Sec|
11 |0. S |
11>/cti 12>/%cti 13>@e 14>/atd 15>/%atd 12 |= New Ti|
*M ON 13 >adj. Td |
14 | None |
15 |= Td Sec|
16>/ctd 17>/%ctd Overview > Unit 1> 2> 3> 16 |0. S |
17 |= New Td|
FULL CONFIG 1
Figure 8.5.1. ATPID Block Default Discrete Faceplate Screen
Table 8.5.2. Special ATPID Discrete Faceplate Screen Entries
Entry Faceplate Display Entry Faceplate Display
/ag Current controller gain /%ag “ Gain”
/cg New calculated controller gain /%cg “ NewGain”
/ati Current integral time /%ati “ Ti Sec”
/cti New calculated integral time /%cti “ New Ti”
/atd Current derivative time /%atd “ Td Sec”
/ctd New calculated derivative time /%ctd “ New Td”
/phs Current autotune evaluation status /%phs “ Phase”

CB: 8-5-4
Continuous Links Screens
Figure 8.5.2 shows the default ATPID block Continuous Links screens.
CB CONTINUOUS LINKS 23-Jun-92 11:47:12

Tag Descriptor
Addr Function ATPID Auto Tuning
PV >*ENTRY Þ.00 Þ100.00 >.00 Þ% P.V.
LS >*ENTRY PVÞ.00 Þ100.00 >.00 Þ% P.V.
RS >*ENTRY Þ.00 Þ100.00 >.00 Þ
FF >*ENTRY Þ.00 Þ100.00 >.00 Þ
E >*VALUE Þ.00 Þ100.00 Þ.00 Þ% F.V.
F >*NONE Þ.00 Þ100.00 Þ.00 Þ
G >*NONE Þ.00 Þ100.00 Þ.00 Þ
Q Þ.00 Þ100.00 >.00 Þ
CONFIG 1
CB CONTINUOUS LINKS 23-Jun-92 11:47:12

Tag Descriptor
Addr Function ATPID Auto Tuning
H >*NONE Þ.0000 Þ1.0000 Þ.0000 Þ
I >*NONE Þ.0000 Þ1.0000 Þ.0000 Þ
J >*NONE Þ.0000 Þ1.0000 Þ.0000 Þ
K >*NONE Þ.0000 Þ1.0000 Þ.0000 Þ
L >*VALUE Þ.0000 Þ1.0000 Þ1.0000 ÞGain
M >*VALUE Þ.0000 Þ1.0000 Þ60.0000 ÞTi Sec
N >*VALUE Þ.0000 Þ1.0000 Þ.0000 ÞTd Sec
O >*VALUE Þ.0000 Þ1.0000 Þ.0000 ÞPM Rad
CONFIG 1
Figure 8.5.2. ATPID Block Default Continuous Links Screens

CB: 8-5-5
Discrete Links Screen
Figure 8.5.3 shows the ATPID block default Discrete Links screen.
CB DISCRETE LINKS 02-Oct-89 15:41:07

Addr =01A-01 Function Þ ATPID Auto Tuning
@a >*TOGGLE Þ151 >AutoTune @i >*OFF Þ*1 OFF
@b >*TOGGLE Þ152 >AutoEntr @j >*OFF Þ*1 OFF
@c >*M ON Þ153 >adj.gain @j >*OFF Þ*1 OFF
@d >*M ON Þ154 >adj. Ti @l >*OFF Þ*1 OFF
@e >*M ON Þ155 >adj. Td @m >*OFF Þ*1 OFF
@f >*M ON Þ*33 > reset @n >*OFF Þ*1 OFF
@g >*OFF Þ*1 OFF @o >*VALUE Þ*1 OFF
@h >*OFF Þ*1 OFF
Block Mode> AUTO
CONFIG 1
Figure 8.5.3. ATPID Block Default Discrete Links Screen

CB: 8-5-6

RS3t
Chapter 9:
Data Compression
Section 1: Introduction to Data Compression . . . . . . . . . . . . . . . . . . . . . . . . . 9-1-1

What is Data Compression? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1-1
Analog Data Compression Algorithms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1-2
Zero Slope (Box Car) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1-2
Backward Slope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1-4
Combined Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1-5
Discrete Data Compression Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1-6
Compression Ratio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1-7
Section 2: How the System Compresses Data . . . . . . . . . . . . . . . . . . . . . . . . . 9-2-1

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2-2
How Events are Generated from Analog Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2-3
Deadbands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2-3
Forced Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2-4
On/Off Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2-4
Analog Event Throttling and Compression Ratio Cutoff . . . . . . . . . . . . . . . . . . 9-2-5
How Events are Generated from Discrete Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2-6
Masking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2-6
Discrete Event Throttling and Compression Ratio Cutoff . . . . . . . . . . . . . . . . . 9-2-7
How Events are Stored . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2-8
How Events are Transmitted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2-9
Eligible Gateways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2-9
Retry Rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2-9
Alarms Produced by Data Compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2-10
Compression Ratio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2-10
Storage Buffer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2-11
Section 3: Configuring Compressors in a Data Compression Block . . . . 9-3-1

Special Data Compression Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3-2
Basic Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3-3
Configuring an Analog Compressor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3-6
Configuring a Discrete Compressor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3-11
Section 4: Hints for Configuring Data Compressors . . . . . . . . . . . . . . . . . . . 9-4-1
RS3: Data Compression Contents

CB: ii
List of Figures
Figure Page
9.1.1 Zero Slope Compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1-3
9.1.2 Backward Slope Compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1-4
9.2.1 Data Compression, Storage, and Transmission . . . . . . . . . . . . . . . . . . . 9-2-2
9.3.1 Moving Among Data Compression Screens . . . . . . . . . . . . . . . . . . . . . . 9-3-2
9.3.2 Data Compression Block Continuous Faceplate Screen . . . . . . . . . . . . 9-3-4
9.3.3 Analog Compressor Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3-6
9.3.4 Discrete Compressor Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3-11

CB: iii
List of Tables
Table Page
9.2.1 Retry Rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2-9
9.3.1 Fields on Data Compression Block Continuous Faceplate Screen . . . 9-3-5
9.3.2 Fields on Analog Compressor Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3-7
9.3.3 Fields on Discrete Compressor Screen . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3-12

CB: 9-1-1
Section 1:
Introduction to Data Compression
This section includes a definition of data compression, descriptions of

the algorithms used to compress data, and a definition of compression
ratio.
What is Data Compression?
Data compression, sometimes called exception reporting, is a means of

selecting and storing only significant changes in the process. You define
significant change for each process variable by defining deviation limits.
Each variable is tracked, and data points are generated only when the
variable exceeds the deviation limits.
Because the data points are not produced at regularly spaced intervals,
each point is stored with a date-time stamp. The data points and their
date-time stamps are used by process historians and supervisory
control computers to monitor and control the process.
Compressed data is useful mainly because it reduces the amount of

PeerWay traffic, but it also reduces the amount of data storage needed,
making the system operate more efficiently for other control purposes
as well.
Typically, data compression will be used with batch processes, where

process data is only required during specific phases of the process.
Continuous processes generally have more data points to report than is
practical to compress in the controller.
RS3: Data Compression Introduction to Data Compression

CB: 9-1-2
Analog Data Compression Algorithms
Analog data is compressed by means of two commonly used

compression algorithms.1 These algorithms, zero slope (also known as
box car) and backward slope, are used together. Values for each
process variable are tested against both algorithms. If a value is outside
the limits allowed by both algorithms, a data point is recorded. The two
algorithms are described below.
Zero Slope (Box Car)
In the zero slope compression method, a deviation limit is defined as a

boundary around the process variable. Whenever the process variable
exceeds the value of the deviation limit, the previous value is stored.
Figure 9.1.1 shows an example of sample versus reconstructed data
using the zero slope method.
The zero slope compression method does not always result in the most
efficient data compression when used alone. An example is the case of
a large tank filling slowly. The zero slope algorithm records a value each
time the level rises above the deviation limits, as though many small
changes were taking place. The change in level could be described just
as accurately by a straight line with two values to mark the start and
completion of filling.
(1) Bader, F.P, and T.W. Tucker. Data Compression Applied to a Chemical Plant Using a Distributed Data
Historian. ISA Transactions, Vol. 26, No. 4.
Hale, John C., and Harold L. Sellars. Historical Data Recording for Process Computers. Chemical
Engineering Progress, Nov. 1981.

CB: 9-1-3
+
.
Reconstructed data
. .
+
.
+ . . .
.
+ . . .
. .
. Sample data
Sample data
Deviation limits . Recorded data
+ Value that caused recording
Figure 9.1.1. Zero Slope Compression

CB: 9-1-4
Backward Slope
Backward slope compression attempts to predict the path of a slowly

moving variable, which theoretically stores less data than a zero slope
algorithm on an equivalent variable. In the backward slope compression
method, a linear projection of the variable is defined from a pair of XY
coordinates. The coordinate points are the most recent deviation from
the projection, plus the immediately preceding pair. Figure 9.1.2 shows
an example of sample versus reconstructed data using the backward
slope method.
The backward slope algorithm allows you to compress steadily

increasing or decreasing data efficiently.
Projection
Reconstructed data
. ´
. . .
Deviation limits .
.
´
.
. ´ .
. . . Sample data
Sample data . Recorded data
´ Value that caused recording
Figure 9.1.2. Backward Slope Compression

CB: 9-1-5
Combined Algorithm
The combination of zero slope and backward slope algorithms used by

the system is expressed below in pseudocode, using the following
variable declarations:
Analog Dynamic Data

V Value of the variable to be compressed, at some block input
Vlast V of the previous block evaluation
Vrec Most recent value “recorded” in the buffer
Trec Time stamp of Vrec
S Slope calculated for Backward Slope test
T Timer for zero slope time limit
P State of the test results, four states for two tests
t Current time of day
ts Evaluation time interval
Analog Static Data

Hbs Backward slope deadband
Hbc Zero slope deadband
Tbc Zero slope time limit (maximum 4 hours)
if analog compression type

if rise of switch /* A new run of compressed data is starting */
Vlast = V = --HUGE /* where HUGE is a very large real number */
if fall of switch /* The run has been terminated, mark it */
V = HUGE
if P ~= 1 /* Backward slope test has not already failed */

if abs ( V -- ( Vrec + S * ( t -- Trec ) ) ) >= Hbs /* Back slope test */
if P == 2 then P = 3 /* Both tests have failed */
else P = 1 /* Backward slope test has failed */
if P <= 1 /* Zero slope test has not already failed and P ~= 3 */

if abs ( V -- Vrec ) >= Hbc /* Zero slope test */
if P == 1 then P = 3 /* Both tests have failed */
else P = 2 /* Zero slope test has failed */
if ( P == 3 ) | ( T >= Tbc ) | (rise of snapshot) /* Both failed or

timed out or switch */
S = ( Vlast -- Vrec ) / ( t -- ts -- Trec ) /* New slope */
Vrec = Vlast /* Do not record the present value */
Trec = t -- ts /* Time stamp of Vlast */
<copy Vrec and Trec to the buffer>
P = 0 /* Start a new test cycle */
T = 0 /* Reset the zero slope limit timer */
Vlast = V /* Save V for next evaluation */

T = T + ts /* Operate the zero slope limit timer */

CB: 9-1-6
Discrete Data Compression Algorithm
Discrete data from a set of user flags can also be compressed, but the
algorithm does not work by means of deviation limits. Instead, the
algorithm checks to see if any of the user flags you indicated for a given
input have changed state since the last recorded value. If any have
changed, new values are recorded, together with a date-time stamp.
To compress discrete data from a single user flag, use a logic step to
generate an event message. For more information, see Chapter 6,
Section 2.
The discrete compression algorithm used by the system is expressed

below in pseudocode, using the following variable declarations:
Discrete dynamic data

Rflags User flag register of the input
Rlast Register of the last value ”recorded” in the buffer
Discrete static data

Rmask Mask of flags to be compressed
if discrete compression type

if ( Rflags & Rmask ) ~= Rlast
<copy Rflags and time of day to the buffer>
Rlast = ( Rflags & Rmask )

CB: 9-1-7
Compression Ratio
Compression ratio is a method of evaluating the efficiency of the

compression.
number of block evaluations

CR =
number of data points recorded
The higher the compression ratio, the more efficient the compression
algorithm. For example, with a compression ratio of 1, 1 data point is
stored for each scan, so no compression is taking place. However, with
a compression ratio of 30, 1 data point is stored for every 30 scans.
The compression ratios for the compressors you configure are shown
on the screens in a Data Compression block. The screens also let you
configure alarms and cutoff points to change the action of the
compressor if the ratio becomes too low. For descriptions of the data
compression screens, see Section 3.

CB: 9-1-8

CB: 9-2-1
Section 2:
How the System Compresses Data
This section includes these topics:

D Overview
D How events are generated from analog inputs
D How events are generated from discrete inputs
D How events are stored
D How events are transmitted
D Alarms produced by data compression
RS3: Data Compression How the System Compresses Data

CB: 9-2-2
Overview
The RS3 compresses data by evaluating linked data in Data

Compression blocks. A Data Compression block uses compressors to
generate events when data are worth storing, and it stores those events
in a controller buffer. The controller buffer transmits groups of events
called messages to a PeerWay interface. From there, the messages are
sent out over the PeerWay to eligible Rosemount Network Interface
(RNI) or VAX nodes.
From the RNI or VAX nodes, historians and supervisory computers have
access to the compressed data. The RNI or VAX nodes must be
configured to accept the compressed data. For information on the RNI
and VAX nodes, see RNI Programmer’s Reference Manual and
RMT/host User’s Manual.
NOTE: The software you need to configure Data Compression blocks is

independent of the RNI and RMT/host software that you must configure
to accept data from the blocks. This separation means that compressed
data will only be available to historians or supervisory computers when
RNI or RMT/host software is available to request it from the RS3.
Figure 9.2.1 shows how events are generated, stored, and transmitted
to RNI or VAX nodes.
Controller Coordinator
Processor
Eligible
RNI or VAX
Node
Buffer for Message PeerWay
Event Storage Interface
Eligible
RNI or VAX
Node
Events
Eligible
DCB RNI or VAX
Node
Compressor(s) Eligible
RNI or VAX
Node
Linked
PeerWay
Input
Figure 9.2.1. Data Compression, Storage, and Transmission

CB: 9-2-3
How Events are Generated from Analog Inputs
Each analog compressor in a DCB receives linked input from an I/O

block or another ControlBlock. The compressor tests the input against
both the zero slope and backward slope algorithms to determine
whether it falls outside the established deviation limits, called
deadbands. If the input exceeds the limits of both algorithms, it shows a
significant change in the process variable, and an event is generated.
An event includes the data point address, the value, and a date-time
stamp. For the exact data structure of an event, see RNI Programmer’s
Reference Manual.
You control when the system applies the algorithms by configuring:

D Deadbands
D Forced events
D On/off switch
D Compression ratio cutoff
Deadbands
You set the deadbands in the “Zero Slope Deadband” and “Backward
Slope Deadband” fields. Both deadbands are configured in the
engineering units of the point being compressed and represent the
positive or negative deviation from the previously recorded value that
defines the extent of the deadband.
The width of the deadbands you configure depends on the amount of

noise you expect. If you expect little fluctuation in the process, you may
want to configure narrow deadbands; while if you expect much
fluctuation, you may want to use wider ones.
For information on the “Zero Slope Deadband” and “Backward Slope

Deadband” fields, see Section 3.

CB: 9-2-4
Forced Events
You can cause the compressor to generate an event without testing the
input against the compression algorithms. There are two ways to force
the generation of events:
D Use a logic step output or discrete input to trigger an event.
You configure this trigger in the “Snapshot Input” field for either
an analog or discrete compressor. If you use the same logic step
output to trigger the compressors for a group of related variables,
you can ensure that you get events with the same date-time
stamp for each of the variables.
D Force an event to be generated after a given time limit. You
configure the maximum time that can pass without recording an
event in the “Time Limit” field for either an analog or discrete
compressor.
For information on the “Snapshot Input” and “Time Limit” fields, see
Section 3.
On/Off Switch
You can prevent the compressor from executing the compression

algorithms by configuring a software switch in the “On/Off Input” field.
The field is available for both analog or discrete compressors.
You can use either a logic step or a discrete input as the switch. When
the logic step or discrete input is off, the compressor does not generate
events. If you do not configure a switch, the default value in the field is
“None”, meaning the compressor is always on.
To compress only data related to a Batch process, you can use a Batch
script to turn this switch on and off in order to start and stop a
compressor.
For information on the “On/Off Input” field, see Section 3.

CB: 9-2-5
Analog Event Throttling and Compression Ratio Cutoff
In the case of a process upset, you may want to reduce the number of
events generated after the upset occurs in order to reduce PeerWay
traffic. The system uses a compression ratio cutoff as the trigger to
begin generating fewer events. You set the cutoff in the “CR Cutoff” field
at a ratio that shows you the process is becoming erratic.
When the compression ratio falls below the cutoff, the system widens
the deadbands by a factor of 10. It continues to use these adjusted
deadbands until it is reset. The “Compression Status”, “Zero Slope
Deadband”, “Backward Slope Deadband”, and “State” fields all indicate
that the adjusted deadbands are in use.
Another way to control the compression ratio cutoff is to change the

length of time over which the compression ratio is sampled. A longer
time span allows the compression ratio to be averaged over more time
samples, so it will be less sensitive to variations over time. You
configure the time span in the “Compression Ratio Window” field.
If you want a critical alarm to occur when the cutoff is reached, you
configure it in the “Cutoff Crit Alarm” field. You can also configure an
advisory alarm to occur before the cutoff in the “CR Advisory Alarm”
field.
To reset all compressors in the block which have had their deadbands
widened (and clear the critical alarms), you use a logic step output or
discrete input. You configure the reset in the “Reset Input” field on the
Continuous Faceplate.
For more information on the fields related to event throttling and

compression ratio cutoff, see Section 3.

CB: 9-2-6
How Events are Generated from Discrete Inputs
Each discrete compressor in a DCB examines the user flags of a linked

input from an I/O block or another ControlBlock. The compressor
compares the states of the flags to those in the last event recorded. If
the state of any of the flags has changed, an event is generated.
An event includes the data point address, the states of the flags, and a
date-time stamp. For the exact data structure of an event, see the RNI
Programmer’s Reference Manual.
As with analog compressors, you configure parameters to control how

and when the discrete compressor generates events. For discrete
compressors, you can configure:
D Forced events
D On/off switch
D Masking
D Compression ratio cutoff
Forcing a discrete compressor to generate events and setting an on/off

switch for it is like doing these tasks for an analog compressor. For
information, see “Forced Events” and “On/Off Switch” earlier in this
section.
Masking
Not all of the 16 user flags of an input must be compressed. You may
decide that only some of the flags are of interest to you. In this case,
you use the “Mask” field to configure the flags that will not be
compressed.
When some flags are masked, the compressor compares only the
unmasked flags to those in the last event recorded. If the state of any of
the unmasked flags changed, an event is generated. The event
contains the true state of all flags, regardless of the mask.
In the “Mask” field, each hexadecimal digit represents the sum of four
single-bit flags:
F F F F
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
p o n m l k j i h g f e d c b a
The default is “FFFF” (all flags compressed).

CB: 9-2-7
Discrete Event Throttling and Compression Ratio Cutoff
As with analog compressors, you can reduce the number of events a

discrete compressor generates after a process upset to reduce
PeerWay traffic. The compressor uses a compression ratio cutoff as the
trigger to begin generating fewer events. You set the cutoff in the “CR
Cutoff” field at a ratio that shows you the process is becoming erratic.
When the compression ratio falls below the cutoff, the compressor
generates only every tenth event. For the other nine, it counts without
generating an event. It continues to use this adjusted pattern until it is
reset. The “Compression Status” and “State” fields indicate that the
adjusted pattern is in use.
Another way to control the compression ratio cutoff is to change the

length of time over which the compression ratio is sampled. A longer
time span allows the compression ratio to be averaged over more time
samples, so it will be less sensitive to variations over time. You
configure the time span in the “Compression Ratio Window” field.
As with analog compressors, you can configure critical and advisory

alarms to be displayed when the cutoff is reached. You use the “Cutoff
Crit Alarm” and “CR Advisory Alarm” fields.
To reset all compressors in the block (and clear the critical alarms), you
use a logic step output or discrete input. You configure the reset in the
“Reset Input” field on the Continuous Faceplate.
For more information on the fields related to event throttling and

compression ratio cutoff, see Section 3.

CB: 9-2-8
How Events are Stored
After the events are generated, they are stored in a controller buffer. A
number of events are allowed to build up in the buffer and then sent out
as a group. Sending groups of events conserves PeerWay transmission
capacity.
Groups of events are stored until:

D The group reaches a size limit
or
D The oldest event in the group has been stored for a given time
limit
When one of these two conditions is met, all the events in the buffer are
sent. The size limit and time limit are not configurable.
Size Limit
Up to 84 events can be included in one message.
Time Limit
The time limits for events to be stored correspond to the type of data
selected on the Continuous Faceplate:
Type of Data Time Limit

Fast (supervisory computers) 10 seconds
Slow (historians) 10 minutes
Discrete 1 minute
For more information on how to select the type of data, see Section 3.

CB: 9-2-9
How Events are Transmitted
Event packages are sent to destination nodes that are either RNIs or
VAXes. Each destination node holds the events in a buffer when they
are received.
Eligible Gateways
The controller looks for eligible RNIs and VAXes to send the event
packages. Only the four lowest-numbered RNI and/or VAX nodes
selected for the node in the Configure Alarm Broadcast (CAB) screen
are eligible to receive transmissions. To designate a node to receive the
event packages, you must go to the CAB screen and select the
appropriate nodes. For information on calling up the CAB screen and
selecting nodes, see CC: 6-1.
If you wish, you can exclude one or more of the four eligible nodes from
receiving events from certain DCBs. However, excluding any of the four
nodes does not allow transmission of events to additional nodes; the
first four are the only nodes that can be eligible. For information on
configuring excluded nodes, see Section 3.
Retry Rates
If a destination node cannot accept the event transmission, it sends a

message back to the controller indicating why not. Based on the
destination node response, the controller tries to send the events again
at varying rates. Table 9.2.1 shows the rates.
The controller does not stop attempting to send the event package
unless the node disappears or becomes ineligible to receive messages.
Table 9.2.1. Retry Rates
Destination Node Response Retry Rate
3 attempts 2 seconds apart and 1 attempt every

Buffer full errors ´ 6
minute thereafter
Fatal gateway errors 1 attempt every 4 minutes
PeerWay errors (e.g., bad

1 attempt every minute
node, bad socket)

CB: 9-2-10
Alarms Produced by Data Compression
Data compression can produce three possible alarms, two that are
related to the compression ratio and one that is related to the storage
buffer.
Compression Ratio
D If the compression ratio falls below the point you designated in

the “CR Advisory Alarm” field, you receive an advisory alarm:
Compression Ratio Low
The alarm is cleared when the compression ratio rises above the
designated point.
D If the compression ratio falls below the point you designate in the
“CR Cutoff” field, and if you selected “yes” in the “Cutoff Crit
Alarm” field, you receive a critical alarm:
Compression Ratio Below Cutoff
You can choose to configure a cutoff without also configuring an
alarm. In this case, the cutoff still occurs, but you do not receive
the alarm.
To clear this alarm, you must have a logic step or discrete input
configured in the “Reset Input” field on the DCB Continuous
Faceplate. The reset input both clears the alarm and readjusts
the deadbands. If you try to reset before the compression ratio
rises above the cutoff point again, nothing happens.
For more information on compression ratio cutoff, see “Event Throttling

and Compression Ratio Cutoff” in this section. For information on the
“CR Advisory Alarm”, “Cutoff Crit Alarm”, “CR Cutoff” and “Reset Input”
fields, see Section 3.

CB: 9-2-11
Storage Buffer
D You receive an alarm if the storage buffer is full and is receiving

events faster than it can send them out again to a particular
node. There are twelve buffers, three for each of the four eligible
nodes, so this alarm can appear in twelve different forms:
<Type> Event Buffer Full to Node <X>
Slow
Fast
Discrete
The alarm is cleared when the buffer can again empty itself
faster than events are received.
For information on event storage, see “How Events are Stored” in this
section.

CB: 9-2-12

CB: 9-3-1
Section 3:
Configuring Compressors in a Data Compression
Block
This section includes the basic steps you take to configure compressors
in a Data Compression block, descriptions of the screens that are
unique to the Data Compression block, and figures and tables that
describe the fields on each of the screens.
NOTE: Do not perform engineering units (EU) conversion for Data

Compression block (DCB) inputs on the Continuous Links screen.
Instead, set EU conversion on the register that the DCB input is linked
to. The DCB will then operate with a scaled value, and that value in the
source block will also be scaled.
RS3: Data Compression Configuring Compressors in a Data Compression Block

CB: 9-3-2
Special Data Compression Screens
Most of the screens in a Data Compression block are the same screens
used for configuring any ControlBlock. The screens that are unique to a
Data Compression block include:
D Continuous Faceplate
D Compressor No. N (up to 16 compressors per block, configured
as analog or discrete)
Figure 9.3.1 shows how to navigate among the data compression

screens.
Previous Block DCB Continuous Next Block

Continuous [PAGE BACK] [PAGE BACK]
Faceplate Continuous
Faceplate Faceplate
[PAGE AHEAD]
[PAGE AHEAD]
[PAGE BACK]
Compressor
No. 1
[PAGE AHEAD]
[PAGE BACK]
Compressor
No. 2
[PAGE AHEAD]
[PAGE BACK]
.
Up to 16 compressors
can be configured for .
each DCB. .
[PAGE AHEAD]
[PAGE BACK]
Compressor
No. N
(last configured
compressor) [PAGE AHEAD]
Figure 9.3.1. Moving Among Data Compression Screens

CB: 9-3-3
Basic Steps
Use the following basic steps when you configure a Data Compression
Block. Illustrations of the specific screens you need and descriptions of
the fields on the screens are included in the following sections.
1. When you first configure the ControlBlock, select “DCB (Data
Compression Block)” as the block function.
2. On the Continuous Faceplate screen, enter the number of
compressors you need, up to 16.
3. On the Continuous Faceplate screen, enter additional
parameters that apply to all compressors in the block, including:
— An input to reset the compressors
— Nodes that should not receive events from this block (as
needed)
4. On each compressor page, configure the following:
— Data type: slow (analog for historian), fast (analog for
supervisory computer), or discrete
— Point to compress: a link to bring in data from another block
— Software switches to turn compression on or off (as needed)
— Compression deadbands, cutoff, and alarms (as needed)
5. To run a DCB when you are finished configuring it, ensure the
block mode is “AUTO” and the controller status is “NORMAL”.

CB: 9-3-4
Configuring the Continuous Faceplate Screen
Figure 9.3.2 shows the Continuous Faceplate screen for a Data

Compression block. Table 9.3.1 describes the fields that are unique to
the faceplate for the Data Compression block. For descriptions of other
fields, see Chapter 2, Section 1.
CB CONTINUOUS FACEPLATE 16-Apr-93 14:26:16

Shed
Tag >DCB-ONE Desc > Mode>
NONE >OUT>A> > >
SC>N +--------+
Addr =129A-68 Function >DCB Data Compression Block A | .00 |
INPUTS Value Units Tag OUTPUT | |
A >60.00 >.00 | |
| |
100-+--------+
+ |
Excluded Destination Nodes 75-+ |
Number of Compressors >5 + |
>15 >0 >0 >0 50-+ |
Sample Time >1. S + |
Reset Input>@a 25-+ |
+------ Compression Status ------+ + |
| 14.67 60.78 31.97 24.48 | Output: 0-+--------+
| 20.05 | Mn Rate Lim >None | .00 |
| | OUT|| |
| | High Lim >100.00 | |
+---------------------------------+ +---------+
Low Lim >.00
Block Mode> LOCAL
Figure 9.3.2. Data Compression Block Continuous Faceplate Screen

CB: 9-3-5
Table 9.3.1. Fields on Data Compression Block Continuous Faceplate Screen
Access
Level
The current compression ratio of each running

compressor in the block. The compressors are listed from
left to right, and top to bottom.
Each compression ratio blinks when an event is generated
by that compressor. The display color for each
compression ratio shows:
Compression
NA Green Normal operation. Display only
Status
Yellow The ratio has fallen below the advisory alarm
point.
Red The ratio has fallen below the cutoff point,
causing the compressor deadbands to be
widened and, optionally, a critical alarm to be
generated.
Nodes that should not receive events from this block.

Normally, compressed data messages are automatically
sent to the first four eligible nodes on the PeerWay. An
Excluded eligible node is a VAX or RNI selected on the Configure
Destination Conf Alarm Broadcast (CAB) screen. Up to 4 nodes
Nodes If you enter one of these four nodes, it will not receive
transmissions. However, excluding any of the four nodes
does not allow transmission of events to additional nodes;
the first four are the only nodes that can be eligible.
Number of
Conf The number of compressors configured for this block. 1-16
Compressors
A discrete input or logic step that resets all compressors in

this block that have widened deadbands because the None
Reset Input Conf compression ratio fell below the cutoff point. For more @a-@o
information on event throttling and compression ratio a-p
cutoff, see Section 2.
The time interval between the start of one round of

scanning inputs, performing calculations, and generating
outputs and the start of the next round. Unlike other
ControlBlocks, the DCB performs only at the “Sample 0-99999.
Time” interval, regardless of the Controller Processor scan Hours (H),
Sample Time Conf time value. However, any logic steps in a DCB are minutes (M),
performed at the scan time rate. seconds (S)
The “Sample Time” may be longer, but not shorter, than 1.S
the Controller Processor scan time. If the DCB “Sample
Time“ value is the same as the Controller Processor scan
time, the value is backlighted.

CB: 9-3-6
Configuring an Analog Compressor
Figure 9.3.3 shows the analog compressor configuration page. This

screen appears when you select either slow (historian) or fast
(supervisory computer) in the “Data Type” field. Table 9.3.2 describes
the fields on the screen.
- To move quickly from this compressor to another:
Cursor to the “Compressor” field, type the number of the destination
compressor, and press [ENTER].
COMPRESSOR NO. 1 16-Apr-93 14:26:31

Tag >DCB-ONE +----------- Internal Monitor ----------+ >OUT>A> > >
| Slope .02 Evals 30 Flags 03 | +--------+
Addr =129A-68 | Vlast .46 Trips 1 | A | 60.00 |
| Vrec .02 Timer 25. | | |
Compressor>1 of 5 +---------------------------------------+ | |
| |
Descriptor > Data Type >Slow 100-+--------+
+ |
Point to Compress >A >=129A-75 Value .0 GPM 75-+ |
+ |
On/Off Input>None Snapshot Input>None Time Limit>60. secs 50-+ |
+ |
Zero Slope Deadband>1.0 Backward Slope Deadband>1.0 25-+ |
+ |
Compression Ratio Window>32 seconds 0-+--------+
| .00 |
CR Cutoff>5. Cutoff Crit Alarm>Yes CR Advisory Alarm>15. OUT|| |
| |
Compression Ratio 14.67:1 State Zero Slope Exceeded +--------+
Block Mode> AUTO
Figure 9.3.3. Analog Compressor Screen

CB: 9-3-7
Table 9.3.2. Fields on Analog Compressor Screen
Access
Level
The boundary condition for the backward slope portion of

the compression algorithm. Represents the positive or
negative deviation from the previously recorded value that
Backward defines the extent of the deadband. Configured in the
Slope engineering units of the point being compressed. .0-999999.
Conf
Default is 1%
Deadband When the number appears backlit, the algorithm is using a
value 10 times the configured deadband. For more
information on analog event throttling and compression
ratio cutoff, see Section 2.
The number of compressor algorithm evaluations divided

by the number of compression values recorded within the
time specified in the “Compression Ratio Window” field.
Compression This parameter provides a performance reference to
NA Display only
Ratio assist in making adjustments to the algorithm deadbands.
NOTE: The compressor algorithm evaluates at the
evaluation rate of the Data Compression block.
The time window (in seconds) over which the compression 32, 40, 64, 80,
ratio is calculated for the compression ratio cutoff test. 128, 160, 256,
Compression 320, 512, 640,
Conf You use this parameter to control the sensitivity of your
Ratio Window 1024, 1280, 2048,
compression ratio. For more information on analog event 2560, 4092, 5120,
throttling and compression ratio cutoff, see Section 2. 8192
The number of this compressor (same as in title line). To

Compressor Oper transfer to another compressor in this block, enter the 1-16
number of the other compressor.
An alarm limit for the compression ratio. When the

CR Advisory compression ratio falls below this value, an advisory alarm 0.-9999.
Conf
Alarm is generated. For more information on alarms produced by 15
data compression, see Section 2.
A minimum compression ratio limit at which the

compressor will be throttled. When the compression ratio
falls below this value, the backward slope and zero slope 0.-9999.
CR Cutoff Conf
deadbands are multiplied by 10. For more information on 10
analog event throttling and compression ratio cutoff, see
Section 2.
Allows you to specify whether a critical alarm is to be

Cutoff Crit generated when the compression ratio falls below the CR
Conf No, Yes
Alarm
Cutoff value.

CB: 9-3-8
Table 9.3.2. Fields on Analog Compressor Screen (continued)
Access
Level
The type of compressed data output that a compressor

generates:
Slow, Fast Analog types. Cause the analog compressor
page to be displayed.
Disc Discrete type. Causes the discrete Slow
Data Type Conf compressor page to be displayed. Fast
The subscriber to compressor output also specifies one of Disc
these types. Configuring Slow or Fast has no effect on the
compressor output, but is a label for the subscriber. This
label provides a means of designating data as intended for
historians (Slow) or for applications that require tighter
deadbands (Fast).
Up to 32
Descriptor Conf Text you enter to identify the compressor.
characters
Allows you to view the internal operation of the

compressor.
Slope slope calculated for the backward slope test
(unscaled, absolute value)
Vlast value (unscaled, absolute) of the previous block
evaluation
Vrec most recent value (unscaled, absolute) recorded
as an event
Evals evaluation counter
Trips events (number of stored data points) counter
Internal Timer timer for zero slope time limit
NA Display only
Monitor Flags hexadecimal digits that represent the sum of
single-bit flags:
80 switches state on each trip
40 indicates “throttling” mode
20 indicates active advisory alarm
10 indicates an event was created this time
08 Indicates DCB configuration was changed
04 indicates snapshot input is on
02 indicates on/off input is on
01 indicates an input is configured
A software switch that determines whether a compressor

executes its compression algorithm. When this switch is
off, the compressor will not execute the compression None
On/Off Input Conf algorithm. @a-@o
a-p
You can configure this switch as a logic step or a discrete
input. “None” means the compressor is always on.

CB: 9-3-9
Access
Level
The linked input that the compressor will compress. You

can configure the link in this field or on the Continuous
Point to Links screen for this block. When you enter the link, the None
Conf
Compress system adds fields for the link’s tag or address and value. A-O
Each compressor can only be assigned one input link.
A software switch that allows you to generate a

None
Snapshot compressed data event on demand. You can configure
Conf @a-@o
Input this switch as a logic step or a discrete input. For more
a-p
information on forced events, see Section 2.
The current state of the compressor. Possible states

include:
OFF The compressor is not running.
Testing Neither the zero slope nor the backward
slope algorithm has been exceeded.
Zero A data point exceeded the limits of the zero
Slope slope algorithm.
Exceeded
Backward A data point exceeded the limits of the
Slope backward slope algorithm.
Exceeded
State NA Event A data point exceeded the limits of both Display only
Generated algorithms.
The “State” field name blinks when an event is generated
by the compressor. The display color for the field name
shows:
Green Normal operation.
point.
generated.

CB: 9-3-10
Access
Level
The maximum time allowed for a compressor without

recording a compression value. Zero seconds is 0-999999. sec
Time Limit Conf
interpreted as no time limit. For more information on 60. sec
forced events, see Section 2.
The boundary condition for the zero slope portion of the

compression algorithm. This condition will be configured
as a +/-- percentage of the previously recorded value.
Represents the positive or negative deviation from the
previously recorded value that defines the extent of the
Zero Slope deadband. Configured in the engineering units of the point .0-999999.
Conf being compressed.
Deadband Default is 1%
When the number appears backlit, the configured
deadband has been replaced by an effective deadband,
which is 10 times the configured deadband. For more
information on analog event throttling and compression
ratio cutoff, see Section 2.

CB: 9-3-11
Configuring a Discrete Compressor
Figure 9.3.4 shows the discrete compressor configuration page. This

screen appears when you select discrete in the “Data Type” field.
Table 9.3.3 shows the fields on the screen.
- To move quickly from this compressor to another:
Cursor to the “Compressor” field, type the number of the destination
compressor, and press [ENTER].
COMPRESSOR NO. 3 16-Apr-93 14:27:05
Tag >DCB-ONE +----------- Internal Monitor ----------+ >OUT>A> > >

| Evals 30 Flags 00 | +--------+
Addr =129A-68 | Trips 1 | A | 60.00 |
| Vrec 0000 Timer 3. | | |
Compressor>3 of 5 +---------------------------------------+ | |
| |
Descriptor >Discrete Data Type >Disc 100-+--------+
+ |
Point to Compress >B >=129A-33/A Value 0000 Mask>FFFF 75-+ |
+ |
On/Off Input>None Snapshot Input>None Time Limit>60. secs 50-+ |
+ |
25-+ |
+ |
Compression Ratio Window>32 seconds 0-+--------+
| .00 |
CR Cutoff>5. Cutoff Crit Alarm>Yes CR Advisory Alarm>15. OUT|| |
| |
Compression Ratio 31.97:1 State Testing +--------+
Block Mode> AUTO
Figure 9.3.4. Discrete Compressor Screen

CB: 9-3-12
Table 9.3.3. Fields on Discrete Compressor Screen
Access
Level
The number of compressor algorithm evaluations divided

by the number of compression values that are recorded
within the time specified in the “Compression Ratio
Compression Window” field. This parameter provides a performance
NA reference to assist in making adjustments to the algorithm Display only
Ratio
deadbands.
NOTE: The compressor algorithm evaluates at the
evaluation rate of the Data Compression Block.
The time window (in seconds) over which the compression 32, 40, 64, 80,
ratio is calculated for the compression ratio cutoff test. 128, 160, 256,
Compression 320, 512, 640,
Conf You use this parameter to control the sensitivity of your
Ratio Window 1024, 1280, 2048,
compression ratio. For more information on discrete event 2560, 4092, 5120,
throttling and compression ratio cutoff, see Section 2. 8192
The number of this compressor (same as in title line). To

Compressor Oper transfer to another compressor in this block, enter the 1-16
number of the other compressor.
An alarm limit for the compression ratio. When the

CR Advisory compression ratio falls below this value, an advisory alarm 0.-9999.
Conf
Alarm 15
is generated.
A minimum compression ratio limit at which the

compressor will be throttled. When the compression ratio
falls below this value, 9 out of every 10 events will be 0.-9999.
CR Cutoff Conf
10
suppressed. For more information on discrete event
throttling and compression ratio cutoff, see Section 2.
Allows you to specify whether a critical alarm is to be

Cutoff Crit generated when the compression ratio falls below the CR
Conf No, Yes
Alarm
Cutoff value.
The type of compressed data output that a compressor

generates:
Slow, Fast Analog types. Cause the analog compressor
page to be displayed.
Disc Discrete type. Causes the discrete Slow
Data Type Conf compressor page to be displayed. Fast
The subscriber to compressor output also specifies one of Disc
these types. Configuring Slow or Fast has no effect on the
compressor output, but it is a label for the subscriber. This
label provides a means of subscribing to data that is
intended for historians (Slow) or for applications that
require tighter deadbands (Fast).
Up to 32
Descriptor Conf Text you enter to identify the compressor.
characters

CB: 9-3-13
Table 9.3.3. Fields on Discrete Compressor Screen (continued)
Access
Level
Allows you to view the internal operation of the

compressor.
Vrec most recent value (in hexadecimal) recorded as
an event
Evals evaluation counter
Trips events (number of stored data points) counter
Timer timer for zero slope time limit
Flags hexadecimal digits that represent the sum of
Internal single-bit flags:
NA Display only
Monitor 80 switches state on each trip
40 indicates “throttling” mode
20 indicates active advisory alarm
10 indicates event created this time
08 indicates DCB configuration was changed
04 indicates snapshot input is on
02 indicates on/off input is on
01 indicates an input is configured
Allows you to specify which of the flags will be not be

compressed. Each hexadecimal digit represents the sum
of four single-bit flags:
F F F F
Mask Conf 0000-FFFF
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
p o n m l k j i h g f e d c b a
The default is “FFFF” (all flags compressed). For more
information on masking, see Section 2.
A software switch which determines whether a

compressor executes its compression algorithm. When
None
this switch is off, the compressor will not execute the
On/Off Input Conf @a-@o
compression algorithm. You can configure this switch as a
a-p
logic step or a discrete input. “None” means the
compressor is always on.
The linked input that the compressor will compress. You

configure the link in this field or on the Continuous Links
Point to screen for this block. When you enter the link, the system None
Conf adds fields for the link’s tag or address and the value of
Compress A-O
the flags in hexadecimal.
Each compressor can only be assigned one input link.
A software switch which allows you to generate a

None
Snapshot compressed data event on demand. You can configure
Conf @a-@o
Input this switch as a logic step or a discrete input. For more
a-p
information on forced events, see Section 2.

CB: 9-3-14
Table 9.3.3. Fields on Discrete Compressor Screen (continued)
Access
Level
The current state of the compressor. Possible states

include:
OFF The compressor is not running.
Testing The discrete flags covered by the mask have
not changed.
Event At least one of the discrete flags covered by
Generated the mask changed.
The “State” field name blinks when an event is generated
State NA by the compressor. The display color for the field name Display only
shows:
Green Normal operation.
point.
generated.
The maximum time allowed for a compressor without

recording a compression value. Zero seconds is 0-999999. sec
Time Limit Conf
interpreted as no time limit. For more information on 60. sec
forced events, see Section 2.

CB: 9-4-1
Section 4:
Hints for Configuring Data Compressors
- Avoid assigning a given input to more than one compressor.

It is possible accidentally to assign one input to more than one
compressor, especially if you configure several DCBs at different
times. The system does not prevent you from doing this, but it is not
advisable. You should avoid it because the RNI or VAX node
receiving the events will be unable to distinguish which of the
compressors produced the event.
RS3: Data Compression Hints for Configuring Data Compressors

CB: 9-4-2
RS3: Data Compression Hints for Configuring Data Compressors

CB: Index-1
RS3t
Index
A priority, 4-1-10, 4-3-2

rate--of--change, 4-1-1
Alarm field
access arrows, 1-1-12– 1-1-13 Block Directory screen, 1-3-3
example, 1-1-13 Block Status screen, 1-3-5
Action field, Continuous Faceplate screen, 2-2-15 Alarm Inhibit field, ControlFile Status screen, 3-4-14
action logic statement, 6-3-1, 6-3-8– 6-3-17 alarm points, setting, 4-1-2
configuring a Fall logic statement, 6-3-16– Alarm Priority field, 4-1-10
6-3-17 Continuous Diagram screen, 4-1-10, 4-2-5
configuring a Rise logic statement, 6-3-14– Discrete Faceplate screen, 5-1-5
6-3-15 alarms, inhibiting, 6-4-30– 6-4-33
configuring an Off logic statement, 6-3-12– Alarms field, Continuous Diagram screen, 4-2-5
6-3-13 algorithm
configuring an On logic statement, 6-3-10– analog data compression, 9-1-2– 9-1-5
6-3-11 backward slope, 9-1-4
screen area for configuration, 6-3-9 combined zero and backward slope, 9-1-5
types, 6-3-1, 6-3-8 discrete data compression, 9-1-6
Actions field, Discrete Diagram screen, 6-2-5 PID controller, 2-2-2
adaptive tuning, 2-2-47– 2-2-48 position, 2-2-2
Additional Images field, ControlFile Status screen, zero slope, 9-1-2– 9-1-3
3-4-14 Analog Compressor screen
Addr field calling up, 9-3-2
ATC Configuration screen, 8-2-5 Data Compression block, 9-3-6– 9-3-10
Block References screen, 3-4-22 analog data compression algorithms, 9-1-2– 9-1-5
Continuous Diagram screen, 4-2-5 analog event generation
Continuous Faceplate screen, 2-1-11 deadbands, 9-2-3
Continuous Links screen, 3-2-6 forced events, 9-2-4
Discrete Diagram screen, 6-2-5 on/off switch, 9-2-4
Discrete Faceplate screen, 5-1-5 throttling, 9-2-5
Discrete Links screen, 3-3-5 analog event throttling, resetting after, 9-2-5
addresses, ControlBlock, 1-1-4 AOB
adjustable ratio and bias, 2-3-38– 2-3-42 system flags, 7-2-3
advisory alarms, 4-1-1 tracking situations, 2-2-24
continuous input, 4-1-2 user flags, 7-2-4
continuous output, 4-1-8 ATC Configuration screen, 8-1-4, 8-2-3– 8-2-14
AIB configuring detailed information, 8-2-8– 8-2-13
system flags, 7-2-3 configuring general information, 8-2-4– 8-2-7
user flags, 7-2-4 ATC Diagnostics screen, 8-1-4
alarm, 4-1-1– 4-1-9 ATPID block
advisory, 4-1-1 configuration guidelines, 8-1-2
continuous input, 4-1-4 configuration screens, 8-1-2
continuous output, 4-1-8 configuring, 8-2-1– 8-2-14, 8-3-2
critical, 4-1-1 Continuous Faceplate screen, 8-2-2
Data Compression block, 9-2-10– 9-2-11 Continuous Links screens, 8-5-4
deadbands for, 4-1-6– 4-1-7 definition, 8-1-2– 8-1-5, 8-2-2
deviation, 4-1-4 discrete faceplate, 8-3-8
generated by logic steps, 6-2-7– 6-2-11 Discrete Faceplate screen, 8-5-3
RS3: ControlBlock Configuration Manual Index

CB: Index-2
Discrete Links screen, 8-5-5 ControlBlock flags, 7-3-7– 7-3-8

evaluation states, 8-5-1 DIB, 7-2-3, 7-2-5
evaluation status, 8-3-6– 8-3-7, 8-3-10 DOB, 7-2-3, 7-2-5
event messages, 8-4-1 HOB, 7-2-3, 7-2-7
links, 8-2-14 MIB, 7-2-3, 7-2-6
message pairs, 8-5-1 PIOB, 7-2-3, 7-2-6
operating, 8-3-1– 8-3-12 SIB, 7-2-3, 7-2-7
uses for, 8-1-3 TIB, 7-2-3, 7-2-8
ATune Opt field, ATC Configuration screen, 8-2-5 block
Auto ControlBlock Mode, 2-1-9 transfer of data between linked blocks, 7-1-2–
Auto Lock field, Continuous Diagram screen, 4-2-6 7-1-3, 7-3-2– 7-3-5
Auto motor controller block mode, effect on, 2-4-5 types, 1-1-1
Auto valve controller block mode, effect on, 2-4-41 block action, overriding, 6-3-28– 6-3-31
autotuning, 8-1-1– 8-1-4 Block Directory screen, 1-3-2– 1-3-3
beginning session, 8-3-2 Block field
configuring, 8-2-1– 8-2-14, 8-3-2 Block Directory screen, 1-3-3
Continuous Links screen, 8-5-4 Block Status screen, 1-3-5
disconnecting ATPID and resuming normal block links, 1-1-1
operations, 8-3-12 between PeerWays, 3-1-6, 3-4-1, 3-4-8
Discrete Faceplate screen, 8-5-3 displaying out--of--range values, 3-2-12– 3-2-13
Discrete Links screen, 8-5-5 into and out of ControlFiles, 3-1-5, 3-4-1,
enabling, 8-3-3 3-4-5– 3-4-7
evaluation, 8-3-6– 8-3-7 into and out of Controller Processors, 3-1-4,
evaluation states, 8-5-2 3-4-1– 3-4-3
event messages, 8-4-1 paths, 3-1-3– 3-1-6
guidelines, 8-1-2 tracing a link to a destination block, 3-4-21–
message pairs, 8-5-1 3-4-22
new PID values, 8-3-8– 8-3-9 using fewer links, 3-4-23– 3-4-26
into nonvolatile memory, 8-3-11 within Controller Processor, 3-1-3, 3-4-1– 3-4-2
reference information, 8-5-1– 8-5-5 within PeerWays, 3-4-1, 3-4-8
setpoint disturbance, 8-3-4– 8-3-5 block mode, changing or testing, 6-4-22– 6-4-25
special screens, 8-1-4 Block Mode field, 2-1-9
Avail Links field, ControlFile Status screen, 3-4-14 Continuous Diagram screen, 4-2-6
Avl Trnd Spc field, ControlFile Status screen, Continuous Faceplate screen, 2-1-11
3-4-14 Continuous Links screen, 3-2-6
Discrete Diagram screen, 6-2-5
Discrete Faceplate screen, 5-1-5
B Discrete Links screen, 3-3-5
block output packet, 3-4-25
Block References screen, 1-1-8, 3-4-20– 3-4-22
back balancing, open output situation, 2-2-23– block status bits, 7-5-1– 7-5-5
2-2-24 codes, 7-5-2– 7-5-4
Back Calc field, Continuous Faceplate screen testing, 7-5-5
Math function, 2-3-18, 2-3-27 Block Status screen, 1-3-4– 1-3-5
tracking, 2-3-28 blocks, identifying configured, 1-3-2– 1-3-3
backward slope algorithm, 9-1-4 Boot Rev field, ControlFile Status screen, 3-4-14
Backward Slope Deadband field, Analog box car algorithm. See zero slope algorithm
Compressor screen, 9-2-3, 9-2-5, 9-3-7
bias, adjustable, 2-3-38– 2-3-42
Bias Bar Scaling field, Continuous Faceplate, C
2-3-40
Bias field, Continuous Faceplate screen, 2-2-37 cascade control
Bias Gain KB field, Continuous Faceplate, 2-3-15 loop, 2-2-27
bias option, PID function, 2-2-33, 2-2-36– 2-2-37 scheme
binary flag notation, 7-1-7– 7-1-8 secondary in Auto Mode, 2-2-28– 2-2-29
bit representations secondary in Manual Mode, 2-2-30– 2-2-31
AIB, 7-2-3, 7-2-4 secondary output constrained, 2-2-32
AOB, 7-2-3, 7-2-4 tracking, 2-2-25– 2-2-33
CIB, 7-2-3, 7-2-5 CIB
COB, 7-2-3, 7-2-5 system flags, 7-2-3
console flags, 7-4-3 user flags, 7-2-5

CB: Index-3
Clear logic statement, 6-3-3, 6-3-6– 6-3-7 transfer of flags, 7-4-1– 7-4-2
COB user flags, 7-4-3
system flags, 7-2-3 console node, linking to a ControlBlock, 7-4-2
user flags, 7-2-5 Cont Gain field, Continuous Faceplate, 2-2-16
codes for testing status bits Continuous Diagram screen, 1-1-8, 1-2-6, 4-2-1–
ControlBlock, 7-5-4 4-2-7
input/output blocks, 7-5-2 calling up, 4-2-3
PLCB, 7-5-3 configuration hints, 4-3-1– 4-3-2
comments in logic statements, 6-3-25 Q page, 4-1-8
Comp SP ControlBlock Mode, 2-1-9 screen fields, 4-2-4– 4-2-7
compression deadbands, Data Compression block, troubleshooting, 4-3-1
9-2-3 Continuous Faceplate screen, 1-1-8, 2-1-1– 2-1-12
compression ratio calling up, 2-1-3
alarms, 9-2-10 common fields, 2-1-10– 2-1-12
cutoff, 9-2-5, 9-2-7, 9-2-10 configuring, 2-1-5– 2-1-7
defined, 9-1-7 Data Compression block, 9-3-4– 9-3-5
compression ratio cutoff continuous functions, 1-1-5
analog event compression, 9-2-5 continuous input, 1-2-5
discrete event compression, 9-2-7 alarms, 4-1-4– 4-1-5
Compression Ratio field display scaling, 3-2-14– 3-2-15
Analog Compressor screen, 9-3-7 sources, 3-2-8
Discrete Compressor screen, 9-3-12 Continuous Links screen, 1-1-8, 1-2-5, 3-2-1–
Compression Ratio Window field 3-2-15
Analog Compressor screen, 9-2-5, 9-3-7 calling up, 3-2-3
Discrete Compressor screen, 9-2-7, 9-3-12 configuring logic, 6-1-2– 6-1-3
Compression Status field, Continuous Faceplate default screen and fields, 3-2-5– 3-2-7
screen, 9-2-5, 9-2-7, 9-3-5 displaying out-of-range values, 3-2-12– 3-2-13
Compressor field scaling of continuous inputs, 3-2-12– 3-2-15
Analog Compressor screen, 9-3-7 continuous output, 1-2-6
Discrete Compressor screen, 9-3-12 alarms, 4-1-8
Computer (DDC) motor controller block mode, continuous variable value or units, displaying on
2-4-5 discrete faceplate, 5-2-7– 5-2-8
Computer (DDC) valve controller block mode, continuous variables, in logic statements, 6-3-18,
2-4-41 6-3-24
Conditions field, Discrete Diagram screen, 6-2-5 control loop
conditions logic statement cascade, 2-2-25– 2-2-33
configuring, 6-3-2– 6-3-7 feedback, 2-2-20
Emulation logic statement, 6-3-4– 6-3-5 role of ControlBlock, 1-1-2
Set/Clear logic statement, 6-3-6– 6-3-7 scaling, 1-1-3
screen area for configuration, 6-3-3 Control Type field, ControlFile Status screen,
types, 6-3-1 3-4-14
configuration constraints, 3-4-1– 3-4-25 ControlBlock
free space and idle time considerations, 3-4-27 addresses, 1-1-4
HIA links, 3-4-10– 3-4-12 AOB tracking situations, 2-2-24
number of ControlFile links, 3-4-5– 3-4-7 Autotuning, 8-1-2– 8-1-5, 8-2-1– 8-2-14, 8-3-1–
number of Controller Processor links, 3-4-2– 8-3-12, 8-4-1– 8-4-3, 8-5-1– 8-5-5
3-4-4 changing or testing operating modes, 6-4-22–
number of PeerWay links, 3-4-8– 3-4-12 6-4-25
configured blocks, identifying, 1-3-2– 1-3-3 configuration hints, 1-4-1
configuring ControlBlocks configuration screens, 1-1-8
hints, 1-4-1 access arrows, 1-1-12
troubleshooting, 1-4-1 navigating, 1-1-9
configuring Data Compression blocks continuous inputs, 1-2-5
basic steps, 9-3-3 continuous outputs, 1-2-6
hints, 9-4-1 definition, 1-1-1– 1-1-13
configuror arrow, 1-1-12 discrete inputs, 1-2-3
console flags, 7-4-1– 7-4-4 discrete outputs, 1-2-4
bit representations, 7-4-3 faceplate screen, 1-1-6
linking a console to a ControlBlock, 7-4-2 functional diagram, 1-2-2
system flags, 7-4-3 inputs, 1-2-1
testing values, 7-4-4 modes, 2-1-9

CB: Index-4
moving between ControlBlocks, 1-1-10 critical alarms, 4-1-1

moving within ControlBlocks, 1-1-9 curve
outputs, 1-2-1 approximated with line segments, 2-3-30
relationship to input/output blocks, 1-1-2 approximated with polynomial equation, 2-3-34
role in control loop, 1-1-2 Cutoff Crit Alarm field
status bit codes, 7-5-4 Analog Compressor screen, 9-2-5, 9-2-10,
ControlBlock alarms, 4-1-1– 4-1-9 9-3-7
advisory, 4-1-1 Discrete Compressor screen, 9-2-7, 9-2-10,
configuring alarm points, 4-1-2– 4-1-9 9-3-12
continuous input, 4-1-4 Cutoff Type field, Continuous Faceplate screen
continuous output, 4-1-8 Setpoint Totalizer function, 2-3-49
critical, 4-1-1 Stack Totalizer function, 2-3-53
deadbands for, 4-1-6– 4-1-7
deviation, 4-1-4
priority, 4-1-10 D
rate--of--change, 4-1-1
setting alarm points, 4-1-2– 4-1-9 D Act field, Continuous Faceplate screen, 2-2-8,
types of, 4-1-1 2-2-15
ControlBlock flags, 7-3-1– 7-3-18 D control algorithm, 2-2-3
bit representations, 7-3-7– 7-3-8 DASMC, 2-4-1, 2-4-3, 2-4-14– 2-4-23
manipulating, 7-3-18 configuration options, 2-4-17– 2-4-19
system flags, 7-3-7– 7-3-8 Continuous Faceplate screen, 2-4-19
testing values, 7-3-10– 7-3-18 continuous input functions, 2-4-21
transfer of flags, 7-3-2– 7-3-6 Continuous Links screens, 2-4-19
ControlBlock functions, 1-1-5– 1-1-7 Discrete Faceplate screen, 2-4-20
continuous, 2-2-1– 2-2-42, 2-2-44– 2-2-46, discrete input functions and output conditions,
2-3-1– 2-3-58 2-4-21
discrete, 2-4-1– 2-4-67 Discrete Links screen, 2-4-20
hints, 2-5-1 interlock function, 2-4-15
tips, 2-5-4– 2-5-5 links required, 2-4-16
troubleshooting, 2-5-2– 2-5-3 DASVC, 2-4-1, 2-4-39, 2-4-50– 2-4-57
ControlBlocks, number of, 1-1-4 configuration options, 2-4-52– 2-4-54
ControlFile Continuous Faceplate screen, 2-4-51
links available, 3-4-1 continuous input functions, 2-4-56
links into and out of, 3-1-5, 3-4-1, 3-4-5– 3-4-7 Continuous Links screens, 2-4-54
viewing links available, 3-4-19– 3-4-20 Discrete Faceplate screen, 2-4-55
ControlFile Links screen, 3-4-19– 3-4-20 discrete input functions and output conditions,
ControlFile Status screen, 3-4-13– 3-4-17 2-4-56
calling up, 3-4-13 Discrete Links screen, 2-4-55
free space and idle time indicators, 3-4-27– links required, 2-4-51
3-4-28 Data Compression block
links indicators, 3-4-13, 3-4-19– 3-4-20 alarms, 9-2-10– 9-2-11, 9-3-3
viewing links available, 3-4-13 algorithms, 9-1-2– 9-1-6
controller algorithm, 2-2-2 analog compression ratio cutoff, 9-2-5
Controller Processor Analog Compressor screen, 9-3-6– 9-3-10
free space, 3-4-27– 3-4-28 analog event throttling, 9-2-5
idle time, 3-4-27– 3-4-28 assigning inputs, 9-4-1
links available, 3-4-1 compression ratio cutoff, 9-3-3
links into and out of, 3-1-4, 3-4-3 configuration hints, 9-4-1
links within, 3-1-3, 3-4-2 configuring, 9-3-3
count function, 6-4-3– 6-4-4 Continuous Faceplate screen, 9-3-4– 9-3-5
CR Advisory Alarm field data type, 9-3-3
Analog Compressor screen, 9-2-5, 9-2-10, deadbands, 9-2-3, 9-3-3
9-3-7 discrete compression ratio cutoff, 9-2-7
Discrete Compressor screen, 9-2-7, 9-2-10, Discrete Compressor screen, 9-3-11– 9-3-14
9-3-12 discrete event throttling, 9-2-7
CR Cutoff field event buffer, 9-2-8
Analog Compressor screen, 9-2-5, 9-2-10, event generation, 9-2-2– 9-2-8
9-3-7 event transmission, 9-2-9
Discrete Compressor screen, 9-2-7, 9-2-10, event triggers, 9-2-4
9-3-12 excluded destination nodes, 9-3-3

CB: Index-5
forced events, 9-2-4 Desc field

masking, 9-2-6 Continuous Faceplate screen, 2-1-11
on/off switch, 9-2-4 Continuous Links screen, 3-2-6
purpose, 9-1-1 Descriptor field
reset input, 9-3-3 Analog Compressor screen, 9-3-8
running, 9-3-3 Continuous Diagram screen, 4-2-6
software switches, 9-3-3 Discrete Compressor screen, 9-3-12
Data Compression screens, navigating among, Discrete Diagram screen, 6-2-5
9-3-2 Discrete Faceplate screen, 5-1-5
data transfer Discrete Links screen, 3-3-5
between console and ControlBlock, 7-1-3 Destination Address field, Block References screen,
between ControlBlocks, 7-1-3 3-4-22
between I/O block and ControlBlock, 7-1-2 destination block
Data Type field ControlBlock, 3-1-2
Analog Compressor screen, 9-3-8 output block, 3-1-2
Discrete Compressor screen, 9-3-12 tracing a link to, 3-4-21– 3-4-22
DdBand field, Continuous Diagram screen, 4-2-5 Destination Tag field, Block References screen,
DDC ControlBlock Mode, 2-1-9 3-4-22
DDC/CSP field, Continuous Faceplate screen, Details Disp field, ATC Configuration screen, 8-2-3,
2-1-11 8-2-5
DDDMC, 2-4-1, 2-4-3, 2-4-31– 2-4-38 Dev Adv field, Continuous Diagram screen, 4-2-5
configuration options, 2-4-33– 2-4-34 Dev Crit field, Continuous Diagram screen, 4-2-5
Continuous Faceplate screen, 2-4-33 Dev Trigger field, Continuous Faceplate screen,
continuous input functions, 2-4-37 Velocity Limiter function, 2-3-58
Continuous Links screens, 2-4-35 deviation alarms, 4-1-4, 4-2-5
Discrete Faceplate screen, 2-4-36 DIB
discrete input functions and output conditions, system flags, 7-2-3
2-4-37 user flags, 7-2-5
Discrete Links screen, 2-4-36 Discrete Compressor screen
links required, 2-4-32 calling up, 9-3-2
DDSMC, 2-4-1, 2-4-3, 2-4-23– 2-4-30 Data Compression block, 9-3-11– 9-3-14
configuration options, 2-4-25– 2-4-27 discrete ControlBlock functions, 2-4-1– 2-4-67
Continuous Faceplate screen, 2-4-25 discrete data compression algorithm, 9-1-6
Continuous Links screens, 2-4-27 Discrete Diagram screen, 1-1-8, 1-2-4
Discrete Faceplate screen, 2-4-28 area for configuring action statements, 6-3-9
discrete input functions and output conditions, area for configuring condition statements, 6-3-3
2-4-29 calling up, 6-2-2
Discrete Links screen, 2-4-28 configuring logic steps, 6-1-2– 6-1-3
links required, 2-4-24 fields, 6-2-4– 6-2-6
Dead Time field, 2-3-5 discrete event generation
Dead Time function, 2-3-1– 2-3-5, 2-3-8– 2-3-11 forced events, 9-2-4
configuring links, 2-3-6 masking, 9-2-6
Continuous Faceplate screen, 2-3-2– 2-3-4 on/off switch, 9-2-4
Continuous Links screen, 2-3-6 throttling, 9-2-7
delay effect, 2-3-2 discrete event throttling, resetting after, 9-2-7
example, 2-3-8– 2-3-10 discrete faceplate
input A plots, 2-3-7 configuration hints, 5-3-1– 5-3-3
deadband option configuration numbered rows on display, 5-2-2–
Continuous Faceplate screen, 2-2-41 5-2-3
effect on output, 2-2-38 display fields, 5-2-2
PID function, 2-2-38– 2-2-39, 2-2-41 displaying continuous variable value or units,
response, 2-2-40 5-2-7– 5-2-8
deadbands, 4-1-6– 4-1-7 displaying discrete variable state, 5-2-4– 5-2-6
analog events, 9-2-3 displaying flag, 5-2-9– 5-2-10
delay function, 6-4-5– 6-4-6 displaying message pair, 5-2-11– 5-2-12
delay period, 2-3-3– 2-3-10 displaying static information, 5-2-13
Deriv Act field, ATC Configuration screen, 8-2-5 dividing lines, 5-2-13
Deriv Time field, Continuous Faceplate screen, troubleshooting, 5-3-1
2-2-15 Discrete Faceplate screen, 1-1-8
derivative term, 2-2-4, 2-2-8 calling up, 5-1-3
algorithms, 2-2-8 configuring logic steps, 6-1-2– 6-1-3

CB: Index-6
fields, 5-1-4– 5-1-7 enba function, 6-4-32– 6-4-33

discrete function (DISC), 2-4-2 Eng Max field
discrete functions, 1-1-5 Continuous Links screen, 3-2-6
discrete input sources, 3-3-6– 3-3-7 displaying out--of--range values, 3-2-12– 3-2-13
discrete inputs, 1-2-3 Eng Zero field
testing for, 7-3-16– 7-3-17 Continuous Links screen, 3-2-6
Discrete Links screen, 1-1-8, 1-2-3, 3-3-1– 3-3-7 displaying out--of--range values, 3-2-12– 3-2-13
calling up, 3-3-3 Enter All field, ATC Configuration screen, 8-2-5
configuring logic steps, 6-1-2– 6-1-3 Equation field, Continuous Faceplate screen, Math
fields, 3-3-4– 3-3-5 function, 2-3-18
discrete outputs, 1-2-4 equations, Math function, 2-3-19
testing for, 7-3-13– 7-3-14 Err DdBand field, 2-2-41
discrete variable state, 5-2-4 Continuous Faceplate screen, 2-2-41
displaying on discrete faceplate, 5-2-2– 5-2-3 error squared option, PID function, 2-2-5– 2-2-6
discrete variables, in logic statements, 6-3-19, Evaluation field, ATC Configuration screen, 8-2-5
6-3-24 evaluation process, input change on following cycle,
display scaling, 1-1-3, 3-2-9, 3-2-14– 3-2-15 6-1-5
DMC, 2-4-1, 2-4-3, 2-4-6– 2-4-13 event buffer, 9-2-2, 9-2-8
configuration options, 2-4-8– 2-4-10 alarm, 9-2-11
Continuous Faceplate screen, 2-4-8 size limit, 9-2-8
continuous input functions, 2-4-12 time limit, 9-2-8
Continuous Links screens, 2-4-10 event generation
discrete faceplate, 2-4-7, 2-4-11 Data Compression block, 9-2-2– 9-2-8
Discrete Faceplate screen, 2-4-11 forced events, 9-2-4
discrete input functions and output conditions, from analog inputs, 9-2-3– 9-2-5
2-4-12 from discrete inputs, 9-2-6– 9-2-7
Discrete Links screen, 2-4-11 using Batch script, 9-2-4
links required, 2-4-7, 2-4-11 event storage. See event buffer
DMVC, 2-4-1, 2-4-39, 2-4-58– 2-4-67 event throttling, Data Compression block, 9-2-5,
configuration options, 2-4-61– 2-4-63 9-2-7
Continuous Faceplate screen, 2-4-61 event transmission
continuous input functions, 2-4-66 eligible nodes, 9-2-9
Continuous Links screens, 2-4-63 gateways, 9-2-9
discrete faceplate, 2-4-59 retry rates, 9-2-9
Discrete Faceplate screen, 2-4-64 event triggers, Data Compression block, 9-2-4
discrete input functions and output conditions, Event Type field
2-4-66 ATC Configuration screen, 8-2-5, 8-3-2, 8-3-6,
Discrete Links screen, 2-4-64 8-4-1
links required, 2-4-59 Discrete Diagram screen, 6-2-10
DOB events, generated by logic steps, 6-2-7– 6-2-11
system flags, 7-2-3 Excluded Destination Nodes field, Continuous
user flags, 7-2-5 Faceplate screen, 9-3-5
duty function, 6-4-7– 6-4-11
DVC, 2-4-1, 2-4-39, 2-4-42– 2-4-49
configuration options, 2-4-44– 2-4-46 F
Continuous Faceplate screen, 2-4-43
continuous input functions, 2-4-48 faceplate, tracking indicators, 2-2-26
Continuous Links screens, 2-4-46 faceplate configuration, 2-1-5– 2-1-7
discrete faceplate, 2-4-42 faceplate configuration line, 2-1-5– 2-1-6
Discrete Faceplate screen, 2-4-47 Fall Hi Lim field, Velocity Limiter function,
discrete input functions and output conditions, Continuous Faceplate screen, 2-3-58
2-4-48 Fall Limit field, Velocity Limiter function, Continuous
Discrete Links screen, 2-4-47 Faceplate screen, 2-3-58
links required, 2-4-42 Fall logic statement, 6-3-8, 6-3-16– 6-3-17
feedback control loop, 2-2-20
feedforward control, 2-2-10, 2-2-17– 2-2-18
E configuring, 2-2-17– 2-2-18
with Lead/Lag, 2-3-10
FF Gain field, Continuous Faceplate screen, 2-2-15
eligible nodes, event transmission, 9-2-9 fhf function, 6-4-2
Emulation logic statement, 6-3-3, 6-3-4– 6-3-5 File Status field, ControlFile Status screen, 3-4-14

CB: Index-7
fill function, 2-3-3, 6-4-2 PID function, 2-2-38– 2-2-40

Filter Gain KA field, Continuous Faceplate, 2-3-15 response, 2-2-39
Filter Time field, Continuous Faceplate screen, Gap Value field, Continuous Faceplate screen,
2-2-15 2-2-40
First input field, Continuous Faceplate, 2-1-7 gateways, event transmission, 9-2-9
First Reset field, Continuous Faceplate screen,
Stack Totalizer function, 2-3-53
flag H
binary and hexadecimal notation, 7-1-7– 7-1-8
bit representation, 7-1-1 hexadecimal flag notation, 7-1-7– 7-1-8
configuration hints, 7-6-1– 7-6-2 HIA links, 3-4-10, 3-4-12
consoles, 7-4-1– 7-4-4 High Lim field, Continuous Faceplate screen
ControlBlocks, 7-3-1– 7-3-18 bias, 2-2-37, 2-3-40
definition, 7-1-1 ratio, 2-2-35, 2-3-40
displaying on a discrete faceplate, 5-2-9– 5-2-10 setpoint, 2-2-16
input/output blocks, 7-2-1– 7-2-8 hints
notation, 7-1-4– 7-1-8 configuring
testing all flags, 7-1-4, 7-1-9 Continuous Diagram screen, 4-3-1– 4-3-2
testing individual flags, 7-1-4– 7-1-5 ControlBlock functions, 2-5-1
testing the rise and fall of individual, 7-1-6 ControlBlocks, 1-4-1
flag notation for logic steps, 7-1-4– 7-1-8 Data Compression blocks, 9-4-1
flags, transfer of, 7-1-2– 7-1-3, 7-2-2, 7-3-2– 7-3-6 discrete faceplate, 5-3-1– 5-3-3
fnow function, 6-4-2 flags, 7-6-1– 7-6-2
forced events, Data Compression block, 9-2-4 logic steps, 6-5-1– 6-5-4
Fourth input field, Continuous Faceplate, 2-1-7 using fewer links, 3-4-23– 3-4-26
free space and idle time, 3-4-27– 3-4-28 HOB
Free Space field system flags, 7-2-3
ControlFile Status screen, 3-4-14 user flags, 7-2-7
Discrete Diagram screen, 6-2-5 Hold field
Function field Continuous Faceplate screen, 2-2-21– 2-2-22,
Continuous Diagram screen, 4-2-6 2-3-45
Continuous Faceplate screen, 2-1-11 Signal Selector function, 2-3-45
Continuous Links screen, 3-2-6 Continuous Links screen, 3-2-6
Discrete Diagram screen, 6-2-5 Hold Forward flag, 2-2-21
Discrete Faceplate screen, 5-1-5 Hold Forward flag information
Discrete Links screen, 3-3-5 ControlBlocks, 7-6-2
functions input/output blocks, 7-6-1
configuring major, 1-1-6– 1-1-7
continuous, 1-1-5
ControlBlock, 1-1-5– 1-1-7 I
discrete, 1-1-5
I control algorithm, 2-2-3
IB control algorithm, 2-2-6
G ID control algorithm, 2-2-3
Idle time and free space, 3-4-27– 3-4-28
Idle Time field, ControlFile Status screen, 3-4-14
gain effect on block output, 2-3-12 if?then:else function, 6-4-34– 6-4-35
Gain K field, Continuous Faceplate screen ifstand function, 6-4-26– 6-4-27
Setpoint Totalizer function, 2-3-49 inha function, 6-4-32– 6-4-33
Stack Totalizer function, 2-3-53 inhibit function, 6-4-30– 6-4-31
Gain KA field, Continuous Faceplate screen input
Dead Time function, 2-3-5 continuous, 1-2-5
Lead/Lag function, 2-3-14 discrete, 1-2-3
Gain KB field, Continuous Faceplate screen, input A plots, 2-3-7
Lead/Lag function, 2-3-14 input blocks, relationship to ControlBlocks, 1-1-2
Gain KC field, Continuous Faceplate screen INPUT field
Dead Time function, 2-3-5 Continuous Links screen, 3-2-6
Lead/Lag function, 2-3-14 Discrete Links screen, 3-3-5
gap option input filtering, 2-2-9
Continuous Faceplate screen, 2-2-40 input sources
effect on output, 2-2-38 continuous, 3-2-8

CB: Index-8
discrete, 3-3-6– 3-3-7 Left Program NVM Free field, ControlFile Status
input types, 1-2-1– 1-2-6 screen, 3-4-16
input/output block flags, 7-2-1– 7-2-8 Left Program NVM Soft Count field, ControlFile
AIB, 7-2-3, 7-2-4 Status screen, 3-4-16
AOB, 7-2-3, 7-2-4 linked blocks, transfer of data between, 7-1-2–
CIB, 7-2-3, 7-2-5 7-1-3, 7-3-2– 7-3-5
COB, 7-2-3, 7-2-5 links
DIB, 7-2-3, 7-2-5 between PeerWays, 3-1-6, 3-4-1, 3-4-10
DOB, 7-2-3, 7-2-5 block, 3-1-1– 3-1-6, 3-3-1– 3-3-7, 3-4-1–
HOB, 7-2-3, 7-2-7 3-4-25
hold forward flag information, 7-6-1– 7-6-2 block output packet, 3-4-25
MIB, 7-2-3, 7-2-6 configuration hints, 3-4-23– 3-4-26, 3-5-1–
PIOB, 7-2-3, 7-2-6 3-5-4
SIB, 7-2-3, 7-2-7 ControlFile links available, 3-4-1
system flags, 7-2-3 ControlFile Links screen, 3-4-19– 3-4-20
testing values, 7-2-9 Controller Processor, 3-1-3– 3-1-4
TIB, 7-2-3, 7-2-8 definition, 3-1-1
transfer of flags, 7-2-2 examples, 3-1-1
user flags, 7-2-4– 7-2-7 HIA, 3-4-10, 3-4-12
valid data flag information, 7-6-1– 7-6-2 indicators, 3-4-13, 3-4-19– 3-4-20
input/output block status bit codes, 7-5-2 into and out of ControlFiles, 3-1-5, 3-4-1,
Inputs field 3-4-5– 3-4-7
ATC Configuration screen, 8-2-5 into and out of Controller Processors, 3-1-4,
Continuous Faceplate screen, 2-1-11 3-4-1– 3-4-4
Integ Time field, Continuous Faceplate screen, into and out of PeerWays, 3-4-1, 3-4-8
2-2-15 introduction, 3-1-1– 3-1-6
Setpoint Totalizer function, 2-3-49– 2-3-50 paths, 3-1-3– 3-1-6
Stack Totalizer function, 2-3-53– 2-3-54 PeerWay links available, 3-4-1, 3-4-8
integral bilinear function, 2-2-6 tracing to a destination block, 3-4-21– 3-4-22
integral term, 2-2-4, 2-2-6 troubleshooting, 3-5-1– 3-5-2
integral windup, 2-2-7 using fewer links, 3-4-23– 3-4-26
Internal Monitor fields viewing ControlFile links available, 3-4-19–
Analog Compressor screen, 9-3-8 3-4-20
Discrete Compressor screen, 9-3-13 within Controller Processor, 3-1-3, 3-4-1– 3-4-2
internal scaling, 1-1-3, 3-2-9– 3-2-11 Load Trig Mag field, ATC Configuration screen,
Invalid link alarm, 3-2-4 8-2-9
Inverted field, Continuous Faceplate screen, Math, Local ControlBlock Mode, 2-1-9
2-3-18 Local Inhib field, ControlFile Status screen, 3-4-17
Local motor controller block mode, effect on, 2-4-5
Local valve controller block mode, effect on, 2-4-41
J Log field, Discrete Diagram screen, 6-2-10
logic statement
applications, 6-3-26– 6-3-31
Jumper Code field, ControlFile Status screen, change/test ControlBlock op. mode, 6-4-22–
3-4-15 6-4-25
change/test Controller Processor op. mode,
6-4-26– 6-4-29
L Clear, 6-3-3, 6-3-6– 6-3-7
combining expressions, 6-3-23
comments in, 6-3-25
lag effect on block output, 2-3-12 configuring, 6-3-1– 6-3-31
Lag Time 1 field, Continuous Faceplate, 2-3-15 continuous variables, 6-3-18
Lag Time 2 field, Continuous Faceplate, 2-3-15 count function, 6-4-3– 6-4-4
lead effect on block output, 2-3-13 delay function, 6-4-5– 6-4-6
Lead Time field, Continuous Faceplate, 2-3-15 discrete variables, 6-3-19
Lead/Lag function, 2-3-1, 2-3-10– 2-3-15 duty function, 6-4-7– 6-4-11
configuring, 2-3-14 Emulation, 6-3-3, 6-3-4– 6-3-5
diagram, 2-3-10 enba function, 6-4-32– 6-4-33
used with feedforward, 2-3-10 examples, 6-3-24
Left CP: Boot field, ControlFile Status screen, Fall, 6-3-16– 6-3-17
3-4-15 functions, 6-4-1– 6-4-37

CB: Index-9
if?then:else function, 6-4-34– 6-4-35 Mask field, Discrete Compressor screen, 9-2-6,
ifstand function, 6-4-26– 6-4-27 9-3-13
inha function, 6-4-32– 6-4-33 masking, discrete events, 9-2-6
inhibit function, 6-4-30– 6-4-31 Math function, 2-3-1, 2-3-17– 2-3-28
list of functions, 6-4-1– 6-4-2 calculating sum of flows example, 2-3-24–
mathematical and logical operators, 6-3-20– 2-3-26
6-3-22 Continuous Faceplate screen, 2-3-17
mode n function, 6-4-24– 6-4-25 Continuous Links screen, 2-3-19
Off, 6-3-12– 6-3-13 equations, 2-3-19
On, 6-3-10– 6-3-11 temperature--correcting air flow measurement
order of precedence, 6-3-23 example, 2-3-21– 2-3-23
period function, 6-4-7– 6-4-11 tracking example, 2-3-27– 2-3-28
ramp function, 6-4-16– 6-4-17 mathematical operators, 6-3-20– 6-3-22
Rise, 6-3-14– 6-3-15 Max Change Mult field, ATC Configuration screen,
Set, 6-3-3, 6-3-6– 6-3-7 8-2-5
setmode n function, 6-4-22– 6-4-23 Max Gain field, Continuous Faceplate screen
setuauto function, 6-4-20– 6-4-21 Math function, 2-3-18, 2-3-27
setuman function, 6-4-20– 6-4-21 Piecewise Linear Interpolator function, 2-3-31
snorm function, 6-4-28– 6-4-29 Polynomial function, 2-3-35
sstand function, 6-4-28– 6-4-29 tracking, 2-3-27
time function, 6-4-18– 6-4-19 Maximum Deriv Time field, ATC Configuration
timer function, 6-4-12– 6-4-13 screen, 8-2-5
treset function, 6-4-37 Maximum Gain field, ATC Configuration screen,
variables, 6-3-18– 6-3-19 8-2-5
wait function, 6-4-14– 6-4-15 message pair, 5-2-11– 5-2-12
writing, 6-3-18– 6-3-24 MIB
logic steps system flags, 7-2-3
changing mode, 6-4-20– 6-4-21 user flags, 7-2-6
configuration hints, 6-5-1– 6-5-4 Minimum Integ Tim field, ATC Configuration screen,
evaluation process, 6-1-4– 6-1-6 8-2-6
flag notation for, 7-1-4– 7-1-8 Minimum Period field, ATC Configuration screen,
generating an alarm or event, 6-2-7– 6-2-11 8-2-9, 8-2-13, 8-3-4
order of, 6-1-4 Mode field
screens used, 6-1-2– 6-1-3 Block Directory screen, 1-3-3
troubleshooting, 6-5-1– 6-5-2 Block Status screen, 1-3-5
logical operators, 6-3-20– 6-3-22 Discrete Diagram screen, 6-2-6
Loop Damping field, ATC Configuration screen, mode n function, 6-4-24– 6-4-25
8-2-9, 8-2-12, 8-3-4 motor controller functions, 2-4-3– 2-4-39
Low Cutoff field, Continuous Faceplate screen common features, 2-4-3
Setpoint Totalizer function, 2-3-49 DASMC, 2-4-14– 2-4-23
Stack Totalizer function, 2-3-53 DDDMC, 2-4-31– 2-4-38
Low Lim field, Continuous Faceplate screen DDSMC, 2-4-23– 2-4-30
bias, 2-2-37, 2-3-40 discrete motor, 2-4-3
ratio, 2-2-35, 2-3-40 DMC, 2-4-6– 2-4-13
setpoint, 2-2-16 effect of block, 2-4-5
LS--PV Track field, 2-2-27, 2-2-30 preconfigured, 2-4-3
cascade control loop, 2-2-27 unconfigured, 2-4-4
Continuous Faceplate screen, 2-2-15 Msg field, Discrete Links screen, 3-3-5
MsgP field, Discrete Diagram screen, 6-2-6
M N
major ControlBlock functions, 1-1-5– 1-1-7 Next Reset field, Continuous Faceplate screen,
changing, 1-1-7 2-3-53
configuring, 1-1-7 No of Inputs field, Continuous Faceplate screen,
manipulating ControlBlock flags, 7-3-18 Signal Selector function, 2-3-44
Manual ControlBlock Mode, 2-1-9 Node Address field, ControlFile Status screen,
Manual function (MAN), 2-3-1, 2-3-16 3-4-17
Manual motor controller block mode, effect on, nonlinear functions, 2-3-29– 2-3-37
2-4-5 norate function, 6-4-2

CB: Index-10
notrack function, 6-4-2

Number of Compressors field, Continuous
P
Faceplate screen, 9-3-5
numbered fields, Discrete Faceplate screen, 5-1-6 P control algorithm, 2-2-3
NV Mem Used field, ControlFile Status screen, PD control algorithm, 2-2-3
3-4-17 PeerWay
links available, 3-4-1, 3-4-8
links between, 3-1-6, 3-4-1, 3-4-8
links within, 3-4-1, 3-4-8
O period function, 6-4-7– 6-4-11
Periodic Reset field, Continuous Faceplate, 2-3-53
PI Act field, Continuous Faceplate, 2-2-16
Off logic statement, 6-3-8, 6-3-12– 6-3-13 PI control algorithm, 2-2-3
Offset Gain KC field, Continuous Faceplate, 2-3-15 PID algorithm terms, 2-2-3
On logic statement, 6-3-8, 6-3-10– 6-3-11 PID control
On/Off Input field algorithm, 2-2-3
Analog Compressor screen, 9-2-4, 9-3-8 configuring, 2-2-13– 2-2-19
Discrete Compressor screen, 9-2-4, 9-3-13 PID controller function, 2-2-1– 2-2-42, 2-2-44–
on/off switch, Data Compression block, 9-2-4 2-2-46
open input situation, hold forward, 2-2-21– 2-2-22 algorithm, 2-2-2
Open Loop Stable field, ATC Configuration screen, bias option, 2-2-33, 2-2-36– 2-2-37
8-2-6, 8-2-7 Continuous Faceplate screen, 2-2-13– 2-2-17
open output situation, back balancing or tracking, (bias option), 2-2-36– 2-2-37
2-2-23– 2-2-24 (ratio option), 2-2-34– 2-2-35
operator Continuous Links screen, 2-2-13
in combined expressions, 6-3-23 (bias option), 2-2-37
logical, 6-3-20– 6-3-22 (ratio option), 2-2-35
mathematical, 6-3-20– 6-3-22 control algorithm, 2-2-2– 2-2-12
operator arrow, 1-1-12 deadband option, 2-2-38– 2-2-39, 2-2-41
Operator ControlBlock Mode, 2-1-9 deadband option effect on, 2-2-38
Operator motor controller block mode, effect on, deadband option response, 2-2-39
2-4-5 error squared, 2-2-5– 2-2-6
operator selectable block output, 2-3-16 feedforward control, 2-2-10
Operator valve controller block mode, effect on, gap option, 2-2-38– 2-2-40
2-4-41 gap option effect on, 2-2-38
OPR Alarm Entry field, Continuous Diagram screen, gap option response, 2-2-39
4-2-6 ratio option, 2-2-33– 2-2-35
Opt field, Continuous Faceplate screen, 2-2-5, tuning, 2-2-44– 2-2-48
2-2-12, 2-2-16, 2-2-33– 2-2-34, 2-2-36 velocity option, 2-2-12
Oscill Deadband field, ATC Configuration screen, Piecewise Linear Interpolator function, 2-3-1,
8-2-10 2-3-29– 2-3-33
OUT1 to OUT96 field, Continuous Faceplate Continuous Faceplate screen, 2-3-30– 2-3-31
screen, piecewise linear function, 2-3-31 Continuous Links screen, 2-3-31
output example, 2-3-32– 2-3-34
continuous, 1-2-6 PIOB
discrete, 1-2-4 system flags, 7-2-3
output blocks, 1-1-1 user flags, 7-2-6
relationship to ControlBlocks, 1-1-2 Plant Unit field
Output field Block Directory screen, 1-3-3
Continuous Diagram screen, 4-2-6 Block Status screen, 1-3-5
Continuous Faceplate screen, 2-1-11 Continuous Diagram screen, 4-2-6
output types, 1-2-1– 1-2-6 Discrete Faceplate screen, 5-1-6
Output: High Lim field, Continuous Faceplate, PLCB status bit codes, 7-5-3
2-1-11 Plnt field, Discrete Diagram screen, 6-2-6
Output: Low Lim field, Continuous Faceplate, Point to Compress field
2-1-11 Analog Compressor screen, 9-3-9
Output: Mn Rate Lim field, Continuous Faceplate, Discrete Compressor screen, 9-3-13
2-1-11 Polynomial function, 2-3-1, 2-3-29, 2-3-34– 2-3-37
Output/Deviation field, Continuous Faceplate, 2-1-7 Continuous Faceplate, 2-3-34– 2-3-35
outputs, 3-4-1 Continuous Links screen, 2-3-35
Overview field, Discrete Faceplate screen, 5-1-6 example, 2-3-36– 2-3-37

CB: Index-11
position algorithm, 2-2-2 Reset Input field, Continuous Faceplate screen,

Pre--Bias field, Continuous Faceplate, 2-3-40 9-2-5, 9-2-7, 9-2-10, 9-3-5
preconfigured motor control functions, 2-4-3– Reset Period field, Continuous Faceplate screen,
2-4-39 2-3-53
preconfigured valve control functions, 2-4-39– retry rates, event transmission, 9-2-9
2-4-68 Right CP: Boot field, ControlFile Status screen,
Prgm field, ControlFile Status screen, 3-4-17 3-4-14, 3-4-15
Prgm Rev field, ControlFile Status screen, 3-4-17 Rise Hi Lim field, Continuous Faceplate screen,
Primary field, ControlFile Status screen, 3-4-17 Velocity Limiter function, 2-3-58
Priority field, Discrete Diagram screen, 6-2-6 Rise Limit field, Continuous Faceplate screen,
process alarms, priorities, 4-1-10, 4-3-2 Velocity Limiter function, 2-3-58
Process Deadtime field, ATC Configuration screen, Rise logic statement, 6-3-8, 6-3-14– 6-3-15
8-2-10 Rpt field, Discrete Diagram screen, 6-2-6
process dynamics, modeling, 2-3-10
process modeling applications, 2-3-10– 2-3-15
Prop Band field, Continuous Faceplate, 2-2-16 S
proportional term, 2-2-4, 2-2-5
algorithms, 2-2-5 Sample Time field
PV Filter Constant field, ATC Configuration screen, Continuous Diagram screen, 4-2-7
8-2-11 Continuous Faceplate screen, 9-3-5
PV1 to PV96 field, Continuous Faceplate screen, SC field, Continuous Faceplate screen, 2-1-12
piecewise linear interpolator function, 2-3-31 SC Time Out field, ControlFile Status screen,
3-4-18
scaling, 1-1-3
Q and logic step evaluation, 6-1-6
continuous inputs, 3-2-9– 3-2-15
example, 3-2-10
Q Alarms field, Continuous Diagram screen, 4-2-7 sensitivity, 3-2-11
Q field, Continuous Links screen, 3-2-6 types, 3-2-9
Q page, Continuous Diagram screen, 4-1-8 Scan Time field, ControlFile Status screen, 3-4-18
screen
Block References, 3-4-21– 3-4-22
R Block References screen, 1-1-8
Continuous Diagram, 4-2-1– 4-2-7
Continuous Diagram screen, 1-1-8
ramp function, 6-4-16– 6-4-17 Continuous Faceplate, 2-1-1– 2-1-12
ramping a variable, 6-4-16– 6-4-17 Continuous Faceplate screen, 1-1-8
Rate Lim field, Continuous Faceplate screen Continuous Links, 3-2-1– 3-2-15
bias, 2-2-37, 2-3-40 Continuous Links screen, 1-1-8
ratio, 2-2-35, 2-3-40 Discrete Diagram, 6-2-1– 6-2-11
setpoint, 2-2-16 Discrete Diagram screen, 1-1-8
rate--limited function, 2-3-57– 2-3-59 Discrete Faceplate, 5-1-1– 5-1-7, 5-2-1– 5-2-13
rate--of--change alarms, 4-1-1 Discrete Faceplate screen, 1-1-8
ratio, adjustable, 2-3-38– 2-3-42 Discrete Links, 3-3-1– 3-3-7
Ratio field, Continuous Faceplate screen, 2-2-35 Discrete Links screen, 1-1-8
Ratio Gain field, Continuous Faceplate screen, Second input field, Continuous Faceplate, 2-1-7
2-3-40 Select Number field, Continuous Faceplate screen,
ratio option, PID function, 2-2-33– 2-2-35 Signal Selector function, 2-3-44
Ratio/Bias function, 2-3-1, 2-3-38– 2-3-42 selector function, 2-3-43– 2-3-46
bias bar scaling example, 2-3-41 Set logic statement, 6-3-3, 6-3-6– 6-3-7
bias term configuration, 2-3-41– 2-3-42 Set Point Trig Mag field, ATC Configuration screen,
Continuous Faceplate screen, 2-3-39– 2-3-40 8-2-11
Continuous Links screen, 2-3-39 setmode n function, 6-4-22– 6-4-23
pre--bias term configuration, 2-3-41 setpoint adjusting
ratio term configuration, 2-3-41 Fall logic statement, 6-3-16– 6-3-17
Remote ControlBlock Mode, 2-1-9 Rise logic statement, 6-3-14– 6-3-15
Remote motor controller block mode, effect on, Setpoint High Lim field, Continuous Faceplate,
2-4-5 2-2-16
Remote valve controller block mode, effect on, setpoint locking and setting
2-4-41 Off logic statement, 6-3-12– 6-3-13
Report field, Discrete Diagram screen, 6-2-11 On logic statement, 6-3-10– 6-3-11

CB: Index-12
Setpoint Low Lim field, Continuous Faceplate, displaying, 5-2-9– 5-2-10

2-2-16 hold forward flag information, 7-6-1– 7-6-2
Setpoint Rate Lim field, Continuous Faceplate, I/O blocks, 7-2-3
2-2-16 testing for, 7-3-11
Setpoint Totalizer function, 2-3-47– 2-3-50, 2-3-55– valid data flag information, 7-6-1– 7-6-2
2-3-56
Continuous Links screen, 2-3-50 T
cutoff types, 2-3-49
setpoint tracking, 2-2-19 Tag field
setuauto function, 6-4-20– 6-4-21 ATC Configuration screen, 8-2-6
setuman function, 6-4-20– 6-4-21 Block Directory screen, 1-3-3
Shed Mode field, Continuous Faceplate screen, Block References screen, 3-4-22
2-1-12 Block Status screen, 1-3-5
SIB Continuous Diagram screen, 4-2-7
system flags, 7-2-3 Continuous Faceplate screen, 2-1-11– 2-1-12
user flags, 7-2-7 Continuous Links screen, 3-2-7
Signal Selector function, 2-3-1, 2-3-43– 2-3-46 Discrete Diagram screen, 6-2-6
Continuous Faceplate screen, 2-3-44 Discrete Faceplate screen, 5-1-7, 5-2-2, 5-2-4,
Continuous Links screen, 2-3-45 5-2-7
siterm function, 6-4-2 Discrete Links screen, 3-3-5
Size field Third input field, Continuous Faceplate, 2-1-7
Block Directory screen, 1-3-3 TIB
Block Status screen, 1-3-5 system flags, 7-2-3
Snapshot Input field user flags, 7-2-8
Analog Compressor screen, 9-2-4, 9-3-9 time function, 6-4-18– 6-4-19
Discrete Compressor screen, 9-2-4, 9-3-13 Time Limit field
snorm function, 6-4-28– 6-4-29 Analog Compressor screen, 9-2-4, 9-3-10
SOURCE field Discrete Compressor screen, 9-2-4, 9-3-14
Continuous Links screen, 3-2-7, 3-2-8 timer function, 6-4-12– 6-4-13
Discrete Links screen, 3-3-5– 3-3-7 timing operations, 6-4-3– 6-4-15
Source Link field, Block References screen, 3-4-22 tips
ssm function, 6-4-2 configuring ControlBlock functions, 2-5-4– 2-5-5
sss function, 6-4-2 configuring discrete faceplate, 5-3-3
sstand function, 6-4-28– 6-4-29 configuring flag, 7-6-1– 7-6-2
Stack Totalizer function, 2-3-51– 2-3-55 configuring links, 3-5-3– 3-5-4
Continuous Faceplate screen, 2-3-52– 2-3-53 configuring logic steps, 6-5-2– 6-5-4
Continuous Links screen, 2-3-54 totalizer functions, 2-3-1, 2-3-47– 2-3-55
Start Cal field, ControlFile Status screen, 3-4-18 tracing a link to a destination block, 3-4-21– 3-4-22
State field track function, 6-4-2
Analog Compressor screen, 9-2-5, 9-3-9 Track Input field, Continuous Faceplate screen,
Discrete Compressor screen, 9-2-7, 9-3-14 2-2-16
Discrete Links screen, 3-3-5 cascade control loop, 2-2-27
status bits, 7-5-1– 7-5-5 Lead/Lag function, 2-3-15
ControlBlock codes, 7-5-4 Math function, 2-3-18
definition, 7-5-1 PID function, 2-2-16, 2-2-27– 2-2-32
input/output block codes, 7-5-2 piecewise linear interpolator function, 2-3-31
PLCB codes, 7-5-3 polynomial function, 2-3-35
testing, 7-5-5 Ratio/Bias function, 2-3-40
Status field, ControlFile Status screen, 3-4-18 Signal Selector function, 2-3-44
Step field, Discrete Diagram screen, 6-2-6 Track PV field, Continuous Faceplate screen,
Steps in MANUAL field, Discrete Faceplate screen, Velocity Limiter function, 2-3-58
5-1-6 Trackband field, Continuous Faceplate screen,
Steps in Manual field Signal Selector function, 2-3-44– 2-3-46
Block Directory screen, 1-3-3 tracking
Block Status screen, 1-3-5 faceplate indicators, 2-2-26
Discrete Diagram screen, 6-2-6 in a cascade control loop, 2-2-25– 2-2-32
supervisor arrow, 1-1-12 indicators, 2-2-26
system flags LS--PV Track field, 2-2-27
consoles, 7-4-3 open output situation, 2-2-23– 2-2-24
ControlBlock, 7-3-2, 7-3-7– 7-3-8 setpoint, 2-2-19

CB: Index-13
transmitter scaling, 3-2-9 valid data flag information

treset function, 6-4-37 ControlBlocks, 7-6-2
troubleshooting input/output blocks, 7-6-1
configuring Continuous Diagram screen, 4-3-1 Value field
configuring ControlBlock functions, 2-5-2– 2-5-3 Continuous Faceplate screen, 2-1-11
configuring ControlBlocks, 1-4-1 Continuous Links screen, 3-2-7
configuring logic steps, 6-5-1– 6-5-2 valve controller functions, 2-4-39– 2-4-68
discrete faceplate, 5-3-1 common features, 2-4-39
links, 3-5-1– 3-5-2 DASVC, 2-4-50– 2-4-57
tuning, adaptive, 2-2-47– 2-2-48 discrete valve controller, 2-4-39
Tuning Display Directory screen, 2-2-46 DMVC, 2-4-58– 2-4-67
Tuning Display field, ATC Configuration screen, DVC, 2-4-42– 2-4-49
8-2-6 effect of block mode, 2-4-41
Tuning Display screen, 2-2-44, 2-2-46 preconfigured, 2-4-40
tuning operations, 2-2-44– 2-2-45 unconfigured, 2-4-40
Tuning Sens field, ATC Configuration screen, variable
8-2-11 continuous, 6-3-18
Tuning Toler field, ATC Configuration screen, 8-2-11 discrete, 6-3-19
Type field examples in logic statements, 6-3-24
Block Directory screen, 1-3-3 in combined expressions, 6-3-23
Block Status screen, 1-3-5 velocity algorithm, 2-2-11
Velocity Limiter function, 2-3-1, 2-3-57– 2-3-59
U Continuous Links screen, 2-3-59
velocity option, PID function, 2-2-12
vfill function, 2-3-3, 6-4-2
Unit 1, 2, 3 field, Discrete Faceplate screen, 5-1-7
Units field
Continuous Links screen, 3-2-7
unlinked inputs, 6-3-19
W
user flag, displaying, 5-2-9– 5-2-10
user flags
wait function, 6-4-14– 6-4-15
console, 7-4-3
When field, Discrete Diagram screen, 6-2-11
ControlBlock, 7-3-2– 7-3-6
I/O blocks, 7-2-4– 7-2-7
testing for, 7-3-12
user--defined discrete ControlBlock, 2-4-2
Z
V zero slope (box car) algorithm, 9-1-2– 9-1-3
Zero Slope Deadband field, Analog Compressor
V function, 6-4-2 screen, 9-2-3, 9-2-5, 9-3-10

CBP1 PDF

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

CBP1 PDF

Hochgeladen von

Copyright:

Verfügbare Formate

RS3t

Performance Series 1, Release 4.0

Fisher-Rosemount Systems, Inc.

Telephone: (612) 895-2000

ControlBlock Configuration Manual 1984-2646-21x0

Please give us your feedback to help improve this manual.

3. What could be changed in this manual to make it more useful?

May we contact you about your comments? j Yes j No

Fisher-Rosemount Systems, Inc.

Seal with tape.

About This Manual

D Chapter 1 Describes ControlBlocks, Inputs and Outputs, and

Changes for This Release

D Updated document frontmatter.

RS3: ControlBlock Configuration Manual About This Manual

Revision Level for This Manual

For This Refer to This Document:

P1R4.0 ControlBlock Configuration Manual

P1R1.0 ControlBlock Configuration Manual Sept 1999 1984-2646-21x0

18R2 ControlBlock Configuration Manual August 1994 1984-2646-18x1

18R1 ControlBlock Configuration Manual October 1993 1984-2646-18x1

17 ControlBlock Configuration Manual August 1992 1984-2646-17x1

16 ControlBlock Configuration Manual January 1992 1984-2646-16x1

15 ControlBlock Configuration Manual January 1991 1984-2646-15x1

References to Other Manuals

Manual Title Chapter Manual Title Chapter-Section

Abbreviations of Manual Titles

RS3: ControlBlock Configuration Manual About This Manual

You should be familiar with the information in the following documents

RS3: ControlBlock Configuration Manual About This Manual

Chapter 1: Introduction to ControlBlocks

Section 1: What is a ControlBlock? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-1

Section 2: Types of ControlBlock Inputs and Outputs . . . . . . . . . . . . . . . . . 1-2-1

Section 3: Block Directory and Block Status Screens . . . . . . . . . . . . . . . . . 1-3-1

Section 4: Hints for Configuring ControlBlocks . . . . . . . . . . . . . . . . . . . . . . . 1-4-1

Chapter 2: Configuring ControlBlock Functions

Section 1: Configuring Common Fields on the Continuous Faceplate . . 2-1-1

RS3: ControlBlock Configuration Manual Contents

Common Fields on the Continuous Faceplate Screen . . . . . . . . . . . . . . . . . . . . . . 2-1-10

Section 2: Configuring PID Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-1

Section 3: Configuring Other ControlBlock Continuous Functions . . . . . 2-3-1

RS3: ControlBlock Configuration Manual Contents

Part 1: Scaling and Summing the Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3-24

Section 4: Configuring ControlBlock Discrete Functions . . . . . . . . . . . . . . 2-4-1

RS3: ControlBlock Configuration Manual Contents

DDSMC Input Functions and Output Conditions . . . . . . . . . . . . . . . . . . . . . 2-4-29

Section 5: Hints for Configuring ControlBlock Functions . . . . . . . . . . . . . . 2-5-1

Chapter 3: Configuring Block Links

Section 1: Introduction to Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1-1

RS3: ControlBlock Configuration Manual Contents

Section 2: Continuous Links Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-1

Section 3: Discrete Links Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3-1

Section 4: Configuration Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-1

Section 5: Hints for Configuring Block Links . . . . . . . . . . . . . . . . . . . . . . . . . 3-5-1

RS3: ControlBlock Configuration Manual Contents

Chapter 4: Configuring a Continuous Diagram Screen

Section 1: Configuring ControlBlock Alarm Points . . . . . . . . . . . . . . . . . . . . 4-1-1

Section 2: Configuring a Continuous Diagram Screen . . . . . . . . . . . . . . . . . 4-2-1

Section 3: Hints for Configuring a Continuous Diagram Screen . . . . . . . . 4-3-1

Chapter 5: Configuring a Discrete Faceplate Screen

Section 1: Discrete Faceplate Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1-1

Section 2: Configuring a Discrete Faceplate . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2-1

Section 3: Hints for Configuring Discrete Faceplates . . . . . . . . . . . . . . . . . . 5-3-1