Sunteți pe pagina 1din 101

Profit Optimizer

A
Distributed Quadratic Program
(DQP)

Installation Reference
for AM, AxM and Open LCN-Side

Rev 1.4
1/00

PR20-400

Copyright, Notices, and Trademarks


Printed in U.S.A. Copyright 2000 by Honeywell Inc.

While this information is presented in good faith and believed to be accurate,


Honeywell disclaims the implied warranties of merchantability and fitness for a
particular purpose and makes no express warranties except as may be stated in its
written agreement with and for its customer.
In no event is Honeywell liable to anyone for any indirect, special or consequential
damages. The information and specifications in this document are subject to change
without notice.

Profit, TDC 3000 and TotalPlant are U. S. registered trademarks of Honeywell Inc.

Other product names are trademarks of their respective owners.

Honeywell
Industrial Automation and Control
2500 West Union Hills
Phoenix, AZ 85053

1/00

Profit Optimizer Installation Reference

Honeywell Inc.

iii

Table of Contents

Copyright, Notices, and Trademarks ....................................................................................iii


Table of Contents....................................................................................................................iii
About This Publication .........................................................................................................viii
Statement of Work .........................................................................................viii
Release Information.......................................................................................viii
Who Should Use This Book ...........................................................................viii
Other Books in the Profit Library....................................................................viii
RMPCT /Profit Course Information ................................................................viii
How This Book Is Organized........................................................................... ix
Writing Conventions Used in This Book .......................................................... x
References...............................................................................................................................xi
Documentation .................................................................................................... xi
Technical Assistance............................................................................................................xii
If You Need Assistance.................................................................................. xii
International Customers ................................................................................. xii
Customers Inside the United States .............................................................. xii
Arizona Customers......................................................................................... xii
Services Provided .......................................................................................... xii
Time Saving Tip ............................................................................................. xii
Section 1 Before You Begin ...............................................................................................1
1.1 Overview .................................................................................................................1
In This Section .................................................................................................1
Profit Optimizer on TPS ...................................................................................1
Scan the Quick Reference ...............................................................................1
1.2 Profit Optimizer Point Requirements.......................................................................2
Profit Optimizer Points .....................................................................................2
On-line Optimizer Points and Simulator Points ................................................3
IllustrationHow Profit Optimizer Points Share Information ...........................4
1.3 Scheduling Points ...................................................................................................5
Execution Order ...............................................................................................5
Scheduling Simulation Points...........................................................................5
Scheduling Interface Points .............................................................................5
Scheduling the Optimizer Point........................................................................5
Profit Optimizer Point Builder ...........................................................................6
1.4 Installation Quick Reference .................................................................................7
Section 2 Checking Your System ......................................................................................9
2.1 Overview ...............................................................................................................9
In This Section .................................................................................................9
Check the System ............................................................................................9
If you Need to Install Load Modules .................................................................9
2.2 Hardware and Software Requirements ...............................................................10
1/00

Profit Optimizer Installation Reference


Honeywell Inc.

iii

Table of Contents

Hardware Requirements................................................................................ 10
Software Requirements ................................................................................. 10
2.3 Configuration Requirements............................................................................... 11
System Paths................................................................................................. 11
How to Quicken Graphics Response............................................................. 11
Network Configuration Requirements............................................................ 11
A Caution about Creating New Units ............................................................. 11
Section 3 Installing the Profit Optimizer Load Module ................................................. 13
3.1 Overview............................................................................................................. 13
In This Section............................................................................................... 13
Do I Need the Profit Optimizer Load Module?............................................... 13
3.2 Installing the Profit Optimizer Load Module (AM Only)....................................... 14
Purpose of This File....................................................................................... 14
Do I Need This file? ....................................................................................... 14
To Load the File Use the Macro and Follow the Prompts ............................. 14
Configuring the AM ........................................................................................ 15
Section 4 Installing the Profit Optimizer Program and the NT-Side Software ............ 17
4.1 Overview............................................................................................................. 17
In This Section............................................................................................... 17
Are Your Paths Correct? ............................................................................... 17
Create a DQP Directory?............................................................................... 17
Before You Do Anything Else ........................................................................ 17
4.2 Directories and Files You Will Be Using ............................................................. 18
Profit Optimizer Media ................................................................................... 18
Parameter Lists ............................................................................................. 18
Custom Data Segments ................................................................................ 18
Object Code................................................................................................... 19
4.3 Compiling and Loading the Profit Optimizer Program ........................................ 20
Back Up ......................................................................................................... 20
ProcedureUsing the Installation Macros .................................................... 20
Procedure Manually Installing the Program Files....................................... 20
4.4 Installing and Configuring the NT-Side Software................................................ 22
Installation Requirements and Techniques ................................................... 22
Access Level ................................................................................................. 22
GANT............................................................................................................. 22
APP................................................................................................................ 22
Section 5 Building an On-line Simulation....................................................................... 23
5.1 Overview............................................................................................................. 23
In This Section............................................................................................... 23
Do I Need to Build a Simulation?................................................................... 23
Profit Optimizer Simulations Need These Points........................................... 23
Point Naming Conventions ............................................................................ 23
Manually Building Points? Read This......................................................... 23
Building Points? Read This ....................................................................... 23
5.2 Building the Simulated BIn MVs ......................................................................... 25
iv

Profit Optimizer Installation Reference


Honeywell Inc.

1/00

Table of Contents

Application Notes ...........................................................................................25


Set These Parameters ...................................................................................25
5.3 Building the Simulated BIn DVs ..........................................................................26
Application Notes ...........................................................................................26
Set These Parameters ...................................................................................26
5.4 Building the Driver Points1st Pass ..................................................................27
Application Notes ...........................................................................................27
Set These Parameters ...................................................................................27
5.5 Building the Simulated BOuts .............................................................................32
Application Notes ...........................................................................................32
Set These Parameters ...................................................................................32
5.6 Attaching Model Coefficients to the Sim BOuts ..................................................34
Application Notes ...........................................................................................34
For Help .........................................................................................................34
Procedure.......................................................................................................34
5.7 Building the Driver Points2nd Pass .................................................................36
Application Notes ...........................................................................................36
Set These Parameters ...................................................................................36
Section 6 Building Profit Optimizer Interface Points .....................................................37
6.1 Overview .............................................................................................................37
In This Section ...............................................................................................37
Point Naming Conventions.............................................................................37
6.2 Building DQP-Side Interface Points ....................................................................38
Application Notes ...........................................................................................38
Set These Parameters ...................................................................................38
6.3 Building Profit Controller (RMPCT)-Side Interface Points...................................39
Application Notes ...........................................................................................39
Set These Parameters ...................................................................................39
6.4 Building BOut Interface Points ............................................................................40
Application Notes ...........................................................................................40
Set These Parameters ...................................................................................40
Section 7 Building Optimization Points and Initializing the Messages .......................43
7.1 Overview .............................................................................................................43
In This Section ...............................................................................................43
Profit Optimizers Optimization Points............................................................43
Optimization Points and the Profit Optimizer Program ..................................44
Loading the Alter Parameter Message File....................................................44
Point Naming Conventions.............................................................................44
Point Building Order .......................................................................................44
7.2 Building the Message Point (AM) ........................................................................45
Application Notes ...........................................................................................45
Set These Parameters ...................................................................................45
7.3 Building the Optimizer Point ................................................................................46
Application Notes ...........................................................................................46
Set These Parameters ...................................................................................46
7.4 Initializing the Profit Optimizer Messages ...........................................................47
1/00

Profit Optimizer Installation Reference


Honeywell Inc.

Table of Contents

Application Notes........................................................................................... 47
Questions and Answers................................................................................. 47
Translating the Messages from English ........................................................ 47
Procedure ...................................................................................................... 47
Initializing messages for the APP Node ........................................................ 48
Section 8 Building DQP_LIST Point ................................................................................ 51
8.1 Overview............................................................................................................. 51
In This Section............................................................................................... 51
What DQP_LIST Does .................................................................................. 51
Point Naming Conventions ............................................................................ 51
8.2 Building DQP_LIST............................................................................................. 52
Application Notes........................................................................................... 52
Set These Parameters................................................................................... 52
Section 9 Installing the Profit Optimizer Graphics ........................................................ 55
9.1 Overview............................................................................................................. 55
In This Section............................................................................................... 55
Read Me ........................................................................................................ 55
Graphics Files and the DQP_LIST Point ....................................................... 55
Work from a Backup...................................................................................... 55
File Descriptions ............................................................................................ 56
9.2 Procedure ........................................................................................................... 57
Graphics and LCN Software.......................................................................... 57
Graphics and the Picture Editor..................................................................... 57
Reading, Verifying, Compiling, and Loading.................................................. 57
Section 10 Bringing the Optimizer On-line..................................................................... 59
10.1 Overview........................................................................................................... 59
In This Section............................................................................................... 59
Using the Optimizer Detail Screen ................................................................ 59
For Help ......................................................................................................... 59
10.2 Installing the Off-line Design Files .................................................................... 60
ProcedureAM Implementations.................................................................. 60
Procedure APP Node Implementations ..................................................... 61
10.3 Setting and Checking the Start-Up Configuration............................................. 62
Procedure ...................................................................................................... 62
10.4 Linking the Object Code ................................................................................... 63
Link List ......................................................................................................... 63
Procedure ...................................................................................................... 64
10.5 Activating the Points, Reading In the Design Files and Tying in Controllers .... 65
Reality CheckCheck ...................................................................................... 65
Procedure ...................................................................................................... 65
Checking the Read-File StampsChecking the Read-File Stamps................. 67
Section 11 Trouble Shooting ........................................................................................... 69
11.1 Running out of AM Memory.............................................................................. 69

vi

Profit Optimizer Installation Reference


Honeywell Inc.

1/00

Table of Contents

Symptoms: .....................................................................................................69
Solution: .........................................................................................................69
Appendix CDS Descriptions.............................................................................................71
Bridged DV Model Point ..............................................................................................71
Appendix DQP Configuration File (TPS Node Only) ......................................................85

1/00

Profit Optimizer Installation Reference


Honeywell Inc.

vii

About This Publication


Statement of Work

The following table describes the audience, purpose, and scope of this book:
Purpose

This book explains how to install the Profit Optimizer software


and build the point database for a Profit Optimizer application
on a TotalPlant Solution network.

Audience

Process and control engineers

For Product Release

Release
Information

All Profit releases (see Release Information below)

LCN releases 500 and 600 series.

All AM releases except 40.43-40.45; 41.1-41.14

This is document version 1.4 for Profit Optimizer software release 160.00
releases after R160.00 see the Release Notes.

This Book

Anyone responsible for installing, implementing, or maintaining Profit Optimizer


can use this book.

Other Books in

See References later in this section for a list of other Profit publications.

Who Should Use

the Profit Library


RMPCT /Profit
Course
Information

Honeywell Hi-Spec Solutions offers training that explains the math and
conceptual underpinning of Profit Controller (RMPCT) and how to implement
Profit Controller applications.
Engineers wanting a more technical exposure to Profit Optimizer can contact
their Honeywell Hi-Spec Solutions sales person.

viii

Profit Optimizer Installation Reference


Honeywell Inc.

1/00

About this Publication


How This Book Is
Organized

The following table summarizes what each section in this book tells you about
this publication and about Profit Optimizer.
In This Section

You Can Find This Information

About This Publication


(You are here)

How to make the best use of this book, and how the
information is ordered.
What information you can find in the different sections.
What writing conventions have been used throughout this
book and the Profit library.

1/00

Section 1, "Before You Begin

Introduction to the Profit Optimizer point database and an


installation quick reference.

Section 2, "Checking Your


System

Pre installation hardware, software, and network


configuration checklist.

Section 3, "Installing the Profit


Optimizer Load Module

Instructions for installing the Profit Optimizer load module,


and NCF requirements.

Section 4, " Installing the Profit


Optimizer NT-Side Software

Instructions for installing the Profit Optimizer Parameter


Lists, Custom Data Segments and object code, and the
software for APP Node implementations.

Section 5, Building an Online


Simulation

Instructions for building and naming the driver point and


bridge output sim points, and how to attach model
coefficients.

Section 6, Building Profit


Optimizer Interface Points

Instructions for building and naming BOut, RMPCT-side


and DQP-side interface points.

Section 7, Building Optimizer


Points and Initializing the
Messages

Instructions for building Optimizer and Message Points

Section 8, Building DQP_LIST


Point

Instructions for building the Profit Optimizer application


list.

Section 9, Installing the Profit


Optimizer Graphics

Instructions for reading, verifying, compiling, and loading


the graphics files for the Profit Optimizer interface.

Section 10, Bringing the


Optimizer Online

Instructions for installing the offline design files, how to set


the startup configuration, and how to link and activate the
Profit Optimizer points.

Section 11, Trouble Shooting

Running out of AM Memory

Appendix, CDS Descriptions

Descriptions of the Profit Optimizer custom parameters.

Appendix, DQPP Configuration


File (TPS Node)

Example configuration file

How to install and initialize the Profit Optimizer messages.

Profit Optimizer Installation Reference


Honeywell Inc.

ix

About this Publication


Writing
Conventions Used
in This Book

The following writing conventions have been used throughout this book and
other books in the Profit Suite library.

Words in double quotation marks " " name sections or subsections in this
publication.

Words in italics name book titles, add grammatical emphasis, introduce


words that are being referenced or defined, or represent mathematical
variables. The context makes the meaning and use clear.

Words in bold type indicate paragraph topics or bring important phrases


to your attention.

Shading brings paragraphs and table entries to your attention.

Windows pull down menus and their options are separated by an angle
bracket >. For example, Under Settings> Communications, set the baud
rate.

Messages and information that you type appear in Courier font.

Acronyms, Scan parameters, point names, file names, and paths appear in
UPPERCASE. The context makes the meaning and use clear.

Command keys appear in UPPERCASE within angle brackets. For


example, press <ENTER>.

TPS user station touch-screen targets appear in rounded boxes. For


example, touch
MODIFY NODE .

Graphic buttons appear in UPPERCASE within brackets [ ]. For example,


touch [TAG].

Point-dot-parameter means a point name and one of its parameters. For


example, point-dot-SP means the SP parameter for the point.

Zero as a value and when there is a chance for confusion with the letter O
is given as . In all other cases, zero as a numerical place holder is given
as 0. For example, 1.0, 10, 101, CV1, parameter P.

The terms screen and display are used inter changeably in discussing the
graphical interfaces. The verbs display a screen and call a screen are also
used inter changeably.

The names Profit Controller (RMPCT), Profit Controller and RMPCT


may be used interchangeably.

The names Profit Optimizer (DQP), Profit Optimizer and DQP may be
used interchangeably.
The names Profit Design Studio, and APC Development Environment may be
used interchangeably.

Profit Optimizer Installation Reference


Honeywell Inc.

1/00

References
The following comprise the Profit Suite library.
Documentation

1/00

Title
General
Profit Controller (RMPCT) Concepts Reference
Profit Controller (RMPCT) Designers Guide (Off-Line Design)
Profit Optimizer Designers Guide (Off-Line Design)
Profit Toolkit Designers Guide
APC Development Environment (Old. Replaced by Designers Guides)
APC Identifier Users Guide
Profit-PID (RPID)
Profit Sensor Users Guide
Open
Profit Suite Installation Guide for Open Systems
Viewer - Controller - Optimizer - Toolkit
Profit Controller (RMPCT) Users Guide for Open Systems
Profit Optimizer Users Guide for Open Systems
Profit Toolkit Users Guide for Open Systems
Profit Trender Users Guide
FCCU Toolkit Users Guide for Open Systems
Fractionator Toolkit Users Guide for Open Systems
LCN
Profit Controller (RMPCT) Installation Reference for AM, AxM and Open LCN-Side
Profit Controller (RMPCT) Commissioning
Profit Controller (RMPCT) Users Guide for AM, AxM and Open LCN-Side
Profit Optimizer Installation Reference for AM, AxM and Open LCN-Side
Profit Optimizer Users Guide for AM, AxM and Open LCN-Side
Profit Suite ToolKit
TDC Data Converter
Performance Monitor
Simulation BackBuilder
Data Collector
RMPCT Cascade
Gain Scheduler
Step Test Builder
PV Validation
Fractionator Toolkit (LCN)
FCCU Toolkit (LCN)
Furnace Pass Balance Temperature Control Users Guide
Non-Linear Level Control Users Guide

Profit Optimizer Installation Reference


Honeywell Inc.

Number
RM09-400
RM11-410
PR11-400
AP11-400
AP09-100
AP09-200
RM11-100
PS09-100
RM20-501
RM11-401
PR11-421
AP11-401
RM11 431
AP13-201
AP13-101
RM20-400
RM20-410
RM11-400
PR20-400
PR11-420
AP09-300

AP13-100
AP13-200
AP09-600
AP09-700

xi

Technical Assistance

If You Need
Assistance

If you need technical assistance, contact your local Honeywell Service


Organization, as explained in the following paragraphs.

Customers

Outside of the United States, contact your local Honeywell Service


Organization. If you are not sure of the location or telephone number, call your
Honeywell representative for information.

Customers Inside
the United States

Within the United States, call the Technical Assistance Center (TAC) at the toll
free number 1-800-822-7673.

Arizona Customers

Within Arizona, the local number for TAC is 602-313-5558.

Services Provided

Calls to TAC are answered by a dispatcher from 7:00 A.M. to 5:00 P.M.,
Mountain Standard Time (6:00 A.M. to 4:00 P.M. when daylight savings time is
in effect).

International

Outside of these hours, emergency callsthose which affect your ability to


control or view a processwill be received by an answering service, and
returned within one hour. TAC maintains its own TPS network, and frequently
can duplicate problems on this equipment.
Time Saving Tip

xii

It is a good idea to make specific notes about the problem before making the
call. This helps to reduce delays and expedite answers.

Profit Optimizer Installation Reference


Honeywell Inc.

1/00

Section 1 Before You Begin


1.1

Overview

In This Section

This section introduces you to the Profit Optimizer point database and includes
a Quick Reference to introduce you to the installation procedures.

Profit Optimizer

The Profit Optimizer resides in either the standard Application Module (AM) ,or
the APP Node.

on TPS

The optimizer receives process inputs, Profit Controller (RMPCT) inputs,


executes its prediction and optimization algorithms, and then returns output to the
controllers as optimization targets, which are then used to drive the process
through the execution of various Profit Controller (RMPCT) points.
Objective Function

Ranges for
Combined
Constraints

Setpoints

Setpoints
Ranges

Scan the Quick


Reference

Profit Output

Ranges

RMPCT
2
Process
Outputs

Figure 1-1

Setpoints
Ranges

RMPCT
1
Process
Inputs

RMPCT 3 Input

Profit Output

RMPCT 2 Input

Profit Output

Process Inputs

RMPCT 1 Input

PROFIT

Process
Inputs

RMPCT
3
Process
Outputs

Process
Inputs

Process
Outputs

Process and RMPCT InputsOptimization Outputs

Use the Quick Reference at the end of this section for an overview of the software
installation and point building process. The Reference gives you a first-look at
the tasks you are going to perform to install Profit Optimizer on your system and
create the point database.
See the procedures in later sections for instructions.

1/00

Profit Optimizer Installation Reference


Honeywell Inc.

Section 1 Before You Begin


1.2

Profit Optimizer Point Requirements

1.2

Profit Optimizer Point Requirements

Profit Optimizer

These are the Profit Optimizer points for an optimizer implementation on TPS.

Points

Table 1-1

Profit Optimizer Point Descriptions

Point

Description

Interface Points

These points supply the input to Profit Optimizer, the output from Profit Optimizer to the Profit
Controllers (RMPCTs) and data for the Profit Optimizer displays.

Optimizer Point

The Profit Optimizer engine. Executes the bridge predictions and optimization algorithms, based
on process and RMPCT values.

Message Point (AM


only)

Outputs Profit Optimizer messages to the CRT or Journal Log.

Application List Point

Always named DQP_LIST. This point contains the names of all optimizers on an LCN, both
simulation and on-line.

Simulation Points

Model points take the place of process points in simulations. Simulations are optional.

Simulation Driver

The data collection point for a simulation.

Profit Optimizer Installation Reference


Honeywell Inc.

1/00

Section 1 Before You Begin


1.2
On-line Optimizer
Points and
Simulator Points

Profit Optimizer Point Requirements

Profit Optimizer points come in two types: application-specific points and


generic points. Application-specific points are comprised of on-line points and
simulation points.
The number of application-specific points are different for each implementation.
You might not need bridge predictions, and you may choose not to run
simulations. Generic points are required for all implementations.

Table 1-2

Lists the point requirements for an on-line optimizer and for running simulations:
Used for . . .

Point Types

Kind of Point

Simulation

On-line

Application-

System Points

Specific

Interface Points

Optimizer Point

Message Point

Simulation Points

Driver Point

DQP_LIST Point

Generic

1/00

Profit Optimizer Installation Reference


Honeywell Inc.

Section 1 Before You Begin


1.2

Profit Optimizer Point Requirements

IllustrationHow
Profit Optimizer

The following illustration might help you visualize how the Profit Optimizer
points pass information, on-line and in simulation.

Points Share
Information
PROFIT Optimizer List
Point

PROFIT Optimizer
Point

PROFIT Message
Point

DQP-Side
Interface Point 1

--- DQP-Side --Interface Point

DQP-Side
Interface Point n

RMPCT-Side
Interface Point 1

--- RMPCT-Side --Interface Point

RMPCT-Side
Interface Point n

RMPCT 1

---- RMPCT ----

RMPCT n

RMPCT 1
CV, MV, DV
Simulation Points

--- RMPCT --CV, MV, DV


Simulation Points

RMPCT n
CV, MV, DV
Simulation Points

PROFIT Bridge-Output
Points

Profit
Bridge Output
Simulation

Bridge Output Simulation


Driver Point

Process
Simulation Driver Point

Simulation Points replace


process points in simulation
mode.

Figure 1-2

How Profit Optimizer Points Pass Information

Profit Optimizer Installation Reference


Honeywell Inc.

1/00

Section 1 Before You Begin


1.3

1.3

Scheduling Points

Scheduling Points

Execution Order

Scheduling
Simulation Points

Profit Optimizer points must execute in a prescribed order to ensure proper data
flow. When giving cycle assignments to your points, this is the order the points
must execute:
RMPCT controllers
Bridge simulation driver point
Simulation bridge output points
Bridge output points
Optimizer point
Building a simulator is optional. When there is a simulator, the simulation points
substitute for the system points.
Schedule the driver point to execute after RMPCT controllers. Schedule bridge
output sim points to execute next.
The sim bridge output point assignments are made in either of two ways. Either
schedule the sim bridge outputs:

Scheduling
Interface Points

All on the same cycle, one cycle after the driver point, or
On the same cycle as the driver point, using the BEFAFT parameter.

When scheduling interface points, be aware of the following: (1) In a simulation,


the interface points must execute after the simulation points. (2) For an on-line
optimizer, the points supplying bridge input values to the bridge output interface
points must execute before the bridge output interface points.
Schedule the bridge output interface points:
One cycle after the simulated bridge output points.

Scheduling the
Optimizer Point

Execution Order The optimizer point executes last, one cycle after the bridge
output interface points.
Scheduling More Than One Optimizer When there is more than one Profit
optimizer on an LCN (simulation or on-line), stagger their execution, as well as
their execution with respect to the RMPCTs. The number of cycles between
optimizers depends upon the number of MVs.

Rule of Thumb Keep the number of cycles between one optimizer equal to the
number of MVs in the previous optimizer.
Example If Profit Optimizer A has ten MVs, and its optimizer point executes on
cycle 10, schedule the first bridge output interface of Profit Optimizer B on cycle
20.
If You Need More Information For more information about point scheduling,
see the TDC 3000x Application Module Implementation #1 Manual (Control
Functions) in the TDC 3000x Bookset.
1/00

Profit Optimizer Installation Reference


Honeywell Inc.

Section 1 Before You Begin


1.3

Scheduling Points

Profit Optimizer
Point Builder

What This Tool Is The Point Builder software automates the Profit Optimizer
point building and optimizer configuration process. This tool is particularly
helpful for applications that require numerous points.
The Point Builder is not necessary to get a Profit Optimizer application onto a
system, but it does save time. The Point Builder builds points, attaches CDS
Packages, schedules, and sets point parameters without having to use Builder
commands or the Point Detail display.
What This Tool Does The Point Builder creates .EB files from entered process
and simulation information, that are then easily transferred from PC to LCN
format and loaded onto the LCN. The .EB files contain pre-built Profit
Optimizer application points so each point does not need to be manually built.
The Point Builder also outputs an executable (.EC) file that automatically links
the CL object code to the points.
How to Get the Software The Point Builder is part of the standard Profit
Design Studio (formerly APCDE) software, and must be ordered separately.

Profit Optimizer Installation Reference


Honeywell Inc.

1/00

Section 1 Before You Begin


1.4 Installation Quick Reference

1.4 Installation Quick Reference


Table 1-3

Installation Quick Reference

Step

Action

See

1.

Make sure your system meets hardware, software,


resource, and configuration requirements.

Section 2, Checking Your System

2.

Modify the NCF.

Section 3, Installing the Profit Optimizer Load


Module

3.

For AM implementations, install the Profit Optimizer load


module.

4.

For APP Node implementations, install and configure the


Profit Optimizer NT-side software.

5.

Install the Profit Optimizer Parameter Lists, Custom Data


Segments, and CL object code.

6.

Build simulated bridge output points.

7.

Attach model coefficients.

8.

Build the driver point.

9.

Section 5, Building an On-line Simulation

. Build DQP-side and RMPCT-side interface points (AM only


implementations)

Section 6, Building Profit Optimizer Interface Points

10. . Build bridge output interface points.

Section 6, Building Profit Optimizer Interface Points

11.

Section 7, Building Optimizer Points and Initializing


the Profit Optimizer Messages

Build the message point (AM only implementations).

12. . Build the optimizer point.


13.

Initialize the Profit Optimizer Messages.

14.

Build the DQP_LIST point (the application point).

Section 8, Building DQP_LIST Point

15.

Verify, compile, and install the graphics files.

Section 9, Installing the Profit Optimizer Graphics

16.

Install the model files from the off-line design.

Section 10, Bringing the Optimizer On-line

17.

Configure the Optimizer Detail screen on the Operator


displays.

18.
19.

Link the CL code to the Profit Optimizer points.

1/00

Activate the points, read in the optimizer design files, and


commission.

Profit Optimizer Installation Reference


Honeywell Inc.

Section 1 Before You Begin


1.4 Installation Quick Reference

Profit Optimizer Installation Reference


Honeywell Inc.

1/00

Section 2 Checking Your System


2.1 Overview
In This Section

This section reviews the hardware, software, and network configuration


requirements for implementing Profit Optimizer.

Check the System

Hardware communication errors, configuration errors, and insufficient system


resources can delay getting your optimizer on-line. Carefully check the system
before rushing to install the Profit Optimizer software.

If you Need to

The load modules required by Profit Optimizer may be on your system already
(see Table 2-2 for a list). If not, see Section 3, Installing the Profit Optimizer
Load Module, for instructions.

Install Load
Modules

1/00

Profit Optimizer Installation Reference


Honeywell Inc.

Section 2 Checking Your System


2.2 Hardware and Software Requirements

2.2 Hardware and Software Requirements


Hardware

These are the hardware (memory board) requirements for the AM.

Requirements

Table 2-1

Hardware (Memory Board) Requirements

Platform

Requirement

AM

4 MW minimum; 6-8 recommended.

APP Node

8 MW minimum; 16 recommended.

Software

These are the software requirements for the AM.

Requirements

Table 2-2

Software Requirements
Platform
AM

APP Node

10

Software
Series

Version Requirement

40

Any except 40.43-40.45

41

41.14 and higher

50

Any

50 and
above

Any

Profit Optimizer Installation Reference


Honeywell Inc.

Load Modules
FILE, CONV, DQP, AMCL1

FILE, CONV, AMCL06_2,


XACCES, XOPTN

1/00

Section 2 Checking Your System


2.3 Configuration Requirements

2.3 Configuration Requirements


System Paths

These are the recommended locations for the Profit Optimizer files:
Table 2-3

Recommended System Paths

Path to File

How to Quicken
Graphics Response
Network
Configuration

Recommended Location

CL Custom GDF

NET>CDSG>

Ext Load Module

NET>&CUS>

NCF Backup Path

$Fn>&ASY

CL Source/Obj

NET>CL, or NET>DQP>

CL Param List

NET>CL>

To quicken the response of the Profit Optimizer displays, make the .DO file
directory one of the first three directories in the schematic search path.
Make sure your NCF meets the following minimums. Instructions for allocating
memory, configuring nodes, and modifying the NCF are given in Section 3:

Requirements

Table 2-4

Network Configuration Requirements

Setting

Minimum Allocation

Maximum OPR, EP, or UP Universal


Stationx Memory
MODIFY NODES Entries

Set Maximum = Total

# BACKGROUND CL TASKS

10
4

# CONCURRENT DATA ACCESSES


BACKGROUND TASK STACK SIZE

32000

CVB SIZE

15000

REDUNDANCY BUFFER INCREASE

USER MEMORY RESERVED

A Caution about
Creating New
Units

Profit Optimizer does not require its own unit. Consider carefully the need for a
new unit and the potential for extra work before creating one.
Adding units to a system can have unforeseen consequences.

1/00

Profit Optimizer Installation Reference


Honeywell Inc.

11

Section 2 Checking Your System

2.3 Configuration Requirements

12

Profit Optimizer Installation Reference


Honeywell Inc.

1/00

Section 3 Installing the Profit Optimizer Load Module


3.1 Overview
In This Section

This section describes how to install the Profit Optimizer Load Module,
configure the Application Module, and write the NCF changes.

Do I Need the Profit

For AM implementations, yes. For AxM and APP implementations, no.

Optimizer Load
Module?

1/00

Profit Optimizer Installation Reference


Honeywell Inc.

13

Section 3 Installing the Profit Optimizer Load Module

3.2 Installing the Profit Optimizer Load Module (AM Only)

3.2 Installing the Profit Optimizer Load Module (AM Only)


Purpose of This
File

The Profit Optimizer load module provides the Profit Optimizer runtime library
used by the custom CL routines.

Do I Need This file?

For AM implementations, yes. For APP Node implementations, nojust go to


Section 4.0.

To Load the File

The necessary load module needed depends on the AM type and the LCN series.
A macro is supplied to install the correct file. Enter the EC command and follow
the prompts.

Use the Macro and


Follow the Prompts

Table 3-1

Installing the Profit Optimizer Load Module

Step

Action

1.

Mount the Profit Optimizer media (Zip disk or CD-ROM).

2.

At the Command Processor line, enter the following command:


EC $Fn>EC>DQP_AM.EC
Where n is your drive number. From here, answer the prompts.

3.

At the prompt, enter your AM type (HMPU, K2LCN, or K4LCN), then press <ENTER>.

4.

At the prompt, enter the first digit of your LCN release (5 for 500, 6 for 600), then press <ENTER>.

5.

At the prompt, enter


$Fn>&CUS
where n is your drive number. Press <ENTER>. When the Profit Optimizer load module for your AM type and LCN
release copies successfully, a prompt displays.

6.

14

Go to Table 3-2 for instructions on configuring the AM.

Profit Optimizer Installation Reference


Honeywell Inc.

1/00

Section 3 Installing the Profit Optimizer Load Module

3.2 Installing the Profit Optimizer Load Module (AM Only)


Configuring the
AM

Table 3-2

These procedures ensure the AM has the minimum configuration required by


Profit Optimizer. Be sure to checkpoint the AM before reloading.
Configuring the AM

Step
1.

Action
From the Engineering Personality Main Menu, touch

LCN NODES

2.

Select the AM node number.

3.

Touch

4.

On Page 2 of the Modify Node screens, make the following entries. Touch each target and type a value. Do not
press<ENTER> until after the last entry.

MODIFY NODE

# BACKGROUND CL TASKS

Attention

10
4

# CONCURRENT DATA ACCESSES


BACKGROUND TASK STACK SIZE

32000

CVB SIZE

15000

REDUNDANCY BUFFER INCREASE

USER MEMORY RESERVED

These are minimum requirements. If your NCF currently has larger values for any of these entries,

keep the larger values.


5.

Page forward to Page 3.

6.

On Page 3 of the Modify Node screens, enter the Profit Optimizer load module and check for system modules
FILE, CONV and AMCL01. When finished, these are the entries:
NAME

PERS

DQP
FILE
CONV

AMO
AMO
AMO

AMCL01

AMO

Attention Type new entries in open ports. Do not overwrite existing entries. FILE and CONV should already
be entered. If not, it is necessary to load these into the &CUS directory.
7.

Set USE DEFAULT PERSONALITY TYPE = NO

8.

Set FURTHER EXTERNAL DIRECTIVES = NO

Continued

1/00

Profit Optimizer Installation Reference


Honeywell Inc.

15

Section 3 Installing the Profit Optimizer Load Module

3.2 Installing the Profit Optimizer Load Module (AM Only)

Table 3-2

Configuring the AM, Continued

Step
9.

16

Action
To write the NCF changes:

Press <ENTER>.

Press <F1>.

Press <F2>, then <ENTER>.

10.

When the NCF is written, checkpoint the AM and reload.

11.

Configure every AM implementing Profit Optimizer.

12.

Go to Section 4.0.

Profit Optimizer Installation Reference


Honeywell Inc.

1/00

Section 4 Installing the Profit Optimizer Program and the


NT-Side Software
4.1 Overview
In This Section

Profit Optimizer applications on TPS require the following program files:

Compiled Parameter Lists

Compiled Custom Data Segments

Object code

NT-side software for APP Node implementations.

This section gives the source directory, file names, file descriptions, and procedures
for installing this code.
Are Your Paths
Correct?

Profit Optimizer files go into standard History Module directories. Check your SET
PATHS display to make sure the destination locations are correct.

Directory?

Consider creating a DQP directory to hold the Profit Optimizer object code (the
.AO files).

Before You Do

Back up the Profit Optimizer disks. Work from the back up.

Create a DQP

Anything Else

1/00

Profit Optimizer Installation Reference


Honeywell Inc.

17

Section 4 Installing the Profit Optimizer Program and the NT-Side Software

4.2 Directories and Files You Will Be Using

4.2 Directories and Files You Will Be Using


Profit Optimizer

These are the directories and files for this part of the installation

Media

Table 4-1

Packing List
Media

Direct
ory

Files

File
Extension

CD or Zip Disk

AO

CL object code

.AO

CDS

CDS Packages

.CL

PL

Parameter Lists

.CL

EC

Installation macros

.EC

RSIM

Parameter Lists, CDS Packages, and object code for


the simulator

.CL
.AO

APP Node only


setup.exe
Parameter Lists

Table 4-2

Custom Data

The following parameter lists are required for Profit Optimizer. These parameter
lists should have been compiled during the Profit Controller installation.
Parameter Lists File Names and Description
File Name

Attaches to Point

DQPBG_PL

DQP bridge output interface point

DQPIF_PL

DQP interface point; RMPCT-side and DQP-side

DMSG_PL

DQP message point

DQP_PL

DQP optimizer point

Compile these CDS files. See Table 4-5 for instructions.

Segments

Table 4-3

18

Custom Data SegmentsFile Names and Description


File Name

Attaches to Point

BGD_CDS

Bridge Output Interface Point

DIN_CDS

DQP-side and RMPCT-side interface points.

DM1_CDS

RMPCT-side interface Points

DM2_CDS

RMPCT-side interface Points


Profit Optimizer Installation Reference
Honeywell Inc.

1/00

Section 4 Installing the Profit Optimizer Program and the NT-Side Software

4.2 Directories and Files You Will Be Using

Object Code

DMOD_CDS

DQP-side interface points

DMSG_CDS

Message point

DMST_CDS

Application list point (DQP_LIST)

DOUT_CDS

DQP-side and RMPCT-side interface points

DQP1_CDS

Optimizer point

DQP2_CDS

Optimizer point

DQP3_CDS

Optimizer point

DQP4_CDS

Optimizer point

HTPS_CDS

Optimizer point

Copy these .AO files onto the History Module. See Table 4-5 for instructions.
Files for APP Node implementations are noted.

Table 4-4
File Name
DQP_MAIN

DQP_OPEN
(For APP Node)

DQP_MSG
HTPS_MSG
(For APP Node)

1/00

Object CodeFile Names and Description


Algorithmic Function

Attaches to Point

Blocks

Handles initialization and overruns

Optimizer point

DQP_RES

Initializes CDS pointers and manages


memory

Optimizer point

DQP_PNTR

Reads in .YS and .YM files

Optimizer point

DQP_READ

Optimizer calculations

Optimizer point

DQP_CALC

Performs integrity checks and initializations

Optimizer point

DTPS_CHK

Performs CDS moves.

Optimizer point

DTPS_PTS

Requests NT-side control calculations

Optimizer point

DTPS_EXE

Generates error messages

Message point

DQP_MSG

Pass error messages from NT-side software

Optimizer point

HTPS_MSG

Profit Optimizer Installation Reference


Honeywell Inc.

19

Section 4 Installing the Profit Optimizer Program and the NT-Side Software

4.3 Compiling and Loading the Profit Optimizer Program

4.3 Compiling and Loading the Profit Optimizer Program


Back Up

Have you backed up yet? If not, do it.

ProcedureUsing

You can compile and load the Profit Optimizer Custom Data Segments using this
executable file:

the Installation
Macros

COMPDQP.EC
To execute, mount your backup. From the Command Processor line enter these
commands:
EC

$Fn>EC>COMPDQP.EC $Fn

where n is a drive number..


After running the macro, copy the .AO files to the net
Procedure
Manually Installing
the Program Files

Command Syntax When manually compiling CDS Packages for the first time,
use the -UL (update library) switch. If there are CDS Packages in the library by
the same name, the message
File .GD Was Not Updated as Requested
is returned. The existing CDS file must be renamed. For subsequent compiles of
each CDS package, use both the -UL and -OCD (overwrite custom data) switches
to update the library and overwrite the old file.
Procedure - Use the instructions in the following table to install the Profit
Optimizer CDS packages, and the optimizer object code.

20

Profit Optimizer Installation Reference


Honeywell Inc.

1/00

Section 4 Installing the Profit Optimizer Program and the NT-Side Software

4.3 Compiling and Loading the Profit Optimizer Program

Table 4-4

Installing the Profit Optimizer Program

Installation
Compile the Parameter
Lists

Compile the CDS


Packages

Step

Action

Mount the backup copy.

Parameter list included as part of RMPCT

Use the CL command to compile the following files from the CDS> directory
(include the -UL switch):
AM Implementations
BGD_CDS.CL
DOUT_CDS.CL
DIN_CDS.CL
DM1_CDS.CL
DM2_CDS.CL
DQP1_CDS.CL

DQP2_CDS.CL
DQP3_CDS.CL
DQP4_CDS.CL
DMOD_CDS.CL
DMSG_CDS.CL
DMST_CDS.CL
APP Node Implementations

For APP Node implementations, compile these additional files as well as the AM
files:
HTPS_CDS.CL
The following files are not required for the APP Node implementation:
DOUT_CDS.CL
DIN_CDS.CL
DM1_CDS.CL
DM2_CDS.CL

Copy the Object Code


To Continue

1/00

Verify that all of the CDS packages appear in the directory NET>CDSG> with a
.GD extension.

Use the CP command to load all .AO files from the AO> directory (did you make
DQP the destination directory?).
6

If you are on an AM, go to Section 5.0.

If you are on an APP Node, there are a couple more files to install, and some
configuration to do. Go to Section 4.5.

Profit Optimizer Installation Reference


Honeywell Inc.

21

Section 4 Installing the Profit Optimizer Program and the NT-Side Software

4.4 Installing and Configuring the NT-Side Software

4.4 Installing and Configuring the NT-Side Software


Installation
Requirements and

To install the DQP NT-Side software, refer to section 4 in the Profit Suite
Installation Guide.

Techniques

Access Level

In order to allow the data to move from the LCN to NT side and back again, the
access level for the LCN must be set to Read/Write. Setting the level done
differently for GANT and APP.

GANT

Use the Configuration Utility on the NT side located under the


Start/Programs/Honeywell TPS menu. With the Configuration Utility running,
select the CL_Init menu item under Configure menu. Set the security setting to
two (READWRIT). Click on OK and then close the window.

APP

Use the Configuration Utility on the NT side located under the


Start/Programs/Honeywell TPS menu. With the Configuration Utility running
Select the TPS Domain menu item under Configure menu.
Select the HCI Component tab
Select the CL Server for the APP that Profit Optimizer is being installed
upon (click on the name in the first column)
Click on Enter/Edit Server Specific Configuration button
Click on Yes
Set the Select Initial Security Setting to READ WRITE (if it already is
READ WRITE, click on the Cancel buttons to exit without any changes
and skip the following steps)
Click on OKs to return to the TPS Domain window
Click on the Replication tab
Click on the Commit Configuration/Replicate button
Click on the window close button to exit the program.

22

Profit Optimizer Installation Reference


Honeywell Inc.

1/00

Section 5 Building an On-line Simulation


5.1 Overview
In This Section

This section explains how to build a Profit Optimizer simulation for TPS.
Simulations require simulated RMPCT controllers, simulated Bridge Output
(BOut) points, and driver points.

Do I Need to Build

No, simulations are not required for an on-line application. But, to verify an offline design, or experiment with different optimizer settings or process conditions
while Profit Optimizer is on-process, build a simulation.

a Simulation?

Profit Optimizer
Simulations Need
These Points

Simulated RMPCTs and BOuts To see how to create simulated RMPCT,


see RMPCT Installation Reference for TPS, Section 5. The simulation
points replace the process points. For an illustration of how simulation points
work with an on-line optimizer, see Figure 1-2.
Driver Point The driver points are get-data points. These points drive the
dynamic simulation by causing the simulated BOuts to respond to moves made
to the simulated Bridge input (BIn) points.

Point Naming
Conventions

What We Suggest The points can be named anything, but these are suggested.
Use the point name to indicate:

That the point is a simulation point.

Whether the point is a BIn, BOut point, or the driver point.

The points sequence.

Point Name Example BO1GETD is a good name for the first driver point.
SIMBI1 and SIMBI2 are good names for the first and second simulated
BIns. SIMBO1 is a good name for the first simulated BOut, and so on. The
advantage of a sequential BI-, BO- naming convention is that it identifies the
simulation point with its interface point numerical counterpart.
Other Point Naming Strategies The point name may be used to describe the
system point or to identify the process. Any naming strategy works within
accepted TPS conventions, as long as the naming is logical, functional, and
consistent.
Manually Building
Points? Read
This
Building Points?
Read This

Attention Your Point-Build Choices If a simulator is desired, the sim


points must be manually built, either one point at a time, or with an EB file.
The Point-Build Template In the TMPL directory of the Profit Optimizer
media there is an EB template that can be used as a quick-start for building the
sim points.
The Point-Build Sequence When building points manually, build the points in
the order that this section describes. Because of entity references, building
points in a different order will cause you grief.

1/00

Profit Optimizer Installation Reference


Honeywell Inc.

23

Section 5 Building an On-line Simulation

5.1 Overview

Build points in the order described in Table 5-1. See the indicated sections for
the parameters you need to set:
Table 5-1
Step

24

Quick ReferencePoint Build Order for Simulation Points2


Action

See

1.

Build the simulated BIn MVs.

Section 5.2

2.

Build the simulated BIn DVs.

Section 5.3

3.

Pre-Build the driver points (a first-pass build).

Section 5.4

4.

Build the simulated BOuts.

Section 5.5

5.

Modify the CDS Packages for the simulated BOuts.

6.

Attach the model coefficients to the simulated BOuts.

Section 5.6

7.

Finish building the driver points (second pass).

Section 5.7

8.

Modify the CDS Packages for the driver points.

Profit Optimizer Installation Reference


Honeywell Inc.

1/00

Section 5 Building an On-line Simulation

5.2 Building the Simulated BIn MVs

5.2 Building the Simulated BIn MVs


Application Notes

Application Requirements Simulated BIn MVs replace the process BIn MVs.
Build a sim BIn MV point for every BIn MV in your application (see Table 5-2
for the parameters you need to set).
Note: BIn MVs are usually MVs of existing RMPCT controllers. These MVs
can be used directly by the driver point. However, if the user wants to
have BIn MV points separate from those supplied by the RMPCTs, then
read on.
Scheduling Sim BIn MV points execute as fast as the driver point they are
configured in, and need to be scheduled before their driver point.
Configuration Wire sim BIn MVs tail-to-mouth. The PV tracks the setpoint.
Point Type Sim BIn MV points are regulatory AM points.
Point Names Name these points anything you want, within convention.
Table 5-2 describes the required point parameter settings or suggested settings for
simulated BIn MV points.

Set These
Parameters

Table 5-2

Building BIn MV Simulation Points

For this Parameter

Enter

Comments

NAME

The point name

See Point Naming Conventions in the Overview.

UNIT

The unit number of the


application

PTDESC

A point description

Description should indicate the points location or purpose, and that


the point is a simulated BIn MV.

KEYWORD

A descriptive search word or


phrase

DQPSIM, SIMPNT or SIMLTNPT are good keywords for these


points.

POINT EXECUTION
PERIOD

Must execute before its


driver point

This frequency ensures that the optimizer point always has the most
current data.

PVALGID

DATAACQ

CTLALGID

PID

NOINPTS

PISRC(1)

The setpoint

All other parameters

Application-specific settings

Set the gain and time constants to .


Wire tail-to-mouth for PV tracking.

After building the BIn MVs, go to Section 5.3 to build the BIn DV points.

1/00

Profit Optimizer Installation Reference


Honeywell Inc.

25

Section 5 Building an On-line Simulation

5.3 Building the Simulated BIn DVs

5.3 Building the Simulated BIn DVs


Application Requirements Simulated BIn DVs replace the process BIn DVs.
Build a sim BIn DV point for every BIn DV in your application (see Table 5-3 for
the parameters you need to set).

Application
Notes

Note: BIn DVs are usually DVs of existing RMPCT controllers. These DVs can
be used directly by the driver point. However, if the user wants to have
BIn DV points separate from those supplied by the RMPCTs, then read
on.
Scheduling Sim BIn DV points execute as fast as the driver point they are
configured in, and need to be scheduled before their driver point.
Configuration Wire sim BIn DVs tail-to-mouth. The PV tracks the setpoint.
Point Type Sim BIn DV points can be regulatory or numeric AM points.
Point Names Name these points anything you want, within convention.
Table 5-3 describes the required point parameter settings or suggested settings for
simulated BIn DV points.

Set These
Parameters

Table 5-3

Building BIn DV Simulation Points

For this Parameter . . .

Enter . . .

Comments

NAME

The point name

See Point Naming Conventions in the Overview.

UNIT

The unit number of the application

PTDESC

A point description

KEYWORD

A descriptive search word or phrase DQPSIM, SIMPNT or SIMLTNPT are good keywords for
these points.

POINT EXECUTION
PERIOD

Must execute before its driver point

PVALGID

DATAACQ

CTLALGID

PID

NOINPTS

PISRC(1)

The setpoint

All other point parameters

Application-specific settings

Description should indicate the points location or


purpose, and that the point is a simulated BIn DV.

This frequency ensures that the optimizer point always


has the most current data.
Set the gain and time constants to .
Wire tail-to-mouth for PV tracking.

After putting the BIn DVs on the system. Go to Section 5.4 for the driver points 1st-pass build.

26

Profit Optimizer Installation Reference


Honeywell Inc.

1/00

Section 5 Building an On-line Simulation

5.4 Building the Driver Points1st Pass

5.4 Building the Driver Points1st Pass


Application Notes

Application Requirements Because it is possible to cascade bridge models, it


may be necessary to have multiple driver points. (See Figure 5.1 & 2 to
determine the number of driver points you will need.) Because the first BOut sim
point executes after the driver point, sim BO1 needs to make a BEFAFT
reference to the driver point. If the driver is not already on the system, you get an
entity reference error. Build one driver point for each level of bridge outputs (see
Table 5-4 for the parameters you need to set).
Scheduling Schedule the driver points to execute at the same frequency as the
optimizer point.
Point Type The driver point is an AM custom point.
Point Name Name this point anything you want, within convention. Suggested
naming: xxxxGETD, where xxxx indicates the process and driver number.
Table 5-4 describes the required 1st-pass point parameter settings or suggested
settings for putting the driver point on the system.

Set These
Parameters

Table 5-4

Building the Driver PointEntering the 1st-Pass Parameters

For this Parameter .


..

Enter . . .

Comments

NAME

The point name

UNIT

The unit number of the application

PTDESC

A point description

Description should indicate this point is the driver point.

KEYWORD

A descriptive search word or phrase

GETD, DQPGETD, DQPDVR, or DRIVEDQP are good


keywords for this point.

POINT EXECUTION
PERIOD

The same execution frequency as the


optimizer point

BEFAFT

Select CYCLE

NORMCYCLE

Enter the cycle number

Recommended naming: xxxxGETD, where xxxx indicates


the process.

Typically two cycles after the RMPCT point where the


bridge inputs come from.

After putting the driver points on the system, go to Section 5.5 to build the BOut sim points.

1/00

Profit Optimizer Installation Reference


Honeywell Inc.

27

Bridge Model

Process
Configuration

Bridge Model
BIn1
RMPCT
1

Bridge
Model
BIn2

BOut1

BOut2

RMPCT
2

BIn1

Point
Schedule
Order

RMPCT
1

RMPCT
2

RMPCT
3

RMPCT
4

Figure 5-1

1/00

BOut3

RMPCT
3

RMPCT
4

PROFIT

BIn2

Driver Point
1

SIM
BOut
1-3

BOut
1-3

PROFIT

No Cascaded Bridge Models

Profit Optimizer Installation Reference


Honeywell Inc.

29

Bridge Model

Process
Configuration

BIn1

BOut1

RMPCT
2

Bridge Model

RMPCT
1

BOut2

RMPCT
3

BIn2

BIn1
Driver
Point
1

SIM
BOut
1

RMPCT
2

RMPCT
4

BOut3

BIn3

Driver Point
2

Figure 5-2

1/00

BIn3

PROFIT
RMPCT
1

Point
Schedule
Order

Bridge Model

BIn2

SIM
BOu1
2

RMPCT
3

Driver Point
3

SIM
BOu1
3

RMPCT
4

BOut
1-3

PROFIT

Cascaded Bridge Models

Profit Optimizer Installation Reference


Honeywell Inc.

31

Section 5 Building an On-line Simulation

5.5 Building the Simulated BOuts

5.5 Building the Simulated BOuts


Application Notes

Application Requirements Simulated BOuts replace the process BOuts. Start


with Table 5-5 and build a sim BOut point for every BOut in your application.
Modify the CDS Package. Then attach the model coefficients, Table 5-6.
Scheduling Schedule the first sim BOut, of the first set of BOuts, to execute after
its driver point. Subsequent sim BOuts, which belong to the same set, execute in
order, SIMBO1, then SIMBO2, then SIMBO3, and so on.
Schedule Sim BOuts of other sets in a similar fashion with respect to their driver
point.
Configuration Enter required CDS parameters.
Point Type Sim BOut points are regulatory AM points.
Point Name Name these points anything you want, within convention.

Set These
Parameters

Table 5-5 describes the required point parameter settings or suggested settings for
simulated BOut points.
Indicates CDS parameters in file RSIM_CDS. All other parameters are
standard point parameters.

Table 5-5

Building BOut Simulation Points

For this Parameter . . .

Enter . . .

Comments

NAME

The point name

See Point Naming Conventions in the Overview.

UNIT

The unit number of the


application

PTDESC

A point description

Description should indicate the points location or


purpose, and that the point is a simulated BOut.

KEYWORD

A descriptive search word or


phrase

DQPSIM, SIMPNT, or SIMLTNPT are good keywords for


these points.

POINT EXECUTION PERIOD

The same execution frequency


as the optimizer point

PVALGID

CL

CTLALGID

NULL

BEFAFT

Select AFTER

PTDISCL

FULL

Continued

32

Profit Optimizer Installation Reference


Honeywell Inc.

1/00

Section 5 Building an On-line Simulation

5.5 Building the Simulated BOuts

Table 5-5

Building BOUT Simulation Points, Continued

For this Parameter . . .


BEFAFTID

Enter . . .

Schedule BO1 to run after its


driver point

Schedule subsequent BOuts of


its set to execute sequentially:
BO2 runs after BO1, BO3
runs after BO2, and so on

CLSLOTS

NOPKG

PKGNAME(1)

RSIM_CDS

All other point parameters

Application-specific settings

I1

Number of sim BIn MVs

I2

Number of sim BIn DVs

IN

The steady state value

All other CDS parameters

Application-specific settings

Comments

See the shaded area for the CDS


parameters.

Same number as in the optimizer.

For the BOut being built.

When all sim BOuts are built, go to Section 5.6 to attach the model coefficients.

1/00

Profit Optimizer Installation Reference


Honeywell Inc.

33

Section 5 Building an On-line Simulation

5.6 Attaching Model Coefficients to the Sim BOuts

5.6 Attaching Model Coefficients to the Sim BOuts


Application Notes

Attaching the model coefficients to the sim BOut points gives the sim points the
same intelligence about the process that the system BOuts have. These
coefficients are in the .EB file that was created when the bridge output models
were built with the Off-Line Design Software.
Attaching the model coefficients to sim points requires editing the .EB file,
creating an entity list, setting pathnames, and then reconstituting the sim BOut
points.

Attention Run the .EB file created in Profit Design Studio(APCDE) through
the text file converter (e.g. WordPad) then write the file to the disk. When
converting the .EB file, to save time convert the .YM and .YS optimizer files at
the same time.
For Help

See the APC Identifier Users Guide, Profit Optimizer Designers Guide and
Profit Controller Designers Guide for information about identifying a process,
building optimizer models, and generating the required TPS files.

Procedure

Table 5-6 explains how to attach the model coefficients to the simulated BOut
points. Instructions assume the TPS text editor is used to edit the .EB file and
create the entity list.

Table 5-6
Step

Attaching the Model Coefficients


Action

Comment

1.

Copy the Offline design .EB file onto the History Module..

2.

Edit the .EB file to replace variable names SIMPV1 . . . SIMPVn Enter each BOut name twice. Once on the
&M line, and again on the &N line.
with the names of the sim BOuts, in order
BO1 . . . BOn.

3.

Create an entity list containing the names of the sim BOuts. List
the BOuts in order, BO1 . . .BOn.

4.

From the Builder Commands, touch

Use File Transfer on a GUS or GANT/APP.

Give the file a dot-EL extension.

RECONSTITUTE
MULTIPLE

Continued

34

Profit Optimizer Installation Reference


Honeywell Inc.

01/00

Section 5 Building an On-line Simulation

5.6 Attaching Model Coefficients to the Sim BOuts

Table 5-6
Step
5

Attaching the Model Coefficients, Continued


Action
Enter the following pathnames (include file extensions):
For Pathname
Enter
Reference Path
Path to source directory
IDF
idfname.DB
Selection List
entlist.EL

Press <ENTER>.

Touch

EXCEPTION
BUILD

Touch

WITH
OVERWRITE

Touch

LOAD
ENTITIES

10

Enter the following pathnames:


For Pathname
Enter
Source File
offline.EB
IDF
idfname.DB
Selection List
Template
entlist

11

Press <ENTER>.

12

Go to Section 5.7 to finish building the driver point.

1/00

Comment
Comment
Make an entry as required.
This is the intermediate data file.
This is the entity list file.

Comment
This is the .EB file from the Offline design.
The IDF file again.
Keep blank.
The entity list file again, this time without the
extension.

Profit Optimizer Installation Reference


Honeywell Inc.

35

Section 5 Building an On-line Simulation

5.7 Building the Driver Points2nd Pass

5.7 Building the Driver Points2nd Pass


Application Notes

Set These
Parameters

These standard parameters for the driver point are already on the system from the
1st-pass build:
NAME

PTDESC

POINT EXECUTION PERIOD

UNIT

KEYWORD

BEFAFT

NORMCYCLE

Setting the parameters in Table 5-7 completes the point build of the driver point,
and completes the simulator.
Indicates CDS parameters in file RGET_CDS. All other parameters are
standard point parameters.

Table 5-7

Building the Driver PointEntering the 2nd-Pass Parameters

For This Parameter . . .


CLSLOTS
NOPKG
PKGNAME(1)

2
1
RGET_CDS

Enter

All other point parameters


I
I1
I2
CODSTN(n)
IN(n)
IN1(n)

Application-specific settings
Number of sim BOuts
Number of sim BIn MVs
Number of sim BIn DVs
In sequence, the simulation BOut tagnames
Names of simulation BIn points supplying SP values
Names of simulation BIn points supplying PV values

PV SOURCE(n)

In sequence, The source type for each BIn MV then


BIn DV

IN2(n)
VALUES(n)

Names of simulation BIn points supplying OP values


In sequence, the steady state value for each
simulated BIn MV, then BIn DV

Comments

See the shaded area for the CDS


parameters.
Same number as.
in the optimizer
BO 1. . . BOn
CV1. . . CVn
0=SP
1=OP
2=PV
BIMV1 . . . BIMVn
.
.
.
BIDV1 . . . BIDVn

All other CDS parameters Application-specific settings


When the driver point is built, go to Section 6.0.

36

Profit Optimizer Installation Reference


Honeywell Inc.

01/00

Section 6 Building Profit Optimizer Interface Points


6.1 Overview
In This Section

Interface points link the Profit Optimizer to the RMPCT controllers and process
variables.
This section explains how to build Profit Optimizer interface points for the Profit
Optimizer.

Point Naming
Conventions

What We Suggest Name the points anything, but the following are suggested.
Use the point name to indicate:

Use the first four characters of the point name for the location or function
of the point.

Whether the point is a BOut (BO), RMPCT-Side (RS) or DQP-Side (DS)


interface point. Use the next two characters of the point name.

The points sequence. Use the last two characters of the point name.

Point Name Examples 24MFBO1 could indicate Unit 24, main fractionator,
BOut number one. ATIPRS3 could indicate the RMPCT-Side interface point
for the third RMPCT controller. ATIPDS3 could indicate the DQP-Side
interface point for the third RMPCT controller.
The advantage of a sequential BO-, RS-, DS- naming convention is that it
identifies the interface point (1) With its location in the optimizer matrix and with
its index on the Operator screens, and (2) With its simulation point numerical
counterpart.
Other Point Naming Strategies Use the point name to describe the system point
or to identify the process. Any naming strategy works within accepted TPS
convention, as long as the naming is logical, functional, and consistent.

1/00

Profit Optimizer Installation Reference


Honeywell Inc.

37

Section 6 Building Profit Optimizer Interface Points

6.2 Building DQP-Side Interface Points

6.2 Building DQP-Side Interface Points


Application Notes

Application Requirements Build one DQP-Side interface point for every


RMPCT controller in the application.
Scheduling This point is not scheduled.
Configuration DQP-Side interface points link the Profit Optimizer to the
RMPCT controllers.
Point Type DQP-Side interface points are custom AM points.
Point Names

Set These
Parameters

Table 6-1

Point names can be anything, within convention.

Table 6-1 describes the required point parameter settings or suggested settings for
DQP-Side interface points.
Building DQP-Side Interface Points

For This Parameter . . .

Enter . . .

Comments

NAME

The point name

See Point Naming Conventions in the Overview.

UNIT

The unit number of the


application

It is required that all DQP-Side interface points reside in the


same unit as the Profit Optimizer point.

PTDESC

A point description

Description should indicate the points location or purpose,


and that the point is an interface point.

KEYWORD

A descriptive search word


or phrase

INTRFACE is a good keyword for these points.

PERIOD

NOPERIOD

CLSLOTS

NOPKG

PKGNAME(1)

DMOD_CDS

PKGNAME(2)

DIN_CDS

PKGNAME(2)

DOUT_CDS

All other point parameters

Application-specific settings

After building the DQP-Side interface points, go to Section 6.3 to build the RMPCT-Side interface points.

38

Profit Optimizer Installation Reference


Honeywell Inc.

1/00

Section 6 Building Profit Optimizer Interface Points

6.3 Building Profit Controller (RMPCT)-Side Interface Points

6.3 Building Profit Controller (RMPCT)-Side Interface Points


Application Notes

Set These
Parameters

Table 6-2

Application Requirements Build one RMPCT-Side interface point for every


RMPCT controller in the application.
Scheduling This point is not scheduled.
Configuration RMPCT-Side interface points link the RMPCT controllers to the
Profit Optimizer.
Point Type RMPCT-Side interface points are custom AM points.
Point Names
Point names can be anything, within convention.
Table 6-2 describes the required point parameter settings or suggested settings for
RMPCT-Side interface points.

Building RMPCT-Side Interface Points

For This Parameter . . .

Enter . . .

Comments

NAME

The point name

See Point Naming Conventions in the Overview.

UNIT

The unit number of the


application

It is required that all RMPCT-Side interface points reside


in the same unit as their respective RMPCT controller
point.

PTDESC

A point description

Description should indicate the points location or


purpose, and that the point is an interface point.

KEYWORD

A descriptive search word or


phrase

INTRFACE is a good keyword for these points.

PERIOD

NOPERIOD

CLSLOTS

NOPKG

PKGNAME(1)

DM1_CDS

PKGNAME(2)

DM2_CDS

PKGNAME(3)

DIN_CDS

PKGNAME(4)

DOUT_CDS

All other point parameters

Application-specific settings

After building the RMPCT-Side interface points, go to Section 6.4 to build the BOut interface points.

1/00

Profit Optimizer Installation Reference


Honeywell Inc.

39

Section 6 Building Profit Optimizer Interface Points

6.4 Building BOut Interface Points

6.4 Building BOut Interface Points


Application Requirements Build one BOut interface point for every bridge
output in the application.

Application
Notes

Scheduling Schedule BO1 to run at least one cycle before the optimizer point.
Schedule subsequent points sequentially: BO2 after BO1, BO3 after BO2,
and so on.
Configuration BOut interface points link the Profit Optimizer point to the bridge
output variables in the process.
Point Type BOut interface points are regulatory AM points.
Point Names Point names can be anything, within convention.
Table 6-3 describes the required point parameter settings or suggested settings for
BOut interface points.

Set These
Parameters

Table 6-3

Building BOut Interface Points

For This Parameter .


..

Enter . . .

Comments

NAME

The point name

See Point Naming Conventions in the Overview.

UNIT

The unit number of the application

It is required that all BOut points for a application reside in


the same unit as the Profit optimizer point.

PTDESC

A point description

Description should indicate the points location or purpose,


and that the point is an interface point.

KEYWORD

A descriptive search word or phrase

INTRFACE is a good keyword for these points.

PTDISCL

FULL

This is required so that the PVFLTOPT and CDS packages


can be specified.

PVALGID

DATAACQ

CTLALGID

NULL

PERIOD

The same execution frequency as


the optimizer point

NORMCYCLE

At least one cycle before the


optimizer point.

Set for BO1 only.

Continued

40

Profit Optimizer Installation Reference


Honeywell Inc.

1/00

Section 6 Building Profit Optimizer Interface Points

6.4 Building BOut Interface Points

Table 6-3

Building BOut Interface Points, Continued

For This Parameter . . .


BEFAFT
PVFLTOPT

Enter . . .

Comments

CYCLE for BO1

AFTER for subsequent points


SINGLLAG

Optional. Filters the signal from the process bridge


output variable.

NOINPTS

PISRC(1)

The point-dot-PV of the process point,


or of the sim BOut point if you have a
simulation

CLSLOTS

NOPKG

PKGNAME(1)
All other point
parameters

Schedule BO2 after BO1, BO3 after BO2, and


so on

BGD_CDS
Application-specific settings

After building the BOut interface points, go to Section 7.0.

1/00

Profit Optimizer Installation Reference


Honeywell Inc.

41

Section 6 Building Profit Optimizer Interface Points

6.4 Building BOut Interface Points

42

Profit Optimizer Installation Reference


Honeywell Inc.

1/00

Section 7 Building Optimization Points and Initializing the


Messages
7.1 Overview
In This Section

The interface/simulation points should be on the system. If not, go back to


sections five and six before continuing.
This section explains how to build the points used by the Profit Optimizer
program to calculate, store, and pass output to the RMPCTs.

Profit Optimizers
Optimization
Points

Table 7-1

Profit Optimizers optimization points consist of an optimizer point and a


message point. All of these points are required. Table 7-1 explains their
purpose:
Function of the Profit Optimizer Optimization Points

Point
Optimizer

Message

1/00

Description
The Profit Optimizer engine functions include:

Integrity checks

Updating Bridge output predictions

Sending optimization solutions to the RMPCTs

PPSing (point processing special) the message point

Writing control and optimization messages to the Profit Optimizer screens.

Detects and reports the following errors in the Profit Optimizer engine calculations which
includes:

I/O errors

Calculation errors

Communication errors with the RMPCTs.

Profit Optimizer Installation Reference


Honeywell Inc.

43

Section 7 Building Optimization Points and Initializing the Messages

7.1 Overview
Optimization
Points and the

Optimization points complete the link between the process, the RMPCTs and the
Profit Optimizer program. The data flow is as follows:

Profit Optimizer

1.

Data comes into the optimizer point through the interface points.

Program

2.

The prediction and optimization routines execute.

3.

Data then returns to the process through the RMPCT controllers in the form
of an optimization solution.

See Figure 1-2 for an illustration of the data flow.


To get the optimization point built and customized, make process-specific entries
to the point parameters to reflect the BOut, DQP-Side, and RMPCT-Side points
that have already been built.
Loading the Alter
Parameter
Message File

This does not apply for APP Node. The message point (introduced on the next
page) stores the messages that are written to the Profit Optimizer Message
Display. These messages indicate the condition of the optimizer and the quality of
optimization, among other things.
The messages must be loaded into the CDS Packages of the message point from an
alter parameter file.
This required step is sometimes delayed and later forgotten while building,
linking, and activating points. Instructions for loading these messages appear at the
end of this section. Failing to load this message file will cause problems. Do not
miss this requirement.

Point Naming
Conventions

What We Suggest The optimization points can be named anything you want.
Some suggestions are:

MSG in the pointname indicates the message point.

DQP, or OPT in the pointname indicates the optimizer point.

Point Name Examples 24MF_DQP or 24MF_OPT might indicate the Profit


Optimizer point for Unit 24, main fractionator. 24MF_MSG might indicate the
message point.
Point Building
Order

44

Build the message point first. Build the optimizer point next (both require an entity
reference to the other). The optimizer point is usually built last.

Profit Optimizer Installation Reference


Honeywell Inc.

1/00

Section 7 Building Optimization Points and Initializing the Messages

7.2 Building the Message Point (AM)

7.2 Building the Message Point (AM)


Application Requirements Build one message point for each Profit Optimizer
application.
Scheduling NOPERIOD: This point is PPSd (point processed special) by the
optimizer point.
Configuration There is an entity reference to the optimizer point. Build this point
in two passes.
Point Type The message point is a custom AM point.
Point Name Point names can be anything, within convention.
Table 7-2 describes the required point parameter settings or suggested settings for
the message point.

Application
Notes

Set These
Parameters

Indicates CDS parameters in file DMSG_CDS. All other parameters are


standard point parameters.
Table 7-2

Building the Message Point

For This
Parameter . . .

Enter . . .

Comments

NAME

The point name

See Point Naming Conventions in the Overview.

UNIT

The unit number of the application

It is best if the message point resides in the same unit as the


optimizer point.

PTDESC

A point description

Description should indicate that this is the message point.

KEYWORD

A descriptive search word or phrase DQPMSG, MESSAGE, or MSGPT are good keywords for this point.

CLSLOTS

NOPKG

PKGNAME(1)

RM1_CDS

PKGNAME(2)

RM2_CDS

PKGNAME(3)

DMSG_CDS

PERIOD

NOPERIOD

All other point


parameters

Application-specific settings

Tagname of the optimizer point

All other CDS


parameters

Application-specific settings

See the shaded area for the CDS parameters.

Entity referencerequires a two-pass build. When the optimizer


point is on the system, come back and fill this in.

After building the message point, go to Section 7.3 to build the optimizer point.

1/00

Profit Optimizer Installation Reference


Honeywell Inc.

45

Section 7 Building Optimization Points and Initializing the Messages

7.3 Building the Optimizer Point

7.3 Building the Optimizer Point


Application
Notes

Set These
Parameters

Table 7-3

Application Requirements Build one optimizer point for each Profit Optimizer
application.
Scheduling Executes at the frequency used in the offline design.
Configuration After putting this point on the system, enter the tagname in P of
the message point to complete the two-pass build required by the entity reference.
Point Type The optimizer point is a custom AM point.
Point Name Point names can be anything, within convention.
Table 7-3 describes the required point parameter settings or suggested settings for
the optimizer point.
Building the Optimizer Point

For This
Parameter . . .

Enter . . .

Comments

NAME

The point name

See Point Naming Conventions in the Overview.

UNIT

The unit number of the


application

This point must be in the same unit as the DQP-Side interface points
and BOut interface points

PTDESC

A point description

Description should indicate that this is the optimizer point.

KEYWORD

A descriptive search word or


phrase

OPT, OPT_PNT, or DQPMSTR are good keywords for this point.

CLSLOTS
NOPKG

For AM

For APP Node

For AM

For APP Node

PKGNAME(1)

DQP4_CDS

PKGNAME(2)

DQP3_CDS

PKGNAME(3)

DQP2_CDS

PKGNAME(4)

DQP1_CDS

PKGNAME(5)

HTPS_CDS

For APP Node only

PERIOD

The execution frequency

Must be the same frequency as the frequency used in the offline design.

BEFAFT

CYCLE

NORMCYCL

The cycle entered for the BOut


interface points + 1

All other point


parameters

Application-specific settings

After building the optimizer point, enter its tagname in the P parameter of the message point, then go to Section 7.4 to
initialize the Profit Optimizer messages.

46

Profit Optimizer Installation Reference


Honeywell Inc.

1/00

Section 7 Building Optimization Points and Initializing the Messages

7.4 Initializing the Profit Optimizer Messages

7.4 Initializing the Profit Optimizer Messages


Application Notes

The distribution media has a file named MSG_ENG.XX. It contains Profit


Optimizer messages (in English) that need to be written to the CDS Packages of
the message point.
Putting messages in the MSG_ENG.XX file delivers the messages
independently of the CDS Packages. This way, the messages can be translated
and put on the system in languages other than English. It also frees the messages
from being release-dependent so they can be easily updated for distribution.

Questions and

Can I Link and Set Points ACTIVE without the Message File? Yes.

Answers

Will the Optimizer Run without the Message File? Yes . . . for awhile.
What Happens if I Forget the Message File? When the Profit Optimizer
program has something to report, it instructs the message point to retrieve and
display a message. The message point then composes the message and writes the
Profit Optimizer Message Display.
W A R N IN G

However, if the CDS Packages have not been initialized with the message
strings, there are none to retrieve and a CL error will occur in the message point.
If the messages are not on the system, then instead of a message you get a CL
error in the message point. The CL error causes the optimizer shuts down. Write
the message strings to the CDS Packages, to avoid this problem.
Translating the
Messages from
English

Procedure

1/00

Call Us First Some messages (or message strings) can be translated easily.
Other messages, especially the shorter strings, can be difficult. The reasons are:
(1) The information may be technically obscure, or (2) The lack of context can
render some phrases nearly impossible to define without help. Before changing
the MSG_ENG.XX file, call us for advice.
Then Copy the File Work from a copy of the MSG_ENG.XX file. Do not
work from the original. The file is in the MSG directory on the distribution
media.
Use a Text Editor to Translate Use any text editor to translate the message
strings. Stay within the double quotes when editing strings (the will be
obvious when you open the file). Exceeding this 40 character space
generates an error when writing the message, causing the optimizer to shut
down.
Call Us Again If there are any doubts about how well any message has been
translated, check with us.
Use the instructions in Table 7-4 to initialize the Profit Optimizer messages.

Profit Optimizer Installation Reference


Honeywell Inc.

47

Section 7 Building Optimization Points and Initializing the Messages

7.4 Initializing the Profit Optimizer Messages

Table 7-4

Initializing Profit Optimizer Messages from the MSG_ENG Alter Parameter File

Step

Action

1.

From the Builder Commands, touch

2.

Enter the following pathnames:

ALTER
PARAMETERS

For Pathname

Enter

Reference Path

$Fn>MSG> where n is the drive number.

Selection List

The name of your message point.

Param = Value List

MSG_ENG.XX

3.

Press <ENTER>.

4.

After initializing the Profit Optimizer messages, go to Section 8.0.

Initializing
messages for the
APP Node

Text for the controller messages is contained in message files that are installed by
the setup program as described in section 4.5. These files are read by the
optimizer program when it starts up. You do not have to do anything with the
message files unless you want to translate them to another language.
Here are instructions to translate messages to another language:
First run the RMPCT setup program as described in section 4.5.
The messages are contained in files in the NT directory
c:\users\HiSpec\bin\DQ. The message files all have the extension .msg.
Use NT Explorer to copy the message files to some other directory. This
provides a backup set of files to which you can refer if you encounter
problems while you are modifying the original files.
Use NT Notepad or other editor to edit each message file in
c:\users\HiSpec\bin\DQ. Change the text as desired.
Each record in a message file is one message.
The messages are in pairs. The first record of a pair is the message that the
controller sends when the condition described by the message goes into effect.
The second record of a pair is the message that the controller sends when the
condition clears.
An all-blank record is not sent. This is typically used as the second message
of a pair when there is no need to send a message when the condition clears.
These records must not be deleted. The position of the records in the file
must be maintained.
You generally should not change a record that contains some information into
an all-blank record. This is because the second message of a pair is used to
clear the first message from the RMPCT status display, and this will not occur

48

Profit Optimizer Installation Reference


Honeywell Inc.

1/00

Section 7 Building Optimization Points and Initializing the Messages

7.4 Initializing the Profit Optimizer Messages

if the second message is blank because all-blank messages are not sent.
You will note that many messages contain fields that start with a percent sign
(%) and end with one of the following characters: c, d, i, o, u, x, e, f, g, n, p, s.
These fields designate a place in the message where variable information,
such as a numerical value or a name, will be inserted by the controller when it
sends the message. You must not change these fields or their order, but you
can remove or add any text, including blanks, before or after these fields.

1/00

Profit Optimizer Installation Reference


Honeywell Inc.

49

Section 7 Building Optimization Points and Initializing the Messages

7.4 Initializing the Profit Optimizer Messages

50

Profit Optimizer Installation Reference


Honeywell Inc.

1/00

Section 8 Building DQP_LIST Point


8.1 Overview
In This Section

This section explains how to build the points Profit Optimizer needs to display
information about your application on the Operator screens.

What DQP_LIST

DQP_LIST (a required tagname) holds the name of every Profit Optimizer.

Does

Every optimizer named in DQP_LIST displays on the Profit Optimizer main menu,
where touch-screen selections are made. Selecting an optimizer from the list makes
that optimizer the active or current application. Every screen then displayed, shows
information about that application until a different optimizer is selected.

Point Naming

For DQP_LIST The point name DQP_LIST is required.

Conventions

1/00

Profit Optimizer Installation Reference


Honeywell Inc.

51

Section 8 Building DQP_LIST Point

8.2 Building DQP_LIST

8.2 Building DQP_LIST


Application Notes

Application Requirements Build one DQP_LIST point for the LCN.


Scheduling This point is not scheduled.
Configuration DQP_LIST holds the name of every Profit Optimizer on the
system. You can enter these names through the D( ) and C1DESC( ) CDS
parameters, or through the Profit Optimizer main menu.
Point Type DQP_LIST is a custom AM point.
Point Name Must be named DQP_LIST.

Set These
Parameters

Table 8-1 describes the required point parameter settings or suggested settings for
the DQP_LIST point.
Indicates CDS parameters in file DMST_CDS. All other parameters are
standard point parameters.

Table 8-1

Building DQP_LIST

For This Parameter . . .


NAME

Enter . . .
DQP_LIST

Comments
This name is required.

UNIT

The unit number of the application

Any existing unit is acceptable.

PTDESC

A point description

Description should indicate that this is the


application point.

KEYWORD

A descriptive search word or phrase

DQP_LIST, LIST, or LISTPNT, are good


keywords for this point.

CLSLOTS

NOPKG

PKGNAME(1)

DMST_CDS

PERIOD

NOPERIOD

All other point parameters

See the shaded area for the CDS parameters.

Application-specific settings

Continued

52

Profit Optimizer Installation Reference


Honeywell Inc.

1/00

Section 8 Building DQP_LIST Point

8.2 Building DQP_LIST

Table 8-1

Building DQP_LIST, Continued

For This Parameter . . .

Enter . . .

Comments

D( )

The names of the Profit Optimizers

There can be up to 30 Profit Optimizer points


on an LCN. List the optimizer names here, or
enter them through the Profit Optimizer main
menu.

C1DESC( )

The names of Profit Optimizer process


graphics

Process schematics are optional. Your


application may not have a graphic. List
schematic names here, or enter them through
the Profit Optimizer main menu. Index the
schematics to the optimizer name.

All other CDS parameters

Application-specific settings

1/00

Profit Optimizer Installation Reference


Honeywell Inc.

53

Section 8 Building DQP_LIST Point

8.2 Building DQP_LIST

54

Profit Optimizer Installation Reference


Honeywell Inc.

1/00

Section 9 Installing the Profit Optimizer Graphics


9.1 Overview
In This Section

This section explains how to install the graphics files that comprise the Profit
Optimizer Operator interface.

Read Me

Installing the graphics requires more than copying object code to the History
Module. Before doing any of the procedures in Table 9-2, read ALL of this
section.

Graphics Files

DQP_LIST must be on the LCN before the Profit Optimizer main graphic file
(DQP.DS) can compile. Without DQP_LIST on the system (it should be, if
Section 8 has been completed) the Picture Editor cannot establish the proper link
to compile the display.

and the
DQP_LIST Point
Work from a
Backup

Use a backup copy to compile the graphics files and write the object code. Do not
use the original Profit Optimizer Zip disk. This warning does not apply if Profit
Optimizer is supplied on a CD-ROM.
Working with backup files is especially important if, the LCN is upgraded from a
400 Release to a 420 or higher release. Once you have compiled the displays on
420, you cannot use those files again to install the graphics on a 400 system, even
though Profit Optimizer uses the same source for both series.
To avoid having to request new source for a new installation, work from a copy.

1/00

Profit Optimizer Installation Reference


Honeywell Inc.

55

Section 9 Installing the Profit Optimizer Graphics

9.1 Overview
File Descriptions

Table 9-1 explains how each graphics file contributes to the Profit Optimizer
interface. If there is trouble later displaying one of the screens, check to see that
the file for that screen is properly compiled.
Table 9-1

Graphics File Descriptions

File Name

56

Description

RMPC_DDB.DF

Global database

DQP.DS

Main Profit Optimizer schematic

RDQP_SEL.DS

Application Selection display (the Profit Optimizer Main Menu)

RDQP_DTL.DS

Profit Optimizer Application Detail display

RDQPCFG1.DS

Profit Optimizer and Interface configuration display

RDQPCFG2.DS

Profit Optimizer Bridged Output Interface configuration display

RDQP_MSG.DS

Profit Optimizer Message display

RDQP_MPC.DS

Profit Optimizer Summary display

RDQP_CV1.DS

Profit Optimizer CV Summary display

RDQP_CV2.DS

Profit Optimizer CV Detail display

RDQP_CVO.DS

Profit Optimizer CV Optimization Tuning display

RDQP_MV1.DS

Profit Optimizer MV Summary display

RDQP_MV2.DS

Profit Optimizer MV Detail display

RDQP_MVO.DS

Profit Optimizer MV Optimization Tuning display

RDQP_DV1.DS

Profit Optimizer DV Summary display

RDQP_DV2.DS

Profit Optimizer DV Detail display

RDQP_BD1.DS

Bridged Output Summary display

RDQP_BD2.DS

Bridged Output Detail display

RDQP_CC1.DS

Combined Constraint Summary display

RDQP_CC2.DS

Combined Constraint Detail display

Profit Optimizer Installation Reference


Honeywell Inc.

1/00

Section 9 Installing the Profit Optimizer Graphics

9.2 Procedure

9.2 Procedure
Graphics and LCN
Software

Profit Optimizer does not support LCN software in the 200, 300 or 400
series. Files for 500 and 600 series are in the 4SCH directory.

Picture Editor

Because Profit Optimizer sub pictures are deeply nested in the main Profit
Optimizer graphics, the Abstract Table can occasionally be altered. Verifying
the files before compiling avoids problems.

Reading, Verifying,

Table 9-2 explains how to write the Profit Optimizer graphics onto a TPS
system.

Graphics and the

Compiling, and
Loading

Table 9-2

Installing the Profit Optimizer Graphics

Step
1.

Action

Comment

Mount a backup of the Profit Optimizer media.

Use a back up for Zip disks.


The CD-ROM uses emulated Bernoulli files.

2.

3.

From the Picture Editor command line, type:


LOAD $Fn>4SCH>RMPC_DDB

This loads the Profit Optimizer/RMPCT global


database, where n is the drive number:

From the Picture Editor command line, type


READ $Fn>4SCH> RDQP_CV1.

4.

Verify the file.


Type:
VER

5.

Compile the file.


Type:

For Series

Use Directory

R500

4SCH

R600

4SCH

This reads in the first picture file. Step 6 lists the rest of
the files.
Follow the prompts to enter the database variable
types as requested (expect several requests for some
variables). Answer i (integer) when prompted for the
variable type.
Select [ENTER],Yes, when asked to overwrite.

SP
COMP

1/00

Profit Optimizer Installation Reference


Honeywell Inc.

57

Section 9 Installing the Profit Optimizer Graphics

9.2 Procedure

Step
6.

58

Action

Comment

Repeat steps 3 - 5 for these files. Check the files as you work them to keep track of where you are:
RDQP_CV1

RDQP_DV1

RDQP_BD1

RDQP_CV2

RDQP_DV2

RDQP_BD2

RDQP_CVO

RDQP_MSG

RDQP_SEL

RDQP_MV1

RDQP_CC1

RDQPCFG1

RDQP_MV2

RDQP_CC2

RDQPCFG2

RDQP_MVO

RDQP_MPC

RDQP_DTL

7.

When you have compiled all files, COPY *.DO to the


History Module.

8.

After writing the object code, go to Section 10.0.

DQP

Use the -V -D switches.

Profit Optimizer Installation Reference


Honeywell Inc.

1/00

Section 10 Bringing the Optimizer On-line


10.1 Overview
In This Section

This section explains how to install the optimizer files from the off-line design,
enter the initial optimizer configuration parameters, link CL blocks to points
and activate points.
With these steps completed, commissioning begins.

Using the
Optimizer Detail
Screen

Optimizer Configuration Parameters Configuration parameters are set in the


Optimizer Detail screen. Profit Optimizer uses tuning, optimization, and
configuration parameters. The start-up parameters set in these sections are
configuration parameters.
The start-up parameters provide the minimum configuration information Profit
Optimizer requires to link and activate points.
Displaying the Optimizer Detail Screen To display the Optimizer Detail
screen, call the Operator interface, select an optimizer from the main menu, and
touch the current optimizer box on the Optimizer Bar.

For Help

1/00

For help displaying and using the Profit Optimizer screens, see Section
2.0 in the Profit Optimizer Users Guide.

For help making entries on the Optimizer Detail screen, see:

Section 3.0 in the Users Guide, and

Section 2.4 in the Profit Optimizer Commissioning reference.

Profit Optimizer Installation Reference


Honeywell Inc.

59

Section 10 Bringing the Optimizer On-line

10.2 Installing the Off-line Design Files

10.2 Installing the Off-line Design Files


ProcedureAM
Implementations

Table 10-1
Step

Installing Off-line Design Files on an AM


Action

Comment

1.

Copy the .YS and .YM files onto the History Module.

When copying the files from an emulated Bernoulli


disk, use the -V -D switches to verify and monitor the
copying process.

2.

On the station keyboard, press <SCHEM>, and enter DQP to call the Operator interface:

3.

Initialize the graphics: On the Optimizer Detail screen,


press [APPLCN MENU].

This displays the Profit Optimizer main menu.

4.

On the main menu, select either [SSVAL] or [FUTUR], then


press <ENTER>.

For this step, it is not important what target is


selected. The selection here is to get the graphics
initialized. This is what these selections do:

SSVAL gives predictions to steady state.

FUTUR gives predictions to three times the


nominal time constant.

5.

Touch the optimizer, then press <ENTER>.

This displays the CV Summary for the selected


application.

6.

Touch the current optimizer box (upper left of the screen).

This displays the Optimizer Detail screen.

7.

On the Optimizer Detail screen, enter the .YM and .YS


filenames and location:

Include the full path, filename, and extension.

8.

60

Table 10-1 describes how to install the off-line design files onto an AM. Part of
this installation requires initializing the Profit Optimizer graphics then entering the
.YS and .YM path, filename, and extension on the Optimizer Detail display.

The name of the .YM file goes in the [CONTROL


MODEL] field.

The name of the .YS file goes in the


[SPECIFICATION] field.

Keep the Optimizer Detail screen displayed. Go to Section


10.3

Profit Optimizer Installation Reference


Honeywell Inc.

1/00

Section 10 Bringing the Optimizer On-line

10.2 Installing the Off-line Design Files


Procedure APP
Node
Implementations

Table 10-3
Step

1/00

Installing Off-line Design Files on an APP Node


Action

Comment

1.

Use NT Explorer to copy the .YS and .YM files into /users/HiSpec/config
on the NT-Side.

2.

On the station keyboard, press <SCHEM>, and enter DQP to call the Operator interface.

3.

Initialize the graphics: On the Optimizer Detail screen, press [APPLCN


MENU].

This displays the Profit Optimizer


main menu.

4.

Touch the optimizer, then press <ENTER>.

The CV Summary screen displays.

5.

Touch the current optimizer box (upper left screen).

The Optimizer Detail screen


displays.

6.

On the Optimizer Detail screen, enter the specification, model and


configuration filenames:

7.

There are three files that are needed to define a Profit Optimizer instance. These
are:
Specification file (extensions .ys) , it contains values for the various
parameters that the operator and engineer can set to specify optimizer
operation. You can optionally specify that this file be read when the
optimizer is activated to provide starting values for the parameters, or later to
reset the parameter values. If this file is not read when the optimizer is
activated, the parameter values in the interface points on the AM side of the
APP will be used as initial values. Limits in the interface points are never
overwritten.
Model file (extensions .ym), it contains the information that defines the
dynamic model of the process that is being optimized. This file is read when
the optimizer is activated, and can be read later to update the model
coefficients.
Configuration file (extension .cfg), it tells the optimizer where its
parameters reside on the AM side of the APP Node. This file is read only
when the optimizer is activated.
Table 10-3 describes how to install the off-line design files onto an APP. Part of
this installation requires initializing the DQP graphics then entering the .YS, .YM
and .CFG filenames on the Optimizer Detail display.

The name of the .YM file goes in the [CONTROL MODEL] field.
The name of the .YS file goes in the [SPECIFICATION] field.
The name of the .CFG file goes in the [CONFIGURATION] field.

The directory was created by the


setup program.

Attention
No extension. No path. Filenames
only.

Keep the Optimizer Detail screen displayed. Go to Section 10.3

Profit Optimizer Installation Reference


Honeywell Inc.

61

Section 10 Bringing the Optimizer On-line

10.3 Setting and Checking the Start-Up Configuration

10.3 Setting and Checking the Start-Up Configuration


Procedure

Table 10-3

Use the procedures in Table 10-3 to set or check the optimizer configuration
before attempting to link and activate points. The following is the minimum
configuration required to link points.
Setting and Checking the Startup Configuration

Step

Action

Comment

1.

On the Optimizer Detail display, check


that the [TAG] and [DESC] fields
contain the name and description of
the optimizer point.

Manually entering the correct information may not be the answer. Errors
here can indicate a point building problem.
If no value is entered for the Descript field in Section 7.3 then DESC
will not be seen here

2.

In the [MSG TAG] field, enter the name


of the message point.

3.

Enter the [NUMBER of RMPCTs], and


BOuts.

For Open installations, the number or RMPCTs should include all


RMPCT(s) regardless of whether they reside in a different LCN than
DQP.

4.

Enter tagnames in parameters P(1),


P1(1), P2(1), P3(1), P4(1), P5(1),
P6(1), P7(1), P8(1),and for AxM
installations, XNAME(0).

From the point detail display of the optimizer point, enter

The first RMPCT controller point in P(1)

The Name of any RMPCT CV interface point in P1(1)

The Name of any RMPCT MV interface point in P2(1)

The Name of any RMPCT DV interface point in P3(1)

The name of any BOut interface point in P4(1)

The name of any RMPCT-Side interface point in P5(1).

The name of any DQP-Side interface point in P6(1).

The name of any RMPCT DV interface point in P7(1).

The name of any RMPCT MV interface point in P8(1).

For AxM installations, the name of the AxM data transfer point in
XNAME(0).

5.

Make any other entries that you want


with the same configuration as in the
YS file.

Only Steps 1-4 are necessary to link. Other settings here are optional,
and some can be a waste of time. Remember, the off-line design files
still have to read in.
When the off-line design files are read in, the .YS file overwrites any
information on the Optimizer Detail screen different from what is in the
file.

6.

62

Go to Section 10.4

Profit Optimizer Installation Reference


Honeywell Inc.

1/00

Section 10 Bringing the Optimizer On-line

10.4 Linking the Object Code

10.4 Linking the Object Code


Link List

All of the object code files are in the AO directory of the distribution disk, except
the two simulation files. The RMPCSIM and RMPCGETD files required for
simulations are in the RSIM directory on the RMPCT distribution disk.
Table 10-4 tells you what CL code links to which point, depending upon the
implementation. See Table 10-5 for instructions.

Table 10-4

Link ListLink These Files to These Points


For This
Implementation .
..

Link These
Files . . .

AM Implementations

DQP_MAIN

Optimizer point

A tagname must exist in each entity


reference before linking.

APP Node
Implementations

DQP_OPEN

Optimizer point

A tagname must exist in each entity


reference before linking.

HTPS_MSG

Optimizer point

A tagname must exist in each entity


reference before linking.

DQP_MSG

Message point

All EXCEPT APP Node


implementation.

RMPCSIM

BOut simulation
points

Only required for simulations.

RMPCGETD

BOut Driver points Only required for simulations.

All Implementations

To These
Points . . .

Comments

See Table 10-5 for the linking order and instructions.

1/00

Profit Optimizer Installation Reference


Honeywell Inc.

63

Section 10 Bringing the Optimizer On-line

10.4 Linking the Object Code


Procedure

At the Command Processor, use this command format to link the CL code to the
application points:
LK

Table 10-5

NET>DQP>OBJCODE

Linking the Object Code

Step
1

POINTNAME

Action
For AM implementations: link DQP_MSG to the message point.

2
IF Your Implementation Is . . .
AM

THEN Link . . .
DQP_MAIN to the optimizer point.

APP Node

DQP_OPEN and HTPS_MSG to the optimizer point.

NOTE: A warning message for a null point ID will appear if any tagnames from Table 10-3, Step 4 are not entered.
When any null point ID message appears, unlink all the blocks, enter the missing tagnames, and re-link the
DQP_MAIN.
3

64

If a simulation exists:
1.

Link RMPCSIM to each sim BOut.

2.

Then link RMPCGETD to all BOut driver points.

When the points are linked, activate the points and read in the design files. See Section 10.5 for the point activation
order.

Profit Optimizer Installation Reference


Honeywell Inc.

1/00

Section 10 Bringing the Optimizer On-line

10.5 Activating the Points, Reading In the Design Files and Tying in Controllers

10.5 Activating the Points, Reading In the Design Files and


Tying in Controllers
Reality
CheckCheck
Procedure

Table 10-6

Before any point can be set ACTIVE, the point database needs to be complete, the graphics installed,
the object code linked, the start-up configuration parameters set, and the off-line design files loaded. If
these requirements are not met, they must be done before proceeding.
Because of the interaction between points, points need to be activated in a prescribed order. Follow the
point activation order in Table 10-6. Read in the design files just before activating the optimizer point.
Point Activation Order

Step

Action

Comment

1.

Activate the BOut driver points.

2.

Activate the simulated BOuts (activate the process BOuts if


they are not already ACTIVE).

3.

Activate the BOut interface points.

4.

Activate the DQP-Side interface points.

5.

Activate the RMPCT-Side interface points.

6.

Activate the message point.

7.

Make sure all RMPCT controller names, all BOut interface


point names, all DQP-side interface points and all RMPCTside interface point names are entered into their respective
parameters.

On the Optimizer Detail screen, touch the


SYSTEM CONFIG targets to enter the names.

8.

Read in the design files:


[w/out Init]

On the Optimizer Detail screen, touch [Read Opt


Model Files] and optionally the [SPECS]. The
targets will not clear until the optimizer point is
activated.

9.

Check if the Profit Optimizer point name is configured in


parameter BNAME(0) and BNAME(1) on all the RMPCT
controllers associated with the optimizer.

If no tagname is entered, enter the tagname from


the RMPCT controller point detail display. You
will need to re-link RMPC_CON.

10.

Check if the RMPCT-Side interface point name is configured


in parameter CNAME(1) on all the RMPCT controllers
associated with the optimizer.

AM ONLY - If no tagname is entered, enter the


RMPCT-Side tagname associated with this
RMPCT controller, from the RMPCT controller
point detail display. RMPC_CON will need to be
re-linked.

11.

Enter the name of the DQP-Side interface point in CNAME(2)


on all the RMPCT controllers associated with the optimizer.

AM ONLY - Enter the DQP-Side tagname


associated with this RMPCT controller from the
point detail display.

12.

For any RMPCT controller that needed a point name entered


in steps 9 or 10, do steps 13 through 16.

[w Init]

or

Otherwise, go to 17 below.
1/00

Profit Optimizer Installation Reference


Honeywell Inc.

65

Section 10 Bringing the Optimizer On-line

10.5 Activating the Points, Reading In the Design Files and Tying in Controllers

Step
13.
14.

Action

Comment

Set the RMPCT controller point INACTIVE.


Configure the RMPCTs.
Each RMPCT controller point used by the optimizer point should have the optimizer point name in the BNAME(1)
parameter, the RMPCT-side interface point name in the CNAME(1) parameter (AM only installations), and the
DQP-side interface point name in the CNAME(2) parameter (AM only installations).

15.

16.

For AM only
Unlink the following blocks from the RMPCT controller point:

From the command line type:

RMPC_CVP
RMPC_DVP
RMPC_CON
For AxM only

UNLK RMPC_CVP POINTNAME

RMPC_MSG
RMPC_END
RMPC_XFR

etc..

Unlink the following blocks from the RMPCT controller point:

From the command line type:

RMPCX_DVP
RMPCX_CON
RMPCX_MSG

UNLK RMPCX_DVP POINTNAME

RMPCX_END
RMPCX_XFR
RMPCX_UNP
RMPCX_PCK

etc..

For AM only
Re-link RMPC_CON object to the RMPCT controller point.

From the command line type:


LK NET>RMPC>RMPC_CON RMPCT controller
point name

For AxM only


Re-link RMPCX_CON for AxM.

From the command line type:


LK NET>RMPC>RMPCX_CON RMPCT
controller point name

66

17.

Set the RMPCT controller point ACTIVE.

18.

If the optimizer point is already ACTIVE, set the optimizer


point INACTIVE then ACTIVE

19.

Activate the optimizer point.

20.

For AM implementations, check the read-in date and time stamps. See the next page for comments.

21.

Commission - See Profit Optimizer Commissioning Reference for help.

Error messages may be sent to message


summary screen

Profit Optimizer Installation Reference


Honeywell Inc.

1/00

Section 10 Bringing the Optimizer On-line

10.5 Activating the Points, Reading In the Design Files and Tying in Controllers

StampsChecking

When an application is first installed the [FILE READ] and [READ TIME]
fields on the Optimizer Detail screen are blank. These fields indicate when the
optimizer was installed, and how long it took to read-in the optimizer files.

the Read-File

Check the [FILE READ] and [READ TIME] fields for date and time entries.

Checking the
Read-File

Stamps

When the model and specification files are read-in, the Read Opt Files
[MODEL] and [SPECS] targets are no longer back lit. Check this.
If either of these conditions fail, there is something wrong. Locate the problem.

1/00

Profit Optimizer Installation Reference


Honeywell Inc.

67

Section 10 Bringing the Optimizer On-line

10.5 Activating the Points, Reading In the Design Files and Tying in Controllers

68

Profit Optimizer Installation Reference


Honeywell Inc.

1/00

Section 11 Trouble Shooting


11.1 Running out of AM Memory
Symptoms:

Solution:

DQP Optimizer Execution Failed 0.00 20009 error message on the LCNs
Message Summary display.

AM, in which DQP point resided, go down.

The solution to this problem is to configure the AM memory (pool#1 heap) to be


larger. This is accomplished with the following steps:
1. On the NCF configuration page of the AM, set Further External Directives?
(toward the bottom of page 3) to YES. Then save the NCF.
2. On the history module volume containing the &CUS directory, create a
directory named &CSD.
3. Create a file NET>&CSD>APCFG0xx.X, where xx is the LCN node number of
the APP Node (e.g. APCFG024.X)
4. Add the following two lines to this file:
HEAP <kilowords>
END
, where <kilowords> is the number in kilo-word to increase heap by (e.g. 1500).
This number is AM specific and should not be set to large or else it will exhaust
the AM memory. We found 1500 to be a good default value.
5. After saving the file, reload the APP Node. If APP Node complains about the
memory, reduce the <kilowords> specified on the APCFG0xx.X file.
The schematic AMDETAIL displays information about current setting of AM
memory. The following parameters are useful information about the Pool#1 Heap:
HEAPTOTL: initial size in words
HEAPFREE: current number of free words
HEAPMIN:

minimum number of free words on heap since node startup

HEAPBCNT: number of available blocks

1/00

Profit Optimizer Installation Reference


Honeywell Inc.

69

Section 11 Trouble Shooting

11.1 Running out of AM Memory

70

Profit Optimizer Installation Reference


Honeywell Inc.

1/00

Appendix CDS Descriptions


Bridged DV Model Point
BGD_CDS
Parameter

Index

IO
X()

DV_identity. Must be -13 to identify this to Pascal


1

Use this Bridge DV (1.0 means dont use)

Critical Bridge DV (1.0 means critical)

Number of bad reads allowed (-1.0 means infinity)

4 . . . 20
T()

Description

Reserved

DV_app

DV_real_idx

DV

DV_hat

DV_est

DV_last_BAD

DV_last

DV_Filt_bias

DV_Filt_Const

10

DV_bar

11

DV_ss

12

DV_Status

13 . . . 20

Reserved

B0

Number of Bridge DV Future Pnts

B1 ( )

1 . . . 21

Indicates (i-1)th DV Block

B2 ( )

1 . . . 21

Projected at (i-1)th DV Block

INITCONF

Bridge DV description

PT

Pointer to current history loc

S1

Size of the history array (A)

1/00

(DV_UFP)

Set to 1.0 after a pointer to the CDS is established

DESCRIPT

A( )

(DV_num_blks)

(DV_blk)

1 . . . 200

Historized bridged DV values

Profit Optimizer Installation Reference


Honeywell Inc.

71

Appendix --- CDS Descriptions

Interface Points (RMPCT side + DQP)


DIN_CDS
Parameter

Index

Description

INI

Identity Number....Must be -11 to identify to Pascal

app_resp_time

IOPPTD01 ( )

1 . . . 80

y_est

IOPPTD02 ( )

1 . . . 80

y_soft_L_active

IOPPTD03 ( )

1 . . . 80

y_ soft_H_active

IOPPTD04 ( )

1 . . . 80

W_y_L

IOPPTD05 ( )

1 . . . 80

W_y_H

IOPPTD06 ( )

1 . . . 80

alpha_y

IOPPTD07 ( )

1 . . . 80

beta_y

IOPPTD08 ( )

1 . . . 80

y_obj

IOPPTD09 ( )

1 . . . 80

y_Opt_Err_Tol

IOPPTD010 ( )

1 . . . 40

u_L_ss

IOPPTD011 ( )

1 . . . 40

u_H_ss

IOPPTD012 ( )

1 . . . 40

u_soft_L

IOPPTD013 ( )

1 . . . 40

u_soft_H

IOPPTD014 ( )

1 . . . 40

u_weight

IOPPTD015 ( )

1 . . . 40

alpha_u

IOPPTD016 ( )

1 . . . 40

beta_u

IOPPTD017 ( )

1 . . . 40

u_obj

IOPPTD018 ( )

1 . . . 40

u_solve

IOLASTS

Last written rmpct, indicates which set of rmpct predictions is


newest

K1 ( )

1-80

T1 ( )

1-40

u1 MV value

S1 ( )

1-40

u_DV1

K2 ( )

1-80

y_bar2 CV prediction (set 2)

T2 ( )

1-40

u2 MV value

S2 ( )

1-40

INH_STAT

72

y_bar1 CV prediction (set 1)

u_DV2

(set 1)

DV value (set 1)
(set 2)

DV value (set 2)

IINITCONF for INPUT CDS

Profit Optimizer Installation Reference


Honeywell Inc.

1/00

Appendix --- CDS Descriptions

Interface Points (DQP side)


DMOD_CDS
Parameter

Index

IN0

Description
Identity number Must be -9 to identify this to Pascal

MODSTAT1

model_id

C1

n_cv (number of CVs in this app)

C2

n_mv (number of MVs in this app)

C3

n_dv (number of DVs in this app)

IN3

n_exitst_spr (number of non-null models in this app)

TF

Design execution frequency

I1 ( )

1 . . . 1000

packed Ijp - index to non -null models

G()

1 . . . 1000

packed unweighted SS gains

D1 ( )

1 . . . 80

Dr (row/CV scaling)

D2 ( )

1 . . . 40

Dc (column/MV scaling)

1/00

Profit Optimizer Installation Reference


Honeywell Inc.

73

Appendix --- CDS Descriptions

Interface Points (RMPCT side)


DM1_CDS
Parameter

Index

IN0

Description
Identity number Must be -9 to identify this to Pascal

MODSTAT1

Model id

C1

n_cv (number of CVs in this app)

C2

n_mv (number of MVs in this app)

C3

n_dv (number of DVs in this app)

X1

n_exitst_spr (number of non-null models in this app)

TF

Design execution frequency

I1 ( )

1 . . . 1000

packed Ijp - index to non -null models

G()

1 . . . 1000

packed unweighted SS gains

D1 ( )

1 . . . 80

Dr (row/CV scaling)

D2 ( )

1 . . . 40

Dc (column/MV scaling)
DM2_CDS

Parameter

Index

Description

IN3

Identity number Must be -10 to identify this to Pascal

MODSTAT2

Model_id

C4

n_cv (number of CVs in this app)

C5

n_mv (number of MVs in this app)

C6

n_dv (number of DVs in this app)

X2

n_exitst_spr (number of non-null models in this app)

TFL

Design execution frequency

I2 ( )

1 . . . 1000

packed Ijp - index to non -null models

GAINOPT ( )

1 . . . 1000

packed unweighted SS gains

D3 ( )

1 . . . 80

Dr (row/CV scaling)

D4 ( )

1 . . . 40

Dc (column/MV scaling)

74

Profit Optimizer Installation Reference


Honeywell Inc.

1/00

Appendix --- CDS Descriptions

Message Point
DMSG_CDS
Parameter

Index

P0
F()
K3 ( )

Tagname of DQP main point


8

Message output to log

Message output to CRT

Clear status msgs (see D7)

All contoller errors (1-50) clear

All critical CVs ok

All critical MVs ok

All critical MVs can be moved

All critical Dvs ok

All non_critical CVs ok

All non_critical MVs ok

10

All non_critical MVs can be moved

11

All non_critical DVs ok

12

No execution overlap

13

Bkgrnd task queue not full

14 . . . 16
K1 ( )

Description

info~ (Build status messages)

warn~

error~

clear~

code~

CV~

MV~

DV~

, code~

10

, rec~

11

, chr~

12

req index~

Continued

1/00

Profit Optimizer Installation Reference


Honeywell Inc.

75

Appendix --- CDS Descriptions

Message Point; continued


DMSG_CDS
Parameter
K1 ( )

Index

Description

13

, size~

14

file~

15

: X(~

16

: T(~

17

: B(~

18

) is bad.~

19

) is unreasonable.~

20

Connection app~

21

Cmbd Cnstr~

22

bDV~

23

: DITYPE(~

24

: CCPAISF~

25

: X(~

26 . . . 30

RM1_CDS
Parameter

Index

Description

D3 ( )

1 . . . 100

Messages

D4 ( )

0 . . . 100

Messaging Strings/Information

RM2_CDS
Parameter

Index

Description

D5 ( )

1 . . . 100

Messages

D6 ( )

1 . . . 100

Messaging Strings/Information

76

Profit Optimizer Installation Reference


Honeywell Inc.

1/00

Appendix --- CDS Descriptions

Master Display Point


DMST_CDS
Parameter

Index

Description

D1 ( )

1 . . . 30

Point names of RMPCT DQP system points

C1DESC ( )

1 . . . 30

User Display Overlay Titles

1/00

Profit Optimizer Installation Reference


Honeywell Inc.

77

Appendix --- CDS Descriptions

Interface Point (DQP side + RMPCT side)


DOUT_CDS
Parameter

Index

Description

IN2

Identity number Must be -12 to identify this to Pascal

DOTYPE

RMPCT to DQP connection type 1 => Cooperative


2 => Direct
3 => User Defined

APPL

Index of this application in DQPs list of RMPCTs

OB_STATE

1 => Optimizing
2 => not enough degrees of freedom

TD

T_dqp design execution frequency

SPOPT

Optimizer speed value pushed to RMPCT

OUT1 ( )

1 . . . 80

CV_wound_up (1->CV is wound up)

OUT2 ( )

1 . . . 40

u_soft_L_active (MV act low soft lim)

OUT3 ( )

1 . . . 40

u_soft_H_active (MV act high soft lim)

D
R1 ( )

last _written_dqp, indicates which set of dqp values is newest (1 or 2)


1 . . . 80

y_dqp1 CV solution (set 1)

B1 ( )

1 . . . 40

u_dqp1 MV solution (set 1)

R2 ( )

1 . . . 80

y_dqp2 CV solution (set 2)

B2 ( )

1 . . . 40

u_dqp2 MV solution (set 2)

B3 ( )

1 . . . 10

bdv_index

B4 ( )

1 . . . 10

bdv_num_blks

B5 ( )

1 . . . 110

bdv_blk

B6

_last_written_bdv_UFP

B7 ( )

1 . . . 110

bdv_UFP1

B8 ( )

1 . . . 110

bdv_UFP2

DTM ( )

1 . . . 10

bdv_dmean (mean deadtime)

INITCONF

78

INITCONF for the OUTPUT CDS

Profit Optimizer Installation Reference


Honeywell Inc.

1/00

Appendix --- CDS Descriptions

Optimizer Point
DQP1_CDS
Parameter
X( )

Index
1

user_n_RMPCT

user_n_bout

opt_speed

initpass

URV_tol

read_YM_flag

ON_OFF_request

read_YS_flag

9 . . . 50
T( )

Reserved

DQP state

program version

YM file version

display # of CVs

display # of MVs

display # of DVs

maximum defaulted SS value

Steady state error

Steady state objective

10

Current ojbective

11

Update points flag

12

ext_n_DV_bin

13

ext_n_bin

14

ext_comb

15

DQP ready flag

16

YS file version

17

T_dqp

18

RM_read_required

19

obj_function

20

DQP_Version

21 . . . 50

1/00

Description

Reserved

Profit Optimizer Installation Reference


Honeywell Inc.

79

Appendix --- CDS Descriptions

Optimizer Point; continued


DQP1_CDS
Parameter

Index

Description
DQP Flag

2=off, 3=on, 4=warm

D1 ( )

1 . . . 50

DQP now_alarm

D2 ( )

1 . . . 50

DQP prev_alarm

BINRINGR ( )

1 . . . 150

Bridged input index

VALUES ( )

1 . . . 150

Bridged input values

STATE1 ( )

1 . . . 40

RMPCT application state

C( )

1 . . . 40

RMPCT app critical flag..1=> Critical 2=> Non-Critical

D1TYPE ( )

1 . . . 40

RMPCT connection type 1 => Cooperative


2 => Direct
3 => User Defined

INTIDLST ( )

1 . . . 40

RMPCT-ID of last model seen by DQP

CPAISF01 ( )

1 . . . 100

Comb Const Low Limit

CPAISF02 ( )

1 . . . 100

Comb Const Hi Limit

CPAISF03 ( )

1 . . . 100

Comb Const Low Error Weight

CPAISF04 ( )

1 . . . 100

Comb Const High Error Weight

CPAISF05 ( )

1 . . . 100

Comb Const alpha_comb Quadratic Objective Coefficient

CPAISF06 ( )

1 . . . 100

Comb Const beta _comb Linear Objective Coefficient

CPAISF07 ( )

1 . . . 100

Comb Const comb_obj Desired Value

CPAISF08 ( )

1 . . . 100

Comb Const comb_est Predicted Value

CPAISF09 ( )

1 . . . 100

Reserved

CPAISF10 ( )

1 . . . 100

Comb Const steady state solution

CPAISF11 ( )

1 . . . 100

Comb Const Windup state:


1=wound up

CPAISF12 ( )

1 . . . 100

Comb Const Scaling factor

CPAISF13 ( )

1 . . . 100

Comb Const Error Tolerant

INTICONF

DQP_initconf

DQP_pool_data_ptr

80

Profit Optimizer Installation Reference


Honeywell Inc.

0 = not wound up

1/00

Appendix --- CDS Descriptions

Optimizer Point; continued


DQP2_CDS
Parameter

Index

DESCRIPT

Description
RMPCT DQP appl description

ZZTEXT ( )

1 . . . 100

RMPCT DQP comb constraint description

P1 ( )

1 . . . 440

RMPCT DQP final CV points


DQP3_CDS

Parameter

Index

Description

P2 ( )

1 . . . 240

RMPCT DQP final MV points

P3 ( )

1 . . . 140

RMPCT DQP final DV points

P4 ( )

1 . . . 50

RMPCT DQP bridge DV model points


DQP4_CDS

Parameter
S1 ( )

N( )
T1 ( )

D7 ( )

Index

Description

Model File

Specification File

Configuration File

Reserved

1...5

Background overlap max, init max overlap cnt, foregrnd CL


error

Start of calculations

Start of last file read

duration of calculations

duration of last file read

1 . . . 38

For messaging

P0 ( )

1 . . . 40

RMPCT main points

P5 ( )

1 . . . 40

RMPCT-side interface points

P6 ( )

1 . . . 40

DQP-side interface points

ANAME

DQP message point

P7 ( )

1 . . . 50

DV Bridge input points

P8 ( )

1 . . .100

MV Bridge input points

1/00

Profit Optimizer Installation Reference


Honeywell Inc.

81

Appendix --- CDS Descriptions

Optimizer Point; continued


HTPS_CDS
Parameter

Index

Description

C7

Size of message buffer.

C8

The number of messages in the buffer has not been processed


by the CL Block.

IN6

1 . . . 10

First part of messages

IN7

1 . . . 10

Second part of messages

IN8

1 . . . 10

Type of messages: 1=Primary 2=Secondary

IN9

1 . . . 10

The number of the line of which message is to be displayed on


the LCN display

IN10

1 . . . 10

The message in code form (1000 * component index + message


index)

B8

1
2...4

Unused for DQP

WatchDog timer flag

Send to message log flag

Send to CRT flag

8 . . . 20
S3

Flag to clear message buffer

1
2 . . . 20

Spares
Configuration filename (without file extension)
Spares

HTPS_MSG
Parameter
D7

Index

Description

1 . . . 38
1

Displayed status msgs


(2/line).

82

Master control status

Exclusive error

Exclusive error 2nd line

23

Overlapped seconds

25

Queue full flag

27

Component status 1

29

Component status 2

31

Component status 3

33

: Warning condition 1
Profit Optimizer Installation Reference
Honeywell Inc.

1/00

Appendix --- CDS Descriptions

35

: Warning condition 2

37

: Warning condition 3

C8

The Number of Messages in the buffer if the CL Block has not


yet finished processing them, otherwise zero.

C7

Size of Message Buffer

IN6

1. . .10

First Part of Messages

IN7

1. . .10

IN8

1. . .10

Second Part of Messages


Type of Messages
1=Primary 2=Secondary

IN9

1. . .10

The number of the line on which the message is to be displayed


on the RMPCT message display.

IN10

1. . .10

The message code.

B8

1. . .20
1

Clear Message FLAG

Send to message log flag RC:F(11) copied here


DQ:F(1) copied here

Send to CRT flag RC:F(12) copied here


DQ:F(2) copied here

1/00

Profit Optimizer Installation Reference


Honeywell Inc.

83

Appendix --- CDS Descriptions

84

Profit Optimizer Installation Reference


Honeywell Inc.

1/00

Appendix DQP Configuration File (TPS Node Only)


Each DQP application for TPS Node has a configuration file with extension .cfg that maps the DQP
parameters to inputs and outputs with its RMPCT controllers and with the control system. Following is
an example configuration file, followed by an explanation of how to modify it for your application.
Header, DQP, standard configuration
Number of controllers, 3
Number of combined constraints, 3
Number of DV bridge inputs, 2
Number of MV bridge inputs, 2
Number of bridge outputs, 3
Server, HS_GANT_1_0, order 1, schedules
// Common data.
Optimizer, Number of RMPCTs
Optimizer, Number of Bridge Outputs
Optimizer, Optimizer Speed Factor
Optimizer, URV Tolerance
Optimizer, Read Model Flag
Optimizer, JZL??
Optimizer, Read Spec Flag
Optimizer, Max Consec Bad Bin Turn Off
Optimizer, Max Consec Bad Bin Reinitialize ,
Optimizer, DQP State
Optimizer, Engine version
Optimizer, Model File Builder Version
Optimizer, Number of CVs plus dividers
Optimizer, Number of MVs plus dividers
Optimizer, Number of DVs plus dividers
Optimizer, SS Deflated Singular Value
Optimizer, SS Error
Optimizer, SS Objective Value
Optimizer, Current Objective Value
Optimizer, Number of DV Bridge Inputs
Optimizer, Number of Bridge Inputs
Optimizer, Number of Combined Constraints
Optimizer, Model Readiness Flag
Optimizer, Spec File Builder Version
Optimizer, Design Exec Period
Optimizer, Model Read Required Flag
Optimizer, Optimization Flag
Optimizer, DQP Version
Optimizer, Requested State
Optimizer, Now Alarm
Optimizer, Prev Alarm
1/00

, DQP_PT, X, 1
, DQP_PT, X, 2
, DQP_PT, X, 3
, DQP_PT, X, 5
, DQP_PT, X, 6
, DQP_PT, X, 7
, DQP_PT, X, 8
, DQP_PT, X, 9
, DQP_PT, X, 10
, DQP_PT, T, 1
, DQP_PT, T, 2
, DQP_PT, T, 3
, DQP_PT, T, 4
, DQP_PT, T, 5
, DQP_PT, T, 6
, DQP_PT, T, 7
, DQP_PT, T, 8
, DQP_PT, T, 9
, DQP_PT, T, 10
, DQP_PT, T, 12
, DQP_PT, T, 13
, DQP_PT, T, 14
, DQP_PT, T, 15
, DQP_PT, T, 16
, DQP_PT, T, 17
, DQP_PT, T, 18
, DQP_PT, T, 19
, DQP_PT, T, 20
, DQP_PT, M,
, DQP_PT, D1, 1
, DQP_PT, D2, 1

Profit Optimizer Installation Reference


Honeywell Inc.

85

Appendix --- CDS Descriptions

// Optimizer, Execution Interval


// Optimizer, Execution Sub Interval
// Optimizer, Execution Offset
// Optimizer, Overruns
// Optimizer, Sub Overruns
// Optimizer, Sim Reset
// Optimizer, Check Point Interval
// Optimizer, Auto Check Point
// Optimizer, Demand Check Point
// Optimizer, Control Restart
// Optimizer, Keep Running
// Optimizer, Calc Start Int Time
// Optimizer, Start Interval Time
// Optimizer, End Control Time
// Optimizer, Calc Start Sub Int Time
// Optimizer, Start Sub Interval Time
// Optimizer, End Sub Interval Time
// Optimizer, Last Model File Name
// Optimizer, Last Spec File Name
// Optimizer, Controller Name
Optimizer, Model File Name
Optimizer, Spec File Name
Optimizer, Config File Name
// Optimizer, Process Model File Name
// Optimizer, Check Point Name
Options, Message Part 1
Options, Message Part 2
Options, Message Type
message type
Options, Message Line
display
Options, Message Clear
display
Options, Message Number Unprocessed
CL to process
Options, Point Execution Status
status
Options, Reset Watchdog
timer

, DQP_PT,
, DQP_PT,
, DQP_PT,
, DQP_PT,
, DQP_PT,
, DQP_PT,
, DQP_PT,
, DQP_PT,
, DQP_PT,
, DQP_PT,
, DQP_PT,
, DQP_PT,
, DQP_PT,
, DQP_PT,
, DQP_PT,
, DQP_PT,
, DQP_PT,
, DQP_PT,
, DQP_PT,
, DQP_PT,
, DQP_PT, S1, 1
, DQP_PT, S1, 2
, DQP_PT, S1, 3
, DQP_PT,
, DQP_PT,
, DQP_PT, IN6, 1 // Messages first half
, DQP_PT, IN7, 1 // Messages second half
, DQP_PT, IN8, 1 // Primary/secondary
, DQP_PT, IN9, 1 // Line number on status
, DQP_PT, B8, 1 // Flag to clear status
, DQP_PT, C8,

// Number of msgs for

, DQP_PT, PTEXECST, // Active/inactive


, DQP_PT, B8, 5

// DV bridge inputs.
Template, Clear
Template, Read Value,
Template, Use this DV,
Template, Alive Flag,

// Reset CL watchdog

, P1,
, C2,
, PTEXECST,

DVBin:DVB1_Name, *, DV1_INTERF_PT , *, *
86

Profit Optimizer Installation Reference


Honeywell Inc.

1/00

Appendix --- CDS Descriptions

DVBin:DVB2_Name, *, DV2_INTERF_PT , *, *
// MV bridge inputs.
Template, Clear
Template, Read Value,
Template, Use this MV,
Template, Alive Flag,
Template, MV Man Action,

, P1,
, MODE,
, PTEXECST,
, C2,

MVBin:MVB1_Name, *, MV1_INTERF_PT, *, *
MVBin:MVB2_Name, *, MV1_INTERF_PT, *, *
// Controllers.
// Auxiliary vars for info used by HS_GANT to determine controller mode as
// known by Open RMPCT.
RMPCT1_Name_M, scalar
, RMPCT1_PT, M
RMPCT1_Name_N2, scalar
, RMPCT1_PT, N, 2
RMPCT2_Name_M, scalar
, RMPCT2_PT, M
RMPCT2_Name_N2, scalar
, RMPCT2_PT, N, 2
RMPCT3_Name_M, scalar
, RMPCT3_PT, M
RMPCT3_Name_N2, scalar
, RMPCT3_PT, N, 2
Template, Clear
Template, Alive Flag
,
, PTEXECST,
// Following could be used instead of above auxiliary vars and code in
// HS_GANT if mode were available directly.
//Template, Controller Mode
,
, B8
,2
RMPCT1_Name, *
RMPCT2_Name, *
RMPCT3_Name, *
Template,
Template,
Template,
Template,
Template,

Clear
Status
Critical
Connection Type
Last Model Used ID

RMPCT1_Name, *
RMPCT2_Name, *
RMPCT3_Name, *
Template,
Template,
Template,
Template,
Template,
1/00

, RMPCT1_PT , *
, RMPCT2_PT, *
, RMPCT3_PT, *

Clear
Odd Model ID,
Odd DQP Model ID,
Odd Scalar 1,
Odd Scalar 2,

, DQP_PT
, DQP_PT
, DQP_PT
, DQP_PT
,*
,*
,*

,*
,*
,*

,*
,*
,*

, STATE1 ,
,C
,
, DITYPE ,
, INTIDLST,

,1
,2
,3

, MODSTAT1,
, MODSTAT1,
, C1,
, C2,
Profit Optimizer Installation Reference
Honeywell Inc.

87

Appendix --- CDS Descriptions

Template,
Template,
Template,
Template,
Template,
Template,
Template,

Odd Scalar 3,
Odd Scalar 4 ,
Odd Scalar 5,
Odd Array 1,
Odd Array 2,
Odd Array 3,
Odd Array 4,

, C3,
, X1,
, TF,
, I1, 1
, G, 1
, D1, 1
, D2, 1

RMPCT1_Name, *
RMPCT2_Name, *
RMPCT3_Name, *
Template,
Template,
Template,
Template,
Template,
Template,
Template,
Template,
Template,
Template,
Template,
Template,

, IntPt1_RS , *
, IntPt2_RS , *
, IntPt3_RS , *

Clear
Even Model ID
Even DQP Model ID
Even Scalar 1
Even Scalar 2
Even Scalar 3
Even Scalar 4
Even Scalar 5
Even Array 1
Even Array 2
Even Array 3
Even Array 4

,
,
,
,
,
,
,
,
,
,
,

RMPCT1_Name, *
RMPCT2_Name, *
RMPCT3_Name, *
Template,
Template,
Template,
Template,
Template,
Template,
Template,
Template,
Template,
Template,
Template,
Template,
Template,
Template,
Template,
Template,
Template,
Template,
88

Clear
In Scalar 1
In Array 1
In Array 2
In Array 3
In Array 4
In Array 5
In Array 6
In Array 7
In Array 8
In Array 9
In Array 10
In Array 11
In Array 12
In Array 13
In Array 14
In Array 15
In Array 16

, MODSTAT2,
, MODSTAT2,
, C4,
, C5,
, C6,
, X2,
, TFL,
, I2
,1
, GAINOPT , 1
, D3
,1
, D4
,1

, IntPt1_RS, *
, IntPt2_RS, *
, IntPt3_RS, *

,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,

,*
,*
,*

,*
,*
,*

, Z,
, IOPPTD01, 1
, IOPPTD02, 1
, IOPPTD03, 1
, IOPPTD04, 1
, IOPPTD05, 1
, IOPPTD06, 1
, IOPPTD07, 1
, IOPPTD08, 1
, IOPPTD09, 1
, IOPPTD10, 1
, IOPPTD11, 1
, IOPPTD12, 1
, IOPPTD13, 1
, IOPPTD14, 1
, IOPPTD15, 1
, IOPPTD16, 1
Profit Optimizer Installation Reference
Honeywell Inc.

1/00

Appendix --- CDS Descriptions

Template,
Template,
Template,
Template,
Template,
Template,
Template,
Template,
Template,

In Array 17
In Array 18
In Scalar 2
In Array 19
In Array 20
In Array 21
In Array 22
In Array 23
In Array 24

RMPCT1_Name, *
RMPCT2_Name, *
RMPCT3_Name, *
Template,
Template,
Template,
Template,
Template,
Template,
Template,
Template,
Template,
Template,
Template,
Template,
Template,
Template,
Template,
Template,
Template,
Template,
Template,
Template,
Template,

,
,
,
,
,
,
,
,
,

, IOPPTD17, 1
, IOPPTD18, 1
, IOLASTS,
, K1
,1
, T1
,1
, S1
,1
, K2
,1
, T2
,1
, S2
,1
, IntPt1_DS
, IntPt2_DS
, IntPt3_DS

Clear
Out Scalar 2
Out Scalar 3
Out Scalar 4
Out Scalar 5
Out Scalar 6
Out Array 1
Out Array 2
Out Array 3
Out Scalar 7
Out Array 4
Out Array 5
Out Array 6
Out Array 7
Out Array 8
Out Array 9
Out Array 10
Out Scalar 8
Out Array 11
Out Array 12
Out Array 13

RMPCT1_Name, *
RMPCT2_Name, *
RMPCT3_Name, *

,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,

1/00

,*
,*
,*

, DOTYPE,
, APPL,
, OB_STATE,
, TD,
, SPOPT,
, OUT1 , 1
, OUT2 , 1
, OUT3 , 1
, D,
, R1
,1
, B1
,1
, R2
,1
, B2
,1
, B3
,1
, B4
,1
, B5
,1
, B6,
, B7
,1
, B8
,1
, DTM , 1

, IntPt1_DS
, IntPt2_DS
, IntPt3_DS

// Combined constraints.
Template, Clear
Template, Low Limit
Template, High Limit
Template, Low Limit Error Weight
Template, High Limit Error Weight
Template, Quadratic Coeff

,*
,*
,*

,*
,*
,*

,*
,*
,*

, DQP_PT , CPAISF01,
, DQP_PT , CPAISF02,
, DQP_PT , CPAISF03,
, DQP_PT , CPAISF04,
, DQP_PT , CPAISF05,

Profit Optimizer Installation Reference


Honeywell Inc.

89

Appendix --- CDS Descriptions

Template,
Template,
Template,
Template,
Template,
Template,
Template,
Template,

Linear Coeff
Desired Value
Predicted Value
Value
SS Value
Status
Scaling Factor
Error Tolerance

, DQP_PT
, DQP_PT
, DQP_PT
, DQP_PT
, DQP_PT
, DQP_PT
, DQP_PT
, DQP_PT

, CPAISF06,
, CPAISF07,
, CPAISF08,
, CPAISF09,
, CPAISF10,
, CPAISF11,
, CPAISF12,
, CPAISF13,

Comb1_Name, *, *, *, 1
Comb2_Name, *, *, *, 2
Comb3_Name, *, *, *, 3
// Bridge outputs.
Template, Clear
Template, Force Bad Flag
,
,X
,1
Template, Critical
,
,X
,2
Template, Max Consecutive Bad
,
,X
,3
Template, RMPCT App Index
T,
,T
,1
Template, RMPCT Var Index
,
,T
,2
// Next entry is for output to LCN. Display is from T(3).
// This must precede entry for PVCALC so PVCALC wins on input.
Template, Read Value
,
,T
,3
Template, Read Value
,
, PVCALC,
Template, Unbiased Model PV
,
,T
,4
Template, Predicted Value
,
,T
,5
Template, Last Good
,
,T
,7
Template, SS Value
,
,T
, 11
Template, Status
,
,T
, 12
Template, Num Data Points
,
, B0 ,
Template, Intervals
,
, B1
,1
Template, Unforced Prediction
,
, B2
,1
Bout:Bout1_Name, *
Bout:Bout2_Name, *
Bout:Bout3_Name, *

, BOUT1_PT , *
, BOUT2_PT , *
, BOUT3_PT , *

,*
,*
,*

The example point names in the file above must be replaced by the actual point names for the
application, as follows:
90

Profit Optimizer Installation Reference


Honeywell Inc.

1/00

Appendix --- CDS Descriptions

Example Name

Replace With

DQP_PT

Name of DQP main point

DVBin:DVBi_Name

Name of ith DV bridge input (must match a name at end of *.ym file)

Dvi_INTERF_PT

Name of DV interface point that provides ith DV bridge input

MVBin:MVBi_Name

Name of ith MV bridge input (must match a name at end of *.ym file)

Mvi_INTERF_PT

Name of MV interface point that provides ith MV bridge input

RMPCTi_Name

Name of ith RMPCT controller (must match a name at end of *.ym file)

RMPCTi_Name_M

Name of ith RMPCT controller followed by _M

RMPCTi_Name_N2

Name of ith RMPCT controller followed by _N2

RMPCTi_PT

Name of ith RMPCT main point

IntPt1_RS

Name of ith RMPCT-side interface point

IntPt1_DS

Name of ith DQP-side interface point

Combi_Name

Name of ith combined constraint (must match a name at end of *.ym file)

Bout:Bouti_Name

Name of ith bridge output (must match a name at end of *.ym file)

BOUTi_PT

Name of ith bridge output interface point

The prefixes Bout: and DVBin: are used to ensure unique names because a bridge output can also
be a DV bridge input. The prefix MVBin: is used for symmetry.

1/00

Profit Optimizer Installation Reference


Honeywell Inc.

91

S-ar putea să vă placă și