Professional Documents
Culture Documents
DeltaV Tips and Tricks - Bob Hedrick - CDI UE 2012
DeltaV Tips and Tricks - Bob Hedrick - CDI UE 2012
DeltaV Tips and Tricks - Bob Hedrick - CDI UE 2012
USERS EXCHANGE
Session Purpose
2012
USERS EXCHANGE
Page 2
2012
USERS EXCHANGE
Page 3
Control Studio
2012
USERS EXCHANGE
Page 4
Bulk Edit
2012
USERS EXCHANGE
Page 5
Bulk Edit
2012
USERS EXCHANGE
Page 6
Bulk Edit
2012
USERS EXCHANGE
In the first dialog box, you will need to browse to a location where you
want to create the format file. By default it will be the BulkEdit folder and
type in the name of your format with the .fmt extension, then click Next.
Page 7
Bulk Edit
2012
USERS EXCHANGE
In the next dialog box you first select the object type, such as Module if
the format is to be used for a module.
Then you browse for a subtype, if you were creating a format for a
class based module or modules of a particular type, simply browse to
an example of this module in the configuration database.
At this point you can select parameters in the left box, which lists
parameters in the module, and send them to the box on the right, which
will be the parameters in the format file.
NOTE: You may have to click Filter Parameters and check additional
categories to get some parameters to show up in the left box so that you
can add them.
Page 8
Bulk Edit
Page 9
2012
USERS EXCHANGE
Bulk Edit
2012
USERS EXCHANGE
After selecting all parameters click Next and in the following dialog box
set the order that parameters should appear in the format file. This is
not required but can help organize parameters for ease later.
Now you can use this new format file to bulk edit many things that are
not possible using standard format files.
To edit a format file, simple choose Edit rather than New when starting
the process and you can edit an existing format file if you realize you
need to add or remove anything.
Page 10
CHARMS
Tip: CHARM I/O Configuration V11, S-series
Not only can CHARM I/O be moved physically around
easily by changing CHARM modules and assigning to
different controllers, but the configuration can also be
easily moved around and modified in ways that are not
possible with other types of I/O.
Methods such as bulk editing work, but there are some
things to know when doing so.
Page 11
2012
USERS EXCHANGE
CHARMS
2012
USERS EXCHANGE
Page 12
CHARMS
2012
USERS EXCHANGE
Not all things you might expect are in channel properties tab.
o For example, to select number of wires for an RTD you must drill
down one level and change NUM_WIRES parameter
o At this level are other things such as COMPENSATION and
FILTER parameters, as well as calibration parameters for user
defined RTD type.
Bulk editing
o The default format files for bulk editing CHARMS do not go beyond
what you can do on properties tab.
o You will need to create custom format to edit information such as
the parameters listed above.
Page 13
HART
Tip: HART Configuration
An Analog Input card can
have HART Enabled on a
Channel basis.
When configuring the channel
type to HART additional
parameters will appear under
properties.
Page 14
2012
USERS EXCHANGE
HART
Analog Input
Channel Type
HART Analog
Input Channel
Type
Page 15
2012
USERS EXCHANGE
HART
It is recommended to Ignore
the HART_ERRORS at the
I/O level to reduce nuisance
alarms.
The module alarms are
typically all that are required.
Page 16
2012
USERS EXCHANGE
HART
Tip: HART Configuration
CAUTION: A HART transmitter can be
re-ranged from DeltaV.
When configuring the AI block using
HART_FIELD_VAL set the EU to no
units, null or - to avoid this.
For DIRECT set the OUT_SCALE and
for INDIRECT set the XD_SCALE.
Page 17
2012
USERS EXCHANGE
zPicture
Tip: Using zPicture to debug
Page 18
2012
USERS EXCHANGE
zPicture
2012
USERS EXCHANGE
Page 19
zPicture
2012
USERS EXCHANGE
Page 20
2012
USERS EXCHANGE
Page 21
2012
USERS EXCHANGE
Page 22
Page 23
2012
USERS EXCHANGE
Page 24
2012
USERS EXCHANGE
Splitter
2012
USERS EXCHANGE
Tip: Splitting the Splitter Should you ever have the need to control more
than two outputs (valves), you can combine splitters to accomplish this.
Page 25
Splitter
2012
USERS EXCHANGE
Page 26
2012
USERS EXCHANGE
Scenario:
Customer needed to control the amount of product being applied. The only
information available was a proximity switch that makes every revolution of a
gear on the supply motor. The customer knows how much product is supplied
for a revolution. The problem is to use this information as a process control
variable in a PID loop.
Solution:
The following slides show a module that was created to count the number of
high signals from a proximity switch. The values were fed into an array.
The values are then totaled and then divided by the number of entries to
provide a rolling average RPM. This is a first in first out array. The number of
samples is adjustable to increase accuracy.
Page 27
2012
USERS EXCHANGE
Array
Page 28
2012
USERS EXCHANGE
CALC2 Logic:
This logic calculates the RPMs of a feeder by counting the number of times a proximity switch makes. The number of revolutions
are brought in and assigned to the variable 'Revolution'.
Every 60sec the trigger variable goes true which moves the next RPM count into the array. The values in the array are added
together and the total is divided by the number of entries which can be adjusted with the parameter 'No-samples'. This gives a
rolling RPM average.
(* Define variables *)
Revolutions := 'IN1';
Trigger := 'IN2';
NoTestReq := 'IN3';
(* Determine the number entries *)
If Trigger=True or FirstScan = False then
FirstScan := true;
NoTestUsed := NoTestUsed + 1;
If NoTestUsed > NoTestReq then
NoTestUsed := NoTestReq;
end_if;
(*Clear variables *)
Total := 0;
i := NoTestUsed - 1;
(* First shift all of the array entries down by one then total their values.*)
WHILE (I >= 1) DO
'^/DATA_ARRAY'[I+1][1]:= '^/DATA_ARRAY'[I][1];
Total := Total + '^/DATA_ARRAY'[I+1][1];
I := I - 1;
END_WHILE;
(*Add the latest RPM entry*)
'^/DATA_ARRAY'[I][1] := Revolutions;
Total := Total + Revolutions;
end_if;
(*
ASSIGN AVERAGE TO OUTPUT *)
IF 'IN2' THEN
'OUT1' := Total / NoTestUsed;
ENDIF;
'OUT2' := Total;
'OUT3' := NoTestUsed
Page 29
Page 30
2012
USERS EXCHANGE
Sessions
Tip: Limit Access to Sessions
Limiting the available sessions on a
node basis.
Example of usage could be to limit
area access to specific sessions.
To setup, go to properties on the
specific session in DeltaV Explorer:
Page 31
2012
USERS EXCHANGE
Sessions
2012
USERS EXCHANGE
Then from the Remote Client Session Properties, select the Reserved for
Node List. Then add the specific node from Thin-Manager that the session
will show up on. All sessions must be assigned, otherwise they will
show up in the drop down menu.
Page 32
Sessions
2012
USERS EXCHANGE
List of valid nodes that can be entered in the Reserved Node List.
Example Thin-Client Node list.
Page 33
User Access
Tip: Limit Access
How to use THISUSER parameter to limit access.
Parameter Security can be used to limit access to
individual parameters, but there are cases where
you may want to block access to a group of
parameters.
This can be done with a transparent rectangle
placed on top of the area to be restricted. The
visibility of the rectangle is then controlled with the
THISUSER/USER_CAN parameter.
In this example, the visibility Data Source is
DVSYS.THISUSER/USER_CAN.B_CV[AREA_A][
TUNING] = 0. If the logged in user does not have
the TUNING key, the transparent rectangle will be
visible and the user cannot click through it.
Page 34
2012
USERS EXCHANGE
Remote Access
2012
USERS EXCHANGE
Page 35
Remote Access
2012
USERS EXCHANGE
Page 36
Remote Access
2012
USERS EXCHANGE
Page 37
Remote Access
2012
USERS EXCHANGE
Page 38
Remote Access
2012
USERS EXCHANGE
Page 39
Dynamic References
2012
USERS EXCHANGE
Page 40
Batch
2012
USERS EXCHANGE
Page 41
Batch Configuration
2012
USERS EXCHANGE
Page 42
2012
USERS EXCHANGE
DeltaV Reporter
Historical Data Mining Tool Included
with your Historical Application Station
DeltaV Reporter
2012
USERS EXCHANGE
This tool is for anyone that can use excel and wants to get added value
from the control system data at their fingertips.
Page 44
DeltaV Reporter
2012
USERS EXCHANGE
Page 45
2012
USERS EXCHANGE
DeltaV Reporter
Page 46
DeltaV Reporter
2012
USERS EXCHANGE
Data is your most important asset, Emerson wanted a tool that was
easy to use rather than one that required a lot of time to learn how to
use.
By using the power of Microsoft Excel you can read and write data to
your control system.
The DeltaV Excel Add-in allows you to get process, event and
diagnostic data and to utilize the proven features of Excel to Generate
reports, Create Charts and Customize tasks.
This add-in is an OPC client built to OPC Standards
Turn the tedious job of rebuilding weekly reports into a task you can do
quickly at your desktop.
Page 47
DeltaV Reporter
Page 48
2012
USERS EXCHANGE
2012
USERS EXCHANGE
Questions
User Tips & Tricks
Page 49
DVC Replacement
2012
USERS EXCHANGE
Page 50
DVC Replacement
Another indication of the
problem being shown with this
on-line value;
Bad ConfigErr
Page 51
2012
USERS EXCHANGE
DVC Replacement
2012
USERS EXCHANGE
Page 52
Redundant Controller
2012
USERS EXCHANGE
Page 53
Redundant Controller
2012
USERS EXCHANGE
Page 54
Graphics
2012
USERS EXCHANGE
Page 55
Graphics
2012
USERS EXCHANGE
Example 2:
Private Sub CommandButton3_Click()
frsWriteValue 1, dvsys.test_pulse/param1.f_cv
frsWait 3000
frsWriteValue 0,dvsys.test_pulse/param1.f_cv
End Sub
Note: These methods should only be used for short duration pulses, because
user input is restricted while the procedure is executing.
Page 56
Wireless Gateway
2012
USERS EXCHANGE
Page 57
Wireless Gateway
Node Address Table has NOT been configured.
Fix-None, Just be aware.
Page 58
2012
USERS EXCHANGE
Page 60
2012
USERS EXCHANGE