Documente Academic
Documente Profesional
Documente Cultură
A
Distributed Quadratic Program
(DQP)
Installation Reference
for AM, AxM and Open LCN-Side
Rev 1.4
1/00
PR20-400
Profit, TDC 3000 and TotalPlant are U. S. registered trademarks of Honeywell Inc.
Honeywell
Industrial Automation and Control
2500 West Union Hills
Phoenix, AZ 85053
1/00
Honeywell Inc.
iii
Table of Contents
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
1/00
Table of Contents
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
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
vii
The following table describes the audience, purpose, and scope of this book:
Purpose
Audience
Release
Information
This is document version 1.4 for Profit Optimizer software release 160.00
releases after R160.00 see the Release Notes.
This Book
Other Books in
See References later in this section for a list of other Profit publications.
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
1/00
The following table summarizes what each section in this book tells you about
this publication and about Profit Optimizer.
In This Section
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
ix
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.
Windows pull down menus and their options are separated by an angle
bracket >. For example, Under Settings> Communications, set the baud
rate.
Acronyms, Scan parameters, point names, file names, and paths appear in
UPPERCASE. The context makes the meaning and use clear.
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 Optimizer (DQP), Profit Optimizer and DQP may be
used interchangeably.
The names Profit Design Studio, and APC Development Environment may be
used interchangeably.
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
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
Customers
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
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
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.
1/00
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
Ranges for
Combined
Constraints
Setpoints
Setpoints
Ranges
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
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
1.2
Profit Optimizer
These are the Profit Optimizer points for an optimizer implementation on TPS.
Points
Table 1-1
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.
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
1/00
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
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 n
RMPCT-Side
Interface Point 1
RMPCT-Side
Interface Point n
RMPCT 1
RMPCT n
RMPCT 1
CV, MV, DV
Simulation Points
RMPCT n
CV, MV, DV
Simulation Points
PROFIT Bridge-Output
Points
Profit
Bridge Output
Simulation
Process
Simulation Driver Point
Figure 1-2
1/00
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.
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
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.
1/00
Step
Action
See
1.
2.
3.
4.
5.
6.
7.
8.
9.
11.
14.
15.
16.
17.
18.
19.
1/00
1/00
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
These are the hardware (memory board) requirements for the AM.
Requirements
Table 2-1
Platform
Requirement
AM
APP Node
8 MW minimum; 16 recommended.
Software
Requirements
Table 2-2
Software Requirements
Platform
AM
APP Node
10
Software
Series
Version Requirement
40
41
50
Any
50 and
above
Any
Load Modules
FILE, CONV, DQP, AMCL1
1/00
These are the recommended locations for the Profit Optimizer files:
Table 2-3
Path to File
How to Quicken
Graphics Response
Network
Configuration
Recommended Location
CL Custom GDF
NET>CDSG>
NET>&CUS>
$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
Setting
Minimum Allocation
# BACKGROUND CL TASKS
10
4
32000
CVB SIZE
15000
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
11
12
1/00
This section describes how to install the Profit Optimizer Load Module,
configure the Application Module, and write the NCF changes.
Optimizer Load
Module?
1/00
13
The Profit Optimizer load module provides the Profit Optimizer runtime library
used by the custom CL routines.
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.
Table 3-1
Step
Action
1.
2.
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.
6.
14
1/00
Table 3-2
Step
1.
Action
From the Engineering Personality Main Menu, touch
LCN NODES
2.
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
32000
CVB SIZE
15000
These are minimum requirements. If your NCF currently has larger values for any of these entries,
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.
8.
Continued
1/00
15
Table 3-2
Step
9.
16
Action
To write the NCF changes:
Press <ENTER>.
Press <F1>.
10.
11.
12.
Go to Section 4.0.
1/00
Object code
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
17
Section 4 Installing the Profit Optimizer Program and the NT-Side Software
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
.CL
.AO
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
DQPIF_PL
DMSG_PL
DQP_PL
Segments
Table 4-3
18
Attaches to Point
BGD_CDS
DIN_CDS
DM1_CDS
DM2_CDS
1/00
Section 4 Installing the Profit Optimizer Program and the NT-Side Software
Object Code
DMOD_CDS
DMSG_CDS
Message point
DMST_CDS
DOUT_CDS
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
Attaches to Point
Blocks
Optimizer point
DQP_RES
Optimizer point
DQP_PNTR
Optimizer point
DQP_READ
Optimizer calculations
Optimizer point
DQP_CALC
Optimizer point
DTPS_CHK
Optimizer point
DTPS_PTS
Optimizer point
DTPS_EXE
Message point
DQP_MSG
Optimizer point
HTPS_MSG
19
Section 4 Installing the Profit Optimizer Program and the NT-Side Software
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
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
1/00
Section 4 Installing the Profit Optimizer Program and the NT-Side Software
Table 4-4
Installation
Compile the Parameter
Lists
Step
Action
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
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 APP Node, there are a couple more files to install, and some
configuration to do. Go to Section 4.5.
21
Section 4 Installing the Profit Optimizer Program and the NT-Side Software
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
APP
22
1/00
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
Point Naming
Conventions
What We Suggest The points can be named anything, but these are suggested.
Use the point name to indicate:
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
1/00
23
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
See
1.
Section 5.2
2.
Section 5.3
3.
Section 5.4
4.
Section 5.5
5.
6.
Section 5.6
7.
Section 5.7
8.
1/00
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
Enter
Comments
NAME
UNIT
PTDESC
A point description
KEYWORD
POINT EXECUTION
PERIOD
This frequency ensures that the optimizer point always has the most
current data.
PVALGID
DATAACQ
CTLALGID
PID
NOINPTS
PISRC(1)
The setpoint
Application-specific settings
After building the BIn MVs, go to Section 5.3 to build the BIn DV points.
1/00
25
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
Enter . . .
Comments
NAME
UNIT
PTDESC
A point description
KEYWORD
A descriptive search word or phrase DQPSIM, SIMPNT or SIMLTNPT are good keywords for
these points.
POINT EXECUTION
PERIOD
PVALGID
DATAACQ
CTLALGID
PID
NOINPTS
PISRC(1)
The setpoint
Application-specific settings
After putting the BIn DVs on the system. Go to Section 5.4 for the driver points 1st-pass build.
26
1/00
Set These
Parameters
Table 5-4
Enter . . .
Comments
NAME
UNIT
PTDESC
A point description
KEYWORD
POINT EXECUTION
PERIOD
BEFAFT
Select CYCLE
NORMCYCLE
After putting the driver points on the system, go to Section 5.5 to build the BOut sim points.
1/00
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
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
31
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
Enter . . .
Comments
NAME
UNIT
PTDESC
A point description
KEYWORD
PVALGID
CL
CTLALGID
NULL
BEFAFT
Select AFTER
PTDISCL
FULL
Continued
32
1/00
Table 5-5
Enter . . .
CLSLOTS
NOPKG
PKGNAME(1)
RSIM_CDS
Application-specific settings
I1
I2
IN
Application-specific settings
Comments
When all sim BOuts are built, go to Section 5.6 to attach the model coefficients.
1/00
33
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
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.
RECONSTITUTE
MULTIPLE
Continued
34
01/00
Table 5-6
Step
5
Press <ENTER>.
Touch
EXCEPTION
BUILD
Touch
WITH
OVERWRITE
Touch
LOAD
ENTITIES
10
11
Press <ENTER>.
12
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.
35
Set These
Parameters
These standard parameters for the driver point are already on the system from the
1st-pass build:
NAME
PTDESC
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
2
1
RGET_CDS
Enter
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)
IN2(n)
VALUES(n)
Comments
36
01/00
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.
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
37
Set These
Parameters
Table 6-1
Table 6-1 describes the required point parameter settings or suggested settings for
DQP-Side interface points.
Building DQP-Side Interface Points
Enter . . .
Comments
NAME
UNIT
PTDESC
A point description
KEYWORD
PERIOD
NOPERIOD
CLSLOTS
NOPKG
PKGNAME(1)
DMOD_CDS
PKGNAME(2)
DIN_CDS
PKGNAME(2)
DOUT_CDS
Application-specific settings
After building the DQP-Side interface points, go to Section 6.3 to build the RMPCT-Side interface points.
38
1/00
Set These
Parameters
Table 6-2
Enter . . .
Comments
NAME
UNIT
PTDESC
A point description
KEYWORD
PERIOD
NOPERIOD
CLSLOTS
NOPKG
PKGNAME(1)
DM1_CDS
PKGNAME(2)
DM2_CDS
PKGNAME(3)
DIN_CDS
PKGNAME(4)
DOUT_CDS
Application-specific settings
After building the RMPCT-Side interface points, go to Section 6.4 to build the BOut interface points.
1/00
39
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
Enter . . .
Comments
NAME
UNIT
PTDESC
A point description
KEYWORD
PTDISCL
FULL
PVALGID
DATAACQ
CTLALGID
NULL
PERIOD
NORMCYCLE
Continued
40
1/00
Table 6-3
Enter . . .
Comments
NOINPTS
PISRC(1)
CLSLOTS
NOPKG
PKGNAME(1)
All other point
parameters
BGD_CDS
Application-specific settings
1/00
41
42
1/00
Profit Optimizers
Optimization
Points
Table 7-1
Point
Optimizer
Message
1/00
Description
The Profit Optimizer engine functions include:
Integrity checks
Detects and reports the following errors in the Profit Optimizer engine calculations which
includes:
I/O errors
Calculation errors
43
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.
3.
Data then returns to the process through the RMPCT controllers in the form
of an optimization solution.
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:
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.
1/00
Application
Notes
Set These
Parameters
For This
Parameter . . .
Enter . . .
Comments
NAME
UNIT
PTDESC
A point description
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
Application-specific settings
Application-specific settings
After building the message point, go to Section 7.3 to build the optimizer point.
1/00
45
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
UNIT
This point must be in the same unit as the DQP-Side interface points
and BOut interface points
PTDESC
A point description
KEYWORD
CLSLOTS
NOPKG
For AM
For AM
PKGNAME(1)
DQP4_CDS
PKGNAME(2)
DQP3_CDS
PKGNAME(3)
DQP2_CDS
PKGNAME(4)
DQP1_CDS
PKGNAME(5)
HTPS_CDS
PERIOD
Must be the same frequency as the frequency used in the offline design.
BEFAFT
CYCLE
NORMCYCL
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
1/00
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.
47
Table 7-4
Initializing Profit Optimizer Messages from the MSG_ENG Alter Parameter File
Step
Action
1.
2.
ALTER
PARAMETERS
For Pathname
Enter
Reference Path
Selection List
MSG_ENG.XX
3.
Press <ENTER>.
4.
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
1/00
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
49
50
1/00
This section explains how to build the points Profit Optimizer needs to display
information about your application on the Operator screens.
What DQP_LIST
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
Conventions
1/00
51
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
Enter . . .
DQP_LIST
Comments
This name is required.
UNIT
PTDESC
A point description
KEYWORD
CLSLOTS
NOPKG
PKGNAME(1)
DMST_CDS
PERIOD
NOPERIOD
Application-specific settings
Continued
52
1/00
Table 8-1
Enter . . .
Comments
D( )
C1DESC( )
Application-specific settings
1/00
53
54
1/00
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
55
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
File Name
56
Description
RMPC_DDB.DF
Global database
DQP.DS
RDQP_SEL.DS
RDQP_DTL.DS
RDQPCFG1.DS
RDQPCFG2.DS
RDQP_MSG.DS
RDQP_MPC.DS
RDQP_CV1.DS
RDQP_CV2.DS
RDQP_CVO.DS
RDQP_MV1.DS
RDQP_MV2.DS
RDQP_MVO.DS
RDQP_DV1.DS
RDQP_DV2.DS
RDQP_BD1.DS
RDQP_BD2.DS
RDQP_CC1.DS
RDQP_CC2.DS
1/00
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.
Compiling, and
Loading
Table 9-2
Step
1.
Action
Comment
2.
3.
4.
5.
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
57
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.
8.
DQP
1/00
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
For Help
1/00
For help displaying and using the Profit Optimizer screens, see Section
2.0 in the Profit Optimizer Users Guide.
59
Table 10-1
Step
Comment
1.
Copy the .YS and .YM files onto the History Module.
2.
On the station keyboard, press <SCHEM>, and enter DQP to call the Operator interface:
3.
4.
5.
6.
7.
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.
1/00
Table 10-3
Step
1/00
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.
4.
5.
6.
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.
Attention
No extension. No path. Filenames
only.
61
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.
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.
3.
4.
For AxM installations, the name of the AxM data transfer point in
XNAME(0).
5.
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
1/00
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 These
Files . . .
AM Implementations
DQP_MAIN
Optimizer point
APP Node
Implementations
DQP_OPEN
Optimizer point
HTPS_MSG
Optimizer point
DQP_MSG
Message point
RMPCSIM
BOut simulation
points
RMPCGETD
All Implementations
To These
Points . . .
Comments
1/00
63
At the Command Processor, use this command format to link the CL code to the
application points:
LK
Table 10-5
NET>DQP>OBJCODE
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
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.
2.
When the points are linked, activate the points and read in the design files. See Section 10.5 for the point activation
order.
1/00
10.5 Activating the Points, Reading In the Design Files and Tying in Controllers
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.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
[w Init]
or
Otherwise, go to 17 below.
1/00
65
10.5 Activating the Points, Reading In the Design Files and Tying in Controllers
Step
13.
14.
Action
Comment
15.
16.
For AM only
Unlink the following blocks from the RMPCT controller point:
RMPC_CVP
RMPC_DVP
RMPC_CON
For AxM only
RMPC_MSG
RMPC_END
RMPC_XFR
etc..
RMPCX_DVP
RMPCX_CON
RMPCX_MSG
RMPCX_END
RMPCX_XFR
RMPCX_UNP
RMPCX_PCK
etc..
For AM only
Re-link RMPC_CON object to the RMPCT controller point.
66
17.
18.
19.
20.
For AM implementations, check the read-in date and time stamps. See the next page for comments.
21.
1/00
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
67
10.5 Activating the Points, Reading In the Design Files and Tying in Controllers
68
1/00
Solution:
DQP Optimizer Execution Failed 0.00 20009 error message on the LCNs
Message Summary display.
1/00
69
70
1/00
Index
IO
X()
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
B1 ( )
1 . . . 21
B2 ( )
1 . . . 21
INITCONF
Bridge DV description
PT
S1
1/00
(DV_UFP)
DESCRIPT
A( )
(DV_num_blks)
(DV_blk)
1 . . . 200
71
Index
Description
INI
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
K1 ( )
1-80
T1 ( )
1-40
u1 MV value
S1 ( )
1-40
u_DV1
K2 ( )
1-80
T2 ( )
1-40
u2 MV value
S2 ( )
1-40
INH_STAT
72
u_DV2
(set 1)
DV value (set 1)
(set 2)
DV value (set 2)
1/00
Index
IN0
Description
Identity number Must be -9 to identify this to Pascal
MODSTAT1
model_id
C1
C2
C3
IN3
TF
I1 ( )
1 . . . 1000
G()
1 . . . 1000
D1 ( )
1 . . . 80
Dr (row/CV scaling)
D2 ( )
1 . . . 40
Dc (column/MV scaling)
1/00
73
Index
IN0
Description
Identity number Must be -9 to identify this to Pascal
MODSTAT1
Model id
C1
C2
C3
X1
TF
I1 ( )
1 . . . 1000
G()
1 . . . 1000
D1 ( )
1 . . . 80
Dr (row/CV scaling)
D2 ( )
1 . . . 40
Dc (column/MV scaling)
DM2_CDS
Parameter
Index
Description
IN3
MODSTAT2
Model_id
C4
C5
C6
X2
TFL
I2 ( )
1 . . . 1000
GAINOPT ( )
1 . . . 1000
D3 ( )
1 . . . 80
Dr (row/CV scaling)
D4 ( )
1 . . . 40
Dc (column/MV scaling)
74
1/00
Message Point
DMSG_CDS
Parameter
Index
P0
F()
K3 ( )
10
11
12
No execution overlap
13
14 . . . 16
K1 ( )
Description
warn~
error~
clear~
code~
CV~
MV~
DV~
, code~
10
, rec~
11
, chr~
12
req index~
Continued
1/00
75
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
1/00
Index
Description
D1 ( )
1 . . . 30
C1DESC ( )
1 . . . 30
1/00
77
Index
Description
IN2
DOTYPE
APPL
OB_STATE
1 => Optimizing
2 => not enough degrees of freedom
TD
SPOPT
OUT1 ( )
1 . . . 80
OUT2 ( )
1 . . . 40
OUT3 ( )
1 . . . 40
D
R1 ( )
B1 ( )
1 . . . 40
R2 ( )
1 . . . 80
B2 ( )
1 . . . 40
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
INITCONF
78
1/00
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
10
Current ojbective
11
12
ext_n_DV_bin
13
ext_n_bin
14
ext_comb
15
16
YS file version
17
T_dqp
18
RM_read_required
19
obj_function
20
DQP_Version
21 . . . 50
1/00
Description
Reserved
79
Index
Description
DQP Flag
D1 ( )
1 . . . 50
DQP now_alarm
D2 ( )
1 . . . 50
DQP prev_alarm
BINRINGR ( )
1 . . . 150
VALUES ( )
1 . . . 150
STATE1 ( )
1 . . . 40
C( )
1 . . . 40
D1TYPE ( )
1 . . . 40
INTIDLST ( )
1 . . . 40
CPAISF01 ( )
1 . . . 100
CPAISF02 ( )
1 . . . 100
CPAISF03 ( )
1 . . . 100
CPAISF04 ( )
1 . . . 100
CPAISF05 ( )
1 . . . 100
CPAISF06 ( )
1 . . . 100
CPAISF07 ( )
1 . . . 100
CPAISF08 ( )
1 . . . 100
CPAISF09 ( )
1 . . . 100
Reserved
CPAISF10 ( )
1 . . . 100
CPAISF11 ( )
1 . . . 100
CPAISF12 ( )
1 . . . 100
CPAISF13 ( )
1 . . . 100
INTICONF
DQP_initconf
DQP_pool_data_ptr
80
0 = not wound up
1/00
Index
DESCRIPT
Description
RMPCT DQP appl description
ZZTEXT ( )
1 . . . 100
P1 ( )
1 . . . 440
Parameter
Index
Description
P2 ( )
1 . . . 240
P3 ( )
1 . . . 140
P4 ( )
1 . . . 50
Parameter
S1 ( )
N( )
T1 ( )
D7 ( )
Index
Description
Model File
Specification File
Configuration File
Reserved
1...5
Start of calculations
duration of calculations
1 . . . 38
For messaging
P0 ( )
1 . . . 40
P5 ( )
1 . . . 40
P6 ( )
1 . . . 40
ANAME
P7 ( )
1 . . . 50
P8 ( )
1 . . .100
1/00
81
Index
Description
C7
C8
IN6
1 . . . 10
IN7
1 . . . 10
IN8
1 . . . 10
IN9
1 . . . 10
IN10
1 . . . 10
B8
1
2...4
8 . . . 20
S3
1
2 . . . 20
Spares
Configuration filename (without file extension)
Spares
HTPS_MSG
Parameter
D7
Index
Description
1 . . . 38
1
82
Exclusive error
23
Overlapped seconds
25
27
Component status 1
29
Component status 2
31
Component status 3
33
: Warning condition 1
Profit Optimizer Installation Reference
Honeywell Inc.
1/00
35
: Warning condition 2
37
: Warning condition 3
C8
C7
IN6
1. . .10
IN7
1. . .10
IN8
1. . .10
IN9
1. . .10
IN10
1. . .10
B8
1. . .20
1
1/00
83
84
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
85
, 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,
// 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
1/00
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
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
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,
89
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
1/00
Example Name
Replace With
DQP_PT
DVBin:DVBi_Name
Name of ith DV bridge input (must match a name at end of *.ym file)
Dvi_INTERF_PT
MVBin:MVBi_Name
Name of ith MV bridge input (must match a name at end of *.ym file)
Mvi_INTERF_PT
RMPCTi_Name
Name of ith RMPCT controller (must match a name at end of *.ym file)
RMPCTi_Name_M
RMPCTi_Name_N2
RMPCTi_PT
IntPt1_RS
IntPt1_DS
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
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
91