Development Environment User's Guide-Honeywell

Advanced Process Control
APC
Development Environment
Users Guide
For Use with
the PROFIT Family of Products
Rev 1.1
3/98
AP09-100
Advanced Process Control
APC
Development Environment
Users Guide
For Use with
the PROFIT Family of Products
Rev 1.1
3/98
AP09-100
Copyright, Notices, and Trademarks

Printed in U.S.A. Copyright 1997 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.
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 85023
(602) 313-4788
ii
APC Development Environment Users Guide

Honeywell Inc.
3/98
Table of Contents
Copyright, Notices, and Trademarks ........................................................................ii
Table of Contents......................................................................................................iii
About This Publication............................................................................................ vii
Statement of Work...................................................................... vii
Release Information.................................................................... vii
Who Should Use This Book ........................................................ vii
Other Books in the APC Library .................................................. vii
How This Book Is Organized ...................................................... viii
Writing Conventions Used in This Book ....................................... ix
References.................................................................................................................. x
RMPCT......................................................................................... x
Other Documents.......................................................................... x
For Technical Assistance ......................................................................................... xi
If You Need Assistance ................................................................ xi
International Customers ............................................................... xi
Customers Inside the United States ............................................. xi
Arizona Customers....................................................................... xi
Services Provided........................................................................ xi
Time Saving Tip .......................................................................... xi
Section 1 Introduction to the APC Development Environment ......................... 1
1.1 Overview.................................................................................................. 1
APC Development Environment ................................................... 1
APC Identifier ............................................................................... 1
RMPCT......................................................................................... 1
PROFIT ........................................................................................ 2
RPID............................................................................................. 2
Step Test Builder .......................................................................... 2
Point Builder ................................................................................. 2
Data Converter ............................................................................. 2
Model Converter ........................................................................... 2
PROFIT Sensor ............................................................................ 2
APC Development Environment ................................................... 3
Section 2 Installing the APC Development Environment.................................... 5
2.1 Overview.................................................................................................. 5
3/98

Honeywell Inc.
iii
Table of Contents
In This Section ..............................................................................5

2.2 System and Software Requirements .........................................................6
Software Requirements .................................................................6
PC Requirements..........................................................................6
2.3 APC Development Environment Installation Quick Reference ................7
How to Use the Quick Reference...................................................7
Quick Reference Table..................................................................7
2.4 Installing the APC Development Environment .........................................8
PC Installation...............................................................................8
Starting the PC Application .........................................................10
Check the Log File ......................................................................10
Check the ini File ........................................................................11
2.5 Installing the Dongle Driver....................................................................13
Dongle Driver Installation ............................................................13
Section 3 Getting Started- The APC Development Environment.....................15
3.1 Overview ...............................................................................................15
In This Section ............................................................................15
APC Development Environment..................................................15
Main Menu ..................................................................................15
File..............................................................................................16
File Types and File Extensions....................................................18
View............................................................................................21
Tools...........................................................................................21
Help ............................................................................................22
Section 4
Getting Started- The Identification Environment............................23
4.1 Overview ...............................................................................................23

In This Section ............................................................................23
4.2 Starting an Identification Session............................................................24
APC Development Environment Options.....................................24
4.3 Reading in Data......................................................................................26
Getting Test Data ........................................................................26
Creating an .mdl File from Plant Data .........................................26
Creating a .pid File from Plant Data ............................................27
4.4 Saving Your Work ..................................................................................28
Saving an .mdl or .pid File ..........................................................28
4.5 Menu Items for Identification Windows ...................................................29
Main Menu ..................................................................................29
Edit .............................................................................................29
View............................................................................................30
Identify ........................................................................................30
Build............................................................................................30
iv

Honeywell Inc.
3/98
Table of Contents
Section 5 Getting Started- The RMPCT Environment ...................................... 31

5.1 Overview............................................................................................... 31
In This Section ............................................................................ 31
5.2 Starting an RMPCT Session ................................................................... 32
APCDE Options .......................................................................... 32
Creating .mdl Documents............................................................ 32
File Types and File Extensions ................................................... 33
5.3 Building the RMPCT Controller/Process Simulator from the .mdl
Window ............................................................................................... 34
Main Menu.................................................................................. 34
5.4 Menu Items for RMPCT Control (.set) Windows ..................................... 35
Main Menu.................................................................................. 35
View............................................................................................ 35
Simulation................................................................................... 35
Control Mode .............................................................................. 36
5.5 Menu Items for RMPCT Process Simulation (.sst) Windows ................... 37
Main Menu.................................................................................. 37
View............................................................................................ 37
Section 6 Getting Started- The PROFIT Environment...................................... 39
6.1 Overview............................................................................................... 39
In This Section ............................................................................ 39
6.2 Starting a PROFIT Session .................................................................... 40
APCDE Options .......................................................................... 40
Creating a PROFIT Document .................................................... 40
6.3 Building the PROFIT Optimizer from the .dqp Window ........................... 43
Main Menu.................................................................................. 43
View............................................................................................ 43
Build ........................................................................................... 43
Section 7 Getting Started- The RPID Environment .......................................... 45
7.1 Overview............................................................................................... 45
In This Section ............................................................................ 45
7.2 Starting an RPID Session ....................................................................... 46
APCDE Options .......................................................................... 46
Creating an RPID Document....................................................... 46
Data Source - Data Files............................................................. 47
Data Source - Manually Entered ................................................ 48
7.3 Building the RPID Controller/Process Simulator from the .pid
Window ............................................................................................... 50
Main Menu.................................................................................. 50
7.4 Menu Items for RPID Control (.soc) Windows......................................... 51
3/98

Honeywell Inc.
Table of Contents
Main Menu ..................................................................................51

View............................................................................................51
Simulation...................................................................................51
Control Mode ..............................................................................52
7.5 Menu Items for RPID Process Simulation (.sos) Windows ......................53
Main Menu ..................................................................................53
View............................................................................................53
Section 8 Getting Started- The Signal Environment..........................................55
8.1 Overview ...............................................................................................55
In This Section ............................................................................55
8.2 Starting a Signal Session........................................................................56
APCDE Options ..........................................................................56
Creating a Signal Document........................................................56
8.3 Building Signals from the .sig Window ....................................................58
Main Menu ..................................................................................58
View............................................................................................59
Build............................................................................................59
Section 9 Getting Started- Tools .......................................................................61
9.1 Overview ...............................................................................................61
In This Section ............................................................................61
Selecting the Tools......................................................................61
9.2 Model Converter .....................................................................................62
Function ......................................................................................62
9.3 Point Builder ...........................................................................................63
Function ......................................................................................63
9.4 TDC Data Converter ...............................................................................64
Function ......................................................................................64
9.5 PROFIT Sensor ......................................................................................65
Function ......................................................................................65
vi

Honeywell Inc.
3/98
About This Publication

Statement of Work
Release Information
The following table describes the audience, purpose, and scope of this book:
Purpose
This book explains how to work APC Development

Environment.
Audience
Process and control engineers
This is document version 110 for APC Development Environment software

release 110.00. For APC Development Environment releases after 110.00 see
the Release Notes.
APC Development Environment R110.00 is compatible with the following
product releases:
PRODUCT
RMPCT
PROFIT
APC ToolKit
RPID
PROFIT Sensor
Identifier
Who Should Use
Release
150.00
100.01
110.00
110.01
100.00
150.00
Anyone responsible for doing advanced process control development work.
This Book
Other Books in the
APC Library
Other books in the APC library describe the use and the important
mathematical and design concepts of the various products supported by APC
Development Environment.
See References later in this section for a list of other APC publications.
3/98

Honeywell Inc.
vii

How This Book Is
Organized
The following table summarizes what each section in this book tells you about
this publication and about APC Development Environment.
In This Section
(You are here)
You Can Find This Information
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.
Section 1, Introduction to
the APC Development
Environment
Introduction to the APC Development Environment, with

a brief description of its functionality.
Section 2, Installing the

APC Development
Environment
System and Software requirements

Installation Quick Reference
Step by Step Installation Procedure
Section 3, Getting Started

- The APC Development
Environment
Explains the basic APC Development Environment

operations.
Section 4, Getting Started

- The Identification
Environment
Brief Overview of the APC Identifier.
Section 5, Getting Started Brief overview of the off-line aspects of RMPCT.

- The RMPCT Environment
Section 6, Getting Started - Brief overview of the off-line aspects of PROFIT.
The PROFIT Environment
Section 7, Getting Started - Brief overview of the off-line aspects of RPID.
The RPID Environment
Section 8, Getting Started - Brief overview of the off-line aspects of the signal
The Signal Environment
generation of the Step Builder.
Section 9, Getting Started - Brief overview of the APC Development Environment
tools:
The Tools
Model Converter
viii
RMPCT Point Builder
TDC Data Converter
PROFIT Sensor

Honeywell Inc.
3/98

Writing
Conventions Used
in This Book
The following writing conventions have been used throughout this book and
other books in the APC 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
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, 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>.
User station touch-screen targets appear in rounded boxes. For example,

touch
brings paragraphs and table entries to your attention.
MODIFY NODE
3/98
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.

Honeywell Inc.
ix
References
The following comprise the APC library.
Title
RMPCT
Number
RMPCT Users Guide for TPS
RM11-400
RMPCT Concepts Reference
RM09-400
RMPCT Installation Reference for TPS
RM20-400
RMPCT Commissioning
RM20-410
RMPCT Off-line Design Users Guide
RM11-410
Title
PROFIT
Number
PROFIT Off-line Design Users Guide for TPS
PR11-430
PROFIT Installation Reference for TPS
PR20-400
PROFIT Concepts Reference
PR09-400
Title
Other Documents
Number
APC ToolKit
AP09-300
Model Converter (Standard with RMPCT)

RMPCT Point Builder (Standard with RMPCT)
TDC Data Converter (Optional APC ToolKit Item)
Data Collector (Optional APC ToolKit Item)
Step Test Builder (Optional APC ToolKit Item)
Performance Monitor (Optional APC ToolKit Item)
APC Development Environment
AP09-100
APC Identifier Users Guide
AP09-200
Robust-PID
PROFIT Sensor Users Guide
RM11-100
PS09-100
Furnace Pass Balance Temperature Control Users Guide
AP09-600
Non-Linear Level Control Users Guide
AP09-700

Honeywell Inc.
3/98
For Technical Assistance

If You Need
Assistance
International
Customers
If you need technical assistance, contact your local Honeywell Service

Organization, as explained in the following paragraphs.
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.
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).
Customers Inside
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
3/98
It is a good idea to make specific notes about the problem before making the
call. This helps to reduce delays and expedite answers.

Honeywell Inc.
xi
xii

Honeywell Inc.
03/98
Section 1 Introduction to the APC Development

Environment
1.1
Overview
APC Development
Environment
This document is a users guide to Honeywells new Advanced Process Control

(APC) Development Environment. APC Development Environment is a
Windows based environment that allows many advanced process control issues
to be addressed through a common interface. APC Development Environment
functionality can be easily expanded by the addition of task specific libraries
(libraries that are dynamically loaded as needed). Several libraries are currently
available for use in the new development environment. Libraries that are
currently supported by the APC Development Environment are given in Table
1-1.
Table 1-1 Current Library Components
1.
Identifier
5.
Step Builder (Signal Generation)
2.
Control Builder
6.
Point Builder
3.
Control Simulator
7.
TDC Data Converter
4.
Process Simulator
8.
Model Converter
5.
PROFIT
9.
PROFIT Sensor
6.
RPID
Additional functionality will be added seamlessly as an evolutionary process.

APC Identifier
With the APC Identifier, you can easily develop a multi-variable dynamic
model of a process that you want to control or simulate. System models in
Laplace domain form are created based on plant data. Combining, rearranging
and evaluating models is accomplished with standard Windows procedures. For
training on the conceptual and practical aspects of the identifier, Honeywells
RMPCT implementation course is recommended (4516s).
RMPCT
Libraries two through four, listed above, comprise the RMPCT Off-Line
Design Software. This software can be easily used to create an RMPCT
controller, based on the model provided by the Identifier. The controller can be
used on-line to control the actual process, and can also be tested on a simulated
process using the off-line software.
3/98

Honeywell Inc.
Introduction to the APC Identifier

1.1 APC Overview
PROFIT
PROFIT supports the easy development of a distributed quadratic optimizer

that runs in a fully dynamic fashion. PROFIT enables you to readily synthesize
a supervisory QP controller that dynamically coordinates multiple RMPCT
controllers. In the APC Development Environment, this is accomplished by
simply merging two or more RMPCT models into an overall PROFIT Model.
RPID
Properly tuned PID loops can be maintained by using the RPID library. This
software determines the proper tuning constants to ensure minimum loop
sensitivity based on parametric uncertainty. Tuning constants for a wide range
of equation types are generated. Calculations are based either on user entered
transfer functions or transfer functions derived from raw data.
Step Test Builder
Effective step test design is provided by the Step Test Builder. This software
allows you to easily create a series of one or more sequences that can be used to
properly excite the actual process. The Step Builder has been designed to work
in conjunction with the APC Identifier. Sequential or/and simultaneous signals
can be readily synthesized and evaluated. Signals are designed for minimum
length and broadband uniform power. The Step Builder is available stand alone
or as part of the APC ToolKit.
Point Builder
By using the RMPCT Point Builder, you can automatically generate an

exception build file that can be used to create all TDC points associated with an
RMPCT controller. The RMPCT Point Builder will also generate several
macros that will ensure that the compile and link phase proceeds effortlessly.
The RMPCT Point Builder is provided as part of the RMPCT design package.
Data Converter
You can use the Data Converter library to automatically convert LCN data to
be APC Development Environment compliant. The Data Converter is available
stand alone or as part of the APC ToolKit
Model Converter
The Model Converter will allow third party models to be converted to APC
Development Environment form. The Model Converter is provided as part of
the RMPCT design package.
PROFIT Sensor
PROFIT Sensor is an on-line, real-time, substitute for laboratory/analyzer

measurement (soft sensor). It offers inferential property estimationa critical
problem for process control and optimization. It can be used to create, train, and
test both linear and non-linear models.
PROFIT Sensor uses ASCII data to create three types of models: 1) Neural
network, 2) Ordinary Least Squares, and 3) Partial Least Squares.

Honeywell Inc.
3/98

1.1 APC Overview
APC Development
Environment
APC Development Environment is currently available for Windows NT and

Windows 95. To observe the available supported and installed functionality of
the APC Development Environment, display the About dialog. An example is
shown below.
The About box will display all supported APC Development Environment
functionality. Those functions checked are installed on the current computer.
3/98

Honeywell Inc.

1.1 APC Overview

Honeywell Inc.
3/98
Section 2 Installing the APC Development Environment

2.1
Overview
In This Section
System and Software Requirements This section lists the system and
software requirements for loading and using the APC Development
Environment
Installation Quick Reference A quick reference is provided indicating the
major tasks involved with installing the software package. If you have installed
the APC Development Environment before, use this quick reference to install
the software package.
Installation Instructions Step-by-step installation instructions are provided
for new users of the APC Development Environment If this is your first
installation of the APC Development Environment use these instructions rather
than the quick reference to install the software.
03/98

Honeywell Inc.
Installing the APC Development Environment

2.2 System and Software Requirements
2.2
System and Software Requirements
Software
Requirements
The APC Development Environment software package consists of two 3 1/2

inch computer floppy disks. Each library component is supplied on an
individual floppy disk.
The two 3 1/2-inch floppy disk set is used to install the APC
Development Environment on the PC computer platform.
PC Requirements
The following table lists the recommended and minimum PC system

requirements for using the APC Development Environment . Depending on
system and data size, identification can be computationally demanding.
Although slower systems may function, maximum computational resources are
recommended.
Recommended Configuration
WIN NT 3.51/4.0 or WIN 95
Minimum Configuration
WIN NT or WIN 95
Pentium 100 MHz
80486 w/math coprocessor
24 MB RAM
16 MB RAM
2GB disk space
1GB disk space
VGA
VGA
Standard Windows video driver
Standard Windows video driver
Disk drive that can read high-density

3 1/2-inch disks
Disk drive that can read highdensity 3 1/2-inch disks
Mouse
Mouse

Honeywell Inc.
03/98

2.3 APC Development Environment Installation Quick Reference
2.3 APC Development Environment Installation Quick

Reference
How to Use the
Quick Reference
Quick Reference
Table
Read and perform the following procedures to install the APC Development
Environment. For detailed instructions and help, see the referenced sections.
The following table outlines the major tasks involved with an APC
Development Environment installation. Use this table if you have installed the
APC Development Environment before. If this is your first installation, use the
detailed instructions provided in Section 2.4.
Step
03/98
Action
Section Reference
1.
Back up the installation disks.
2.
Make sure your computing systems

meet the minimum requirements.
See Section 2.2, System and

Software Requirements.
3.
Run the APC Development

Environment Setup.
See Section 2.4, Installing the

APC Development Environment"
4.
Run the Dongle Driver Install

program.
5.
Install any/all desired library

functions by running the associated
setup script.

Honeywell Inc.

2.4 Installing the APC Development Environment

PC Installation
Before installing the APC Development Environment you should check to make
sure that all necessary disks (for both the DE and any/all libraries) are available.
All disk sets come with an automated installation program called SETUP. You
should always use SETUP to load the program files onto your system to ensure
that all of the files get properly installed. You should install the APC
Development Environment Version 110 first, then direct SETUP to install each
library into the same directory as that of the APC Development Environment.
To run the SETUP program for the DE, perform the following steps:
1.
Insert the APC Development Environment installation disk 1 of 2 disk into

drive A.
2.
Run SETUP.EXE. Select Start>Run from the Windows Taskbar
3.
Click <OK>. This will initiate the installation procedure as shown below.

Honeywell Inc.
03/98

03/98
4.
Click <INSTALL> to continue the installation.
5.
Ensure that the APC DEVELOPMENT ENVIRONMENT box is checked

and select <OK> as shown in the following screen.
6.
You must tell the installer where to place the files. Specify the directory by
entering the entire pathname in the Target Directory dialog box shown
below.
7.
After clicking on <OK> the SETUP program will install the DE files on
your computer system. When the installation is complete the following
screen will appear.

Honeywell Inc.

Starting the PC
Application
8.
The APC Development Environment is now installed on your system.
9.
Repeat the setup procedure described above for each library element.
Install the dongle driver (see section 2.5). Be sure to do this before starting
APC Development Environment .
Select Start>Programs>Honeywell APC Development Environment>
Or from the program manager, click on your APC Development Environment

icon. If all the software was installed correctly, the About Dialog box will have
the appropriate check marks and version information displayed as shown in
Section 1
Check the Log File
If any libraries are not checked that should be or version numbers appear to be
incorrect, check the log file. Select File>Open>c:\windows\APCDE32.log. An
example of the information contained in the log file is shown below.
12:45:09 08Oct97
APC Development Environment: 32 bit Version 110.00.0000
Loaded Math Library: HMATH32.DLL Version 110.00.0000
Loaded Utility Library: HUTIL32.DLL Version 110.00.0000
Loaded Identification Library: HIDENT32.DLL Version 150.00.0000
Loaded Controller Build Library: HBUILD32.DLL Version 150.00.0000
Loaded Simulation Library: HSIM32.DLL Version 150.00
Loaded Controller Library: HCNTRL32.DLL Version 150.00
Loaded Run Block Library: HBLOCK32.DLL Version 150.00
Loaded Robust PID Library: HPID32.DLL Version 110.01.0000
Loaded Profit Library: HBLDQP32.DLL Version 100.01.0000
Loaded Signal Generation Library: HSIG32.DLL Version 100.01.0000
Loaded Point Builder Library: HBLDEB32.DLL Version 110.03.0000
Loaded TDC Data Converter Library: HCONV32.DLL Version 100.00.0000
Loaded Model Converter Library: HDMCNV32.DLL Version 100.00.0000
PROFIT Sensor neural net builder is not present
Any problems with loading libraries will be described here. Inability to locate a
library or library version incompatibility will prevent a library load.
10

Honeywell Inc.
3/98

Check the ini File
Default parameters that can be adjusted by the user are contained in the
ini file. Select File>Open>c:\windows\APCDE32.ini. An example of the
information contained in the ini file is shown below.
[DllLoadOption]
Special=0
DynamicLoad=1
[DTTolOption]
DTTol=.001
[SSC Options]
Code=3TQR37ZAKjEI
[Memory Buffer]
SwapMode=0
UserMemBuf=20
UserMemABuf=4
[Color options]
PltMargBkgndClr=48300031
PltMargTextClr=33554560
CustomColor0=16777215
[Recent EB File List]
[Recent File List]
03/98

Honeywell Inc.
11

It is ill-advised to change any of these parameters without contacting a

Honeywell consultant. The exception is the recent file lists and possibly
the sample rate relaxation variable DTTol (see the APC Identifier Users
Guide).
12

Honeywell Inc.
3/98

2.5 Installing the Dongle Driver

Dongle Driver
Installation
The Advanced Process Control Development Environment is protected by the

SentinelPro dongle which should be connected to the parallel port of your
machine. After installing the APC Development Environment, a driver needs to
be installed. Do the following:
1.
Insert the APC Development Environment Disk 2, containing the

Sentinel Systems Drivers, into a diskette drive.
2.
Run INSTALL.BAT. Select Start>Run from the Windows Taskbar.
NOTE: On NT platforms, you must logon as the system administrator to be

able to install the driver.
03/98
3.
Execute the installation program "INSTALL.BAT as shown above.

The Windows NT driver installation program is located in the
DONGDRV\WIN_NT directory and Windows 95 driver installation
program is located in the DONGDRV\WIN_95 directory.
Pull down the "Function" menu and choose "Install Sentinel Driver"
submenu.

Honeywell Inc.
13

5.
When asked for the source path, use the default path as shown below.
6.
After exiting the installation program, restart your computer to make

the new driver take effect.
The driver needs to be installed only when you first install the 32-bit version of
APC Development Environment. You do not need to install it again when you
upgrade or add optional products to the APC Development Environment.
14

Honeywell Inc.
3/98
Section 3 Getting Started- The APC Development

Environment
3.1 Overview
In This Section
This section explains the basic operation of the APC Development

Environment. Read this section to find out how to:
APC Development
Environment
Start the Environment

Operate Main Menus
Create/Save files
Open files
To invoke the APC Development Environment, either click on the APC icon or
double click on the APCDE32.exe file. The about dialog box shown in Section 1
will be displayed illustrating the current configuration. When the development
environment is launched, an APCDE32.log file will automatically be created
(rewritten if one already exists) in the WINNT directory if using NT and in the
Windows directory if using Window 95. This .log file contains APC
Development Environment version compatibility information. Any problems
associated with incorrect versions etc. will be summarized in this file.
Once the correct configuration has been established, the about dialog box can be
closed. At this point the APC Development Environment can be used to perform
any of the configured functions. An empty environment without the tool or
status bar will appear as shown below.
Main Menu
In the empty environment, there are only four main menu choices: File, View,
Tools and Help. All Library functions listed in Section 1 are accessed through
either the Files or Tools menu. The View option can be used to configure the
tool and status bars. On-line help is not yet available. This main menu option
only enables the display of the About dialog box shown in Section 1.
Main menu options and their associated pull down menus will automatically
change depending on which type of document or file is selected and depending
on the data contained in the selected document.
A brief discussion of the menu items for the empty environment follows.
03/98

Honeywell Inc.
15
Getting Started - The APC Development Environment

3.1 Overview
File
Manipulation of all documents is accomplished through the file options. The

word document as used here refers to the visual representation on the screen
of the data contained in a file. The document or file is presented to the user in
terms of an open window. Therefore every window will be associated with a
specific document or file type. Each file type can be identified by its three
character file extension name (i.e. filename .mdl). File options are:
New Enables the creation of a new and therefore empty document

(window).
Open Allows the user to access an existing document or file
Save (not shown since there are no open documents) Allows the user to
save the contents of the selected window into the appropriate file.
Print Setup Configure printing options
Exit Closes the environment. Will also close any open windows with a
prompt to save if recently modified.
All major functions are accessed through the New and Open options. Support
functions are accessed through the Tools main menu option to be discussed
shortly. To create a new document (window) select File>New. This will invoke
the New dialog box shown below:
Document types and their associations are:
16
Model Dev File - This is the basic multiple-input multiple-output model

file. It has an .mdl extension and is associated with APC Identifier,
RMPCT and PROFIT. The .mdl document must be present to build the
RMPCT controller and the associated process simulator. PROFIT can be
built if more than one .mdl files exist.
Honeywell Inc.
03/98

3.1 Overview
DQP Model File - This is the basic file that supports the creation of the
PROFIT optimizer. It has a dqp extension and while it is synthesized
from multiple .mdl files, it is strictly associated only with PROFIT. The
.dqp document must be present to build PROFIT. The PROFIT associated
process simulator is not yet available.
RPID Dev File - This is the basic multiple-input single-output model file.
It has a pid extension and is associated with both the APC Identifier and
RPID. The .pid document must be present to build the RPID controller
and the associated process simulator.
Signal Dev File - This is the basic file that supports test signal design. It
has an sig extension and is associated only with the Step Builder.
While these are the only files that can be created through the New option, many
additional file types can be accessed through the Open option. To open any
supported file select File>Open.
03/98

Honeywell Inc.
17

3.1 Overview
From the pull down list, choose the extension of the files that you want to
display. From the file list, select the desired file.
File Types and File
Extensions
File types and extensions that can be opened by the APC Development
Environment are given in Table 3-1.
Table 3-1
File Extension
File Types and File Extensions

File Description
File Type
MPT
Multiple point data file
ASCII
PNT
Single point data file
ASCII
MDL
APC MIMO model file
Binary
PID
APC MISO model file
Binary
FIR
Externally generated file of FIR models
ASCII
XFR
Externally generated file of transfer

functions
APC message file
ASCII
Binary
SST
RMPCT Controller settings file for

simulation
RMPCT Process settings file for simulation
SOC
RPID Controller settings file for simulation
Binary
SOS
RPID Process settings file for simulation
Binary
PLT
Binary
DQP
Plot settings file for simulation (open

through SET window)
PROFIT file
SIG
Signal generation file
Binary
INF
SET
ASCII
Binary
Binary
Certain relationships exist among these files. These relationships are:

.mdl documents (windows) are created whenever .mpt, .pnt, .xfr or .fir
files are opened. They also can be created by using the File>New option
as described above. Permanent .mdl files are created whenever .mdl
documents are saved
.pid documents are created whenever .mpt, or .pnt files are opened
through the File>New>RPID Dev>Data Files option. Permanent .pid files
will be created whenever .pid documents are saved
.inf documents are created automatically as necessary to report progress.
Permanent .inf files are created whenever .inf documents are saved.
18
.set documents are created whenever an .mdl document is used to build a

controller. These files are automatically saved

Honeywell Inc.
03/98

3.1 Overview
.sst documents are created whenever an .mdl document is used to build a

process simulator. These files are automatically saved
.soc documents are created whenever a .pid document is used to build a

controller. These files are automatically saved
.sos documents are created whenever an .pid document is used to build a

process simulator. These files are automatically saved
.dqp documents are created whenever multiple .mdl files are opened
through the File>New>DQP Dev>Select RMPCT Applications option.
Permanent .dqp files are created whenever .dqp documents are saved
Permanent .plt files are created by selecting View>Trend Plots>Save As

with the Trend window open when running an RMPCT or RPID
simulation
sig documents can be created only through the File>New option described
above. Permanent .sig files are created whenever .sig documents are
saved.
An overview of the various window (document) types and their association with
files and major functions is illustrated in the environment shown below.
Any window that is selected is the window with the current focus. This window
has its title bar highlighted and the window name is displayed in the
environment title bar (demo.mdl in the illustration shown above.). The main
menu items (and sometimes additional tool bars) will change according to the
selected window.
Note, that the extension name in the window title bar defines the window type
and hence the file name.
03/98

Honeywell Inc.
19

3.1 Overview
Icons displayed in the window title bar can be used to identify functionality.
The relationship between functionality and icon is as follows:
Identification
RMPCT
PROFIT
RPID
Signal Generation
Messages
Other files that are associated with the APC Development Environment are
shown in Table 3-2.
Table 3-2
File Types and File Names
File
*.XM
Model file read by RMPCT engine
ASCII
*.XS
Settings file read by RMPCT engine
ASCII
*.YM
Model file read by PROFIT engine
ASCII
*.YS
Settings file read by PROFIT engine
ASCII
*.XP
Process model file for PC simulation
ASCII
*.EB
Process model file for LCN simulation
ASCII
Main point builder file
ASCII
Signal output sequence
ASCII
*PBLD.EL
Pre-build entity list for LCN points
ASCII
*_BLD.EL
Main-build entity list for LCN points
ASCII
*PBLD.EB
Pre-build exception build file for LCN points
ASCII
*_BLD.EB
Main-build exception build file for LCN

points
Link macro for LCN points
ASCII
Compile macro for LCN points
ASCII
*.EBB
*XG
*LINK.EC
COMPILE.E
C
20

Honeywell Inc.
ASCII
03/98

3.1 Overview
View
In the empty environment, view pertains only to the tool and status bar. In the
environment shown above neither have been selected. Enable these options by
selecting as shown below.
These default options will result in the following empty environment.
The toolbar icons correspond to: New, Open, Save, Cut, Copy, Paste, Print,
Display About dialog box and Display Help (not available) respectively.
Tools
In release 110 of the APC Development Environment, the following tools are
supported.
Tools do not correspond directly to basic document types, rather they are used in
association with the various APC development functions as follows.
03/98
Model Converter - This tool provides a mechanism for creating .fir files
from non-native software. The .fir files can then be directly imported into
the APC Development Environment through the File>Open option.
Point Builder - This tool will automatically create all the exception build
and command files that are necessary to install an RMPCT controller on
any of the currently supported platforms.
TDC Data Converter - This tool provides a mechanism for converting

LCN PV data directly into .pnt files. The .pnt files can then be directly
imported into the APC Development Environment through the File>Open
option.
PROFIT Sensor - This tool can be used to create, train, and test both
linear and non-linear models for inferential property estimation.

Honeywell Inc.
21

3.1 Overview
All of the tools listed above, except PROFIT Sensor, are fully integrated into the
APC Development environment. By selecting Tools>PROFIT Sensor in the
current environment, a separate standalone executable will be launched. This
action can be equivalently accomplished by double clicking on PROFIT_S.exe.
Full integration of PROFIT Sensor is planned for future releases.
Help
22
This main menu option only allows access to the About APC Development
Environment dialog box. Full online help is scheduled for next year.

Honeywell Inc.
03/98
Section 4 Getting Started- The Identification Environment

4.1 Overview
In This Section
This section is a brief overview of the APC Identifier. Read this section
to find out how to:
Start an identification session
Open data files
Create/Save model files or load existing files
View main menus.

For a detailed discussion on the Identifier see the APC Identifier Users
Guide.
03/98

Honeywell Inc.
23
Getting Started with the Identification Environment

4.2 Starting an Identification Session
4.2
Starting an Identification Session
APC Development
Environment
To begin an identification session, the File option must be selected. The

following choices are available.
Options
Selecting [New] at this level results in the creation of an empty document. The
user specifies the type of document by selecting from the New dialog box shown
below.
Only Model Dev.File and RPID Dev.File are associated with an identification
session. Each identification session is automatically associated with a specific
document or file having the .mdl or .pid extension respectively. Any .mdl file
contains all the information necessary to represent a general Multiple-Input
Multiple-Output (MIMO) identification session; while any .pid file contains all
the information necessary to represent a Multiple-Input Single-Output (MISO)
identification session.
An empty document assumes that either data is not available and the user is
going to enter all pertinent information by hand or the user is going to merge
information into it from one or more existing files.
Data/Models from one or more files can be combined or merged into a new
document by simply selecting and dragging the desired information from the
source file(s) to the destination document. For a complete discussion of the
merge operation see Section 3 of the APC Identifier Users Guide
It is much more common to begin or resume an identification by selecting
[Open]. The environment displayed to the user depends directly on the type of
file or document that is opened. The APC Development Environment supports
many environments. Each environment is characterized by a specific set of
24

Honeywell Inc.
03/98
Getting Started - The Identification Environment

4.2 Starting an Identification Session
Main Menu options which are in turn associated with a particular document
type or file extension.
File Types and File
File types and extensions associated with the Identifier are:
Extensions
Table 4-1
File Extension
03/98
File Types and File Extensions

File Description
File Type
MPT
ASCII
PNT
ASCII
MDL
APC MIMO model file
Binary
PID
APC MISO model file
Binary
FIR
ASCII
XFR
Externally generated file of transfer

functions
ASCII
INF
APC message file
ASCII

Honeywell Inc.
25
Getting Started with the Identification Environment

4.3 Reading in Data
4.3
Reading in Data
Getting Test Data
The starting point for identification of a multivariable process model is a file

containing test data obtained from the process.
Test data consists of sampled values, for the independent and dependent
variables, taken over a period during which the independent variables are
excited by a test signal. The Identifier can read in test data from files having
data from one point (.pnt), or from multiple points (.mpt).
Creating an .mdl
File from Plant Data
26
To open a file, select File>Open, then select the desired directory. From the pull
down list, choose the extension of the files that you want to display (in this case
.mpt). From the file list, select the desired file.
1.
Select a multi-point (.mpt) file to start from the beginning with the
variables and test data in that file (as shown in the above figure).
2.
Select any number (up to 2k total characters) of single-point (.pnt) files to

start from the beginning with the variables and data in all the selected
files. The information is collected into a single model file (.mdl). The
different selection methods are:
To select a single file, click on the file name in the file name box
To select additional files, hold <CTRL> and click on the file names
Honeywell Inc.
03/98

4.3 Reading in Data
(<CTRL> toggles the selection state)
Creating a .pid File

from Plant Data
To select all files in a range, drag the cursor over the range of file
names. Or click on the first name and then hold <SHIFT> and click
on the last name
Select an .mdl file to open a saved file where you last left off.
To create a .pid file, it is necessary to select File>New>RPID Dev.File. This
invokes the RPID environment which supports MISO identification. In this
environment the data source is specified explicitly by selecting the source type
from the dialog box shown below.
If Data Files is selected, an Open dialog box is displayed and data files can
be selected exactly as described above. If Manually Entered is selected, then
an empty document will be opened. An empty document assumes that either
data is not available and the user is going to enter all pertinent information by
hand or the user is going to merge information into it from one or more
existing files.
03/98

Honeywell Inc.
27

4.4 Saving Your Work
4.4
Saving Your Work
Saving an .mdl or
.pid File
By selecting File>Save the APC Development Environment creates a permanent

copy of an appropriate .mdl or .pid model file depending on the current
environment. This file is saved in the appropriate directory. All information
related to the model and its development is saved in these files.
You can save an .mdl or .pid file at any time and open it later to continue where
you left off. APC Development Environment always saves your work to the
appropriate model file APC Development Environment never overwrites a
raw data file.
There are three ways to save the file:
28
Select File>Save
Click the toolbar button that looks like a diskette (same as File>Save)
Select File>Save As.

Honeywell Inc.
03/98

4.5 Menu Items for Identification Windows
4.5
Menu Items for Identification Windows
Main Menu
When either an .mdl or .pid window has the focus, the main identification menu
is displayed as shown below.
A brief overview of the menu options follows.

Edit
To view the edit functions select Edit from the main menu.
Depending on the current state of the identification procedure and what

variables are selected, different editing options are available or not as is
appropriate.
03/98

Honeywell Inc.
29

4.5 Menu Items for Identification Windows
View
Different views let you display different information about your identification
data plots for different ranges, model trials, normalized scaling, zoom and many
other options. The fundamental view options are obtained be selecting View
from the main menu as shown below.
Identify
To access the main identification functions, Select>Identify from the main

menu. A drop down selection list as shown below will display the five main
identification functions: Set Overall Options, Fit FIR Models, Fit Parametric
Models, Select Final Trials and Load & Go.
Build
This option enables the construction of either an RMPCT or RPID controller

and/or process simulator depending on whether the menu applies to an .mdl or
.pid window. The build options are accessed as follows.
30

Honeywell Inc.
03/98
Section 5 Getting Started- The RMPCT Environment

5.1 Overview
In This Section
This section gives a brief overview of the off-line aspects of RMPCT. Read this
section to find out how to:
Start an RMPCT session
Open data files
View main menus
For a detailed discussion on RMPCT see the RMPCT Off-Line Design Users
Guide.
03/98

Honeywell Inc.
31
Getting Started - The RMPCT Environment

5.2 Starting an RMPCT Session
5.2
Starting an RMPCT Session
APCDE Options
To begin an RMPCT session, the File option must be selected. The following
choices are available.
If an .mdl file already exists, select Open and start where you left off. Otherwise
you must create a new .mdl document.
Creating .mdl
Documents
To create an .mdl document within the APC Development Environment use the
APC Identifier as described in Section 4.
With an .mdl window present, identification may begin. When the models are
complete, the .mdl document can be used to build an RMPCT controller. Before
this is described in the next section, it is useful to understand the various files
that are involved in the RMPCT off-line design. These files are summarized
next.
32

Honeywell Inc.
03/98

5.2 Starting an RMPCT Session
File Types and File
File types and extensions associated with RMPCT off-line design are:
Extensions
Table 5-1
File Types and File Extensions for RMPCT
File Extension
03/98
File Description
File Type
MPT
ASCII
PNT
ASCII
FIR
ASCII
XFR
Externally generated file of transfer functions
ASCII
MDL
APC MIMO model file
Binary
SET
RMPCT Controller settings file for simulation
Binary
SST
RMPCT Process settings file for simulation
Binary
PLT
Plot settings file for simulation (open through

SET window)
Binary
XM
Model file read by RMPCT engine
ASCII
XS
Settings file read by RMPCT engine
ASCII
XP
ASCII
INF
APC message file
ASCII

Honeywell Inc.
33

5.3 Building the RMPCT Controller/Process Simulator from the .mdl Window
5.3 Building the RMPCT Controller/Process Simulator from

the .mdl Window
Main Menu
When an .mdl window has the focus, the main identification menu is displayed as shown
below.
Since this is an identification document, the menu items are the same as described in Section
4. Here the build options apply to an RMPCT controller and simulator. After the builds
(controller and process) are completed, a .set and a .sst file for the controller and process
respectively will be automatically created. The environment now appear as shown below.
Selecting different windows will automatically change the main menu. Menu items for both
the .set and .sst documents will be described in the next sections
34

Honeywell Inc.
03/98

5.4 Menu Items for RMPCT Control (.set) Windows
5.4
Menu Items for RMPCT Control (.set) Windows
Main Menu
When a .set window has the focus, the main controller menu is displayed.
View
Different views let you display different information about the controllertrend
plots for different ranges, CV MV and DV summary information, normalized
scaling, zoom and many other options. The fundamental view options are
obtained be selecting View from the main menu as shown below.
Selecting the operational tool bar as shown above allows the user to operate the
controller from the tool bar displayed at the bottom of the environment rather
than from the view>summary options.
Simulation
03/98
This option is used to activate, deactivate, pause or resume the simulation.

Additional options allow the user to control both speed and data historzation
and other controller parameters. Select Simulation from the main controller
menu to set these options.

Honeywell Inc.
35

5.4 Menu Items for RMPCT Control (.set) Windows
Control Mode
Use the control mode as shown below to turn the controller the on, off or warm
mode.
Selecting different windows automatically changes the main menu. Menu items
for the .sst documents are described in the next sections
36

Honeywell Inc.
03/98

5.5 Menu Items for RMPCT Process Simulation (.sst) Windows
5.5 Menu Items for RMPCT Process Simulation (.sst)

Windows
Main Menu
When a .sst window is selected, the main menu automatically adjusts and is
displayed as shown below.
View
Different views let you display different information about the processCV MV
and DV information on biases, input and output unmeasurable disturbances and
noise characteristics. The fundamental view options are obtained by selecting
View from the main menu as shown below.
03/98

Honeywell Inc.
37

5.5 Menu Items for RMPCT Process Simulation (.sst) Windows
38

Honeywell Inc.
03/98
Section 6 Getting Started- The PROFIT Environment

6.1 Overview
In This Section
This section is a brief overview of the off-line aspects of PROFIT. Read this
Start a PROFIT session
View main menus.
For detailed discussions on PROFIT see PROFIT Off-Line Design Software

Users Guide or PROFIT Installation Reference for TPS.
03/98

Honeywell Inc.
39
Getting Started - The PROFIT Environment

6.2 Starting a PROFIT Session
6.2
Starting a PROFIT Session
APCDE Options
To begin a PROFIT session, the File option must be selected. The following
If a PROFIT (.dqp) file already exists, select Open and start where you left off.
Otherwise you must create a new PROFIT document.
Creating a PROFIT
Document
To create a PROFIT model document within the APC Development

Environment, it is necessary to select File>New from the main menu as shown
below.
This will allow the specification of the proper document type. Selecting
File>New will result in the new dialog box shown below.
40

Honeywell Inc.
03/98

If DQP Model. File is selected as shown, then you are asked if you wish to
combine multiple RMPCT controllers (actually multiple .mdl files). If no is
selected from the dialog as box shown below, then an empty .dqp document is
opened.
If yes is selected, you are asked which .mdl files are to be combined into an
overall PROFIT optimizer as shown below.
Select the desired .mdl file from the appropriate directories and add them to the
list. When all desired files have been selected click [Finish]. This will extract
all pertinent information from the various .mdl files and create a new .dqp
document named DQPMDL*.dqp that will be opened as illustrated below..
03/98

Honeywell Inc.
41

When the models are complete, the .dqp document can be used to build a
PROFIT optimizer. Before this is described in the next section, it is useful to
understand the various files that are involved in the PROFIT off-line design.
These files are summarized next.
File Types and File
File types and extensions associated with PROFIT are:
Extensions
Table 7-1
File Extension
42
File Types and File Extensions for PROFIT

File Description
File Type
MDL
APC MIMO model file
Binary
DQP
PROFIT Optimizer model file
Binary
YM
Model file read by PROFIT engine
ASCII
YS
Settings file read by PROFIT engine
ASCII
XP
ASCII
INF
APC message file
ASCII

Honeywell Inc.
03/98

6.3 Building the PROFIT Optimizer from the .dqp Window
6.3
Building the PROFIT Optimizer from the .dqp Window
Main Menu
When a .dqp window has the focus, the main menu is displayed as shown
below.
View
Different views let you display different information about the PROFIT
optimizer. The main views pertain to individual controller information
(RMPCT) and overall optimizer information (PROFIT) as shown below.
Descriptive Info and Final Model Xfer Function views are available through the
RMPCT option. Specific PROFIT views are obtained by selecting View>DQP.
The following choices are available.
Build
03/98
To build the PROFIT optimizer, the view must first be set to either Application
Gain Matrix or DQP Gain Matrix. Then select [Build] as shown below.

Honeywell Inc.
43

6.3 Building the PROFIT Optimizer from the .dqp Window
Note, there is currently no support for off-line PROFIT simulation.
44

Honeywell Inc.
03/98
Section 7 Getting Started- The RPID Environment

7.1 Overview
In This Section
This section is a brief overview of the off-line aspects of RPID. Read this
Start an RPID session
Open data files
View main menus.
For a detailed discussion on RPID see the RPID manual.
03/98

Honeywell Inc.
45
Getting Started with the RPID Environment

7.2 Starting an RPID Session
7.2
Starting an RPID Session
APCDE Options
To begin an RPID session, the File option must be selected. The following
If an RPID (.pid) file already exists, select Open and start where you left off.
Otherwise you must create a new RPID document.
Creating an RPID
Document
To create an RPID model document within the APC Development Environment,

it is necessary to select File>New from the main menu as shown below.
This will allow the specification of the proper document type. Selection of
File>Open at this point, if data were to be used to generate models, would
incorrectly result in the creation of a MIMO .mdl document and the RPID
design and simulation functions would not be available in the session. Selecting
File>New results in the new dialog box shown below.
46

Honeywell Inc.
03/98

If RPID Dev. File is selected as shown, then the Data Source dialog box
illustrated below will appear.
Data Source - Data

Files
03/98
You must now choose whether your Robust PID file is based on raw data from
.pnt or .mpt files or whether you want to manually enter the transfer function.
Selecting the Data Files radio button and clicking on [OK] results in the
following dialog box.

Honeywell Inc.
47
Getting Started -- The RPID Environment

You may select either .mpt or .pnt files as long as the total number of variables
are limited to one CV, one MV and up to 10 DVs. The selection choices are:
To select a single file, click on the file name in the file name box.
To select additional files, hold <CTRL> and click on the file names
(<CTRL> toggles the selection state).
To select all files in a range, click on the first name and then hold
<SHIFT> and click on the last name.
Click [Open]
At this point selected data is read into the APC Development Environment and
an RPID identification document titled RPIDDev*.pid is opened as illustrated
below.
With data loaded into the proper document (.pid), identification may begin. See
the APC Identifier Users Guide for information on creating models.
Data Source Manually Entered
48
If it is desired to enter transfer function manually, choose the data source

Manually Entered instead of Data Files as indicated below.

Honeywell Inc.
03/98

Now you have a window representing your empty RPID model file. Enter the
transfer functions manually as described in the APC Identifier Users Guide or
merge from existing documents
When the models are complete, the .pid document can be used to build an RPID
controller. Before this is described (in the next section), it is useful to
understand the various files that are involved in the RPID off-line design.
These files are summarized next.
File Types and File
File types and extensions associated with RPID are:
Extensions
Table 7-1
File Types and File Extensions for RPID
File Extension
03/98
File Description
File Type
MPT
ASCII
PNT
ASCII
FIR
ASCII
XFR
Externally generated file of transfer functions
ASCII
PID
APC MISO model file
Binary
SOC
RPID Controller settings file for simulation
Binary
SOS
RPID Process settings file for simulation
Binary
PLT
Plot settings file for simulation (open through

SET window)
Binary
XP
ASCII
INF
APC message file
ASCII

Honeywell Inc.
49

7.3 Building the RPID Controller/Process Simulator from the .pid Window
7.3 Building the RPID Controller/Process Simulator from the

.pid Window
Main Menu
When a .pid window has the focus, the main identification menu is displayed as
shown below.
Since this is an identification document, the menu items are the same as
described in Section 4. Here the build options apply to an RPID controller and
simulator. After the builds (controller and process) are completed, an .soc and
an .sos file for the controller and process respectively are automatically created.
The environment will now appear as follows.
Selecting different windows will automatically change the main menu. Menu
items for both the .soc and .sos documents are described in the next sections.
50

Honeywell Inc.
03/98

7.4 Menu Items for RPID Control (.soc) Windows
7.4
Menu Items for RPID Control (.soc) Windows
Main Menu
When an .soc window has the focus, the main controller menu is displayed as
shown previously.
View
Different views let you display different information about the controllertrend
plots for different ranges, CV MV and DV summary information, normalized
scaling, zoom and many other options. The fundamental view options are
Selecting the operational tool bar allows the user to operate the controller(s) from
the tool bar displayed at the bottom of the environment rather than from the
view>summary options.
Simulation
03/98
This option can be used to control the simulation. The simulation can be
activated, deactivated, paused or resumed. Additional options allow the user to
control both speed and data historzation. Select Simulation from the main
controller menu to set these options.

Honeywell Inc.
51

7.4 Menu Items for RPID Control (.soc) Windows
Control Mode
Use the control mode as shown below to turn the controller on or off .
Selecting different windows will automatically change the main menu. Menu
items for the .sos documents is described in the next sections.
52

Honeywell Inc.
03/98

7.5 Menu Items for RPID Process Simulation (.sos) Windows
7.5
Menu Items for RPID Process Simulation (.sos) Windows
Main Menu
When an .sos window is selected, the main menu automatically adjust and is
displayed as shown below.
View
Different views let you display different information about the processCV MV
and DV information regarding biases, input and output unmeasurable
disturbances and noise characteristics. The fundamental view options are
03/98

Honeywell Inc.
53

7.5 Menu Items for RPID Process Simulation (.sos) Windows
54

Honeywell Inc.
03/98
Section 8 Getting Started- The Signal Environment

8.1 Overview
In This Section
This section i a brief overview of the off-line aspects of the Signal generation of
the Step Builder. Read this section to find out how to:
Start a Signal session
View main menus
For a detailed discussion on the Signal generator see the Step Builder section of
the Toolkit manual.
03/98

Honeywell Inc.
55
Getting Started -- The Signal Environment

8.2 Starting a Signal Session
8.2
Starting a Signal Session
APCDE Options
To begin a Signal session, the File option must be selected. The following
If a Signal (.sig) file already exists, select Open and start where you left off.
Otherwise you must create a new Signal document.
Creating a Signal
Document
To create a Signal document within the APC Development Environment, it is

necessary to select File>New from the main menu as shown below.
This allows the specification of the proper document type. Selecting File>New
results in the new dialog box shown below.
If Signal Dev. File is selected as shown, then an empty .sig document is opened
56

Honeywell Inc.
03/98
Getting Started - The Signal Environment

8.2 Starting a Signal Session
as illustrated below.
At this point, the .sig document can be used to generate signals with desirable
spectrum and correlation characteristics. Before this is described in the next
section, it is useful to understand the various files that are involved in the Signal
off-line design. These files are summarized next.
File Types and File
File types and extensions associated with the Signal generator are:
Extensions
Table 8-1
File Types and File Extensions for Signal
File
Extension
03/98
File Description
File Type
SIG
Main Signal file
Binary
XG
Sequence file (parameter list or free format)
ASCII
INF
APC message file
ASCII

Honeywell Inc.
57

8.3 Building Signals from the .sig Window
8.3
Building Signals from the .sig Window
Main Menu
When a .sig window has the focus, the main menu is displayed as shown below.
While the Edit options here are the same as in all basic documents, selecting
Edit>Var Info from a .sig document invokes the special dialog box shown
below.
This dialog box allows the user to set all parameters that are used to synthesize
the signals.
58

Honeywell Inc.
03/98

View
Different views let you display different information about the signals. The
main views are shown below.
In addition to the standard data views (first three views) which are also present
in .mdl documents, the .sig document has a correlation and in the future will
have a power spectrum view.
Build
To create the signals, select [Build] as shown below.
Use this option to either build and analyze one or more signals or to export
these signals for external use
03/98

Honeywell Inc.
59

60

Honeywell Inc.
03/98
Section 9 Getting Started- Tools

9.1 Overview
In This Section
This section is a brief overview of the APC Development Environment Tools.

Read this section to find out how to:
Invoke the Tools
For a detailed discussion on the Tools. See the corresponding section of the
APC ToolKit Users Guide Or the PROFIT Sensor Users Guide.
Selecting the Tools
From any environment select [Tools], this is illustrated below for an empty
environment.
Since the tools do NOT directly interact with any documents, they can be
invoked at any time. Simply select the tool for the desired function. The
following paragraphs discuss how the tools are initiated.
03/98

Honeywell Inc.
61
Getting Started - Tools

9.2 Model Converter
9.2
Function
Model Converter
Use this tool to convert non-native FIR models into standard .fir format. Select
Tools>Model Converter. The following dialog box is displayed.
Enter the input and output file names (use browse to define any pathname) and
simply click [Convert]. The resulting .fir file can then be opened to create an
.mdl or .pid document.
62

Honeywell Inc.
03/98

9.3 Point Builder
9.3
Function
Point Builder
Use this tool to build all necessary files for a complete on-line controller
installation. Select Tools>Point Builder. The following dialog box is displayed.
This tool can be used to build both the on-line controller and simulator. Use the
Import and Process Models buttons to extract information automatically from the
.mdl files and .eb files generated by RMPCT simulation builder respectively.
03/98

Honeywell Inc.
63

9.4 TDC Data Converter
9.4
Function
TDC Data Converter

Use this tool to convert raw historized .PV data from the TDC. Select
Tools>TDC Data Converter. The following dialog box is displayed.
Enter the input and output file names (use browse to define any pathname) and
simply click [Convert]. The resulting .pnt files can then be opened to create an
.mdl or .pnt document.
64

Honeywell Inc.
03/98

9.5 PROFIT Sensor
9.5
Function
03/98
PROFIT Sensor
Use this tool to create models for inferred variable calculations. Select
Tools>PROFIT Sensor. This tool is NOT yet fully integrated into the APC
Development Environment. As such, when it is selected, a stand alone
executable is invoked. This program currently runs independently of the
Development Environment. For a detailed discussion on this tool. See the
PROFIT Sensor Users Guide.

Honeywell Inc.
65

9.5 PROFIT Sensor
66

Honeywell Inc.
03/98

Development Environment User&#39;s Guide-Honeywell

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Development Environment User&#39;s Guide-Honeywell

Загружено:

Авторское право:

Доступные форматы

Advanced Process Control

the PROFIT Family of Products

Advanced Process Control

the PROFIT Family of Products

Copyright, Notices, and Trademarks

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

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

Other product names are trademarks of their respective owners.

APC Development Environment Users Guide

APC Development Environment Users Guide

In This Section ..............................................................................5

Getting Started- The Identification Environment............................23

4.1 Overview ...............................................................................................23

APC Development Environment Users Guide

Section 5 Getting Started- The RMPCT Environment ...................................... 31

APC Development Environment Users Guide

Main Menu ..................................................................................51

APC Development Environment Users Guide

About This Publication

This book explains how to work APC Development

Process and control engineers

This is document version 110 for APC Development Environment software

Who Should Use

Anyone responsible for doing advanced process control development work.

APC Development Environment Users Guide

About This Publication

You Can Find This Information

What information you can find in the different

What writing conventions have been used

Introduction to the APC Development Environment, with

Section 2, Installing the

System and Software requirements

Section 3, Getting Started

Explains the basic APC Development Environment

Section 4, Getting Started

Brief Overview of the APC Identifier.

Section 5, Getting Started Brief overview of the off-line aspects of RMPCT.

RMPCT Point Builder

TDC Data Converter

APC Development Environment Users Guide

About This Publication

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

Words in bold type indicate paragraph topics or bring important phrases

Messages, and information that you type appear in Courier font.

Acronyms, parameters, point names, file names, and paths appear in

Command keys appear in UPPERCASE within angle brackets. For

User station touch-screen targets appear in rounded boxes. For example,

brings paragraphs and table entries to your attention.

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

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

APC Development Environment Users Guide

RMPCT Users Guide for TPS

RMPCT Concepts Reference

RMPCT Installation Reference for TPS

RMPCT Off-line Design Users Guide

PROFIT Off-line Design Users Guide for TPS

PROFIT Installation Reference for TPS

PROFIT Concepts Reference

Model Converter (Standard with RMPCT)

APC Development Environment

APC Identifier Users Guide

Furnace Pass Balance Temperature Control Users Guide

Non-Linear Level Control Users Guide

APC Development Environment Users Guide

Development Environment User's Guide-Honeywell

Development Environment User's Guide-Honeywell