Lab Update User's Guide - Honeywell Process · 2011. 11. 14. · 5/01 Lab Update User’s Guide ix Honeywell Inc. References The following comprise the Profit Suite library. Documentation

Profit Toolkit - Lab UpdateUser’s Guide

5/01

Rev 1.1

AP13-111

ii Lab Update User's Guide 5/01

Honeywell Inc.

.

Profit Toolkit - Lab UpdateUser’s Guide

5/01

Rev 1.1

AP13-111

iv Lab Update User's Guide 5/01

Honeywell Inc.

Copyright, Notices, and Trademarks

Copyright 2001 by Honeywell International Inc.

While this information is presented in good faith and believed to be accurate, Honeywelldisclaims the implied warranties of merchantability and fitness for a particular purpose andmakes no express warranties except as may be stated in its written agreement with and for

its customer.In no event is Honeywell liable to anyone for any indirect, special or consequential damages.

The information and specifications in this document are subject to change without notice.

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

Other product names are trademarks of their respective owners.

HoneywellIndustrial Automation and Control

16404 N. Black Canyon HwyPhoenix, AZ 85053

5/01 Lab Update User's Guide v

Honeywell Inc.

Table of Contents

TABLE OF CONTENTS ........................................................................................................... VABOUT THIS PUBLICATION ................................................................................................ VII

Statement of Work ......................................................................................... viiRelease Information....................................................................................... viiRMPCT Course Information........................................................................... viiWriting Conventions Used in This Book ........................................................viii

REFERENCES......................................................................................................................... IXDocumentation................................................................................................ ixOpen ................................................................................................................. ixTPS System........................................................................................................ ixEmbedded Uniformance ........................................................................................ ix

FOR TECHNICAL ASSISTANCE ............................................................................................ XIf You Need Assistance....................................................................................xInternational Customers...................................................................................xCustomers Inside the United States ................................................................xArizona Customers ..........................................................................................xServices Provided ............................................................................................xTime Saving Tip ...............................................................................................x

SECTION 1 - LAB UPDATE....................................................................................................11.1 Overview ...............................................................................................................1

In This Section .................................................................................................1Installation Requirements – PHD Client Software ...........................................1Prerequisites for Configuring Lab Update........................................................1Terminology .....................................................................................................1Usage of Lab Update .......................................................................................2Steps to Successfully Configuring a Lab Update Application..........................3Execution Period..............................................................................................3Deactivating a Single Lab Bias Calculation .....................................................3How Lab Update Interfaces with PHD .............................................................3Establishing a Connection with PHD ...............................................................3Configuring PHD to Historize Inferred Values .................................................3What Values Need to be Historized by PHD? .................................................4Do we Historize the Biased or Unbiased Inferred Value? ...............................4What About Engineering Units?.......................................................................4Retrieving Current Inferred Values from PHD .................................................4User Commands ..............................................................................................4Averaging the Inferred Values .........................................................................4Lab Value Minimum and Maximum Range......................................................5Conditioning the Bias Prior to Output. .............................................................5Bias Output ......................................................................................................5

1.2 Detailed Description..............................................................................................7Calculation Algorithm .......................................................................................7Input table ........................................................................................................8Output table....................................................................................................13Return Status Table .......................................................................................14

Table of Contents

vi Lab Update User's Guide 5/01

Honeywell Inc.

1.3 Configuring PHD for Lab Update History Collection......................................16What Parameters Need to be Historized .......................................................16

1.4 Configuring Embedded PHD for Lab Update History Collection ...................17Embedded PHD Configuration.......................................................................17How to Find the Embedded PHD TagName..................................................17

1.4 Configuring Oracle Based PHD for Lab Update History Collection....................18Recommended PHD Tag Naming Convention ..............................................18OPC RDI Configuration..................................................................................18Summary of OPC RDI Configuration Steps...................................................18Using the PHD RDI Specification form to Configure the OPC RDI ...............18Important Note on OPC RDI Configuration....................................................19Important Note: OPC RDIs will Automatically Launch Profit ToolkitApplication......................................................................................................19Configuring Tags in PHD ...............................................................................19Sample Tag Configuration .............................................................................19

1.5 Lab Update User Display....................................................................................21Overview ........................................................................................................21Lab Update Data Section...............................................................................25Additional Features ........................................................................................28

5/01 Lab Update User's Guide vii

Honeywell Inc.

About This PublicationStatement of Work The following table describes the audience, purpose, and scope of this book:

Purpose This book explains how to use the Lab Update Toolkit Function. TheLab Update Function is used to update bias values for inferred valuecalculations.

Audience Process and control engineers

ReleaseInformation

This is document version 1.1 for Lab Update Toolkit Release 200.00.

RMPCT CourseInformation

Honeywell offers several courses that explain the math and conceptualunderpinnings of RMPCT as well as application implementation of the AdvancedProcess Control suite of products.

Engineers wanting a more technical exposure to RMPCT can contact:

Honeywell Automation College

2500 W. Union Hills Drive

Phoenix, AZ 85027

602-313-5669

About This Publication

viii Lab Update User's Guide 5/01

Honeywell Inc.

WritingConventions Usedin This Book

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

• Words in double quotation marks " " name sections or subsections in thispublication.

• Words in italics name book titles, add grammatical emphasis, introducewords 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 toyour attention.

• Shading brings paragraphs and table entries to your attention.

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

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

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

• Command keys appear in UPPERCASE within angle brackets. For example,press <ENTER>.

• TPS user station touch-screen targets appear in rounded boxes. For example,touch MODIFY NODE .

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

• Point-dot-parameter means a point name and one of its parameters. Forexample, 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 isgiven as Ø. In all other cases, zero as a numerical place holder is given as 0. Forexample, 1.0, 10, 101, CVØ1, parameter PØ.

• The terms screen and display are used inter changeably in discussing thegraphical interfaces. The verbs display a screen and call a screen are also usedinter changeably.

• These names may be used interchangeably.

Former Name Product Name

RMPCT Profit Controller

DQP Profit Optimizer

APC Development Environment or APCDE Profit Design Studio

RPID Profit PID

5/01 Lab Update User’s Guide ix

Honeywell Inc.

References

The following comprise the Profit Suite library.Documentation Title Number

General

Profit Controller (RMPCT) Concepts Reference RM09-400Profit Controller (RMPCT) Designer’s Guide (Off-Line Design) RM11-410Profit Optimizer Designer’s Guide (Off-Line Design) PR11-400Profit Toolkit Designer’s Guide AP11-400APC Identifier User’s Guide AP09-200Profit-PID (RPID) RM11-100Profit Sensor User’s Guide PS09-100

Open

Profit Suite Installation Guide for Open SystemsViewer - Controller - Optimizer - Toolkit

RM20-501

Profit Controller (RMPCT) User’s Guide for Open Systems RM11-401Profit Optimizer User’s Guide for Open Systems PR11-421Profit Trender User’s Guide RM11 431Profit Toolkit User’s Guide for Open Systems AP11-401Profit Toolkit Function Reference AP11-410FCCU Toolkit User’s Guide for Open Systems AP13-201Fractionator Toolkit User’s Guide for Open Systems AP13-101Lab Update User’s Guide AP13-111Wrapper Builder User’s Guide AP11-411Profit Bridge User’s Guide AP20-401

TPS System

Profit Controller (RMPCT) Installation Reference for AM, AxM and Open LCN-Side RM20-400Profit Controller (RMPCT) Commissioning RM20-410Profit Controller (RMPCT) User’s Guide for AM, AxM and Open LCN-Side RM11-400Profit Optimizer Installation Reference for AM and Open LCN-Side PR20-400Profit Optimizer User’s Guide for AM and Open LCN-Side PR11-420Profit Suite Toolkit AP09-300TDC Data ConverterData CollectorStep Test Builder

Performance MonitorRMPCT CascadePV Validation

Simulation BackBuilderGain Scheduler

Fractionator Toolkit (LCN) AP13-100FCCU Toolkit (LCN) AP13-200Furnace Pass Balance Temperature Control User’s Guide AP13-600Non-Linear Level Control User’s Guide AP09-700

Embedded Uniformance

Excel Companion User’s Guide (Profit Embedded PHD) AP20-510Power Point Companion User’s Guide (Profit Embedded PHD) AP20-520Process Trend User’s Guide (Profit Embedded PHD) AP20-530

x Lab Update User’s Guide 5/01

Honeywell Inc.

For Technical Assistance

If You NeedAssistance

If you need technical assistance, contact your local Honeywell ServiceOrganization, as explained in the following paragraphs.

InternationalCustomers

Outside of the United States, contact your local Honeywell Service Organization.If you are not sure of the location or telephone number, call your Honeywellrepresentative for information.

Customers Insidethe United States

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

ArizonaCustomers

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 isin effect).

Outside of these hours, emergency calls—those which affect your ability tocontrol or view a process—will be received by an answering service, andreturned within one hour. TAC maintains its own TPS network, and frequentlycan duplicate problems on this equipment.

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

For Technical Assistance

5/01 Lab Update User's Guide xi

Honeywell Inc.

5/01 Lab Update User’s Guide 1

Honeywell Inc.

Section 1 - Lab Update1.1 Overview

In This Section Lab Update corrects inferred property calculations (such as Fractionator or FCCUtoolkit calculations) based on laboratory property test results. In simple terms thebias is the difference between the inferred calculation and the lab results.

Lab Update works in conjunction with PHD that is responsible for collectinghistory data relating to the inferred values that will be biased. As such, for LabUpdate to work, either Oracle Based PHD or Embedded PHD is required.

InstallationRequirements –PHD ClientSoftware

PHD Client software must be loaded on the same machine as Lab Update - thisallows Lab Update to collect history data from PHD.

If Embedded PHD and Lab Update are running on the same machine then the PHDClient software does not need to be installed as the PHD client software is alreadyinstalled with the Embedded PHD installation.

Similarly if Lab Update and Oracle Based PHD are installed on the same machinethen the PHD Client software does not need to be installed.

Prerequisites forConfiguring LabUpdate

The user responsible for configuring the Lab Update Toolkit should haveexperience or training in the following areas:

• Profit Toolkit Environment including:

• Profit Toolkit Design Configuration (in Profit Design Studio)• Profit Toolkit RunTime Configuration (in Profit Design Studio)• Profit Viewer and Profit Toolkit RunTime

• In addition the user should have PHD experience in the following areas:

• RDI Configuration• Tag Configuration

Terminology Application – When the word “application” is used in this section it generallyrefers to a Profit Toolkit application that contains one or many Profit Toolkitfunctions. Examples of applications are a Lab Update application containing LabUpdate functions, or a Fractionator application containing Fractionator functionssuch as RVP, etc.

Function – Also referred to as Profit Toolkit Function. This is any function thatruns in Profit Toolkit. Example of a Profit Toolkit Function is the Fractionator RVPfunction. Important Note: Lab Update too, is an example of a Profit ToolkitFunction. Many instances of each function can be created.

Inferred Calculation/Property/Value – This is a calculated or predicted value.Generally inferred values need to be corrected, and as such require a Lab Update.An example of an inferred value is the RVP calculation that is part of theFractionator toolkit.

PHD – Process Historian Database. Uniformance product that collects history data.


2 Lab Update User's Guide 5/01

Honeywell Inc.

Usage of LabUpdate

It is recommended that the user configure Lab Update in a separate Profit Toolkitapplication from its associated inferred value application. The following diagramshows a conceptual layout of how Lab Update interacts with other Profit Toolkitfunctions that calculate the inferred values.

The diagram shows that a single instance of the lab update function can updatebiases for a configurable number of inferred calculations. The user may decidethat one lab update function can be configured to update biases for all inferredproperty calculations associated with all Fractionator or FCCU application, oralternately the user may decide that a separate Lab Update function is required foreach inferred value application.

Lab Update requires that inferred calculated values be historized. This is requiredbecause the bias is corrected based on a lab sample (and corresponding inferredcalculation) that occurred at some time in the past.

As shown in the diagram above, the mechanism used to collect inferred valuehistory data is PHD. The Lab Update function gets the history data from PHD.

The user needs to configure PHD to historize the inferred values.

Lab Update Application

Lab UpdateFunction #1

Fractionator Application

Frac Function #1

Frac Function #2

Frac Function #n

FCCU Application

FCCU Function #1

FCCU Function #2

FCCU Function #n

Lab UpdateFunction #n

PHD


5/01 Lab Update User's Guide 3

Honeywell Inc.

Steps toSuccessfullyConfiguring aLab UpdateApplication

The steps to configuring a Lab Update Application successfully are:

1. Determine which inferred values require a bias update.

2. Configure PHD RDIs (configure OPC RDIs if collecting from a Profit Toolkitapplication) to allow collection of inferred values.

3. Configure PHD tags to collect history for all the inferred values and biases.

4. Configure Lab Update via the Profit Design Studio (APCDE).

5. Create a short cut that allows the user to launch the Lab Update Run-Timedisplay.

Execution Period It is recommended that Lab Updates execution period be set to 30 seconds. Thissetting is done during Design Configuration by setting parameterAPPLICATION\Etime to 0.5 (i.e. half a minute).

This allows Lab Update to validate the PHD connection in an efficient mannerwithout overloading the host computer.

Deactivating aSingle Lab BiasCalculation

The parameter BiasState can be set to 0 to inactivate an individual biascalculation. When a calculation is inactivated, no commands are accepted, andnone of the values relating to the value are updated (for example the currentinferred value is not updated). The calculation can be re-activated by settingBiasState to 1.

How Lab UpdateInterfaces withPHD

PHD needs to be configured to collect history for all inferred values and biasesthat are configured as part of the Lab Update toolkit.

The Lab Update toolkit runs independently of PHD. Lab Update’s history retrievalmechanism is triggered when a sample has been tested and is returned from thelab and is entered by the operator.

This causes Lab Update to retrieve a set of values from PHD relating to theinferred value calculation and bias value around the sample time. Lab Updatethen calculates the average of this set of values, then calculates the lab bias basedon this average. It then conditions and outputs the bias.

Establishing aConnection withPHD

A single string parameter called – ConnectionString – is provided to establish aconnection with PHD. The connection string should be set as follows:

HOSTNAME/3000

Where HOSTNAME is the name of the host on which PHD resides, and 3000 isthe port number for the connection. Note that 3000 is the port that is typicallyconfigured for PHD use.

Configuring PHDto HistorizeInferred Values

See Section 1.3 for details on configuring PHD.



Honeywell Inc.

What ValuesNeed to beHistorized byPHD?

For each calculation that needs a bias update, the following two parameters needto be historized in PHD:

• The biased inferred value (i.e. inferred value which includes the bias);

• The bias;

Do we Historizethe Biased orUnbiasedInferred Value?

The user should configure PHD to historize the biased inferred value in user units.

What AboutEngineeringUnits?

The user should configure PHD to collect the inferred value in the same units asreturned by the lab.

So if a toolkit (such as the Fractionator or FCCU toolkit) is calculating theinferred value, then generally the parameter PHD should collect is usually calledValue_User_Units. This parameter is the biased output in user units.

Note that if the toolkit inferred calculation is unitless, for example Watson K, thenValue_TK_Units should be used, as this is the only returned value. Note that thisvalue too, is the biased value.

RetrievingCurrent InferredValues from PHD

The current inferred values are shown on the Lab Update display for operatorconvenience. These values are retrieved from PHD, and as such (depending on thePHD collection interval) may lag the actual inferred values.

User Commands From the Lab Update display the user can send several commands related to theLab Update. The list of commands are:

• Update the Sample Time.

• Trigger a calculation of the lab bias.

• Output the lab bias.

Averaging theInferred Values

It is usually desirable to calculate the bias based on the lab value and an averageof the inferred values retrieved from the history file.

As such, a parameter - AveragePeriod - is provided allowing the user toconfigure the period over which to average the retrieved inferred values.

If a sample time of time t is entered and the Averaging Period is 30 minutes, thenthe average inferred value is calculated based on history retrieved in the followingrange:

t – 15 to t + 15

For example, if the sample time is January 1, 2000 9:00am, and AveragePeriod is30 minutes, then averages will be calculated based on values from January 1, 20008:45am to 9:15am.

Common reasons for averaging include:



Honeywell Inc.

• Uncertainty relating to the sample time (i.e. sample might have reallyoccurred a few minutes later or earlier).

• Uncertainty in process deadtimes.

Lab ValueMinimum andMaximum Range

The value that is returned by the lab and entered by the user is subject to a rangecheck. The bias will not be updated and an error message will be raised if the labvalue is outside this range. The parameters that determine this range areLabValueMin and LabValueMax.

Conditioning theBias Prior toOutput.

Several configuration parameters are provided allowing the user to condition thebias prior to outputting the bias. The conditioning parameters are:

1. BiasMax - BiasMax clamps the bias such that the Bias is never greater thanBiasMax.

BiasCalc = min(BiasCalc, BiasMax)

2. BiasDeadband should be set according to the uncertainty of the lab value. Forexample, if the lab calculation is accurate to within ±2 DegF for a D86 calculationthen the user should enter this as the bias deadband. Bias deadband impacts theBias by reducing the bias to a more conservative value. If the bias is within thedeadband then the bias does not change:

If BiasCalc > BiasDeadband

Then BiasCalc = BiasCalc – BiasDeadband

3. BiasMult is the bias multiplier. This parameter allows the user to skew thebias. This multiplier is applied prior to applying the digital filter.

BiasCalc = BiasMult * BiasCalc

4. BiasFilterCoeff is a digital filter coefficient that updates the bias based on theprevious bias. The coefficient must be a value between zero and one. It impactsthe bias as follows:

BiasCalc = (BiasCalc * BiasFilterCoeff) + BiasAverage (1 – BiasFilterCoeff)

Note that if BiasFilterCoeff = 1, then the old bias does not have any impact on thebias calculation.

Note that BiasAverage is the average bias value around the sample time.

Bias Output The final biases are stored in the Bias array. Each Bias parameter in the Bias arraymust be output to the bias parameter of the inferred function requiring update.

This connection is done via the Profit Design Studio – Profit Toolkit RunTimeConfiguration. For toolkit applications such as Fractionator and FCCU toolkit, theLab Update Bias should be connected via OPC to the Bias parameter of the toolkitfunction.



Honeywell Inc.

The External Custom Variable connection shown in the following diagram showsthe Lab Update Bias parameter connected via OPC to theRVP1\Added_Bias_Raw in the FRAC1 Fractionator application.

Note: Be sure to connect the Bias output parameter, not the Bias input parameter.

Section 1 - Lab Update1.2 Detailed Description


Honeywell Inc.

1.2 Detailed DescriptionCalculationAlgorithm

The following diagram shows the algorithm used by Lab Update to update thebias corresponding to an inferred value. Note that the file storage diagram shownbelow is for conceptual purposes only and is not representative of how PHDactually stores data.

PHD Returnsaverage ofseveral “rows”of data

Request Datafrom PHD

PHD Writes Datato Database

Lab Update

User triggers Update of Bias

Bias = BiasCalc if BiasMode=CALC

Bias = BiasCalc if BiasMode=USER

PHD

Values Returned from Lab.

User Enters the Lab Value.

Retrieve history values for the

Inferred value for a given time

range which is based on the

Sample Time , Averaging Period

and Deadtime

Calculate Average of Inferred

Values

Calculate Bias by subtracting the

average inferred value from the

lab value

When sample is taken, user

Triggers Update of Sample Time

Condition the bias

TAGNAME1 TAGNAME2 TAGNAME3BPD DEG F PSIG06-11-99 06-11-99 06-11-991003.43 54.41 210.00 11:00:081003.43 54.03 210.00 11:00:381003.43 53.99 210.00 11:01:081003.43 53.57 210.00 11:01:38



Honeywell Inc.

Input table The input table provides a description of the function inputs.

Input TableInput[ ] denotes array

Source Only Req’d if Eng. Units Description

Description String Description of the Lab Update Function.

e.g. “Fractionator #1 Lab Update”

Comment String Operator comment associated with the Lab Update.

MinConfidence Minimum confidence required for PHD averagecalculation.

PHD is responsible for the average inferred valuecalculation. PHD will calculate an average even ifthere are uncertain values over the time period usedfor its average calculation. When doing this PHDoutputs the average with a reduced confidence.

This parameter is the user setting for the minimumacceptable confidence for the average value returnedby PHD. Generally this value should be set high to 70,80 or 90. This vaguely means that 70, 80 or 90percent of the raw values used in the averagecalculation are reasonable values.

ConnectionType For future use only.

Currently only PHD is supported, however in thefuture other connection types are envisioned.

ConnectionString String The connection string to connect to the historymechanism.

If ConnectionType = 1 (PHD) then

ConnectionString = “HOSTNAME/3000”

Where HOSTNAME is the name of the host machinewhere the PHD data is being stored.

And 3000 is the port number typically used with PHD.

ConnectionNumber For future use only.

ConnectionStatus Connection status, 0 = Not Connected, 1 = Connected

InNum Total number of inferred values that require a lab biasupdate.

Note that this parameter must be configured duringProfit Design Studio, Profit Toolkit DesignConfiguration.

InName[ ] InNum > 0 String PHD Tag name of the historized biased inferred valuein user units. (i.e. the inferred value should includethe bias).

History data will be retrieved from PHD based on this



Honeywell Inc.



tagname.

The tag name that applies will typically be the sameas the inferred value toolkit variable name since byconvention PHD history tagnames are typically namedthe same as the values they are collecting.

For example: RVP1\VALUE_USER_UNITS

InName can be a maximum of 32 characters long (thisis the maximum tag length PHD supports. This valueis not case sensitive).

Note that Embedded PHD tags are valid.

InBiasTagName [ ] InNum > 0 String PHD Tag name of the historized bias value.

History data will be retrieved from PHD based on thistagname.

The tag name that applies will typically be the sameas the bias toolkit variable name since by conventionPHD history tagnames are typically named the sameas the values they are collecting.

For example: RVP1\Added_Bias_Shift

Note that when the inferred value is coming from aProfit Toolkit, and the bias is filtered then the usershould collect the filtered bias (Added_Bias_Shift)rather than the raw bias (Added_Bias_Raw).

InBiasTagName can be a maximum of 32 characterslong (this is the maximum tag length PHD supports.This value is not case sensitive).

Note that Embedded PHD tags are valid.

InTagNo[ ] InNum > 0 PHD Tag Number for inferred value.

Internal tag number that corresponds to InName.Allows for quicker retrieval of PHD tag.

User should not enter this value, it is set automaticallyby Lab Update.

InBiasTagNo[ ] InNum > 0 PHD Tag Number for bias value.

Internal tag number that corresponds toInBiasTagName. Allows for quicker retrieval of PHDtag.

User should not enter this value, it is set automaticallyby Lab Update.

InDesc [ ] InNum > 0 String Array of descriptions corresponding to each of theinputs. It is required that the user fills in thedescription, as this is what the operator sees on theLab Update operating display.



Honeywell Inc.



InUnits[ ] InNum > 0 String Array of engineering units corresponding to each ofthe inputs.

Command[ ] InNum > 0 Array of commands relating to updating the biasvalue.

Valid commands are:

0 – No command.

1 – Calculate the bias (BiasCalc) value.

2 – Output Bias.

3 – Set the sample date/time to the current time.

LabValue[ ] InNum > 0 Array of lab values.

Value is the value that is returned by the lab andentered by the operator following completion of the labtest.

LabValueMin[ ] InNum > 0 Array of minimum permissible lab values.

The bias will not be updated if the value returned bythe lab is less than LabValueMin.

If LabValueMin is set to NaN then this check is notperformed.

LabValueMax[ ] InNum > 0 Array of maximum permissible lab values.

The bias will not be updated if the value returned bythe lab is greater than LabValueMax.

If LabValueMax is set to NaN then this check is notperformed.

LabDeadtime[ ] InNum > 0 Minutes Array of deadtime values between the process andthe sample point.

LabSampleDateTime[ ]

InNum > 0 Date/TimeString

Array of date/times indicating when the lab samplewas taken.

This value should be entered in the following format:

dd-mmm-yyyy HH:MM:SS

e.g. 19-Mar-2000 20:51:30

AveragePeriod[ ] InNum > 0 Minutes The number of minutes that the historized inferredvalue should be averaged over.

AveragePeriod must be a positive value.

For example, if 30 minutes is entered, and theLabSampleTime is 10:00am then the bias iscalculated based on the average value of thehistorized inferred values from 9:45am to 10:15am.

InferredValue[ ] InNum > 0 Array of current biased inferred values.

These values are automatically retrieved from PHD.



Honeywell Inc.



The user should not connect these values.

InferredValueAverage [ ]

InNum > 0 Array of average inferred values.

These values are automatically updated after beingretrieved from PHD.


Bias[ ] InNum > 0 Array of bias values to output.

BiasCalc[ ] InNum > 0 Array of calculated lab biases. These are calculatedafter the lab sample value is entered.

The user may choose not to output this bias.

BiasDelta[ ] InNum > 0 The change in bias between last bias and currentbias, for information only.

BiasMax[ ] InNum > 0 Array of maximum bias values permitted. The bias willbe clamped to BiasMax if the bias is greater thanBiasMax.

BiasMax must be a positive value.

If BiasMax is set to NaN then the bias will not beclamped.

BiasDeadband[ ] InNum > 0 Array of deadband values associated with the valuereturned by the lab. This is effectively the uncertaintyof the lab value in absolute units.

The BiasDeadband cannot be greater than themaximum bias BiasMax.

E.g. A lab value for flash point may have anuncertainty of 2 DegF.

BiasFilterCoeff[ ] InNum > 0 Array of digital filter coefficients.

BiasFilterCoeff must be greater than zero less than orequal to one.

Impacts the bias as follows:

BiasCalc = BiasCalc * BiasFilterCoeff – BiasOld(1 –BiasFilterCoeff)

BiasMult[ ] InNum > 0 Array of bias multiplier. This multiplier is appliedagainst the bias.

BiasAverage [ ] InNum > 0 Array of average bias values.

These values are automatically updated after beingretrieved from PHD.


LabState[ ] InNum > 0 For future use only.



Honeywell Inc.



BiasState[ ] InNum > 0 Bias state is a flag which allows the user to turn asingle bias calculation on or off.

0=OFF

1=ON

Note: When BiasState is set to OFF for a bias, nocalculations or validations are done for the bias.

CommandMessage[ ]

String InNum > 0 Message that is returned after a command failure.

LastConnectionString

String Saved ConnectionString - do not configure thisparameter

LastConnectionNumber

String For future use only.

RetNum The maximum number of simultaneous messages tobe raised for this function.

The default value setting is 15. It is recommended thatthis value not be changed.

Note that this parameter must be configured duringProfit Toolkit Design Configuration.



Honeywell Inc.

Output table The output table provides a description of the function outputs.

Output Table

Output Eng.Units

Description

Ret_Status Number of error messages.

This sign (i.e. positive, negative) of Ret_Status also controls the coloring of thefunction error status.

Red = positive = at least one error message is displayed.

Yellow = negative = There are only warning message(s).

RetStatus[ ] Array of current function return statuses. See Return Status Table below for details.

RetMessage[ ] String Array of messages containing the current set of error messages raised against thefunction.

RetFloat[ ] Array of float arguments associated with error messages. For internal use only.

RetString[ ] String Array of string arguments associated with error messages. For internal use only.

LastConnectionString String Saved ConnectionString - do not configure this parameter

LastConnectionNumber String For future use only.

ConnectionStatus Connection status, 0 = Not Connected, 1 = Connected

InTagNo [ ] PHD Tag Number for inferred value.

Internal tag number that corresponds to InName. Allows for quicker retrieval of PHDtag.

User should not enter this value, it is set automatically by Lab Update.

InBiasTagNo[ ] PHD Tag Number for bias value.

Internal tag number that corresponds to InBiasTagName. Allows for quicker retrievalof PHD tag.

User should not enter this value, it is set automatically by Lab Update.

InRowError[ ] Array of values which indicate whether a corresponding row has no errors/warnings,an error, or a warning.

This value is positive if the row has an error.

This value is negative if the highest priority is a warning.

This value is zero if the row has no errors/warnings.

Bias[ ] Array of final absolute bias values that need to be connected to bias value that needsupdating.

BiasDelta[ ] The change in bias between last bias and current bias, for information only.

BiasCalc[ ] The calculated lab bias for the corresponding input.

Command[ ] Array of bias commands. Once the Command has been acted upon by Lab Update,then Command is set to zero.

InferredValue[ ] Array of current inferred values.



Honeywell Inc.

Output Table

Output Eng.Units

Description

InferredValueAverage[ ] Array of average inferred values. This value is updated whenever the user requeststhe average value to be calculated, or when a lab update command is given.

BiasAverage [ ] Array of average bias values. These values are automatically updated after beingretrieved from PHD. The user should not connect these values.

LabSampleDateTime [ ] Stringdate/time

Array of date/times indicating when the lab sample was taken.

CommandMessage[ ] String Message that is returned after a command failure.

LabState [ ] String For future use only.

Return Status Table Shows the error and warning messages associated with the function.

Return Status

Statusvalue

Description

• nn designates the row in which the error occurred

• ______ designates the inferred value which is being biased

0 No error occurred.

1 The PHD tagname for ___ (parameter – InBiasTagName\ nn) is too long. Must be less than 32 characters.

2 Error- The PHD tagname for ___ (parameter – InName\nn) is too long. Must be less than 32 characters.

3 Error- Command for ___ (row nn) is out of range. Command must be 1, 2 or 3.

4 Error- Lab Sample Date Time for ___ (row nn) is an improper format. Proper format is e.g. 19-Mar-2000 20:51:30.

5 Error - Maximum lab value (LabValueMax) for ___ (row nn) must be greater than the minimum lab value.

6 Error - The averaging period (AveragePeriod) for ___ (row nn) is a bad value.

7 Error - The averaging period (AveragePeriod) for ___ (row nn) is too small. Averaging Period must be > 0.

8 Error - The maximum bias value (BiasMax) for ___ (row nn) is too small. The maximum bias must be > 0.

9 Error - The bias deadband (BiasDeadband) for ___ (row nn) is too small. The bias deadband must be > 0.

10 Error - The filter coefficient (BiasFilterCoeff) for ___ (row nn) must be > 0 and <= 1.

11 Error - The filter coefficient (BiasFilterCoeff) for ___ (row nn) is a bad value.

12 Error - The deadband (BiasDeadband) for ___ (row nn) is greater than the maximum bias.

13 Error - The bias multiplier (BiasMult) for ___ (row nn) is a bad value.

14 Error - Fix errors associated with ___ (row nn) then repeat the request.

15 Error - Connect to PHD then repeat the request for ___ (row nn).

16 Error - Minimum confidence is a bad value.



Honeywell Inc.

Return Status

Statusvalue

Description

• nn designates the row in which the error occurred

• ______ designates the inferred value which is being biased

17 Error - Minimum confidence is out of range. Minimum confidence must be > 0 and <= 100.

18 Error - Parameter ___ for row nn is blank.

19 The bias state (BiasState) for ___ (row nn) is a bad value

20 The bias state (BiasState) for ___ (row nn) must be either 0 or 1

21 Error - PHD Error is: ___.

22 Error - PHD Tag - ___ - in row nn cannot be found in history database.

23 Error - If tags have recently been added or modified in history, then restart this toolkit.

24 Error - Attempting to connect to PHD. See associated message for PHD return status from phd_sethost function.

25 Error - Attempting to get history data from PHD. See associated message for PHD return status from phd_getdatafunction.

26 Error - Attempting to get tag numbers from PHD. See associated message for PHD return status from phd_genlistfunction.

27 Error - Attempting to get current values from PHD. See associated message for PHD return status fromphd_getlist function.

28 Error - Unsuitable data type retrieved from PHD for ___ (row nn), must be numeric data type.

Section 1 - Lab UpdateConfiguring PHD for Lab Update History Collection


Honeywell Inc.

1.3 Configuring PHD for Lab Update History Collection

What ParametersNeed to beHistorized

Remember, for each inferred value requiring a bias update, two values need tohistorized in PHD, the biased inferred value and the bias.

Considering that the Lab Update function biases inferred values based on labvalues entered in user units, the value that needs to be historized in PHD is thebiased inferred value in user units.

If the inferred value is collected from the Fractionator or FCCU toolkit, then theparameter is typically called ToolkitFunctionAliasName\Value_User_Units.Where ToolkitFunctionAliasName is the name of the Fractionator or FCCU toolkitfunction.

An example of this is RVP1\ Value_User_Units.

The bias that needs to be collected is typically called Added_Bias_Shift if the biasis filtered.

Section 1 - Lab UpdateConfiguring Embedded PHD for Lab Update History Collection


Honeywell Inc.

1.4 Configuring Embedded PHD for Lab Update HistoryCollection

Embedded PHDConfiguration

Configuring Embedded PHD for Lab Update history collection is much simplerthan configuring Oracle Based PHD because a History Builder tool (shownbelow) is provided with all Profit Toolkit, Controller and Optimizer products. Thistool allows a user to configure any Toolkit, Controller and Optimizer parametersfor history collection.

How to Find theEmbedded PHDTagName

In order for Lab Update to collect history it needs to know (via the InName andInBiasTagName parameters) the PHD tagnames which contain the history data.

The tagnames can be found in the Embedded PHD history configuration file. Thisfile is built when Build is selected in the History Builder. Once the file is built,open the file (*.csv), and the PHD tagnames are shown under the first columncalled “TagName”. Another way of determining the tagname is to look it up usingthe Profit Tag Explorer provided with all Profit applications.

Note that in some cases the History Builder will truncate the tagname because itexceeds the maximum tagname length of 32 characters.

Section 1 - Lab Update1.4 Configuring Oracle Based PHD for Lab Update History Collection


Honeywell Inc.

1.4 Configuring Oracle Based PHD for Lab Update HistoryCollection

RecommendedPHD TagNamingConvention

It is generally recommended that as a convention - the PHD tag names match theparameter names of the values that PHD is collecting. For example, if updating aReid Vapor Pressure function from the Fractionator toolkit then the PHD tag wouldbe named something like RVP1\Value_User_Units.

Similarly, the bias tag might be named RVP1\Added_Bias_Shift. Note that PHDtags are limited to 32 characters, so in some cases the name may have to beshortened.

OPC RDIConfiguration

If PHD is collecting history from a Profit Toolkit (such as Fractionator or FCCUToolkit), Profit Controller or Profit Optimizer application then an OPC RDI needsto be configured. The reason for this is that Profit Toolkit, Controller andOptimizer are all OPC applications.

See your PHD document “OLE for Process Control RDI Functional Specification”for more details on setting up an OPC RDI.

The following section in this document describes a summary of the steps requiredto complete an OPC RDI configuration.

The basic parameters associated with configuring an OPC RDI are to specify thename of the application where the data resides. The user also needs to specifySCANTIME, rather than POLL.

Summary ofOPC RDIConfigurationSteps

The steps required to configure an OPC RDI are summarized as follows:

1. Use the PHD RDI Specification form to enter Configuration information forthe OPC RDI.

2. Run RDI_Services.exe to complete the configuration.

Using the PHDRDISpecificationform toConfigure theOPC RDI

If configuring the OPC RDI via the PHD RDI Specification form, then theparameters should be configured as shown in the associated diagram.



Honeywell Inc.

Note the following details:

OPC SERVER should be configured with an “HCI” preceding the toolkitapplication name. For example HCI.FRAC1

MACHINE NAME should be left blank if the same as the HOST NAME.

Important Noteon OPC RDIConfiguration

A separate OPC RDI is required for each Profit Toolkit Application that PHD iscommunicating with. If, for example, a user has two Profit Toolkit applications –one Fractionator application (called FRAC1) and one FCCU application (calledFCCU1), and history needs to be collected from both applications, then two OPCRDIs need to be setup.

Note that the OPC SERVER names for these applications are HCI.FRAC1 andHCI.FCCU1.

Important Note:OPC RDIs willAutomaticallyLaunch ProfitToolkitApplication

If PHD has an OPC RDI connection to a Profit Toolkit application then PHD via itsOPC RDI will continually try to launch the Profit Toolkit application after theProfit Toolkit application has been killed. This can result in a sort of chicken andegg application that makes it difficult to restart the Profit Toolkit application from aclean (i.e Null) checkpoint as the old checkpoint files are read back in each time.

The best method to restart from a clean checkpoint - without stopping PHD - is toexecute the following steps:

• First delete the checkpoint files (.cpt and .cpt.bu)

• Then terminate the Profit Toolkit application.

• PHD will automatically restart the Profit Toolkit application.

ConfiguringTags in PHD

This section details PHD Tag Configuration for the inferred values to be historizedby PHD.

Sample TagConfiguration

The diagram on the following page shows a sample Tag Configuration for PHDhistorizing inferred values from a Profit Toolkit application such as Fractionator orFCCU toolkit. As mentioned earlier for Profit Toolkit applications PHD collectsthe data via an OPC RDI.

Note that the key fields for configuring PHD to collect data from a Profit Toolkitvia OPC are:

• COLLECTION – Set to ENABLE.

• SOURCE TAG SPEC – this is the name of the Profit Toolkit variable, this isgenerally the ToolkitFunctionAlias\parameter name,

e.g. RVP1\Toolkit_User_Units. Note that it is a good convention for the PHDTagname and SOURCE TAG SPEC to be identical.

• SYSTEM TYPE – Set to OPC if inferred values are being collected from aProfit Toolkit such as Fractionator or FCCU Toolkit.

• TAG TYPE – If OPC is the SYSTEM TYPE, then set the Tag Type to F4 - for



Honeywell Inc.

four-byte float.

• COLLECTOR NAME – Set to the name of the OPC RDI of the Toolkitapplication that PHD is collecting the data from (e.g. OPCRDI_1). Note thateach Profit Toolkit application requires its own OPC RDI.

• SCAN SECONDS – Recommended value is 30 seconds. However if the userrequires faster viewing of inferred values on Lab Update display, then aquicker scan time can be chosen.

• SCALE Hi/Lo Extreme – Specify a wide range (for example –100000 to+100000).

• Attribute – Set this to “Value”.

• Quantum – Set to –1.

Section 1 - Lab Update1.5 Lab Update User Display


Honeywell Inc.

1.5 Lab Update User DisplayOverview The Lab Update Display allows user to view current values of lab update data and

to send lab update commands in order to update the bias of an inferred(calculated) value. The following diagram shows the Lab Update Display.

Launching the LabUpdate Display

Lab Update Display can be launched by double clicking the LabUpdate.exeexecutable from Windows Explorer. The executable can be found as follows:/Program Files/Honeywell/HiSpec Solutions/ProfitToolkit/LabUpdateToolkit/LabUpdate.exe.



Honeywell Inc.

Command LineOptions

The user can also launch the LabUpdate display with the following commandline options:

/a [LabUpdateAppName]

/f [LabUpdateFunctionName]

Where

[LabUpdateAppName] is the Lab Update application name.

[LabUpdateFunctionName] is the lab update function alias name within the LabUpdate application. The alias name is specified in the Profit Toolkit DesignConfiguration in Profit Design Studio (APCDE).

When the command line arguments (/a [LabUpdateAppName] /f[LabUpdateFunctionName]) are specified, the Lab Update display automaticallyestablishes a connection to the specified application and then displays the dataassociated with the specified function. When the command line arguments arenot specified, the user must enter these values from the Lab Update display.

Creating a Shortcutfor Launching LabUpdate

The easiest way to launch the Lab Update display is to create a shortcut. Asimple way to create the shortcut is to navigate in Windows Explorer to thefollowing directory:

ProgramFiles\Honeywell\HiSpec Solutions\ProfitToolkit\LabUpdateToolkit\LabUpdate.exe

Once in the directory right-click on the LabUpdate.Exe file then select CreateShortcut (this is standard with NT). This creates a file called Shortcut toLabUpdate.exe.

The user should then right-click on the shortcut file and select Properties. In theProperties dialog box select the Shortcut tab and add the following commandline options to the Target.

/a [LabUpdateAppName] /f [LabUpdateFunctionName]

The end-target should look similar to the following line:

ProgramFiles\Honeywell\HiSpec Solutions\LabUpdate.exe /a [LabUpdateAppName] /f [LabUpdateFunctionName]

The user should then move the shortcut to a location that is convenient for theoperator to click on (for example the desktop).

An example shortcut is:

C:\Program Files\Honeywell\HiSpec Solutions\LabUpdate.exe /a LabUpApp /f LabUpdate1

Note: Users who have several Lab Update functions should create severalshortcuts to access each Lab Update function.



Honeywell Inc.

Connecting To aLab UpdateApplication

To connect to a Lab Update application, enter in the application name on the“Connect To Application” text box and click the “Connect” button. If theapplication is not currently running, the connection request will automaticallylaunch the application; otherwise it will simply establish the connection.

The user can connect to a different Lab Update application at any time. Note thatwhen user connects to a different Lab Update application, the currentlyconnected application will be disconnected without terminating the application.

Select a LabUpdate within anapplication

Once a connection to a Lab Update application is established, the Lab Updatedisplay will automatically select the first Lab Update function within theapplication.

If the user requires another Lab Update function within the application then thismay be selected in the “Lab Update Selection” list box.

Selecting a lab update function from the list will cause the Lab Update Display todisplay the lab update data for the function. Refer to the Lab Update DataSection table below for detail description of each column on the display.

DisplayConventions

The selectable/enterable columns are indicated by a small green triangle underthe column header.

Colors: Yellow indicates a warning. Red indicates an error.

Lab Update DataSection

Refer to the Lab Update Data Section table below for detail description of eachcolumn.



Honeywell Inc.

Comment Board The comment edit box allows user to enter in any comment string. The boxshows the last comment entered. Users may use this comment board to conveyinformation relating to lab updates that may span several shifts.

Message Section The message section displays the current error/warning messages associated withthe lab update function. Warning messages are displayed in yellow and errormessages are displayed in red. The message section displays both the messageindex number in the “Msg #” column and the actual message under “Message”column.Message text shown in the message board will generally contain the row numberthat contains the warning/error.



Honeywell Inc.

Lab Update DataSection

The Lab Update Data Section contains multiple rows of data. Each row isassociated with updating a bias for a single inferred value.

Item onDisplay

View Only orSelectable

Description

Each row is associated with a different inferred calculation. The colors on the row numberindicates the current status of the row:

• If there is a warning against the row then this value will turn yellow.• If there is an error against the row then this value will turn red.• If the status is OK then this value will turn cyan.

When this cell value is selected, a window displaying configuration parameters associated withthis inferred calculation pops up. The window, as shown below, is currently set to VIEW ONLY.

# Selectable

Note: some parameters are shown in bold indicating that these parameters are NOT rowspecific parameters.



Honeywell Inc.

Item onDisplay


Description

Descrip-tion

View Only Description of the inferred value whose bias will be updated (e.g. D86 30% Point)

Units View Only Engineering units of the inferred value (in user units) whose bias will be updated (e.g. Deg C)

The date/time the sample was taken. When this cell is selected a dialog box appears showingthe current date/time.

To set the sample time to the current time the user can press ENTER.

Alternately the user can change the date/time, and then press ENTER. A calendar control isprovided to update the date.

Note that after entering the sample time the bias is not updated. Only after entering the LabValue and outputting the bias is the bias actually updated.

If the user presses CANCEL, the sample time will not be updated.

SampleTime

Selectable

The value returned by the lab. Select this entry to calculate new bias against the lab value. Ifthe user presses CANCEL, the new bias will not be calculated. After selecting Lab Value thefollowing dialog appears:

LabValue

Entry



Honeywell Inc.

Item onDisplay


Description

After the user enters the Lab Value, a dialog box is displayed requesting the user to confirm thelab value:

Selecting No will cancel the bias calculation.

Selecting Yes allows the Lab Update application to proceed with calculating the lab bias. Thisstep may take a few seconds as the Lab Update application communicates with PHD to retrievethe history information required to perform the bias calculation.

If a successful bias is calculated the following dialog appears:

The Update Bias Output shows the user the Calculated Bias and the Delta Bias. The Calculatedbias is the bias that will be output to correct (i.e. bias) the inferred value. The Delta bias is theamount by which the bias will change bias of the inferred value.

Selecting Enter will output the bias. Selecting Cancel will cancel the bias output, and the usercan start again.

AvgInferred @

SampleTime

View Only The average inferred value around the sample time. This value is retrieved from PHD.

CurInferredValue

View Only The current inferred value. Note that this value may be collected via PHD and as such may lagthe actual inferred value.

CalcBias

View Only The calculated bias (in user units). This value is updated after the Lab Value is updatedsuccessfully.

DeltaBias

View Only The delta bias. The amount that the bias will change. This value is updated after the Lab Valueis updated successfully.

BiasOutput

View Only The bias that is output.



Honeywell Inc.

AdditionalFeatures

When user right click on the Lab Update Data Section, a pop-up menu isdisplayed.

The following functionality are currently available from the pop-up menu:

1. Configuration Parameters – to bring up the Configuration Parameters displayfor the row. User can also access this display by selecting the row number.

2. Tool Tip On/Off – to turn on/off tool tip display of the data section.

3. About Lab Update – to bring up the Lab Update product information.



Honeywell Inc.

Documents

Lab Update User's Guide - Honeywell Process · 2011. 11. 14. · 5/01 Lab Update User’s Guide ix Honeywell Inc. References The following comprise the Profit Suite library. Documentation