OperTune Users Guide
OperTune Users Guide
OperTune Users Guide
Scout Suite
Scout Suite OperTune
User's Guide
OPR-R310-003
R310.1
07/10
Release R310.1
Honeywell
This work contains valuable, confidential, and proprietary information. Disclosure, use or
reproduction outside of Honeywell Inc. is prohibited except as authorized in writing. This
unpublished work is protected by the laws of the United States and other countries.
Notices and Trademarks
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 customers.
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.
Honeywell International
Process Solutions
2500 West Union Hills
Phoenix, AZ 85027
1-800 343-0228
Contacts
World Wide Web
The following Honeywell web sites may be of interest to Industry Solution customers.
Corporate http://www.honeywell.com
Telephone
Contact us by telephone at the numbers listed below.
Symbol Definitions
The following table lists those symbols used in this document to denote certain conditions.
Symbol Definition
Symbol Definition
3. APPENDIX ................................................................................... 87
3.1 Parameter Definitions ....................................................................................87
3.2 [Optional] Advanced OperTune Configuration ...........................................90
Key Configuration Steps...................................................................................................... 90
3.3 Troubleshooting ............................................................................................99
1. Error: Windows Firewall has blocked some features of this program .......................... 99
2. Error: OperTune Read conflict, the point is already in use ....................................... 100
To reset the configuration in Experion PKS system: ......................................................... 100
3. Connection issues: ........................................................................................................ 100
4. Opertune configured...................................................................................................... 101
5. When you launch OperTune you get an error message as shown in figure below: ....... 102
6. Error message – RDI Tag is not active.......................................................................... 102
7. When you launch OperTune you get an error message as shown in figure below: ....... 103
8. Not able to restart Uniformance RDI Server SE service: ............................................... 104
Figures
Figure 1 OP Step Size Selection ............................................................................... 16
Figure 2 Closed Loop Settling Time Selection .......................................................... 17
Figure 3 Point Selection Display ................................................................................ 24
Figure 4 Point Name Entry ........................................................................................ 24
Figure 5 Trend Display............................................................................................... 25
Figure 6 Pre-Tune Display ......................................................................................... 28
Figure 7 Main Display ................................................................................................ 30
Figure 8 Tuning Constants Display............................................................................ 34
Figure 9 Tuner Settings ............................................................................................. 37
Figure 10 Tuner Limits Display ................................................................................ 41
Figure 11 Current Values Display ............................................................................ 43
Figure 12 Controller Settings ................................................................................... 45
Figure 13 Controller Limits Display .......................................................................... 47
Figure 14 Results Display ........................................................................................ 49
Figure 15 OperTune short cut key from windows menu .......................................... 53
Figure 16 OperTune Splash Screen ........................................................................ 54
Figure 17 OperTune first window for tag name entry............................................... 54
Figure 18 Experion station display ........................................................................... 56
Figure 19 Experion Station – Loop Tune tab ........................................................... 57
Figure 20 Experion Station – OperTune shortcut .................................................... 58
Figure 21 ActiveX warning ....................................................................................... 58
Figure 22 Point selection Display window ................................................................ 59
Figure 23 Point name entry window ......................................................................... 60
Figure 24 LoopScout LSmetrics location ................................................................. 61
Figure 25 OperTune Trending Tool.......................................................................... 62
Figure 26 OperTune Pre Tune - Skip ....................................................................... 63
Figure 27 OperTune pre-requisites check................................................................ 65
Figure 28 OperTune Trending Tool.......................................................................... 65
Figure 29 OperTune Pre-tuning ............................................................................... 66
Figure 30 OperTune Pre-Tune - change OP size .................................................... 67
Figure 31 OperTune Pre-Tune - PV target crossing ................................................ 68
Figure 32 OperTune Pre-Tune Completion ............................................................. 69
Figure 33 OperTune main tuning form ..................................................................... 72
Figure 34 OperTune initialization successful ........................................................... 73
Figure 35 OperTune working status ......................................................................... 74
Figure 36 OperTune results display ......................................................................... 75
Figure 37 OperTune results display ......................................................................... 76
Figure 38 OperTune results display – PI only option ............................................... 78
Figure 39 OperTune Tuning solutions tab................................................................ 79
Figure 40 OperTune Tuning Constants display ....................................................... 80
Figure 41 OperTune Configurations ......................................................................... 81
Scope
The OperTune User’s Guide covers the following topics:
Acronyms
Acronyms Description
SP Set Point
PV Process Variable
OP Output
MAN Manual
Key Features
Automation
OperTune is highly automated and integrated with Experion PKS. You can read the
following configuration parameters from the system:
• Controller action
• OP operating limits
• Mode
• Filter constants
OP Excitation
OperTune automatically generates movements in the OP using a PRBS input. You do not
have to step (bump) the loop manually. You can control the excitation using OP step size,
and closed loop settling time parameters. These parameters can be changed during
OperTune operation.
Uncertainty
OperTune systematically deals with the limitations of controller performance including
disturbances, loops with non-minimum phase characteristics (delays) and unreasonable
closed loop specifications. OperTune performance is measured in terms of a fit error that
expresses all of these effects in one number. It is desirable to reach a fit error of less than
0.2.
Safety
Safety limits on the OP are configurable through OperTune. During OperTune operation
the limits are never exceeded. You can stop the tuning process at any time during the test.
Multiple Solutions
For every sampling instance, OperTune simultaneously computes ten potential solutions.
The principle of iterative refinement is used in computing the estimates. The candidate
solutions cover a wide range of settling times from twice-as-fast to five-times-slower
than the user specification. The operator can provide a reasonable estimate of the closed
loop settling time as a starting point or can let OperTune estimate it automatically.
Multiple Sessions
Using OperTune several loops can be tuned at the same time from the same console. You
can start multiple sessions of OperTune to take advantage of this feature.
Op Bias
User can use OP Bias value to give additional inputs to OP while tuning
Guidelines for choosing the OP step size change and desired closed loop settling time are
described in the following subsections.
Conceptually, the closed loop settling time defines how quickly the controller recovers
from an upset. The desired closed loop settling time is defined as the time in minutes for
the elimination of 95% of the PV error (difference between the SP and the PV) after a
setpoint change or significant disturbance. For many processes, the closed loop settling
time is roughly set to three times the dominant process time constant, if this is known. If
you are used to Lambda Tuning, this value is three times the Lambda parameter.
The Closed Loop Settling Time figure displays the selection of the closed loop settling
time for a typical loop.
Overview of Procedure
This section explains the procedures required to complete PID loop tuning using
OperTune.
Typically you will follow the general order of the steps in the following table. Detailed
instructions for each modular procedure are included in subsections of this document on
the page number shown. Other OperTune R310 documents referenced in this section can
be found on the Scout_Suite_Opertune_Document.zip that is available in loopscout
website
Complete the steps in the order given to begin working with OperTune.
Step Action Doc Ref
1 Ensure that you have met all prerequisites for OperTune. Release
Notes
2 Follow detailed instructions to successfully install Installation
OperTune R310. Guide
3 A: Starting OperTune from the Windows Start Button Section 2.3
Or Page 52
Page 55
4 Select PID Control Strategy (point) to Tune Section 2.5
Page 60
5 [Optional] Perform Open Loop Pre-Tuning Section 2.6
Page 70
7 Selecting the best tuning solution Section 2.8
Page 76
8 [Optional] Accessing Tuning Solutions Display Section 2.9
Page 79
Page 81
10 [Optional] Other Operator Operations Section 2.11
Page 85
2. Enter the required tag name that needs to be tuned. You are also allowed to start
multiple threads of the program to tune different loops simultaneously.
TIP
Tagname: The name of the control strategy. Click the
text field to type a new tagname. For Experion, the
tagname does not include the block name.
Field Description
Loop Scout analysis is Un select Loop Scout analysis is not done only when
not done you have subscribed for Loop Scout Services
Trend Display
1
2
3
4
5
6
7
8
10
11
12
13 14
Sl No Field Description
4 Confirm loop type Click on the loop type and select the appropriate
loop type from the options given in the window.
• Flow
• Pressure
• Temperature
• Level loop
5 Inform the operations You can inform the operations and get the
and get the necessary permits
necessary permits
Sl No Field Description
9 Trend Range Preset Series of buttons, appearing to the far left of each
Buttons trend Y-axis label, used to reset the trend range.
The Full button will reset the range to the full range
of the DCS point. The Auto button will automatically
adjust the range to include all data points +/- 5% of
range.
10 Trend Range Field A text box appearing on the left side, above and
below each trend’s engineering units. These
textboxes control the displayed range for Y-axis of
each trend. Initially, these textboxes are set to the
control system-configured PV and OP ranges.
11 PV, SP, and OP The current process value, PV; setpoint, SP; and
output, OP, of the control strategy. These values are
updated from the control system once per second.
13 History Button Shows the previous tuning solutions for the loop.
Pre-Tune Display
The Pre-Tune Display is the main interface for OperTune pre-tuning.
12
Sl No Field Description
Sl No Field Description
5 Trend Range Field A text box appearing on the left side, above
and below each trend’s engineering units.
These textboxes control the displayed range
for Y-axis of each trend. Initially, these
textboxes are set to the control system-
configured PV and OP ranges.
9 PV, SP, and OP The current process value, PV; set point,
SP; and output, OP, of the control strategy.
These values are updated from the control
system once per second.
Sl No Field Description
Main Display
The Main Display is the primary interface during control strategy tuning. This display
contains the main control elements for starting, stopping, and monitoring the tuning run.
The Main Display contains buttons to access more detailed configuration and monitoring
displays.
Error! Objects cannot be created from editing field codes.
Sl no Field Description
Sl no Field Description
Loop Scout data.
5 Select Desired Closed Textbox for entering the desired closed loop
Loop Settling Time Field setting time for the control strategy, expressed in
minutes. OperTune uses this setting to optimize
default = 1 min the response of the PID strategy. If the desired
Auto and fixed options closed loop settling time is too fast for the
process, OperTune will automatically select a
default = Auto slower response depending upon a series of
convergence criteria. If the pre-tune test step is
performed, the desired settling time is filled in
with the result of the pre-tune analysis. Once the
tuning process starts user cannot change this
value.
Sl no Field Description
Button OperTune is tuning, the button is relabeled Stop,
allowing you to stop tuning. Stopping the run,
voids any results.
12 Loop Scout If you are using Loop Scout, four key loop
Metricsection (optional) performance metrics are displayed in this
section, as determined by the last execution of
• Loop Scout Loop Scout. If Loop Scout is not used, these
analysis done on fields are not populated with values.
• Performance
• Criticality
• Valve Stiction
ATTENTION
Trend Range Preset Buttons, Trend Range Field, Trend Time Buttons are
identical to the fields found on the Pre-tune Display. Refer to the
descriptions in Pre-Tune Display section for more details.
16 Loop Type Indicator Label shown in the lower left corner of the
Controller frame, shown as Flow Loop in Figure
7. This indicator displays the inferred loop type
for the control strategy (Flow, Pressure,
Temperature, Level, or Other). The inferred loop
type can be used to restrict the range of tuning
constants calculated; however by default
OperTune uses a wide range for the tuning
32 Scout Suite OperTune User's Guide R310.1
Honeywell 07/10
2. Working with OperTune
2.2. OperTune Displays
Sl no Field Description
constant calculations.
19 Point Details Button Button used to access the control system Point
Detail display.
ATTENTION
If you Exit the OperTune Main Display at any time during any procedure
or while using other OperTune screens, the application will quit and
your data will not be retained.
1
2
3
5
6
7
8
9
10
11
12
13
14
15
Sl no Field Description
3 Current DCS Tuning The current values for the PID gain, integral time,
Constants section and derivative time as read from the control
system. The Tf (filter) value is the filter time
associated with the PV filter.
4 OperTune Calculated The current values for the PID gain, integral time,
Tuning Constants and derivative time as read from the Internal
OperTune Controller
Sl no Field Description
data.
7 Closed Loop Settling Column of ten fields showing the settling times
Time column for which the PID parameters are being
optimized, for each of the ten candidate
solutions.
11 Td (derivative or rate) Displays the working PID rate in minutes for each
column of the ten indicated OperTune analysis results.
14 Stop OperTune and This button becomes active as soon as the first of
Take Successful ten candidate solutions reaches a Complete
Solutions Button status. When clicked, this action stops OperTune
analysis and invokes the OperTune Results
display.
Sl no Field Description
TIP
OperTune analysis for five-times-longer than the Desired Closed Loop
Settling Time can take an extended amount to time to complete. You can
use this button to stop OperTune sooner and work with available solutions.
Configurations Window
The Configuration Window is displayed when you click the Configurations button in
the Main display window. Configuration window consists of five tabs
Tuner Settings
In the Configurations window, click the Tuner Setting tab.
1
2
3
4
5
6
7
8
9
10
11
TIP
In general fields that are displayed with a gray background are Read-
Only. Fields that are displayed with a white background accept input.
Sl no Field Description
Sl no Field Description
Value Meaning
Sl no Field Description
5 Desired Settling Textbox for entering the desired closed loop setting time
Time for the control strategy, expressed in minutes.
OperTune uses this setting to optimize the response of
default = 1 min the PID strategy. If the desired closed loop settling time
is too fast for the process, OperTune will automatically
select a slower response depending upon a series of
convergence criteria. If the pre-tune test step is
performed, the desired settling time is filled in with the
result of the pre-tune analysis. Same as Desired
Settling Time field on Main Display.
Tuner Limits
In the Configurations window, click the Tuner Limits tab.
Sl no Field Description
Sl no Field Description
5 OP High Limit / OP OP high and low limits used to clamp the output.
Low Limit Values These values can be adjusted to limit the range of
OP movement from OperTune. Changes to these
defaults = DCS OP limits values do not change the DCS OP limits.
Current Values
In the Configurations window, Click Current Values tab.
1
2
3
Sl no Field Description
Controller Settings
In the Configurations window, click the Controller Setting tab.
1
2
Sl no Field Description
Sl no Field Description
Value Meaning
5 Control Action PID control action as read from the control system. This
value is displayed as 1 if control action is Reverse and
displayed as 0 if set to Direct. This value is read-only.
Controller Limits
In the Configurations window, click the Controller Limits tab.
Sl no Field Description
2 PV HIGH Alarm / PV PV high and low cutoff values for closed loop
LOW Alarm control. If during the course of a closed loop test,
the PV exceeds the PV cutoff value, the OP
default = DCS limits excitation signal is temporarily halted and the OP
is programmatically moved by OperTune to bring
the PV back within bounds. Once the violation is
cleared (by more than the deadband), the
excitation signal is restarted.
Results Display
The OperTune Results Display shows the final result of the tuning run. It displays
automatically on completion of the OperTune tuning run.
TIP
OperTune will find the lowest error solution and change the
background color to green. This solution will appear first, but can be
found again by looking for the green background.
Sl no Field Description
1 Current DCS Tuning The current values for the PID gain, integral time,
Constants section and derivative time is as read from the control
system. The Tf (filter) value is the filter time
associated with the PV filter.
5 Closed Loop Settling Displays the resultant settling time for which the PID
Time parameters are being optimized.
8 Ti (integral or reset) Displays the working PID reset time for the currently
displayed OperTune analysis result.
9 Td (derivative or rate) Displays the working PID rate for the currently
displayed OperTune analysis result.
11 Result Indicator Lever Located near the bottom of the display, this lever
indicates which of tuning results for different closed
loop response times is displayed in the Results
display. Clicking the indicators to the left reveals the
results for faster control (smaller closed loop settling
time) and clicking to the right displays results for
slower control. Initial results default to the solution
with the user-entered settling time. While OperTune
may converge for a fast settling time, the result, when
implemented, may have an undesirable amount of
overshoot. Using a resultant solution with a slower
control interval eliminates this overshoot.
12 Faster / Slower Buttons Method of selecting faster or slower results to the left
or right by one speed interval.
13 SP Change response The tuning plot at the bottom left displays the
plot response of the loop when there is a change in the
set point.
14 Load change response The tuning plot at the lower right displays the
plot response of the loop when there is a change in load.
After prerequisite steps are complete (You can refer OperTune Quick start Guide for pre-
requisite steps), perform the following steps to start the OperTune application from the
windows Start button menu.
Step Action
1 Set the desired controller mode on the DCS to Manual and Mode Attribute to
Program before starting OperTune. (OperTune will post a warning
otherwise).
Step Action
The Scout Suite OperTune splash screen is displayed for a few seconds.
After prerequisite steps are complete (You can refer OperTune Quick Start Guide in Help
for pre-requisite steps). Perform the following steps to Start OperTune application from a
specific Experion PID Point Detail display.
Step Action
1 Ensure the control system Mode is set to Manual and Mode Attribute is set to
Program before starting OperTune. OperTune will present a warning
message and will not start unless the mode is correct.
The specific Experion PID Point Detail display for the point appears.
Step Action
Step Action
3 Click the OperTune button to start the automatic loop tuner for this point.
Step Action
1 After starting OperTune from the Windows Start button, Scout Suite OperTune
R310-Select Tagname display appears, the tag name text box indicates.
Please key in the controller name
When starting OperTune from the Experion PID Point Detail display, the tag
name should be displayed in the text box.
Step Action
Use the Select LSMetrics.xml button to select the Loop Scout information file if
you have moved this file to this station – otherwise select OK.
Step Action
3 In this step all the Tuning Pre-requisites are checked and clamping values for
PV & OP are entered.
After all the conditions are passed, Click Next to proceed to OperTune PreTune
Display.
Step Action
4 In this step you choose to pre-tune the loop in open loop mode or skip this step
and proceed to OperTune's main display to execute the automated closed loop
tuning sequence. Choose either A or B.
A. Jump right to tuning. Use skip button to Jump to tuning. OperTune starts
tuning with default values.
Or
B. Use the pre-Tune function to estimate the settling time and OP move size.
Perform this option if you want to use OperTune in open loop mode to
perform a pre-tuning step and let the loop tuner recommend the initial
values to use for desired closed loop settling time and percent OP move
during closed loop tuning.
Step Action
2 In this step all the Tuning Pre-requisites are checked and clamping values for
PV & OP are entered. After all the conditions are passed, Click Next to
proceed to OperTune Pre-Tune Display. PV, OP & SP values are updated
from the control system.
Step Action
4 The current PV is displayed in the lower trend, which also includes the current
PV High and PV/Low limits displayed as upper and lower control limits. The
noise band around the current PV is shown in the trend.
5 The current OP is trended in the upper trend display, and the values shown in
the Controller section on the right are read from the current values on the
control system.
Step Action
6 Select the change OP size by text box and enter the value. Using increase
or decrease button to add the percentage input to the OP value. The
percentage value will be added or subtracted from the current OP value.
It is recommended that you make slight changes, one increment at a time and
wait for the response to settle.
When the PV High target is exceeded, then the text box is highlighted by a
green color.
Step Action
7 Based on the OP value, the PV value oscillates between low or high targets.
When the PV value is above the PV target high then, the PV target high box
is highlighted by a green color .
Step Action
8 After both the PV High and PV Low targets are exceeded and PV is brought
back within the PV High & Low targets, OperTune automatically moves to
Scout Suite OperTune 310 tuning display.
ATTENTION
• The DCS point must be in MAN, and if it is a Honeywell controller the
MODE ATTRIBUTE must be in PROGRAM for OperTune to work.
Step Action
TIP
Some basic rules of thumb:
• Flow loops should usually use a closed loop settling time of under 3 mins
Note: PI is the default, but PID may allow faster tuning and OperTune will
usually calculate a very small D component.
CAUTION
Step Action
ATTENTION
OperTune will read in the OPHI and OPLO limits from the controller. To
constrain the OperTune OP moves to a specific range refer to page 42 and
look for OP High Limit / OP Low Limit Values. Changing these values will
ensure that OperTune never moves the OP beyond these limits. Changes to
the limits here are not written down to the DCS.
ATTENTION
1 The OP moves and desired closed loop settling time are initialized from the
pre-Tune step, or from Loop Scout, or from defaults. You can change either
or both of these values before the tuning starts.
To begin automated PID loop tuning, from the OperTune Main Display, click
Start OperTune.
Step Action
2 As the OperTune tuning sequence is executed, you can read the status bar
displayed in the lower left corner of the OperTune Main Display to monitor
OperTune’s progress. A short initialization period begins where the future OP
bias moves are displayed as a flat line.
When the initialization period is complete, this status is displayed in the status
bar: Initialization Successful.
ATTENTION
If you want to change OperTune’s mode to MAN to run in open loop, it is
recommended to do so before OperTune has started. Complete this change
from the Configuration Details Display, if desired.
Step Action
The future values show a PRBS signal as soon as the initialization period is
completed. The future OP bias value plot shows the future PRBS signal which
gets added to the control OP signal.
NOTE: OperTune can be configured to fix the settling time (radio button) so
that the re-calculation and re-initialization does not occur.
Step Action
TIP
To adjust the trajectory of the PV or change the limits while tuning, refer to
Section 2.10,
6 After the tuning is successful, the Scout Suite OperTune R310 Results
window is displayed. Click <<Faster or Slower>> to select the required tuning
constant.
7 Select the required result, and click Send Selected Tuning to Controller to get
the selected result to your system. For information on how to pick the best
solution refer to 2.8 Selecting the best tuning solution.
If you click away from the suggested solution, the green background changes to grey
OperTune does not offer the ability to manipulate tuning constants once the solution is
complete because any change affects the response of the system, and ultimately the
robustness.
In most cases you should be able to pick the recommended solution from OperTune and
use it directly. Ensure you take care of the operational conditions and configurations
considered if the tuning is much more or much less aggressive than the original values.
Special care should be taken with level loops if the objective of the loop is regulatory.
OperTune by default picks a slower settling time in an attempt to smooth the flow out of
the vessel. If the level loop objective is regulatory, consider carefully whether a faster
settling time is required or not. Refer to the TIP- Some basic rules of thumb in Execute
OperTune’s Automated Tuning Sequence section on page 71 for more tips and
explanations.
Filtering
Tuning constants are calculated with the filter in place. If the PV filter has a lag that is
“slow” relative to the desired closed-loop settling time it will affect solutions. Typically
the filter lag should be 1/90 to 1/120 times the settling time. In OperTune the suggested
filter lag is the higher of 0.05 min or 1/90*settling time. So if the chosen settling time is 1
min the recommended filter would be 0.05 min and if the chosen settling time is 9
minutes the recommended filter would be 0.1 minutes. The value of the current filter
overrides this calculation as long as it is greater than 0.05. If the filter is in an upstream
device and if you know the value of the filter lag you can manually enter it in the
configuration page. And Yes, if there is NO filter the “calculated/recommended” filter is
incorporated in the dynamics calculated for tuning.
Generally it is best to implement the filter as recommended by OperTune directly on the
controller point if filtering is available with the controller algorithm (controller algorithm
and hardware dependent).
NOTE: Filter constants are not written automatically to the DCS. The user has to
configure filter constants manually.
1 From the OperTune Results Display, click the appropriate button to send the
result down to the DCS. If the controller type selected was PI – then PI Only
selection will be enabled.
If the controller type selected was PID, then both buttons will be enabled.
Note: Usually if PID is selected the D (T2) component is usually small enough
that you can download only PI to the controller if desired, however care must be
taken to understand the loop type and desired operational characteristics. Refer
to the TIP- Some basic rules of thumb in Execute OperTune’s Automated
Tuning Sequence section on page 71 for more tips and explanations.
2 The Scout Suite R310 Tuning Constants window appears. It displays the 10
sets of tuning constants and updates as OperTune performs the analysis.
TIP
If OperTune has converged for one or more solutions the ‘Stop OperTune and
take successful solutions’ button will be enabled. The user can then stop the
tuning and select the successful solution(s) immediately.
3 After tuning is complete, Tuning Solutions button on the tuning form will show
the Scout Suite R310 Tuning Constants window and the Scout Suite R310
Results window, when it was closed prematurely.
2 From the Configurations display, you can view the current configuration
settings for the different tabs of OperTune.
In the required tab you can click any of the non-read-only text boxes to
change the value.
1 Select the OP Bias text box and enter the value. The percentage value will be
added or subtracted from the current OP value.
Step Action
2 Type the PV value, and click OK. This changes the PV High/Low limit as per
the selection.
Note: The SP can also be changed from the tuning options page on page 37
Stop Command
This option is used to stop the tuning in progress. You can use this option when you want
to stop the current tuning process.
Click Stop to stop the tuning process as shown in the figure.
2 For example, if you chose to click Full, then the trend maximum and
minimum values are set to high and low limits of OP/PV for respective OP
and PV trends. If you chose to click Auto, then the trend maximum and
minimum values are set to Max + 5% of the range and Min - 5% of the range.
3 If you want to change the value manually, then click in the text box. The High
PV Range window appears.
4 Type the high PV range in the text box and click OK. The PV values changes
as per the input.
5 Similarly the changes are done for the OP. To manually change the OP
value, click OP text box.
6 The High OP Range value window appears. Type the high OP value and
click OK.
3. Appendix
3.1 Parameter Definitions
Parameter Name Description Usage in Algorithm
Desired Closed- Provide input for the Desired This key parameter sets the
Loop Settling Closed Loop Settling Time (in expected closed-loop settling time
Time minutes). This is the desired for the PV following a step- SP
time in minutes for PV to track change. The value is equal to
a step SP change. This value three times the time constant of
should be greater than 0.2 the closed-loop system. OperTune
Min. attempts to tune a set of loops two
times faster and ten times slower
than what you have entered for
the desired closed- loop settling
time. The parameter is also used
for PRBS signal design, and
setting the duration of the test.
How much % can Operator input of the step size OP step size sets the magnitude
OperTune move for the PRBS signal. of the PRBS signal. Under open-
the OP? (OP Step loop excitation, the signal is
Size) designed to switch between
(OP0+OP step size) and (OP0-OP
step size). Under closed loop
excitation, OP calculated by the
algorithm also contains some
contribution from a PID. The PID
used is a detuned version of the
best-ranked current tuning.
Operator may change this value
during testing.
OP High Limit Operator input for the Maximum limit on the OP.
Maximum OP value. Operator may change this value
during testing.
OP Low Limit Operator input for the Minimum limit on the OP.
Minimum OP value. Operator may change this value
during testing.
Effective OP Bias Operator input for the OP bias This value can be adjusted
Value during tuning This could be
useful where the PV is drifting too
far from the SP for the operator’s
comfort. Simply enter a positive
or negative value to move the OP
up or down respectively. For
example, setting this value to 2
will result in an immediate 2%
increase to the OP while
OperTune is tuning. Similarly
setting this value to -1 will result
in an immediate decrease of 1%
to the OP. Changing this value
does not stop the tuning – the
tuner simply sees an additional
bump.
OperTune’s default
recommendation for stable plants
is based on not having overshoot.
If you can afford to allow some
overshoot and thus want to get
more aggressive tuning solutions,
then you can set the Xparameter
between two and four instead of
six.
OP signal PRBS Operator shall enter limit on PRBS is designed not to switch
minimum the minimum switching time for faster than this limit.
switching time the PRBS signal.
(mins)
Step Action
Desired Closed Loop Settling Time (Minutes) < pre-tune value >
How much % can OperTune move the OP? < pre-tune value >
Scout suite recommends using the values generated during pre-tuning for
best results.
Step Action
2 From Point Selection: Or, if you chose not to perform the pre-tune step, then
use skip button from the pre-tune tune window.
Review the default values displayed in these fields to ensure they are
reasonable.
Step Action
Step Action
OperTune Mode – A
Configure in open mode to determine tuning will be done in open loop (PRBS
signal only). AUTO configuration specifies closed loop tuning (control signal +
PRBS). Safe auto mode will put the open loop mode for initial period of time,
and then once the solution starts converging; it will be put into auto mode. In
Manual OP mode (mode =3), user has full control to execute the control
signal during tuning. If you want to change to any mode, it is recommended
to do so after starting OperTune and select the configure window and change
the mode.
Controller Type - B
Step Action
5 In Manual OP mode (Mode =3), you need to enter the OP value in the
Change OP box.
ATTENTION:
Making a change to the Controller Type during tuning is not allowed.
OperTune asks for a restart in tuning.
Step Action
6 The OP High and OP Low Limits for OperTune can be changed (these values
are not sent to the DCS). From this display. In most cases, the defaults read
from the control system are acceptable to use for the tuning sequence. – C
Step Action
OperTune can respond to the PV. By setting these limits OperTune will
change the direction of its response to keep the PV away from the alarm
limits. The user can adjust these here or on the main tuning display as
described in [Optional] Making Adjustments During Tuning on page 81.
Note: The PV HIGH Alarm and PV LOW Alarm values do not correspond to
the values by the same name on the control system. These values are the
same values as on the main tuning display as described in PV Low/High
Limits Change.
Step Action
8 To change the values in this display, click in the text box. The dialog appears,
confirming the field to be edited in the dialog title.
9 When edits to the OperTune Configuration Details Display are complete, click
OK to close the display.
3.3 Troubleshooting
1. Error: Windows Firewall has blocked some features of this program
When OperTune is launched for the first time after installation, you may receive a
message stating that Windows has blocked some features. Please choose the
appropriate check box, and then click Allow access. This will add opertune.exe
to the firewall exception list. Once OperTune.exe is added to the windows firewall
exception list, you will not receive this message in future.
If OperTune fails to do a complete shutdown then the configuration file will still
have the last tuned controller marked as being in use. OperTune will check to
ensure a point is not currently being tuned before it will successfully connect to a
controller. If this happens there will be a record in the OperTuneError.log file as
follows:
mm/dd/yyyy hh:mm:ss OperTune Read conflict, the point is already in use. RDI
name = EPKS1 [frmSelectPoint:lblPointName_Click]
If this error occurs, then use the following steps to reset the RDI configuration
XML file. This will reset the configuration and allow you to tune to work any PID
point.
3. Connection issues:
If connection issues are suspected, OperTune log files can be found in the
…\Program Files\Honeywell\Uniformance\RDIServer\LogFiles\ folder.
If the OperTune log files do not point to the problem, the data engine (RDIServer)
log files can be found in the
…\Program Files\Honeywell\Uniformance\RDIServer\SiteTemp\ folder.
For Experion systems look for RDIEPKS1.OUT
4. Opertune configured
Application path: C:\Program Files\Honeywell\Uniformance\RDIServer
OperTune Log path:
C:\ProgramFiles\Honeywell\Uniformance\RDIServer\LogFiles
OperTune Log File names: OperTuneError.log
OperTuneMessage.log
RDI log path: C:\Program Files\Honeywell\Uniformance\RDIServer\SiteTemp
RDI Log File names: RDI<DCS type>1.out ex: RDIEPKS1.OUT
Service that should run while using OperTune: UniformanceRDIServerSE
Registry information available at:
HKEY_LOCAL_MACHINE\SOFTWARE\Honeywell\OperTune
Importance of some of the registries:
Username: represents the LoopScout user name
LastRDIName: represents the DCS type last connected
DataFilePath: tuning session result upload folder
AutoselectFilterX: filters used to decide loop type from loop name
Currentversion: version of OperTune
Application name: Application name
ReInitCount: Number of times re-initialisation will happen when tuning is done in
auto mode
RDI key:
Service for RDI:
5. When you launch OperTune you get an error message as shown in figure below:
Reason:
Uniformance RDIServer SE service is stopped or not running.
Resolution:
• Start uniformanceRDIServerSE service.
• Wait for few seconds and then launch OperTune.
7. When you launch OperTune you get an error message as shown in figure below:
Reason:
When Opertune_1_0.dll does not get registered while installation, Matlab object
cannot be created and hence you get this error
Resolution:
1. Go to C:\Program Files\Honeywell\Uniformance\RDIServer
2. Locate Opertune_1_0.dll
3. Execute the following command from Start> Run as shown in the figure:
Reason:
This is an issue with the windows service. Exact reason provided by
Microsoft is:
The ServiceBase class calls the OnStop method directly from the Service
command handler that is defined in the ScDispatcherLoop of the
Advapi32.dll f ile. After 30 s econds, i f t he S cDispatcherLoop t hread i s not
ready to receive a new service command from the service control manager,
Windows Service Controller marks the service as "time out." Therefore, you
receive this error message.
Resolution:
This exception message is generated by the Operating System. Please
follow the Microsoft support link http://support.microsoft.com/kb/839174 to
resolve this problem.
TIP
Restarting the machine can be a quick work around
for the problem.
This error can occur when there is some issue in the loop or RDI service is not
running properly.
Resolution:
• Check in the station for any issue in the loop
• If OperTune is connected to the serve remotely then check DCOM
configuration.
• Check if OperTune is violating the limit of number of connection to the server
• Connect to the server via some third party OPC client to check if OperTune
only is having problem.
Reason:
This exception is generated by OperTune, when OPC server is heavily loaded,
or when the OPC server is unable to provide required data due to some other
issue
Resolution:
It is recommended not to run more than 3 instances of OperTune when this
exception is generated.
11. Error number 11021 is generated during the invoking of OperTune.
Reason:
This exception is generated when there is a security related issue between the
RDI and the OPC server, and hence, the connection cannot be established.
Resolution:
Check the OPC server (or redirection manager if used) for any issue. Invoke
Opertune when the issue is resolved and server is able to provide data
continuously. This can be tested via any third party OPC client.
Honeywell International
Process Solutions
2500 West Union Hills
Phoenix, AZ 85027