Professional Documents
Culture Documents
D800010X072
Contents
Developing the Control Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
System Capacities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Using Fieldbus Technology in the Control Strategy . . . . . . . . . . . . . . . . . . . . . . . . . 9
Using Fieldbus Blocks in the Control Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Deciding Where to Run Control Function Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Fieldbus Control Strategy Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Downloading the Block Configuration and Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Troubleshooting Fieldbus Loops . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Changing Function Block Parameter Values in Fieldbus Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
iii
iv
System Configuration
vi
System Configuration
Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501
vii
viii
System Configuration
Makes high-level decisions that apply to the overall system and plant and uses the DeltaV Explorer to define the
system characteristics. (The configuration engineer does not need to be concerned with lower details initially.)
Moves down a level in detail and decides how to logically divide system into areas. Areas are logical divisions of
a process control system. They can be physical plant locations or main processing functions.
Progresses another level and identifies the modules that control the field devices within those areas. The
configuration engineer can use the existing modules in the library as starting points for the modules required by
the control strategy.
All of the previous steps can be done in the DeltaV Explorer. Using the library provided, more than three-fourths of
the control strategy can be developed by duplicating existing library modules in the DeltaV Explorer. Then, the
Developing the Control Strategy
control strategy for the unique modules is defined using Control Studio. In Control Studio, engineers can define and
modify the control strategies, cut and paste a large portion of the configuration, and then fill in the details.
Engineers can also decide when to move to the next level of detail. In each level, most of the structure and
characteristics for typical control strategies are already configured for the engineer, except for minor details.
For example, module templates are used as a starting point for modules. The templates can define everything about
the type of control, except for a few operating parameters. Using this type of general approach, the engineers can lay
out the control strategies at each level, cut and paste the major pieces, fill in details, and then reveal the next level of
detail.
DeltaV software supports three types of common control languages for configuration: function blocks, sequential
function charts, and structured text. Within a single control module, you can intermix these control languages. For
example, a single module can leverage function blocks for closed loop analog control and Sequential Function Charts
to perform interlocking.
All three languages execute within the controller in their native form. There is no translation from one language to
another prior to execution.
System Configuration
System Capacities
The following tables specify the capacity values of the DeltaV system. Refer to Batch System Capacities for batchrelated capacity limits.
Inside this topic
Capacity Limits for System Topology
Capacity Limits for Workstations
Capacity Limits for Remote Networks and Workstations
Capacity Limits for Controllers
Capacity Limits for Remote I/O Nodes
Capacity Limits for SIS
Capacity Limits for System Topology
Description of System Capacity
Limit
120
1001
602
25,000
System Capacities
Limit
50
1. This is a fixed system limit. The system does not permit the configuration of more
than 100 controller nodes.
2. Additional - not counted against Control Network nodes or controller nodes.
3. This is a fixed system limit. The system does not permit the configuration of more
than 60 workstation nodes.
4. Graphic updates slow considerably when the total data links exceeds 7200. No
warning message is given.
5. If the limit is reached, a message warns that the application can't connect to the
database and it shuts down.
6. This is a tested limit, not a fixed limit.
Capacity Limits for Workstations
Description of Workstation
Capacity
Limit
<300
(recommended)
300 to 600
(performance degradation)
>600
(significant performance degradation)
>1000
(not supported)
500,000
History values
250*
Open pictures
16,000
System Configuration
Description of Workstation
Capacity
Limit
100
255
Named sets
Alarm types
255
200
150
30,000
1,500
2,000
SCADA tags
25,000
History values
20,0001
System Capacities
Fixed Limit
2*
10 total
*Additional remote workstations can access the ProfessionalPLUS for engineering data
if they use another machine as their Remote Access Server.
Capacity Limits for Controllers
Limit
100 ms
64
750
Controller interfaced to PROVOX I/O 750
Controller interfaced to RS3 I/O - 750
SCADA tags
3,200
Modules1
750
10%
400K
20 per second
10,000
System Configuration
Limit
16,000
2506
Fixed Limit
16
System Capacities
Limit
Application Limits
Total function blocks per SIS module (including
blocks in composites)
250*
127*
127*
32 (simplex)
32
24
32
Workstation Limits
Simulated Logic Solver Cards assigned to a
ProfessionalPLUS workstation with Windows Server
2003
System Limits
SISNet Repeater pairs in a DeltaV system
32
256
Logic Solvers
1024
System Configuration
properly with all approved fieldbus devices. To access a visual representation of the macrocycle, click the View
Schedule button on the Advanced tab to launch the Macrocycle Viewer application.
Use these guidelines to determine the actual macrocycle:
1
The actual macrocycle is equal to the requested macrocycle if the calculated macrocycle is less than or equal to
(<=) the requested macrocycle.
The actual macrocycle is equal to the calculated macrocycle if the calculated macrocycle is greater than (>) the
requested macrocycle. The following table provides some examples that show how the actual macrocycle is
determined:
If the requested
macrocycle is:
1 second
0.6 seconds
1 second
1 second
1.2 seconds
1.2 seconds
0.5 seconds
1 second
1 second
0.5 seconds
0.8 seconds
0.8 seconds
10
System Configuration
Note Be especially careful when using periodic writes to static fieldbus parameters in an expression since this type of
write can increment the block's static revision parameter (ST_REV), which then causes the controller to issue two
more requests to read static View List data. Refer to the Fieldbus Foundation specification for more information on
the View List. For the DeltaV system, VIEW_3 is constantly being read, but VIEW_4 is requested when the static
revision counter (contained in VIEW_3) is incremented.
Limit Periodic Writes to Static or Non-Volatile Parameters
It is recommended that you limit the number of periodic writes to all static or non-volatile parameters such as
HI_HI_LIM, LOW_CUT, SP, TRACK_IN_D, OUT, IO_OPTS, BIAS, STATUS_OPTS, SP_HI_LIM, and so on.
Static parameter writes increment the static revision counter, ST_REV, and are written to the device's non-volatile
memory. Consult the device documentation to determine if a parameter is static or non-volatile. If writes to a static
parameter are unavoidable, it is recommended that the module logic first read the parameter value, then compare the
existing value to the new value, and write the new value only if it is outside an acceptable deadband.
Note Fieldbus devices have a non-volatile memory write limit. If a static or non-volatile parameter is configured to
be written periodically, the device can stop its normal operation or fail to accept new values after it reaches its limit.
Use Valid Input and Output Links
When linking to fieldbus resident function block parameters, the DeltaV system restricts users to only input and
output parameters. Other non-linkable parameters are not visible for the links. Similarly, Show and Hide parameters
are not supported for fieldbus function blocks.
Use Valid Channel Assignments
Fieldbus Input (AI) and Output (AO) function blocks must have a valid channel number for device signals. When you
configure a fieldbus AI and AO block, you must set the channel parameter to a valid number or the blocks will remain
in OOS mode. Refer to the device documentation and to the Valid Units and Channel Values for Fieldbus Devices
topic.
Use Valid XD_SCALE
Fieldbus Input (AI) and Output (AO) function blocks must have a valid XD-SCALE. When you configure fieldbus
AI and AO function blocks, you must set valid XD-SCALE units or the block will remain in OOS. Only the AI
function block XD-SCALE units can change the units in the transducer. XD_SCALE EU100 and EU0 do not have to
match because only XD_SCALE units are transferred to the transducer block. Check proper scale and unit
information using the transducer block properties for the specific transmitter. To find units for a device, refer to the
Valid Units and Channel Values for Fieldbus Devices topic.
Assign Fieldbus Function Blocks to Devices
If a module contains any <unassigned> fieldbus function blocks, the LAS is unable to generate the schedule for the
entire module even if the module contains properly linked and assigned function blocks.
You are notified of any <unassigned> modules during a download of the fieldbus device. In Control Studio, click the
right mouse button on the function block and then click Assign to Fieldbus Device.
Configuring Fieldbus Function Block Tags
Fieldbus function block tags configured in the DeltaV Explorer are included in device downloads. This means that
the function block tag in the DeltaV system matches the tag in the device. As a result, users reading function block
11
tags directly from a device can easily locate that function block in the DeltaV system and vice versa. Here are a few
things to keep in mind about naming fieldbus function blocks:
1
It is recommended that function block tags in a fieldbus device are not changed with a handheld digital device.
Changing a function block tag in the DeltaV Explorer requires a device download.
When a function block tag is changed in the DeltaV Explorer, a blue triangle appears on the device indicating
that the change must be downloaded to the device to synchronize the device database with the DeltaV database.
When a device is downloaded, control and I/O running in the device is suspended. Be sure to follow appropriate
control safeguards.
12
System Configuration
13
Control performance becomes an issue if the PID block runs in the controller and the AI and AO blocks run in
devices on the segment. In this case, the AI and AO blocks execute once each macrocycle, but execution and
communication with the PID block in the controller is asynchronous. The difference between this hybrid control and
control in the controller using classic I/O is that with classic I/O, input and output data can be transferred to and from
the I/O bus every 25 milliseconds. With hybrid control, this transfer of data occurs at the macrocycle rate of about
500 milliseconds to 1 second. There is no real control benefit achieved by executing the PID block in the controller
faster than three times the macrocycle rate. If the macrocycle is 500 milliseconds, the fastest control interval of
benefit is 2 seconds. A 1 second macrocycle supports a practical control interval no faster than the 5 second option.
Therefore, hybrid control can compromise the controllability of loops with fast dynamics.
As can be seen in the Macrocycle Viewer, when one or more blocks run in the controller, the control loop is not
synchronized to the macrocycle and all blocks in the control loop run at the beginning of the macrocycle followed by
scheduled Compel Data transfer messages. This allows the H1 card to optimize non-scheduled communication since
all scheduled CD messages occur successively and devices that quickly respond with CD response messages will free
up additional bandwidth for unscheduled traffic.
Conserves Controller CPU Resources
Running a function block in a field device instead of in the controller reduces the block's controller CPU demand by
approximately 50 percent. Running the block in the device eliminates the demand on the controller CPU caused by
the execution of the block's control algorithm. However, there is processing required to communicate view list data
between the field block and the extended block (sometimes called a shadow block) in the controller. The net result is
about a 50 percent reduction in controller CPU resources when the block resides in the device.
Reduces the Number of VCRs on the Segment
There are two types of VCRs (Virtual Communication Relationships) on each port: publisher and subscriber VCRs.
An H1 interface card can support up to 50 total publisher and subscriber links on each port. Running the PID block in
the controller consumes three VCRs on the port for one simple loop. Running the PID block in the transmitter
consumes two VCRs and running it in the valve consumes one VCR. Running one VCR or two VCRs does not
significantly reduce the number of devices the segment will support. However, using three VCRs for a simple loop
can significantly reduce the number of devices the segment will support.
Running the PID Block in the DeltaV Controller
Provides Additional Control Options
The FFPID extended block may not support all the parameters supported by the PID block in the fieldbus device. You
can configure the full set of parameters when the PID block runs in the controller. Or, you can use the FFPID_RMT
extended block with compatible devices to use the full set of parameters.
May Facilitate Input Output Conditioning (if required)
When a control loop goes beyond the simple AI-PID-AO combination, there may be a rationale for having the PID
block reside in the controller. In most cases however, there are calculation blocks available in fieldbus devices for this
purpose. Examples of conditioning include, but are not limited to the following:
If you find it necessary to perform this type of conditioning in the controller, you do not lose anything by also running
the PID block in the controller because anything done in the controller (such as conditioning) eliminates synchronous
14
System Configuration
control. However, it is usually possible for the entire loop to reside in field devices on the segment, thus maintaining
synchronous execution. For example:
Use the Input Selector function block to select the input from multiple sensors.
Use the Signal Characterizer block to characterize both the forward and backward paths of the control
output.
Enable rate limiting by placing the AO block in Auto mode and manipulating the setpoint during startup or
shutdown (Setpoint rate limits apply in Auto mode but not in Cas mode).
15
16
System Configuration
For this example, we will use a basic control strategy composed of an AI, AO, and PID block, and we will configure
one parameter for an AI block. The intent of this example is to explain how to use the DeltaV Control Studio
application to create a control strategy - not to show you how to create a control strategy for a particular device.
Consult your device documentation for function block parameter definitions and recommended values and other
configuration options for your device.
Selecting the Blocks
Click the down arrow in the list box at the top of the palette and select IO. This makes the I/O function blocks
available to you.
1
Drag the Analog Input function block from the palette to the diagram pane to create a generic AI block. The
handles around the AI block indicate that it is selected.
At this point, you may want to rename the AI block to make it meaningful to you. Select the block with the right
mouse button and click Rename.
17
there are pros and cons to each method. Refer to the Deciding Where to Run Control Function Blocks topic for help
in making the decision. For this exercise, we will run the blocks in the device.
1
18
Select the block with the right mouse button and click Assign I/O | To Fieldbus. (To run the blocks in a controller,
click Assign I/O | To Signal Tag.)
System Configuration
Click the Browse button and find the device to which you want to assign this block. Navigate through the
controller, I/O card, port, and device to get to the blocks. Some devices may have more than one AI block
because the device may be capable of outputting more than one variable. In this image, the device, PDT2, has
two AI blocks: FFAI1 and FFA12.
Select one of the AI blocks and click OK. Now that the block has been assigned to a device, we will configure a
parameter for the device.
For information on how assigning blocks to fieldbus devices affects loop performance and how you can achieve
maximum performance, refer to the topic Using DeltaV Tune with Fieldbus Devices.
Configuring the Parameters
If it is not already selected, select the AI block, and you will see its default set of parameters listed in the parameter
pane. In order for the device to work properly, you must configure the device's parameters.
1
19
Click the Select All button to make all parameters visible to you.
The CHANNEL and XD_SCALE parameters must be correctly configured for AI and AO blocks or a configuration
error will occur when the device is downloaded.
20
System Configuration
Let's take the CHANNEL parameter as an example of how to configure a parameter. Because each device may be
capable of more than one measurement, when you configure an AI block, you specify which measurement you want
the block to process. The value for the CHANNEL parameter tells the block which measurement to process.
3
Double-click the CHANNEL parameter to open the Properties dialog for this parameter. The device
manufacturer publishes valid values for the channels, and much of this information is available in DeltaV Books
Online. Now, we'll find that information in books online.
21
The help contains a link to the Valid Units and Channel Values for Fieldbus Devices topic. Click the link to open
this topic in DeltaV Books Online. Once in Books Online, click your device in the list of devices to find the valid
units and channel values for the device.
Now you know how to configure a parameter for a block. Experiment with Control Studio and open the Properties
dialog boxes for other AI parameters or drag another block onto the diagram and look at its parameters. When you are
ready, configure the other blocks in your control strategy. Consult the device documentation for recommended
parameter values. Then, connect all inputs and outputs, assign the strategy to a node, and save and download the
strategy.
Connecting Inputs and Outputs
Algorithms that determine how information is exchanged between devices run in the background in Control Studio.
You wire the blocks together in Control Studio to create the algorithms that describe how you want the blocks to
execute. The output of one block flows into another block as an input. In our example control strategy, the output of
the AI block flows into the PID block as input, the output of the PID block flows into the AO block as input, and so
on.
22
System Configuration
Click the connection point where you want the wire to begin. The cursor turns into a
Hold the left mouse button down and drag the cursor to the end point.
Release the left mouse button at the end point and the line is drawn between the two points.
If you have trouble drawing the connections, use the Connection tool
on the toolbar.
on the toolbar.
Select the controller to which you want to assign the module and click OK.
Saving a Strategy
Once you have created your control strategy and assigned it to a node, you must save it. A strategy is saved as a
module.
1
In the Look in: box, select the location (Area) where you want the strategy to run.
23
Select the device with the right mouse button and click Download | Fieldbus Device. DeltaV software informs
you if items subordinate to this one also need to be downloaded and can verify the configuration if you choose.
Make sure the modules associated with the devices on the segment have been downloaded. The module
information must be sent to the H1 card before devices are downloaded.
Read the important Warning and if you are sure you want to download, click Yes.
When the download is complete, the blue triangle disappears from the device.
There may be other blue triangles in the DeltaV Explorer hierarchy. Download those items if you are comfortable
doing so or read the DeltaV Explorer help on downloading for more information.
Confirming a Module's Correct Operation
Control Studio's On-line mode is a powerful tool for confirming a module's correct operation and for diagnosing
module problems. You must assign and download a module before you can view it in On-line mode.
1
Click View | On-line to create an online session in which you can examine module and block parameters.
If the module is operating correctly, the outputs are displayed next to the block.
If there is a problem with a function block, a red X appears on the function block. To determine the source of the
problem, perform the following steps:
Check the BLOCK_ERR parameter (double-click a parameter to edit it) and determine if the block is out of
service (OOS) or if it has a block configuration error. Among the problems that can cause a block to be out
of service are misconfiguration, bad sensor input, and problems with the download.
Check the status of the block's input and output parameters. For example, a status of BadNoCom indicates
that information is not being sent to the block's inputs.
If the block has a bad PV, verify that the correct XD_SCALE, UNITS, and RANGE are transferred.
If the data has intermittent bad status, check the required macrocycle and the module execution rate. The
module execution rate should be >= 2 times the actual macrocycle.
Remember that if you make any changes in On-line mode, the changes are not saved in the database. Use Control
Studio or Explorer to upload the changes to the database.
24
System Configuration
Using Methods
For the example, we'll use the Set Sensor Connections method to configure the sensor connections for a Rosemount
Multivariable Temperature Transmitter, Model 3244 MV. The interface to this method is much like a software Wizard
and the method resides in the Transducer block for this device. Refer to the Device Descriptions and Methods topic
for more information about methods. Depending upon the type of device you are working with, you might have to put
AI and AO blocks in Out of Service or Manual mode before running a method. (Refer to the device documentation
for a description of the methods available for the device.)
1
Select the device, click the right mouse button on the Transducer block, and select Sensor Config | Set Sensor
Connections.
Select the sensor that you want to configure and click Next.
25
Click the down arrow on the list box, select the sensor type, and click Next.
Click the down arrow on the list box, and select the sensor connection type (2, 3, or 4-wire connection).
26
System Configuration
Select the device with the right mouse button and click Configure.
The Device Configuration dialog box opens. The Resource block parameters are displayed by default when the dialog
opens.
27
The tabs along the top of the dialog indicate the various parameter groupings. Click a tab to view the parameter
values.
Enter or select new values for parameters that can be edited. When you edit a value, the tab and edited field
changes to yellow.
Remember that help is available for any of the fields on this dialog. Select the
the field for which you want help, and click the mouse button.
Click the Transducer block to view and edit the Transducer block parameters.
Click the tabs to view parameter values and enter or select new values for editable parameters.
When you are finished, either click the OK button to commit parameter changes and close the dialog box or click
the Apply button to commit parameter changes and continue working in this dialog box.
28
System Configuration
A Valve is Hunting
You have the most recent firmware updates for the H1 card and controller. Run the DeltaV Controller Update Utility
to upgrade the firmware.
You have read the device documentation and know the function block parameter definitions and recommended values
and other configuration options for your device.
You have the most recent version of the Fieldbus Specification for reference. Visit the Fieldbus Foundations website
at www.fieldbus.org to learn how to get the most recent version of the specification.
Can't Download a Module
) on the module diagram in Control Studio online or debug. Common errors are:
Incorrect function block MODE: A red X on an AI or AO block could indicate an incorrect mode. Typically, an
incorrect mode causes unexpected block output, static output values, or no signal from an active transmitter. Be sure
that the Target and Actual modes for the AI block is AUTO and the Target and Actual modes for the AO block is
CASCADE.
Incorrect Transducer or Resource block MODE: Also check that the Transducer and Resource blocks' Actual
modes are AUTO. Be sure that a Transducer block that configures a Primary, Secondary, or Tertiary variable is in
29
AUTO mode. If it is in Out of Service (OOS) mode, the PV value on a function block that references a channel will
be bad. Be aware that some devices make use of a default Transducer block mode such as Manual to facilitate device
commissioning. It is possible that a default Transducer block mode is contributing to loop inoperability.
Incorrect CHANNEL: A red X on an AI block, an unexpected AI value, or a transmitter or valve that does not return
a value could indicate an incorrect channel. Because each device may be capable of more than one measurement,
when you configure an AI block you must specify which measurement you want the block to process. The value for
the CHANNEL parameter tells the block which measurement to process. The device manufacturer publishes valid
channel values and much of this information is available in DeltaV Books Online. It is possible that the value for the
CHANNEL parameter changed between device revisions and an incorrect channel number and or Engineering Units
is in use. To find the correct channel number in Books Online, select the channel parameter in the parameter view
window, select What's This from the context menu, and follow the link to the Valid Units and Channel Values for
Fieldbus Devices topic.
Tip Use Event Viewer if you're having problems isolating module parameters that failed to download. Open the
Event Viewer and, in the Desc2 column, look for the block and parameter associated with Attribute Override
Failure:MODULE/PARAMETER. For example Attribute Override Failure:AI1/XD_SCALE.
Incorrect choices for L_TYPE parameter: An incorrect choice for L_TYPE parameter can cause a red X on a
fieldbus function block in Control Studio. If L_TYPE is set for Indirect or Indirect Square Root and the XD_SCALE
is set incorrectly for the type and channel of the device, an error can occur. A red X can occur if L_TYPE is set to
Direct and the device requires that OUT_SCALE equals the XD_SCALE or if the device does not support Direct for
L_TYPE.
Incorrect choice of Engineering Units in XD_SCALE: A red X on a fieldbus function block in Control Studio or
the block going to Out of Service could indicate an incorrect choice of Engineering Units (EU) in XD_SCALE
depending upon the setting of the L_TYPE parameter. Some fieldbus functions blocks use an XD_SCALE parameter
that defines scaling ranges, engineering units, and the number of decimal places used to display the engineering units
associated with the channel input value. An incorrect EU value will cause an Attribute Override Failure which will be
listed in the Event Viewer (see the preceding Tip). The Primary Value Type configured in the Transducer block
should match the EU configured in the fieldbus block. The majority of fieldbus devices can be configured through the
EU in the XD_SCALE parameter.
Incorrect choice of Engineering Units in OUT_SCALE: A red X on a fieldbus function block in Control Studio or
the block going to Out of Service could indicate an incorrect choice of Engineering Units (EU) in OUT_SCALE
depending upon the setting of the L_TYPE parameter. Some fieldbus functions blocks use an OUT_SCALE
parameter that defines scaling ranges, engineering units, and the number of decimal places used to display the
engineering units associated with the OUT value of the fieldbus function block. An incorrect EU value will cause an
Attribute Override Failure which will be listed in the Event Viewer. A configuration error can occur if the Primary
Value Type configured in the Transducer block does not match the OUT_SCALE EU configured in the fieldbus
function block.
Block Out of Service: A red X on a block in Control Studio could indicate that the block is Out of Service (OOS).
This can be caused by a device problem or can occur if the Resource and/or Transducer block is OOS. Select the
device in DeltaV Explorer and click Status/ Conditions to access the device's Resource and Transducer blocks. The
status should be clear with no errors. Use DeltaV Diagnostics and look at device communication statistics and port
communication statistics and check the port integrity.
Bad status on input block's PV: Bad status on an input block's PV can be caused by incorrect choice of Engineering
Units (EU) and range in the XD_SCALE parameter or an incorrect output value in the Transducer block. The Primary
Value Type in the Transducer block should match the EU configured for the AI or AO block.
30
System Configuration
Note The use of bad status on an input block's PV can be a design decision. For example, it can be used to show that
the input PV or status propagation from a linked block is outside a qualified range.
SHED_OPT is zero: A red X on an AO or DO block in Control Studio online could indicate that the value for
SHED_OPT is zero. The value for SHED_OPT must be non-zero.
A module may fail to download because the device will not download. Refer to Can't Download a Device to ensure
that the problem does not originate at the device.
Can't Download a Port
Often, a port will fail to download because a module or modules is not downloaded. Use the Event Viewer to isolate
parameters that failed to download. Open the Event Viewer (click Start | DeltaV |Operator | Process History View)
and in the Desc 2 column of the event grid look for the block and parameter associated with Attribute Override
Failure.
Also, in DeltaV Explorer check for blue triangles
on modules assigned to controllers. A blue triangle indicates an
item that needs downloading. Modules with extended blocks, (a DeltaV function block that communicates with a
function block running in a fieldbus device) must be downloaded before the port to which the device is connected is
downloaded.
Common module download failures are described in Can't Download a Module.
Don't Understand Block Errors
31
Device-Specific Errors
The following errors refer to internal device errors that may be serious and may require service or device
replacement. Refer to the device documentation if you encounter these errors:
Lost NV Data
Lost Static Data
Memory Failure
The following errors are used by the manufacturer to alert users of a possible device problem and to alert users that
the device needs maintenance now or in the near future:
Device Needs Maintenance Now
Device Needs Maintenance Soon
Intermittent Block Errors
Intermittent function block errors that show up as a red X on an output in Control Studio in online mode and/or block
errors that come and go in Event Viewer could be caused by an incorrect module execution time or an incorrect
requested macrocycle. The module execution time and the macrocycles are independent. Module execution time
determines how often a module executes while the macrocycle is the execution time for a single iteration of the
fieldbus function blocks running in all the devices on the port. The requested macrocycle is user-specified and the
calculated macrocycle is system-calculated. The calculated macrocycle time includes an adjustment that allocates
time for unscheduled data transfers. As a rule of thumb, the module execution time should be >= 2 times the
calculated macrocycle. Modules with all blocks running in field devices can run with a module execution rate equal
to or greater than the macrocycle.
Output Blocks are not Tracking a Valve's Actual Position
If an output block (AO or DO) is not tracking an actual valve position, try selecting Output Readback in the device's
Resource block if the device supports Output Readback. When this option is selected, the output block uses the
Readback parameter from the Transducer block as its Readback value (showing the actual valve position). If this
option is not selected, Readback is the value of the measured or implied actuator position associated with the OUT
value, in percent.
PID Block's Actual Mode is Stuck in IMAN
When a PID block is the upstream block of a cascade pair, it will go to IMAN as its Actual mode when its
downstream partner, (an AO block for example), is not in CASCADE preventing the PID from closing the cascade.
Putting the AO block in CASCADE mode usually causes the PID to leave IMAN and return to its Target mode.
Note Some devices' AO block will not go into CASCADE mode if AUTO is not enabled in the Permitted mode. The
Permitted mode can be changed only in Control Studio in edit mode.
Additionally, be sure that the PID's BKCAL_IN is connected to the downstream block's BKCAL_OUT. Failure to
make this connection can result in the PID's Actual mode going to IMAN.
Can't Download a Device
Non-Emerson devices may repeatedly fail to download. This can occur if the default values have been overwritten.
First try decommissioning and then recommissioning the device. If this does not work and the device supports "Reset
to Factory Defaults", reset the device to the factory defaults. Finally, refer to the device documentation.
32
System Configuration
A device can fail to download if the device does not support the requested macrocycle (the user-specified execution
time for all the fieldbus function blocks on the segment). Refer to the device documentation for supported macrocycle
times.
Can't Commission a Device
A device that does not commission could be lacking its device description (DD) files. Refer to problems
commissioning devices for more information on troubleshooting this issue.
A duplicate address on a port can also prevent a device from commissioning. Check each device's NodeAddr
parameter in DeltaV Diagnostics or check the Port's Status parameter for a status of Duplicate Address on Link and
then check each device's NodeAddr parameter.
A Valve is Hunting
Run a valve signature and calibrate the valve.
Devices are Dropping Off the Segment
Device alerts and PV Bad Alarm indications could mean that devices are dropping off the segment. This can be due to
low voltage or noise on the segment. Noise can be caused by inadequate termination, the device itself, shielding, or
grounding. The Fieldbus Segment Checkout Procedure provides some help in isolating voltage and noise problems.
Devices dropping off the segment can also be caused by scheduling problems involving the module execution rate
and/or the macrocycle. Refer to Intermittent Block Errors for information on module execution rate and macrocycles.
33
DeltaV Operate to write the value through a datalink that allows data entry
Control Studio online or debug to write the value for any writeable function block parameter in the device
34
System Configuration
Locks - Prevent users from changing the parameters and parameter fields assigned to the lock and prevent
users from performing certain functions. You use the Explorer to assign locks to parameters, parameter
fields and functions. It is helpful to think of a lock as something that specifies the name of the key that grants
access.
Keys - Provide permissions to individual users or whole groups of users. Each key is associated with a lock.
You grant keys under the group and user properties dialogs. Users can be granted any number of keys or
none at all.
Groups - Enable you to classify users together and grant keys to everyone in the group.
Users - Are DeltaV system and Windows users. You can assign users to one or more groups. The DeltaV
User Manager application also allows you to create new Windows users without accessing the Windows
User Manager application. When you create a new user, you can specify whether the user is a Windows user,
a DeltaV system user, or both.
Areas - Some keys can be granted to DeltaV users for specific areas. Use this feature to grant write access to
operators for control modules within the operators' responsibility and withhold access to other similar
modules outside their responsibility. Other keys apply to all areas and the only choice when granting these
keys is <Sitewide>.
DeltaV Locks
In the DeltaV system, locks prevent users from changing the parameters and parameter fields assigned to the lock and
prevent users from performing certain functions.
Locks for parameters are assigned to parameter names rather than to specific instances of parameters. In other words,
a lock on HI_LIM applies to all instances of parameters named HI_LIM. To lock a specific instance of a parameter,
you must create a unique name for that parameter, such as HI_LIM1.
Locks and keys assigned at the field level override those on the parameter itself. This means that specific parameter
fields can be open to a large number of users while the parameter as a whole remains generally restricted.
Note Because security settings on fields have precedence over parameter security settings, you must be very careful
when defining access to fields. For example, if access to GAIN is restricted, but access to the CV field has been
defined as less restricted, users with the less restrictive access will be able to change the GAIN parameter.
When users make write requests to a specific parameter field, the system checks for a lock on the field. If there is no
lock, the system checks for a lock on the parameter itself. When there is no lock on the parameter, the default lock is
used. Users can write to the field of the parameter only when they have a key corresponding to the lock. Additionally,
35
the workstation properties can restrict parameter writes by area. That is, the parameter can only be written to if the
user has the key for the area and that area is assigned to the current workstation.
Locks are also assigned to various user functions such as downloading, uploading, changing the configuration
database and so on. Functions are assigned to default locks initially. You can change the lock associated with a
function.
Security is located under the setup component in the Explorer hierarchy. Assign locks to parameters and parameter
fields through the Parameter Security and Field Security properties under the Security section. Assign locks to
functions through the Function Security properties under the Security section. You can also assign a default lock
(keep in mind that many users might have a key to this lock). When you do not assign a lock to a parameter or field,
the default lock applies.
If you want to remove all security from a parameter, the lock specified for that parameter must be assigned to all
users. For example:
1
Rename an unused lock (for example, User Lock 10) to something descriptive like, "Everyone".
Use the "Everyone" lock on parameters that to which everyone needs write access (or at least to fields that do not
have a field name lock defined).
Assign the "Everyone" key to the "All Users" group, sitewide (that is, in all plant areas defined).
Make sure all DeltaV users are members of the "All Users" group.
The result is that all DeltaV users get the "Everyone" key in all defined plant areas. This enables them to write to
parameters associated with the Everyone key unless a field name lock exists.
If you create a new parameter in Control Studio with a unique name, you must add the parameter to the Parameter
Security section in Explorer in order to assign a lock to it. Otherwise, the default lock applies.
Note that there might be locks on the fields of a parameter you create. Field locks are determined by the parameter
type on which the parameter is based.
Locks Assigned to Function Block Parameters
Any function block parameter that is writable has a lock assigned to it. You can change the lock assignments made by
the system. Keys to all of the parameter and field locks (except Diagnostic) can be granted to specific plant areas.
Refer to the following table for a default list of the parameter and field locks and a description of each lock's function:
Parameter and Field Locks
Lock
Alarms
concern alarms and the alarm horn. The Alarms lock affects access to
the HORN parameter and the HENAB, MACK, and NALM fields.
Control
Restricted Control
36
System Configuration
Lock
Tuning
Diagnostic
System Records
affect the records kept by the system, such as parameters that turn off
the recording of event records.
Default
Associated
Lock
Operation Function
Can Apply
to Specific
Area?
ACTION_VERIFY
Restricted
Control
Yes
ADMIN_CONFIG_DB
System Admin
No
CHANGE_CONFIG_DB
Can Configure
No
CHANGE_DEVICE_DB
Can Calibrate
No
CHART_SAVE
Can Configure
No
37
Function
Default
Associated
Lock
Operation Function
Can Apply
to Specific
Area?
DIAGNOSTIC_DATA_CLEAR
Diagnostic
No
DIAGNOSTIC_SWITCHOVER
Diagnostic
No
DOWNLOAD_CONFIG
Can Download
No
INSPECT_TUNE
Tuning
Yes
REPLACE_DEVICE
Can Calibrate
No
UPDATE_FIRMWARE
System Admin
No
UPLOAD_CONFIG
Can Configure
No
USER_SECURITY_ATTACH_LOCKS
Can Configure
No
USER_SECURITY_USERMANAGER
Can Configure
No
38
System Configuration
Function
Default
Associated
Lock
Operation Function
Can Apply
to Specific
Area?
VC_ADMINISTRATOR
System Admin
No
VC_CHECKOUT_CHECKIN
Can Configure
No
VC_DEVICE_CHECKOUT_CHECKIN
Can Calibrate
No
VC_DOWNLOAD_CHECKEDOUT
System Admin
No
VC_DOWNLOAD_UNAUTHORIZED
System Admin
No
VC_PURGE_RECOVER_ITEMS
System Admin
No
VC_ROLLBACK_ITEMS
System Admin
No
VC_SET_LABEL
Can Configure
No
Lock Examples
Removing a parameter or field from the security dialog lists in DeltaV Explorer may have unintended consequences.
The following examples illustrate the effect of removing parameters and fields from the security dialog lists.
Example 1: Attempt to write FIC101/MYPARAM.CV
Parameter name is MYPARAM. MYPARAM is not listed in the Parameter Security dialog.
Result: The lock in effect is Control. Users with the Control key in FIC101's plant area can write it.
Example 2: Attempt to write FIC101/MYPARAM.CV
Parameter name is MYPARAM. MYPARAM is configured as Tuning in the Parameter Security dialog.
Result: The lock in effect is Tuning. Users with the Tuning key in FIC101's plant area can write it. Users with the
Control key in FIC101's plant area cannot write it.
39
Field name is PRI. PRI is configured as System Records in the Field Security dialog.
Result: The lock in effect is System Records. Users with the System Records key in FIC101's area can write it. Users
with the Tuning key in FIC101's plant area cannot write it. Users with the Control key in FIC101's plant area cannot
write it.
40
System Configuration
Electronic Signatures
Inside this topic
Configuring Electronic Signatures
Electronic Signature Properties
Signature Policies
Assigning Policies to Modules
Signature Policy Inheritance
Using Signature Policies with Contained Modules
Electronic Signatures at Run Time
Using Electronic Signatures When Acknowledging Alarms on Pictures
Electronic signatures are user names and passwords that provide accountability for operator writes to certain module
parameters and fields from DeltaV Operate and Control Studio online. Electronic Signatures do not apply to writes to
OPC and to the DeltaV Excel Add-In application. Electronic signatures is a DeltaV system preference that can be
disabled (hidden) if not required or enabled selectively on an area-by-area, module-by-module basis. Electronic
signatures does not change the existing DeltaV security feature that controls who is able to make changes to
parameters. Rather, it uses a signature to authenticate the operator's identity. That is, the signature is used as an
additional check to ensure that the operator is who he claims to be. The operator must have a valid user name and
password and the required privileges to perform the action in the area in which the module resides. The write is not
allowed if the operator fails to enter a valid username and password and if the operator does not have the required
privileges in the area in which the module resides.
Depending upon the criticality of a module to the process, no signature, one signature (confirmer), or two signatures
(confirmer and verifier) can be configured. It is possible to allow the same person to be both the confirmer and
verifier of an operator write. Typically, the verifier is a higher-level employee whose signature approves the change
the confirmer is making. The verifier must hold the key to the ACTION_VERIFY function lock. To allow the same
person to be both Confirmer and Verifier, select Properties from the Electronic Signatures context menu and select the
checkbox. If the electronic signature succeeds, the date and time the electronic signature authentication occurred, the
node from which the change occurred, a description of the action, and the confirmer and verifier names are recorded
in the event chronicle and can be seen through the Process History View application. Similarly, failed attempts at
confirming or verifying an action are also recorded and visible through the Process History View. In addition to the
Process History View application, failed confirm or verify attempts are also recorded in the Batch Historian if it is
collecting chronicle events and can be viewed through the Batch History View application.
Operator Comments
The operator has the option of entering a comment about the parameter change. Operator comments are recorded in
the Desc2 field in the Process History View application. This field is truncated at 240 characters. By default, the
system adds the string VALUE SIGNED FOR = xxxxx before the comment. That is, the system adds additional
characters to your comment and these additional characters are counted in the 240 character limit. So for example if
you changed a value to 365 and entered the comment "changed value for tank1" the Desc2 field will total 48
characters and read:
VALUE SIGNED FOR = 365 (changed value for tank1)
The system calculates the length of the string VALUE SIGNED FOR = xxxxx plus the length of the comment. If the
comment will cause Desc2 to exceed 240 characters, the system posts a message asking that the comment be
shortened. The length of the comment is limited to the lesser of: 200 characters or what fits in the Desc2 field. If
VALUE SIGNED FOR is a string that exceeds that 240 characters, the value is truncated at 240 characters in the
Desc2 field in Process History View and no comment is saved with the value.
The DeltaV system does not enforce the use of operator comments; this decision is left to plant managers.
Electronic Signatures
41
Note Do not use the Enter key to create a line break in the Comment field. Pressing the Enter key in the Comment
field is the same as selecting the OK button; it dismisses the dialog and performs the command.
42
System Configuration
reside and define a signature policy for the modules. If electronic signatures is not enabled for an area, no signatures
will be required for writes to modules in that area. To enable electronic signatures in a process area, select Properties
from the area's context menu and select Enable Electronic Signature. It is necessary to download the Setup data after
making a change to electronic signature properties. When the change affects either the Batch Executive or the
Campaign Manager, those subsystems must be downloaded.
Signature Policies
Signature policies define the module parameters and fields that will require a signature before an operator can write to
it, the type of signature required, and the default signature requirement for the module parameters and fields not listed
in the signature policy. The signature requirement options are Comment Only, Confirm, Confirm and Verify, None.
Note The signature policy for Field Confirmation takes precedence over the policy for Parameter Confirmation even
if the Field Confirmation requirement is less stringent than the Parameter Confirmation requirement.
Electronic Signatures
43
not required. Then when the configuration is ready for normal operation, Electronic Signatures can be enabled at the
level of granularity required for your situation.
Each module can have only one policy assigned to it; however, there is no limit to the number of signature policies
allowed in the database.
Tip Carefully consider the use of slew buttons in operator graphics. Slew buttons are used to gradually increase or
decrease a value and can be difficult to use on parameters that are subject to Electronic Signatures since each click on
a slew button is a separate parameter write.
To assign a policy to a non-class-based module or module template, select Electronic Signature from the module's
context menu and browse to the policy.
Unit classes
Phase classes
44
System Configuration
Datalink Stamper
Datalink Formatter
When an operator clicks a button or presses Enter after writing to a parameter that is subject to an electronic
signature, the electronic signature dialog box opens. The parameter is not written until the required signature is
provided. The following image shows the Electronic Signature dialog box that opens in Control Studio online when a
Confirm and Verify signature is required for a parameter write. The appearance of this dialog varies depending upon
the signature requirement.
Electronic Signatures
45
46
System Configuration
Electronic Signatures
47
48
System Configuration
Select the Control or Equipment Module Class at the Library level and choose Configure from the context menu.
Enter a parameter name that will not reveal the path and click OK.
Now select the Control or Equipment Module Class and click Hide Internal Structure.
You must have DeltaV System Admin and Can Configure keys to access the Hide Internal Structure feature. Refer to
the Parameter and Function Security topic for more information on locks and keys.
To hide an item's internal structure:
1
Select the item (Composite Template, Control Module Class, Equipment Module Class, and Phase Class).
Note An item cannot be hidden if it is in a protected category. Refer to Protecting Your Engineering Standards for
information on hiding items in protected categories.
49
Opened in Edit mode in Control Studio (instances of the item can be opened in Control Studio in online and
debug modes).
Copied
Converted to another type that would reveal the internal structure. For example, a linked composite cannot
be converted to an embedded composite.
A hidden item's properties and history collection cannot be changed. However, a hidden item can be deleted. An
instance of a hidden item can be modified from the Properties, History Collection, and Configure dialogs. Parameter
shortcut values can be changed on an instance.
After an item's internal structure has been hidden, it can be accessed only with the password used to hide the
structure. In most cases the owner of the intellectual property has the password. When a configuration that contains
hidden items is exported, the hidden items and password are encrypted. The password persists even if the hidden item
is exported, then deleted, and imported or re-imported into a different database. An item from an unencrypted
configuration cannot be imported into the DeltaV system if that item already exists in the database and its structure is
hidden.
It is important to provide information about the owner of a hidden item. For example, suppose a problem arises with
a control module with a hidden internal structure and users need to contact the module's owner for help. It is
recommended that you use one or more string parameters to hold information about the owner and/or the item's
revision. Before hiding an item's internal structure, use Control Studio to add the string parameters. Be sure to add the
parameters at the item's top level to ensure that the parameters remain visible after the item is hidden. Refer to the
Control Studio online help for information on adding parameters.
If DeltaV Version Control (VCAT) is enabled, do not check in an item that is unhidden. If an unhidden item is
checked in, the internal structure of that version of the item can be viewed in VCAT history.
50
System Configuration
Composite and module templates (specific parameters of class-based templates can also be protected,
regardless of the protection status of the category).
Select the library category (Composite and Module Templates, and Control Module, Equipment Module, Phase,
and Unit Classes) and choose Protect from the context menu.
Click OK.
Items in protected categories cannot be modified, deleted, moved or overwritten and new items cannot be added to a
protected category.
Note The Hide Internal Structure command cannot be applied to an item in a protected category. To hide an item in a
protected category, first hide the item and then protect the category to which the item belongs.
To protect a parameter in a class-based template:
1
Select the parameter of a class-based template and choose Protect from the context menu.
51
It is not possible to remove the protection in instances of the module made from the template.
Protection is not automatically preserved during a manual database export and import. To preserve protection when
manually exporting and importing a database, check the 'Include the data for a DeltaV software upgrade' checkbox.
However, protection is automatically preserved when a DeltaV installation is upgraded with the DeltaV Upgrade
Wizard.
52
System Configuration
Expressions
One of the fundamental capabilities required in a controller is its ability to compute expressions. An expression is
structured text that represents a calculation and has a specific syntax. The expressions provide information for
process operators so that they can make control decisions. This section provides an overview of the functions,
operators, and syntax used for expressions.
To write an expression, use the Expression Editor. The Action, Calc/Logic, and Condition function blocks, as well as
the Sequential Function Charts, allow you to enter expressions for execution in the controller.
Caution When writing expressions using an external editor, only use a plain ASCII text editor (Notepad is
recommended). Using other editors can cause the expression to change during the load and save process.
Expressions can be used for the following applications:
Action Block Expression The expression in the action block allows you to evaluate an equation and assign
the result of the evaluation to a parameter within the DeltaV system.
Condition Block Expression Used with Boolean-valued expression. To set the condition, you must specify
an expression as TRUE. Note that the timed part of condition definitions should not be part of the
expression, but rather part of the definition of the condition.
Calculation/Logic Block Expression Used with a collection of expressions whose results can be assigned
to function block parameters or module parameters.
For example, for an expression in a Calc/Logic block (CALC1) in the composite, COMPOS1, that is in the
composite, COMPOS2, that is a block in the module, MOD, you can:
Reference a CALC1 parameter within the block, IN1.CV.
Reference a COMPOS1 parameter within a composite, ^/ATTR.CV.
Reference a COMPOS2 parameter outside a composite, /COMPOS2/PARAM.CV.
Reference a Module (MOD) parameter, /MSTATUS.CV.
Reference another Module parameter, //FIC101/PID/SP.CV.
Reference a diagnostic parameter from the module, //NODEX/OINTEG.
Reference a DST parameter for the module, //DST/FIELD1_VAL_PCT.
SFC Step Actions Used to assign the result of an expression to a database item, which can be an SFC step,
state variable, or a parameter.
SFC Step Transitions Used with a Boolean-valued expression. When it is evaluated as TRUE, the
transition is triggered and associated steps are enabled or disabled.
SFC Step Mode Used to allow operators (with the appropriate privileges) complete control over SFC
execution by requiring that all transitions be forced. The operator also has the power to redo a given step
before proceeding or to restart the sequence from a different point by changing the active step. The SFC can
be placed into Step mode from Control Studio Online or Debug views.
Syntax Rules
An expression is made up of operands, operators, functions, constants, and comments. Each expression must follow a
specific syntax to be valid. The basic rules for valid DeltaV syntax expressions include:
Expressions
53
The Condition function block evaluates a multi-line expression. The assignment operator (:=) is not a valid
operator.
The Action block requires the use of the assignment operator (:=). All other operators are valid in the Action
block provided the final evaluation of the expression is an assignment.
The expression should end with a semi-colon (;). DeltaV software usually adds a semi-colon for you if one is
not there.
The number of characters in an expression cannot exceed 9941. You can reduce expression length by
relocating part of the expression or by making the expression code more compact.
Note The expression evaluator is stack oriented and allows a maximum of 32 operands and operators. The use of
parentheses to organize the expression minimizes the stack usage. The equations are evaluated using RPN (Reverse
Polish Notation).
Relative Notation
The following rules indicate the relative notation of parameters in an expression.
Relative Notation Rules
Notation
Relates to
Rule
Rule
//
External
Module relative
Block relative
/+/
Phase relative
Assignment Statements
The := operator is an operator in DeltaV expressions. This operator allows for the assignment of calculated values to
locations inside and outside of the current block. Examples of the assignment operator follow:
'Block1.mode.target' := MAN;
RADIUS := .5;
OUT1:= 5 *RADIUS;
Assignment statements can be in any of the following formats:
output := value;
or
'external reference path' := value;
or
temporary variable := value;
54
System Configuration
If you wanted to increment a module-level parameter called SYRUP, the expression might look like this:
'/SYRUP' := '/SYRUP' + 1;
Note The assignment operator is not valid in the Condition block. However, the assignment operator is required in the
Action block.
If-Then-Else-End_if Statements
The IF-THEN-ELSE-END_IF structure allows you to execute conditional code in expressions. When a block tests a
condition that evaluates to TRUE, it executes one set of the statements; otherwise, it executes a different set of
statements. The following example illustrates the IF-THEN-ELSE-END_IF structure:
IF '/Block1.mode.ACTUAL' = MAN THEN
'/Block1.mode.TARGET':= AUTO;
ELSE
OUT1:= IN1;
END_IF;
Note DeltaV software allows you to use ENDIF or END_IF for your convenience. However, structured text typically
requires the use of the keyword END_IF.
In the preceding example, the condition tested is whether 'Block1.mode.ACTUAL' is equal to manual. Notice that the
'=' operator is not used as an assignment operator, but rather to test the two operands for equality. If the condition is
TRUE, the 'Block1.mode.TARGET' is set to AUTO; otherwise, OUT1 is set to the value of IN1. Multiple statements
can be placed between the THEN keyword and the ELSE keyword as well as between ELSE and the END_IF
keyword.
It is not always necessary to use the ELSE portion of the statement. For example, if you wanted to set the parameter
CALC block parameter OUT1 to TRUE when the process variable of PID1 in LIC-549 goes above 75, the expression
would look like this:
IF '//LIC-549/PID1/PV.CV' > 75 THEN
'OUT1.CV'
:= TRUE;
ENDIF;
Note The CV extension in this example stands for current value. If the choice exists, ST stands for status.
After you enter an expression, you can validate the expression syntax. The validation process identifies syntax
problems with the expression and any unresolved parameters. The expression can be saved to the database with
syntax errors, but the errors should be corrected before downloading the expression.
While-Do-End_While
The WHILE-DO-END_WHILE structure allows you to continue executing a group of statements while the value of
an expression is True. This structure is available in the Calc/Logic and Action function blocks.
The following example illustrates the WHILE-DO-END_WHILE structure:
Expressions
55
I := 1;
WHILE (I <= 5) DO
'^/PARAM1'[I][1]:= I + .12;
I := I + 1;
END_WHILE;
Note The indices are outside of the single quotes unless the .CV field is used. The parameter syntax must be exactly
as shown in the example ('^/PARAM1'[I][1]). It is recommended to show all access to the matrix parameter (an input
or output parameter defined as a floating point array type) using two dimensions where the second is always [1].
Warning If a WHILE loops more than 1998 counts, the loop will be stopped, BLOCK_ERR and MSTATUS will be
set, and the loop will not be executed until the module is downloaded.
Exit
This structure prematurely exits the innermost WHILE-DO loop currently being executed. The EXIT statement can
only appear inside the statements of a WHILE_DO loop.
The following example illustrates using EXIT in a WHILE-DO loop:
I := 1;
WHILE (I <= 5) DO
'^/PARAM1'[I][1]:= I + .12;
IF ('^/PARAM1'[I][1] > 5) THEN
EXIT;
END_IF;
I := I + 1;
END_WHILE;
Note This command is only available in the Calc/Logic and Action function blocks because that is where the
WHILE-DO construction is supported.
GOTO label
The GOTO label structure transfers processing to the statement identified by the specified label. A label definition is
a string followed by a colon (:).
The following example illustrates the GOTO label construct:
REM This expression takes IN1 to the IN2 power
cnt:=0;
answer:=1;
REM The following statement creates the label begin
begin:
IF cnt>=IN2 THEN
GOTO end;
END_IF;
answer:=answer*IN1;
cnt:=cnt+1;
GOTO begin;
end:
OUT1:=answer;
56
System Configuration
Assignment Assigns the result of an expression to a destination. For example, the following action text
sets a parameter to 1:
'//XV-101/DC1/SP_D':=1;
Boolean Sets a destination to TRUE. This destination must be a module-level Boolean parameter of the
module you are working on. The action text for this type of action is the Boolean parameter, and the action
qualifier defines the action (when to set this parameter to TRUE). For example, if you want to set a Boolean
parameter to TRUE for the module called MPARAMETER, enter the following action text:
MPARAMETER
Non-Boolean Executes a specific block. This block can be either a composite block or a function block,
but it must be in the module you are working on. Action Text for this type of action is the function block
name. The action qualifier defines the action (when to execute this block). For example, to execute a PID
block called PID1, enter the following action text:
PID1
Tip To add a block to an SFC, select the Hierarchy View. Click the right mouse button and then click Add. Select the
type of block to add, and answer the questions.
Note Blocks that are not referenced by a non-Boolean action run continuously in the controller.
This expression assigns the value of 2 times the RADIUS to the DIAMETER variable:
DIAMETER := 2.0 * RADIUS;
This expression assigns the value of 2 times pi times the RADIUS to the CIRCUMFERENCE variable:
CIRCUMFERENCE := 2.0 * pi * RADIUS;
This expression assigns the value of pi times the RADIUS squared to the AREA variable:
AREA := 3.14 *(RADIUS * * 2);
These expressions assign the variables to outputs of the Calc/Logic function block:
OUT1 := DIAMETER;
OUT2 := CIRCUMFERENCE;
OUT3 := AREA;
Expressions
57
Some keywords are reserved for DeltaV expressions and cannot be used as local variable names. Refer to the
Keywords topic for information on the reserved keywords.
From the above information, it is apparent that variables do not have to be declared. They are assumed to be variables
because of the absence of quotation marks (,) around their names. Variable names are not case sensitive.
All variables are floating point numbers. The value of a variable is retained from one scan to the next. The initial (first
scan) value of a variable is zero.
The scope/visibility of variables is limited to the Calc/Logic function block in which they exist.
VAR...END_VAR; This structure is used to declare local variables in expressions in CALC function
blocks. If the Option Explicit statement is used it must be followed by VAR...END_VAR to declare local
variables. Otherwise, any temporary variables that are not declared within the VAR...END_VAR structure
(when using Option Explicit) will not be accepted by the structured text parser.
Option Explicit; (* This is optional.*)
VAR
(* Used to declare local variables *)
T63;
T64;
T17;
T18;
END_VAR;
T63 := .5;
T64 := -15.803;
T17 := SIGN(T63);
T18 := SIGN(T64);
T62 := 88; (* This will give an error with the option explicit since no
T62 declared; otherwise no error is flagged. *)
(* *) - This is a comment notation. Anything between "(*" and "*)" is treated as a comment, even if it spans
lines. These comments do not nest. The first occurrence of "*)" will terminate the comment no matter how
many instances of "(*" have occurred. The content of this comment has no effect on any processing.
REM - This denotes that a remark is following. Text on the line following "REM " (note the space after
REM is required) is treated as a comment. The content of this statement has no effect on any processing.
Temporary Variables
Temporary variables allow you to simplify complex calculations by using variables to temporarily store values.
The following rules apply to temporary variables:
58
System Configuration
I/O References
You can reference I/O signals in your expressions and use them in your calculations. You need to supply the full path
of the signal, and possibly the parameter. For example, if you were referencing the input signal on the first channel,
CH1, of the second card, C02, in a controller's subsystem, and the controller was CTRL3, the reference to that
channel in your expression could look like this:
'//CTRL3/IO1/C02/CH1/FIELD_VAL_PCT
When you are reading data from a channel, you do not have to specify the parameter field. If you do not specify a
field, the default (.CV) field is implied.
When you are writing data to a channel, you can reference specific parameters. If you do not specify a field, the
default (.CV) field is implied.
You can read and write data to the I/O channels in your expressions to obtain the behavior you want. For example,
suppose you wanted to convert an analog value to its corresponding temperature in Celsius. For this example, assume
you have a temperature transmitter that sends an analog signal of 1 to 5 Volts. The voltage corresponds to a range of 0
to 200C, and you want to convert the analog value to a temperature value so that you can display it for the operator.
First, you need to know which channel the 1-to-5 volt signal is on. For this example, assume that it is the signal on the
channel we used previously.
For the calculation, you would need to subtract 1.0 from the voltage because the temperature scale is zero-based.
Then, you would need to multiply the value by 50 because 1.0 volt corresponds to 50 degrees in this example. The
expression for the conversion might look like this:
CELSIUS := '//CTRL3/IO1/C02/CH1/FIELD_VAL_PCT' *(4.0/100.0)* 50;
Expressions
59
'array'[row][column]
In this form the array index references (row and column) are outside of the single quotes. The row and
column specifiers can be variables or expressions. This form returns the default field (.CV) value of an array
element. The index values are checked against the matrix definition.
For example:
'ARRAY1'[MY_INDEX][2*abs(a)]
The row index value is a variable and the column index variable value is an expression.
'array[row][column].field'
In this form the entire array reference is enclosed in single quotes and field is required. In this form row and
column specifiers must be integer constants. The index values are checked against the index dimensions.
You must use this form to access fields other than CV.
For example:
'ARRAY1[2][3].AWST'
Note Matrix Parameter indices start at 1 but an index of 0 (zero) is interpreted as 1. For example, an index of [0][0] is
interpreted as [1][1].
60
System Configuration
Use either of these forms to access array elements in expressions. Note that you must enter array indexes manually in
the expression editor.
To add and display historical array parameters, the syntax must be entered as follows:
'Module/reference[2][1].CV'
To display and use the array parameter in DeltaV Operate, reference the array on the graphic as follows:
'DVSYS.Module/reference[2][1].F_CV'
Note The DeltaV system updates array parameter values in the workstations every 10 seconds. Array values that
change more frequently than 10 seconds cannot all be properly displayed at the workstations.
When using matrix parameter referencing and the array resides in a different controller from the module writing to it,
create the logic (in the module) to confirm each array element write before attempting the next array element write.
Confirmation is not needed if the array and module both reside in the same controller.
The following expression multiplies the input, IN1, by 2.0 and pi to compute a temporary variable:
CIRCUM := IN1 * 2.0 * 3.14;
The following expression assigns the value of the input, IN1, to the output, OUT1:
OUT1:= IN1;
The following expression assigns the status field of input to the status field of the output:
'OUT.ST' := 'IN2.ST';
Note The single quotes are required when a parameter field (CV or ST) is appended.
External References
External references are a built-in feature of the DeltaV software that allows you to refer to any input, output, or
parameter that is available in any module in the DeltaV system. These external references are best configured by
using the parameter browser available in all the expression dialogs. The browser brings up a graphical list of areas,
blocks, and parameters. By selecting a parameter from the browser, you can avoid the potential of typographical
errors and case-sensitivity when referencing block parameters.
Note When using a reference field other than the .CV field, you will need to type the field name. Refer to the External
Reference Parameter topic for field descriptions.
References are denoted in expressions by surrounding the reference in single quotes (' '). Paths to external references
are denoted by double slashes (//). For example, if a block in module LOOP1 is named BLOCK1, an external
reference to a parameter in BLOCK1 looks like:
Expressions
61
IF ('//LOOP1/BLOCK1/MODE.ACTUAL' = MAN)THEN
OUT1 := 5.0;
ENDIF;
Internal References
Internal references are DeltaV built-in parameter data types. They allow you to refer to any input, output, or
parameter that are available within the current module or phase. The best way to configure internal references is by
using the parameter browser available in all of the expression dialogs. By selecting a parameter from the browser, you
can avoid the potential of typographical errors and case sensitivity when referencing block parameters.
Note When using a reference field other than the .CV field, you will need to type the field name. Refer to the Internal
Reference Parameter topic for field descriptions.
For a module, MOD, that contains the composite, COMPOS2, that contains the composite, COMPOS1, that contains
the function block, PID1, all of the internal references shown below refer to the same parameter:
Module relative /COMPOS2/COMPOS1/PID1/GAIN
Module relative /PID1/GAIN
Block relative ^/COMPOS1/PID1/GAIN
For phases, a reference to a phase parameter looks like:
Phase relative /+/WDOG_STATE.CV
Dynamic References
A dynamic reference parameter is a variation of the external reference parameter that lets you define a path to a value
that is selected at run-time during execution of the algorithm. The selection is based on information not available at
configuration (for example, an operator entry, a recipe parameter passed from batch control, or a run-time value of a
control variable).
The best way to configure dynamic references is by using the parameter browser available in all of the expression
dialogs. By selecting a parameter from the browser, you can avoid the potential of typographical errors and case
sensitivity when referencing block parameters. Refer to the Dynamic Reference Parameter for field descriptions.
Dynamic references are established by assigning a parameter reference path string to the .$REF field of a dynamic
reference parameter. For example, if a tank has two input valves, INLETA and INLETB, the value for the dynamic
reference parameter, INLET.$REF, can be assigned the setpoint of INLET_A using a statement such as:
'INLET.$REF' := "//INLETA/SP"
Following is an example using a string variable to store the parameter reference path:
'STRINGVAR' := "INLETA/SP"
'INLET.$REF' := 'STRINGVAR'
62
System Configuration
button on the Browse Dialog to check the type of parameter that you are
For a numeric value, the expression would look similar to the following:
'//CTLR1/IO1/C02/CH02/STATUS' = 0;
Strings
Strings can be used in all types of expressions in the DeltaV system. The use of strings allows great flexibility when
constructing or selecting parameter reference paths in internal, external, and dynamic reference parameters.
A reference parameter/field can be assigned a string constant or a string variable. String constants are enclosed in
quotation marks (" "). String variables are enclosed in single quotes (' ').
Note Strings referring to module names and associated paths must always use uppercase letters.
Supported string functions are described below.
// empty string
constant
Numeric Value to String Conversion If the right side of the assignment evaluates to a numeric value and
the left side of the assignment is a string parameter, the numeric value is converted to a string, and the string
is assigned.
String to Numeric Value Conversion If the right side of the assignment evaluates to a string value and
the left side of the assignment is a numeric parameter, the string is converted to a float, which is then
converted to the type of the numeric parameter.
Expressions
63
String Comparison Using Relational Operators Two relational operators, equal (=) and not equal (!=),
can be used to compare string parameter/fields or string constants, as in the following:
IF
THEN
IF
THEN
IF
THEN
IF
THEN
('OUTLET_POS.$REF' = "VLV1004/AO/OUT.CV")
("VLV1004/AO/OUT.CV" != 'OUTLET_POS.$REF')
('TEMPSTR2.CV' = 'TEMPSTR1.CV')
('TEMPSTR2.CV' != 'TEMPSTR1.CV')
String Concatenation The full path is constructed from a partial path string (for example, a module name)
and concatenated with a another string (such a string constant) using a plus operator (+). For example:
'OUTLET_POS.$REF' := 'MODULE.CV' + "/PID/SP.CV";
Note Strings written from expressions are limited to 256 characters. The software does not check if the limit is
exceeded and no messages appear. You must ensure that strings written from expressions are no longer than 256
characters.
If one of the terms is a string and the other is numeric, the numeric term is converted to a string and the two strings are
concatenated, resulting in a string. For example:
'TEMPSTR.CV' := "FIC";
'TEMPNUM.CV' := 105;
'TEMPSTR2.CV' := 'TEMPSTR.CV' + 'TEMPNUM.CV''
IF 'TEMPSTR2.CV' = "FIC105" THEN // would be true
String Selection Function (SELSTR) The SELSTR function allows selection from up to five string
constants or string parameters, based on an input to the string selection function. It is intended to take the
place of a series of IFTHEN statements and temporary string parameters.
SELSTR takes float one term (expected to hold an integer value) and five string terms (usually string constants),
returning a string that corresponds to the value of the float term:
Float Value
String Returned
<1.0
empty string
>=6
empty string
64
System Configuration
For example:
'OUTLET_POS.$REF':= SELSTR('SEL.CV',
"FIC101",
"FIC102",
"FIC103",
"",
"") + "/PID1/SP.CV";
Operands
An operand is the data or item in the expression that is operated on. All values are managed as floating point data.
This includes parameters of function blocks that are floating point values.
The valid operands in an expression are:
Inputs (references to inputs of a function block that are float with status data types).
Outputs (references to outputs of a function block that are float with status data types).
Input Device Signal Tags (DSTs) (references to input signals that are float with status data types.
Note The expression evaluator is stack oriented and allows a maximum of 32 operands and operators. The use of
parentheses to organize the expression minimizes the stack usage. The equations are evaluated using RPN (Reverse
Polish Notation).
Operators
Operators allow you to make complex calculations with arithmetic operations within expressions. Operators use
operands to act upon. Normally, operators are used in the following order:
Operand1
Operator
Operand 2;
For example:
OUT1 := 5;
This example shows the use of the addition operator:
OUT1 :=5 + 5;
Normally, the value of the calculation is assigned to either an output, external reference, or temporary variable. The
following operators are supported in DeltaV expressions:
+, -, *, /, AND, OR, NOT, XOR, MOD, !, =,<>, ~=, !=, <, >, <=, >=, **, :=, (,), x?y:z, ~, ^,&, %
Note The equality operator (=) takes precedence over the AND and OR operators. However, it is important to write
your expressions using parenthesis so that the result is as expected.
Expressions
65
Operator Description
Operator
Description
Notes
Multiply
Divide
Add
Subtract
?:
Conditional
66
System Configuration
Operator
Description
Notes
&
Bitwise AND
The AND (bit) operator compares each bit of its first operand to
the corresponding bit of its second operand. If both bits are 1, the
corresponding resultant bit is set to 1. Otherwise, the
corresponding resultant bit is set to 0.
AND
Logical AND
Bitwise OR
OR
Logical OR
Bitwise NOT
! or NOT
Logical NOT
Bitwise
Exclusive OR
The OR (bit) operator compares each bit of its first operand to the
corresponding bit of its second operand. If one bit is 0 and the
other bit is 1 (non-zero), the corresponding resultant bit is set to 1.
Otherwise, the corresponding resultant bit is set to 0.
XOR
Logical
Exclusive OR
Expressions
67
Operator
Description
Notes
MOD or %
Modulus
operator
Equality test
>
Greater than
<
Less than
>=
Greater than or
equal to
<=
Less than or
equal to
!= or <> or ~=
**
Raise to power
The power operator computes the first operand raised to the power
of the second operand. If the first operand is negative and the
second operand is not an integer, the result is zero.
:=
Assignment to
output
Note The expression evaluator is stack oriented and allows a maximum of 32 operands and operators. The use of
parentheses to organize the expression minimizes the stack usage. The equations are evaluated using RPN (Reverse
Polish Notation).
68
System Configuration
Operation
Symbol
Order of
Evaluation
Parenthesis
(Expression)
Nonassociative
Raise to power
**
Left
Logical NOT
Bitwise NOT
! or NOT
~
Left
Multiply
Divide
Modulus Operator
*
/
MOD or %
Left
Add
Subtract
Unary minus
+
-
Left
Equality test
Greater than
Less than
Greater than or equal to
Less than or equal to
Does not equal
=
>
<
>=
<=
!= or <> or ~=
Left
Bitwise AND
&
Left
Bitwise Exclusive OR
Left
Bitwise OR
Left
10
Logical AND
AND
Left
11
Logical Exclusive OR
XOR
Left
12
Logical OR
OR
Left
13
Conditional
?:
Right
Functions
The DeltaV software supports a wide variety of functions. DeltaV functions are generally in the following format:
FunctionName( param1, param2, ..., paramN)
Note that the function name is followed by a parenthesis, and the parameters of the function are separated by
commas. These functions can be used in either the Assignment or IF-THEN-ELSE-END_IF expression constructs.
Expressions
69
Expression Functions
Function
Description
Notes
ABS (x)
Absolute value of x
ACOS (x)
Arc cosine of x
ASIN (x)
Arc sine of x
ASR16 (i,n)
ATAN (x)
Arc tangent of x
COS (x)
Cosine of x
EXP (x)
Exponential of x
EXPT (x,y)
EUP (e,p0,p100)
Conversion from
Engineering Units (EU)
(e) to percent given the
values at 0% (p0) and
100% (p100).
FRACT (x)
LN (x)
Natural logarithm of x
LOG (x)
Log base 10 of x
LOG2 (x,y)
Log base x of y
70
System Configuration
Function
Description
Notes
LOGEVENT
MAX (x,y)
Maximum of x and y
MIN (x,y)
Minimum of x and y
PEU (p,p0,p100)
ROL (x,y)
ROR (x,y)
ROTL (x,y)
ROTL16 (i,n)
ROTR (x,y)
ROTR16 (i,n)
ROUND (x)
SELSTR (x,a,b,c,d,e)
Select a string
Expressions
71
Function
Description
Notes
SHL (x,y)
SHR (x,y)
SIGN (x)
Sign indicator of x
SIN (x)
Sine of x
SQRT (x)
Square root of x
STR_TO_TIME (x)
Epoch time of x
STBT (i,b,n)
SYSSTAT (x)
TAN (x)
Tangent of x
TIME (x)
Time of x, where x is a
named set value of
$time_format
TIME_TO_STR (x, y)
Time y expressed in
format x
TRUNC (x)
Floor function
Constants
Constants are predefined, unchangeable values in expressions. These constants let you test values against DeltaV
system values without you having to know their internal representations.
72
System Configuration
Explanation
FALSE
TRUE
Note Comparing TRUE/FALSE constants in an expression should only be used against Boolean elements or when
the floating point value is either 0.0 (FALSE) or >=1.0 (TRUE).
DeltaV Status Constants
Status constants are implemented as an 8-bit status word. The numeric value of the status word is determined by
which bits are set.
A CALC block's OUT parameters default to a status of GOOD (128). The expression must explicitly set the status.
Status propagation is not automatic in the Calc block. You can set the status to a numeric value (refer to the topic
Function Block Status Values).
You can also use the GOOD, BAD or UNC constants (for example, 'out1.st' := UNC). There are also constants for the
limit status (the two least significant bits of the status word). If the signal is also limited or constant, you can use these
additional constant words (LIMITED_CONSTANT, LIMITED_HIGH, LIMITED_LOW), but you must combine
them with the status constant (GOOD, BAD, UNC). For example, to set the status to GOOD High Limited, use the
expression 'out1.st':= GOOD | LIMITED_HIGH. The "|" operator is a bitwise OR function. The expression writes a
value of 130 to the status.
Constant
Explanation
BAD
GOOD
LIMITED_CONSTANT
LIMITED_HIGH
Expressions
73
Constant
Explanation
LIMITED_LOW
UNC
Explanation
AUTO
CAS
When a mode parameter is connected to an input and compared to CAS (cascade) using
the equality operator (=), the result will be TRUE if the Actual mode is set to CAS. If
CAS is used for assignment, the cascade Target mode will be written. The numeric
value of the CAS constant is 32.
Note The CAS constant is not compatible with fieldbus block modes. The Fieldbus
specification calls for the AUTO bit and the CAS bit to be set in order to request the
CAS target mode. For fieldbus function blocks, use the numeric value 48 to set the
target mode to CAS. This value (48) sets both the AUTO bit (16) and the CAS bit (32).
IMAN
LO
MAN
OS
74
System Configuration
Constant
Explanation
RCAS
ROUT
A manual mode where the OUT value is supplied by an external control program rather
than directly by the operator. OUT is supplied through the ROUT_IN parameter. The
block maintains a back calculation output value (ROUT_OUT) to provide bumpless
transfer when the mode is changed.
These constants can be used as numerical values only. Never assign values to constants or use these reserved words as
temporary variables in Calc/Logic blocks.
Comments
Comments are statements placed in an expression that act solely as a documentation tool for users. They have no
effect on the expression. The structures of a comment can take two forms:
REM A single line comment. Any text placed on a line that follows the line that this keyword is on is
ignored. The following example demonstrates a comment using this structure:
(* *) A multiline comment structure that must have the start and the end comment operator to be complete.
The following example demonstrates a comment using this structure:
Keywords
The following are reserved keywords in the DeltaV expressions, and they cannot be used as variable names:
ABS
EXP
MAX
SHL
ACOS
EXPT
MIN
SHR
AND
EUP
MOD
SIGN
ASIN
FALSE
NOT
SIN
ASR16
FRACT
OR
SQRT
ATAN
GOOD
OS
STBT
AUTO
GOTO
PEU
SYSSTAT
Expressions
75
BAD
IF
REM
TAN
CAS
IMAN
ROL
THEN
COS
LIMITED_CONSTANT
ROR
TRUE
DO
LIMITED_HIGH
ROTL
TRUNC
ELSE
LIMITED_LOW
ROTL16
UNC
END_IF
LN
ROTR
VAR
END_VAR
LO
ROTR16
XOR
END_WHILE
LOG
ROUND
WHILE
LOG2
SELSTR
MAN
IDLE
ACTIVE
STOPPED
COMPLETED
BLOCKED
Start Sequence
Stop Sequence
Reset Sequence
The COMMAND parameter of the SFC module reflects the commands that transition the SFC into different states.
The following figure shows the state transitions and commands for SFCs:
76
System Configuration
Expressions
77
Actions
Each step is associated with a number of actions. An action can assign a parameter value, set a variable, or run a
function block. Therefore, there are three different types of actions:
Assignment assigns the result of an expression to a variable. When an assignment action is active, the
specified expression is evaluated, causing the destination parameter to be written with the result. No special
action is taken when the transition to inactive occurs.
Boolean references a module-level Boolean parameter of the module you are defining. The associated
Action Text is the Boolean parameter. The action qualifier determines when the parameter is set to TRUE.
Non-Boolean references a function block that is in the module hierarchy. The Action Text is the function
block name. The action qualifier defines when the function block executes.
Note You cannot write directly to a Device Signal Tag (DST) value in an action, even though the action parser allows
you to configure it.
Each action must have a configured action qualifier, which helps define when the action is active. Whether or not an
action is active can be determined given its action qualifier and the step that is associated with the action. The step
that is associated with an action is the step that initiated the action.
Note If an action modifies a destination while that destination is currently being updated by an active action, the
results will be unpredictable.
There are two basic types of action qualifiers: non-stored and stored. An additional type of qualifier, the reset action
qualifier (R), is used in conjunction with stored qualifiers to reset a stored action.
Non-Stored Action Qualifiers:
N Non-Stored
L Time Limited
D Time Delayed
P Pulse
Stored Action Qualifiers:
S Set (Stored)
SD Stored and Time Delayed
DS Delayed and Stored
SL Stored and Time Limited
Actions with a non-stored type of qualifier are only active while the associated step is active or for a portion of the
time that the step is active, depending on the specific qualifier.
Actions with a stored type of qualifier either are active for only a portion of the time that the associated step is active
or remain active after the associated step has gone inactive, depending on the specific qualifier.
78
System Configuration
Note Actions within a step are initially executed at step time=0 seconds. This affects the execution of time-relation
actions. For example, if you configure a step action with a time delay of 10 seconds (time>=10), that step action is
idle from step time=0 to step time=10. When the step time>=10 seconds, the action is executed. It is important to use
the >= operator to ensure that the transition will trip when running on a heavily loaded system or when the system is
being downloaded. Using time=10 operator requires that the time be 10 seconds and no more or less. If the timer
count is 10.1 due to a download, then the action will not trip. Using >= allows that step to trip at any point
immediately after 10 seconds.
A third type of action qualifier, the overriding reset (R) qualifier is used to reset a stored Boolean or Non-Boolean
action. For example, if you want to start an action in Step 1 and continue it until Step 5, you can either use a nonstored qualifier for the first four steps, or you can use a stored qualifier in Step 1 and a reset in Step 5. You can also
reset a stored qualifier by performing an assignment action and setting the active parameter of the action to False.
This is the only way to reset a stored assignment action. Refer to the Overriding Reset (R) Qualifier for Resetting
Stored Actions topic for more details.
Note The order of execution of actions in a given SFC step is effectively in parallel. The order of the actions in the
Action View does not imply any execution order in the controller.
Expressions
79
The assignment statement is evaluated (and the assignment made) on each scan through the step actions until either
the time limit specified as part of the action configuration is met or the step goes inactive.
Boolean Action
The Boolean destination referenced is written to TRUE for each scan through the step actions until either the time
limit specified as part of the action configuration is met or the step goes inactive.
Non-Boolean Action
The function block referenced is evaluated for each scan through the step actions until either the time limit specified
as part of the action configuration is met or the step goes inactive.
80
System Configuration
Expressions
81
If A1 was not reset, it would stay active and keep the same output. (The delay would not recur.) So, if you did not
want the delay to occur every time through the sequence, you would not reset the action every time. The same is true
for a Time Delayed and Stored (DS) qualifier.
The only difference between the Stored and Time Delayed (SD) and the Time Delayed and Stored (DS) qualifier
occurs when the step goes inactive before the delay is finished. If this happens before the delay is complete in an SD
action, the action is stored, but in a DS action if the step goes inactive before the delay is complete, the action is not
stored because the delay did not complete.
Note When the SFC stops, all actions stop.
Also note that when the SFC stops, all actions stop. Therefore, you cannot have a stored action reset the sequence
when the sequence stops.
Assignment Action
The assignment statement is evaluated (and the assignment made) on each scan through the step actions, once the
time delay specified as part of the action configuration is met. The action actually goes active (and can be reset) when
the step initially goes active. The action then stays active until a reset action is evaluated for this assignment
statement. Refer to the reset action qualifier (R) description to see how a reset can be done for an assignment action.
Boolean Action
The Boolean destination referenced is written to TRUE for each scan through the step actions, once the time delay
specified as part of the Action configuration is met. The action actually goes active (and can be reset) when the step
initially goes active. The action then stays active until a reset action is evaluated for that same Boolean destination.
Refer to the reset action qualifier (R) description to see how a reset can be done for a Boolean action.
Non-Boolean Action
The function block usage referenced is evaluated for each scan through the step actions once the time delay specified
as part of the action configuration is met. The action actually goes active (and can be reset) when the step initially
goes active. The action then stays active until a reset action is evaluated for that function block usage. Refer to the
reset action qualifier description to see how a reset can be done for a non-Boolean action.
82
System Configuration
Expressions
83
A1 references a Boolean parameter called PARAM1. When the step S1 becomes active, the action A1 becomes active
and the parameter PARAM1 is set to TRUE. In summary, you have an action A1 with:
Type:
Boolean
Qualifier:
Stored
Text:
'/PARAM1/
A1 stays active after the step becomes inactive because it is a stored action. Therefore, the parameter, PARAM1,
continues to be set to TRUE until you reset the action. To reset the action and the Boolean parameter, PARAM1, you
must create a step with an action that has a reset qualifier. For example, if you wanted to reset the Boolean parameter,
PARAM1, during step S3, you could define a Boolean action for step S3 that has a Reset action qualifier and uses
PARAM1 for the action text. Then, when S3 becomes active, PARAM1 is reset. In summary, you would create an
action with:
Type:
Boolean
Qualifier:
Reset
Text:
PARAM1
84
System Configuration
You can use this approach for either a Boolean or a non-Boolean action. However, to reset an assignment action, you
must write the reset text differently. For example, suppose the same SFC contains a stored assignment action, A2, in
step S1. When the step S1 becomes active, A2 becomes active and increments the parameter, PARAM2. In summary,
you have an action A2 with:
Type:
Assignment
Qualifier:
Stored
Text:
'PARAM2' := 'PARAM2' + 1;
The action stays active after the step becomes inactive because it is a stored action. Therefore, the parameter,
PARAM2, continues to be incremented until you reset the action. To reset an assignment action, you must make the
action inactive. You do this by setting the ACTIVE parameter to False. Therefore, you would create a non-stored
action that sets 'S1/A2/ACTIVE' to False. For this example, you could use a Pulse (P) action qualifier. In summary, to
reset the assignment action, A2, you would create an action with:
Type:
Assignment
Qualifier:
Pulse (P)
Text:
'S1/A2/ACTIVE' := False;
Note If there is a parallel divergence in your sequence, you must put the reset action in all of the paths of the parallel
divergence to make sure that the action gets reset.
Expressions
85
If a confirm condition times out (the Confirm Timeout time expires or the Confirm Timeout expression becomes
TRUE before the Confirm expression becomes TRUE), the FAILED_CONFIRMS parameter is incremented by 1 and
the CONFIRM_FAIL parameter is set to TRUE.
The CONFIRM_FAIL parameter is available at the action level, the step level, and in the SFC. It can be used to send
an alarm so that the operator can take appropriate action.
It is left to the user to configure the transition (following the action with a confirm) to allow confirmation to occur.
This can be achieved by the transition expression being:
'S2/PENDING_CONFIRMS.CV' = 0 AND 'S2/CONFIRM_FAIL.CV' = False
An action with a pulse qualifier can have a built-in delay. This is useful when one or more pulse actions in a step do
not occur immediately after the step becomes active. For example, delays can be used to achieve sequencing within a
step. In this case, each action in the step (except the first one) has a delay configured. The second action is delayed
until the first is completed. The third is delayed until the second is completed, and so on. This technique offers several
advantages. Using a single step can help simplify complex diagrams. If a sequence must occur very quickly, doing the
sequence in a single step can avoid the one-scan delay required by each transition expression.
A delay uses either a delay time value or a delay expression. To add a delay time or expression, select the action and
go to the Action Properties dialog's General tab. As a default, there is no delay time on an action with a pulse
qualifier. If you want an action to be delayed until the previous action has completed, select Expression and enter a
delay expression. Typically, the previous action will already have a confirm expression configured. The delay
expression can check the previous action's state to see when it is complete. The previous action's state will be
complete when its confirm expression evaluates to true. Then, the delay expression will evaluate to true, causing its
pulse action to occur.
The delay expression checks the STATE parameter of the previous action. The path is StepName/ActionName/
STATE. The following example delay expression checks to see if the value of the STATE parameter in action A1 of
step S1 is complete.
'S1/A1/STATE.CV' = '$sfc_action_states:Complete'
86
System Configuration
Standard alarm detection (PV alarms) is provided in the input and PID function blocks. The alarm limits are
configured within the function block. When the alarm condition is detected, the alarm active parameter is set
to 1 (for example, the high limit has been exceeded: HI_ACT = 1).
Custom alarms can be applied to any parameter within a control module. When the parameter is non-zero,
the alarm is set to active (1).
Fieldbus device alarms are generated by fieldbus devices based on the built-in fieldbus device alerts and
PlantWeb alerts when the device alarms are enabled.
HART device alarms are generated by the system based on internal device information. The DeltaV system
polls the HART devices and translates the information into DeltaV alarms.
Asset alarms are generated by external, mechanical assets such as turbines, engines, pumps, and motors and
by external, optimization assets. Asset alarms are integrated into the DeltaV system through an External
Asset Server running on an Application Station.
The DeltaV Operate application provides special preconfigured displays that show operators the most important
active alarms under their control. Active alarm lists can be shown by plant area or unit. With the appropriate security
keys, the operator can acknowledge alarms and suppress noisy alarms until the cause can be resolved.
This section refers to alarms generated in function blocks and modules as process alarms because they are typically
triggered by a process change. This section also refers to alarms that are derived from a fieldbus or HART device as
device alarms.
custom alarms
Standard alarms consist of HIGH-HIGH, HIGH, LOW-LOW, LOW, DEVIATION HIGH, and DEVIATION LOW.
Standard alarms are only available in function blocks with built-in alarm state computation.
87
Custom alarms are supported at the module level (except unit modules and phase logic modules). Custom alarms
reference existing parameters or user-defined expressions. A custom alarm can be used as an alarm for the operator or
an event to be logged. You customize the alarm by selecting from a set of options.
DeltaV process alarms require alarm calculation and alarm detection.
Calculation - Many DeltaV function blocks include alarm state calculations. Any Boolean parameter can provide the
alarm calculation component for a module. This component is the input to alarm detection. You can also create your
own alarm state calculations by using function blocks that support expressions (for example, the Calc/Logic and
Condition function blocks).
Detection - In order for a module to detect the result of an alarm state calculation, you must associate the result of
that calculation with a specific alarm parameter. When the alarm state calculates to the TRUE value, the associated
alarm parameter triggers.
For the standard alarms, simply select the function block on the diagram, click the right mouse button, and then click
Assign Alarm. The software determines the detection parameters for you. For custom alarms, click the alarm view
pane (lower-right window in Control Studio), click the right mouse button, and then click Add. You select the
detection parameters for the alarm.
88
System Configuration
89
Plant Areas
Each module is associated with a single plant area. Even if the module appears in the DeltaV Explorer under a unit
module and the unit module is under a process cell, they are all under a plant area and, therefore, are associated with
that plant area.
Devices and Area Association
Fieldbus and HART devices are also associated with areas. If the device is not associated with a control strategy its
area defaults to the area of its associated controller or Logic Solver.
HART Device Area Association - HART device alerts default to the associated controller's alarm area (in the case of
Logic Solvers, this is the Logic Solver's alarm area.). If you configure and saved an I/O block in a module that
references the DST for the HART Device, the module's area becomes the alarm area for the device alerts. This area
remains the associated alarm area until the reference or the module is deleted. If you delete the module, the area
returns to the default controller area. If you rename the module, the new name is reflected as the associated module
name for the device alerts. Also, if a second module is created with an I/O block referencing the same DST, the area
remains assigned to the first module.
To change the area assignment, you must first delete the existing I/O reference in the existing module and then
configure and save the different module with a new I/O reference.
You can find the area and module that the HART device alarms are currently associated with from the Alarms &
Displays tab of the device properties dialog as shown below.
90
System Configuration
Fieldbus Device Area Association - When you assign a module's function block to the primary function block in a
fieldbus device, the device is associated with the plant area (and unit) that contains the referencing module. The
primary function block of a device is the function block with the lowest block index number. This block normally
appears as the first block under the device in the DeltaV Explorer. For fieldbus devices, if the module is deleted or if
the module function block associated with the primary function block in a fieldbus device is deleted, the device
defaults to the area associated with its controller.
91
Note A module must also be assigned to the node where it is to execute (a controller or an Application Station is
acceptable for some modules). This is done by assigning (dragging and dropping) the module to the Assigned
Modules subsystem under the desired execution node.
If you do not want an operator to have the authority to control an area (that is, have write parameters in associated
modules), you can configure your system so that the operator has no parameter writing privileges (security write
keys) in that area. Subsequently, when that operator is logged on, alarms from that area are not displayed in the Alarm
Banner or the Alarm List pictures. This way, you can control which alarms are seen by a particular operator. To define
which areas a user is responsible for, define parameter security write keys for specific areas in the DeltaV User
Manager. For information on how to lock alarm parameters, refer to the Parameter and Function Security topic.
Additionally, you can configure the workstation to restrict control to only the areas assigned to the workstation
through the workstation's properties dialog. Therefore, when a user that has sitewide privileges logs on to the
workstation, that user can only affect control to the areas assigned to the workstation. This prevents a user from
controlling an area when the alarms cannot be displayed on the workstation. This is the default configuration when
you create a workstation.
The workstation shows the alarms it processes to DeltaV Operate only if the current user has any parameter security
write keys for the area that contains the alarm. For example:
Areas in the workstation's Alarms and Events
subsystem
Additionally, this user can only write to parameters in Areas C & D when logged on to this workstation (providing the
user has the key for the lock to which the parameter is assigned).
Alarm Priorities
Alarm priorities indicate to the operator the importance of an alarm. The priority affects the order in which alarms
appear in the Alarm Banner and the Alarm List pictures in DeltaV Operate.
The system presents all alarms that you configure with the same alarm priority the same way throughout the system.
If you modify the definition of a particular alarm priority, all alarms configured using that alarm priority will use the
new definition.
There are 12 possible alarm priority levels: numeric values 4 through 15 plus a special log only priority level (value
3). The highest priority value is 15 (it is used for the most important alarms). The lowest priority value is 4.
DeltaV systems prior to release 5.x used a priority system with three alarm priority levels plus the special log only
priority level (value 3):
0
CRITICAL
WARNING
ADVISORY
LOG
92
System Configuration
For backward compatibility, version 5.x no longer uses priority levels 0,1 and 2 in new configurations but will
automatically convert those old priority levels into one of the new levels (4-15).
Events with Log priority (level value 3) are not considered alarms. Use the Log priority to designate an event that is
important enough to be recorded in the Event Chronicle but is not something the operator needs to be aware of.
Events with Log priority are not displayed in the Alarm Banner and the Alarm List links and do not turn on the alarm
horn.
By default, only four of the 12 (plus Log) priority levels are available for configuring alarm parameters in the system:
Default Alarm Priority Definitions
Level
Value
Alarm
Priority
Name
Auto
Acknowledged
Auto Ack
Inactive
Horn Sound
15
CRITICAL
No
No
Buzz.wav
11
WARNING
No
No
Alert_tone.wav
ADVISORY
Yes
No
Beep.wav
LOG
Yes
No
none
You can define up to eight additional priorities using the DeltaV Explorer. You can also modify the alarm priority
names to better describe your alarm prioritizing system. Priority levels that are not explicitly configured are given the
same properties as the next higher configured priority level.
The acknowledged status of the alarm, the current alarm state, the priority value, and the time stamp on the alarm
determine the alarm's importance in the system. Alarms with the larger priority values have the higher importance.
Refer to the Alarm Importance topic for more information.
The following figure shows the dialog in the Explorer for an alarm priority.
93
94
System Configuration
Wave file - Determines the sound associated with active alarms of this priority. The DeltaV system includes several
WAV format files. When you download the system, these files are copied to \DeltaV\data\sounds. When an alarm
goes into the active state, the system plays a WAV file in a loop-back mode so that it sounds until the operator
acknowledges the horn. You can disable the sound for alarms of a certain priority by deleting the WAV file reference.
Alarms that are auto-acknowledged still play their wave files.
Alarm States
In the DeltaV system, alarms have six potential states, determined by the values of the fields of the alarm parameter.
The following table shows the relationship between the alarm states and values of the alarm parameter fields:
State
OPSUP
Field
ENAB
Field
CUALM
Field
LAALM
Field
NALM
Field
Suppressed
1 ("YES")
(either 0 or 1)
Determined
by alarm state
Determined by
alarm state
Forced to 0
("NO")
Disabled
0 ("NO")
0 ("NO")
Forced to 0
("OK")
Forced to 0
("OK")
Forced to 0
("NO")
Inactive
acknowledged
0 ("NO")
1 ("YES")
0 ("OK")
0 ("OK")
0 ("NO")
Active
unacknowledged
0 ("NO")
1 ("YES")
Non-zero
(alarm word)
Non-zero
(alarm word)
1 ("YES")
Active
acknowledged
0 ("NO")
1 ("YES")
Non-zero
(alarm word)
Non-zero
(alarm word)
0 ("NO")
Inactive
unacknowledged
0 ("NO")
1 ("YES")
0 ("OK")
Non-zero
(alarm word)
1 ("YES")
Any time the state of an alarm changes, the system updates the alarm's information in DeltaV Operate and generates
an alarm state change event that can be recorded in the Event Chronicles.
Alarm Types
An alarm type defines a set of characteristics that determine how alarms appear on displays and in the Event
Chronicle. Each standard alarm is associated with one of these alarm types. If you create a custom alarm, you select
or create the alarm type associated with it. Device alarms do not require alarm types. The alarm words are defined by
the device's definition data, and the information communicated from the device is automatically converted into
device alarm messages.
Note that the alarm type does not define an alarm calculation for the alarm, you must define the alarm calculation for
custom alarms. See Custom Alarm Calculation for more information. A single alarm type can be assigned to several
alarms to give them the same display characteristics.
There are 19 predefined alarm types. You can use these alarm types as they are, modify them, or create additional
ones. Alarm type names are case sensitive.
95
Alarm
Word
Category
Alarm
Message
ADAPT
INSTRUMENT
Any Alarm
ANY
SYSTEM
CFN
PROCESS
Change of State
COS
PROCESS
Change of State
Communication Error
COMM
INSTRUMENT
Communication Error
Deviation Alarm
DEV
PROCESS
Discrete Device
FAILED
PROCESS
%P1
FLT
SYSTEM
IOF
INSTRUMENT
High Alarm
HIGH
PROCESS
HIHI
PROCESS
INSPECT
INSTRUMENT
Low Alarm
LOW
PROCESS
LOLO
PROCESS
New Alarm
NEW
SYSTEM
OCD
INSTRUMENT
Overrange
OVER
INSTRUMENT
Rate of Change
RATE
PROCESS
Statistical Alarm
ERROR
SYSTEM
Underrange
UNDER
INSTRUMENT
Note %P1 and %P2 represent the values of user-defined parameters. When configuring an alarm with Control Studio,
check to see if the alarm message expects any user-defined parameters. If so, configure which parameter in that
module should be read at the time of alarm detection to replace the %P1 (and %P2) in the alarm message. Userdefined parameters typically capture the value that caused the alarm, the limit value that was in effect at the time the
alarm was detected, and so on.
When the custom alarm requires a message that is different from the available Alarm Types messages, you must
create a new alarm type. Before trying to use the alarm type in assigning an alarm to a module, you must create the
new alarm type.
The following figure shows the dialog in the Explorer for an alarm type.
96
System Configuration
97
For example, if you want the operator to see a message like the following for an alarm:
High Alarm 80 Alarm Limit 72
you would type the following in the alarm message box:
High Alarm %P1 Alarm Limit %P2
and use the following parameters for %P1 and %P2:
Parameter 1: PV
Parameter 2: HI_LIM
For process alarms, the alarm message affects all the alarms associated with the alarm type unless you override both
the message and message parameters for a specific alarm in Control Studio.
For device alarms, the alarm message is determined by the information available from the device for the most recent
condition change contributing to the alarm's activation. Fieldbus devices do not report a second condition
contributing to an alarm until the first condition clears. The only message displayed describes the first condition
causing the alarm.
Alarm Importance
The acknowledged status of the alarm, the current alarm state, the priority value, and the time stamp on the alarm
determine the alarm's importance in the system:
After the acknowledgement status is considered, alarms that are still active are considered more important
than alarms that have already cleared but have not been acknowledged by the operator yet.
When more than one alarm has the same acknowledgment status and active status, alarms with larger
priority values have the highest importance.
When more than one alarm has the same priority value, active status, and acknowledgment status, the newer
alarm has a higher importance.
For example, the most recent, acknowledged, active alarm with a priority value of 15 is the most important alarm in
the system. Then, a new alarm occurs that is unacknowledged and has a priority value of 4. This new alarm is of
higher importance than an acknowledged alarm with a priority value of 15 because of the acknowledgement status of
the alarms.
98
System Configuration
Alarm Configuration
Inside this topic
Configuring Standard Alarms
Standard Alarms Calculation
Standard Alarm Detection
Conditional Alarming
Deviation Alarming
Standard Alarm Presentation
Modifying Process Alarms
Configuring Device Alarms
Device Alarm Requirements
Enabling Device Alarms
Configuring Asset Optimization Alarms for PlantWeb Alerts
The following sections describe how standard and device alarms are configured. For information on how to create a
custom alarm, refer to the Custom Alarms topic. For information on alarm fields, refer to Events and Alarms
Reference topic.
Standard Alarms
DI function block
DISC
An example of a predefined alarm calculation is the HI alarm on the AI (analog input) function block. The HI alarm
compares the PV to a limit value as follows:
HI alarm is true if PV > Alarm Limit (HI_LIM)
To create a standard alarm, select the function block on the diagram in Control Studio, click the right mouse button
and then click Assign Alarm. On the Block Alarms dialog, select the alarms you want to use. The system provides
default information, including the name of the alarm, the alarm limit, and the alarm priority.
99
100
System Configuration
For example, the HI alarm shown in the preceding check box has the following parameters:
Conditional Alarming
The conditional alarming feature enables you to easily add alarm time delays and enable/disable alarms to minimize
nuisance alarms.
For example, when an upstream pump is turned off, the downstream low flow alarm is temporarily not meaningful.
The low flow alarm becomes a nuisance alarm when the pump is off and should be disabled. The LO_ENAB
parameter can be used to dynamically enable/disable the alarm. When this pump is turned back on, it may be best for
the low flow alarm to remain disabled for a short period of time, allowing the flow rate time to rise above the low
flow alarm limit. The LO_ENAB_DELAY parameter causes a delay in setting an alarm immediately after the alarm
has been enabled using the LO_ENAB parameter.
Function blocks and extended function blocks that have built-in standard alarms also support conditional alarming.
Conditional alarming for a function block is enabled by selecting the context choice Assign Alarm and then checking
the Conditional alarming check box. When conditional alarming is enabled, five new parameters are added to the
block for each available ACT parameter (HI_ACT, HI_HI_ACT, LO_ACT, LO_LO_ACT, DV_HI_ACT,
DV_LO_ACT and DISC_ACT). In the descriptions that follow, the term alarm_ is used to represent either HI,
HI_HI, LO, LO_LO, DV_HI, DV_LO, OR DISC, depending to the particular alarm being configured. The ACT
parameter indicates the current status of its alarm condition, with 1 (true) representing an alarm condition. The five
additional parameters are:
alarm_ENAB This parameter enables /disables conditional alarm processing for a single alarm. The default value
for this parameter is enabled (1), when conditional alarming for a function block is enabled. You can write to the
alarm_ENAB parameter to dynamically enable/disable the alarm based on external process conditions.
When alarm_ENAB is disabled (0):
alarm_DELAY_ON This parameter delays the time (in seconds) that it takes for alarm_ACT to be true (1) after the
alarm condition is detected. If the alarm condition clears before the delay time is reached, the alarm_ACT parameter
remains false (0) and the timer is reset. Every time the alarm condition clears, the timer resets.
alarm_DELAY_OFF This parameter delays the time (in seconds) that it takes for alarm_ACT to be set to 0 (false)
after the alarm condition clears. If the alarm condition reoccurs before the delay time is reached, the alarm_ACT
parameter remains true (1) and the timer is reset. Every time the alarm condition is detected, the timer resets.
101
alarm_ENAB_DELAY This parameter delays the time (in seconds) before alarm processing begins immediately
after the alarm is enabled (alarm_ENAB becomes true). The alarm_ACT parameter is forced to 0 for the time
specified (in seconds). The timer resets whenever alarm_ENAB goes from zero to 1.
alarm_HYS - This parameter is used as a deadband when resetting base alarm conditions for analog values. The
block uses the value of alarm_HYS instead of the standard ALARM_HYS. When conditional alarm detection is
enabled, the block uses ALARM_HYS as the deadband for deviation alarm conditions only.
Example
Conditional alarm behavior is influenced by the module and block execution scan rates. For example, if a module
executes at a five second scan rate and a block in the module executes every 10 module scans, then the block runs
every 50 seconds. If any conditional alarming delay is set to 50 seconds or less, the delay condition is met the next
time the block runs. So if the alarm condition is met, the alarm becomes active between 0 and 50 seconds after the
alarm condition was met. If the delay condition was set to 51 seconds, the alarm would become active between 51 and
100 seconds after the alarm condition was met.
Deviation Alarming
PID, FLC, ALM and RTO are designed to minimize nuisance deviation alarms due to SP changes. The DV_HI_ACT
or DV_LO_ACT parameters available in these blocks are forced to false for a period of time after a setpoint change is
made that is large enough to (without the suppression) cause the deviation alarm condition to become active
immediately. Changes in SP when the block is in Cas or RCas mode do not impact the calculation.
The ACT parameter is forced to False until the deviation alarm condition would normally be reset (if it had not been
suppressed).
For example, if the deviation limit is 2 and a SP change of 3 is made, a deviation alarm would typically occur.
However, since this deviation is due to a user SP change, the deviation alarm is disabled until the error (SP-PV) is less
than 2.
102
System Configuration
Failed (FAILED_ALM) - the device has determined that it can not perform its critical functions.
Maintenance (MAINT_ALM) - the device has determined that it requires maintenance soon.
Advisory (ADVISE_ALM) - the device has determined a condition that does not fall into the other
categories. The severity of an advisory alarm depends on the device type.
Certain fieldbus devices may have only two device alarms: Not Communicating (COMM_ALM) and abnormal
(ABNORM_ALM). The meaning of an abnormal alarm function depends on the device type.
Refer to the device documentation for a more specific description of the parameters.
The interface shows the individual alarms for a fieldbus device in the right pane along with their configurable
parameters. The interface for HART devices is similar.
Device alarms can be enabled to participate in the DeltaV alarm interface tools such as the alarm banner and the
alarm summary.
103
for fieldbus device alarm support, the H1 fieldbus card is a Series II card. Earlier cards do not support device
alarms.
the HART or fieldbus device follows module naming conventions. If the device name does not conform to
the module name rules, device alarms cannot be enabled and the system notifies the user.
Also:
Review the Plant Areas topic in order to understand in which area the device is assigned.
Assign the area that contains the device to the Alarms and Events subsystem of the appropriate workstations
Many Fieldbus devices have configurable properties that enable/disable conditions detected within the
device from contributing to causing a device alarm. Conditions that should cause an alarm should be enabled
within the device. These properties can be accessed through the Configuration properties of the device in
DeltaV Explorer.
Fieldbus devices that support PlantWeb alerts have configurable properties that can suppress communication
of each device alarm. If the device is to communicate that device alarm to the DeltaV controller, that device
alarm must not be suppressed within the device. These conditions can be accessed through the Conditions
dialog for the device in DeltaV Explorer.
HART device alarms can be suppressed through the HART device detail displays. Certain HART devices
from Emerson companies have unique detailed displays. All other HART devices (those that use the
standard status information for their alarms) use the HARTgeneric_dt.grf picture. Detail displays show all
the active conditions. Refer to Device Detail Displays for more information.
Right-click Properties.
Click the Enable Device Alarms check box. The figure below shows the Fieldbus Device Properties dialog. The
HART Device Properties dialog is similar.
104
System Configuration
The Enable Device Alarms property determines whether the alarms are available within the DeltaV system. If this
box is not checked, the alarms will not be available through parameter browsers. In addition, the individual alarms do
not appear in the Explorer and device alarm communications will not be attempted with the device. If you disable
device alarms for a device, any configurable properties of the individual alarms (alarm enable and priority) are
discarded. If the device alarms for a device are subsequently enabled again, the configurable properties are set to their
default values.
You enable or disable individual alarms as follows:
1
Right-click Properties.
105
The enabled/disabled property for the individual alarms corresponds to the .ENAB field for the alarm. Control
modules, OPC client applications and Operators using displays can change the .ENAB field for the alarm.
Note For fieldbus devices, changing the .ENAB field for a device alarm does not change the corresponding alarm
enable status in the field device. Also note that when you download the field device (along with the device alarms),
the corresponding enable is set to be consistent with the setting in the field device.
In general, it is possible to read and write the parameter fields of device alarms from control modules that run in the
same node. This type of reading and writing is typically limited to enabling or disabling certain device alarms based
on the operating state of the module. For example, you might want to disable advisory alarms, which depend on the
process to be active to work properly, when the unit is idle.
Advisory (ADVISE_ALM) a device condition exists that does not fall into the other categories. The
severity of the alarm depends upon the device type.
Abnormal (ABNORM_ALM) the meaning of an abnormal alarm depends on the device type.
Use the DeltaV Explorer to configure asset alarms (after you enable Asset Optimization Alarms in System
Preferences). Configuration involves adding an External Asset Server to an Application Station, configuring the
server properties, synchronizing the server configuration with the DeltaV system, and configuring properties for the
plant hierarchy, asset folders, and assets. The connection with the External Asset Server is made through the server
connection URL and the server access credentials (user name and password). The server connection URL and server
access credentials are configured in the Server Properties dialog box. Be sure to download the workstation after
configuring asset alarms.
Adding and Configuring an External Asset Server
Refer to the Getting Started with Your DeltaV Digital Automation System manual for information on adding an
Application station to the DeltaV Explorer. From the Application station, click External Asset Interfaces/New
External Server to add an External Interface Server to the configuration. Once an External Asset Server has been
106
System Configuration
added to the DeltaV system, you can delete it, rename it, configure its properties and synchronize its configuration
with the DeltaV system. Use the What's This help for information on the fields in the Properties dialog. Here are a
few things to keep in mind when configuring the server properties:
Description it is recommended that a meaningful description be used as this is what's seen in the DeltaV
Diagnostics program.
Server Connection URL and Access Credentials IP address or Node address obtained from the server's
manager + asmx application name, unique for each server.
Alert Synchronization Period the DeltaV system periodically polls the Asset Server for new alarm
information. Use this field to specify the time period between each poll. The range is 5 to 1440 minutes.
Node Integrity Depends on Server's Integrity the default action is for the overall integrity of the External
Asset Server to be rolled into the Application Station's integrity. It is recommended that the default be used
because operators are immediately made aware of alarms when they are visible at the Application Station.
Default Asset Alarms as new assets are created during synchronization, alarms are initially configured
based on the defaults. Alarms that are grayed on the Default Asset Alarms page are not supported on the
external asset system.
107
108
System Configuration
Description
A default description is taken from the asset server. Because the description appears in the DeltaV Operate Alarm
Banner and Alarm Summary, it is highly recommended that you ensure that the description is meaningful to
operators.
Primary Control and Faceplate Displays
Like other DeltaV device alarms, asset alarms can be associated with a faceplate display that operators use to respond
to alarms on the asset. The default asset alarms faceplate is Asset_FP. Similarly, assets can be assigned to a primary
control display. Refer to Responding to Alarms for information on the asset alarm faceplate and primary control
displays.
Area Associations
Assets can be associated with a plant area for alarm and event reporting. Area associations can be made at the
workstation, plant hierarchy, and asset folder levels. All subordinate levels are included in the area association of the
parent level unless the subordinate level is associated with a different area. Review plant areas for more information.
Module Associations
Assets can be associated with modules. For example, the vibration alarms for a pump can be detected and reported
through an asset module while the pump is monitored and operated through a control module. An asset associated
with a module is associated with the same plant area and, if applicable, the same unit/equipment/control module as
the associated module. The asset is also moved if the associated module is moved to a different area. This ensures that
all alarms, both asset and control alarms for a single piece of equipment, are always reported in the same area. If the
associated module is deleted, the asset alarm's area association is determined by the asset's parent level in the
hierarchy.
Enabling and Disabling Asset Alarms
Like other alarms, asset alarms must be enabled in order to be visible to the DeltaV system. Alarms can be enabled/
disabled for an individual asset through the Alarm page of the Asset Property dialog and enabled/disabled for an asset
and all subordinate assets through the Disable/Enable All Asset Alarms commands on the asset's context menu.
Working with Asset Alarms
The presentation and response to asset alarms in the DeltaV system is similar to other device alarms. Review the
following topics for information:
Alarm Presentation
Responding to Alarms
Diagnosing Problems
Use the DeltaV Diagnostics program to diagnose problems at the External Asset Interfaces Subsystem and server
levels. Refer to Books Online and the DeltaV Diagnostics help for information on using DeltaV Diagnostics.
Asset Alarm Requirements
For asset alarms to participate in the DeltaV system, be sure that:
The areas that contain the assets are assigned to the Alarms and Events subsystem on the Application Station
as well as any Operator Station from which asset alarms are viewed.
109
Alarm Presentation
Inside this topic
Alarm Banner
Customizing the Alarm Banner
Alarm Thresholds
Menu Commands
Troubleshooting the Alarm System
The alarm priority and current alarm state determine many of the presentation characteristics for an alarm. For more
information on alarm priority, alarm state, and alarm type, refer to the System Alarm Management topic.
The following sections describe the components of the interface application that operators use to manage alarms.
Alarm Banner
The Alarm Banner is in the lower section of the screen in DeltaV Operate. It provides buttons for the five most
important alarms monitored by this workstation for the current DeltaV user. Multiple (from two to four) monitor
workstations display the ten most important alarms. The Alarm Banner enables the operator to focus on the most
important alarms first. Any alarms of a priority (typically lower priority alarms) not shown in the alarm banner do not
sound the horn on that workstation.
The buttons show the name of the modules, units, and devices in alarm. The banner can show all active process
alarms in a module, or you can configure the alarm priorities so that only the most important alarm for a module or
unit occupies a position in the alarm banner (see the description for the Alarm Banner shows field). Maintenance
workstations are designed for managing fieldbus devices and so show only device alarms in the alarm banner.
The operator can access the display needed to correct the alarm condition by clicking the alarm in the Alarm Banner.
For device alarms, the alarm banner shows alarms with the Warning priority. Each device alarm may be triggered by
one of several device conditions. The banner shows one active alarm even if more than one device condition is
causing the alarm. For example, if two device conditions are causing a Maintenance alarm, the banner only shows
one Maintenance device alarm. For HART device alarms a message indicates that multiple conditions are active.
There is also an extended information button next to each alarm button (refer to the following figure). When you click
an extended information button, the associated alarm's time stamp, parameter name, alarm word, and alarm priority
are displayed at the bottom of the banner.
If you enable the Primary Control button and click one of the five alarm buttons (for example, CAS5), DeltaV
Operate displays the primary control display (in the main process graphic area). If you enable the Faceplate button
and click one of the five alarm buttons, DeltaV Operate displays the faceplate assigned to the module.
The control display is a property of the module or fieldbus device. You can define displays for a module using the
Explorer or Control Studio. Define the displays for a device using the Device Properties in Explorer.
110
System Configuration
111
Changing the default alarm presentation or a presentation method that you selected is quick and easy. Simply change
each alarm priority in the DeltaV Explorer and download the Changed Setup Data to each workstation. Alarm priority
changes are immediately seen on the workstations.
Alarm
Presentation
Methods
Alarm Banner
Behavior
Typical Use
Alarm
Philosophy
What if a module
has one alarm
that is critical
and another
alarm that is
not? What do I
see in the alarm
banner?
Systems with a
smaller number of
alarms per operator.
It is important for
operators to see
each individual
alarm.
The module is
shown twice
displaying the
critical alarm and
the other alarm in
priority order.
2. Show alarms by
module (All alarm
priorities
configured to
Module.)
Systems with a
medium number of
alarms per operator.
Showing every
alarm adds too
much clutter to the
alarm banner.
Operators need to
see which modules
have alarm activity.
Showing only the
highest priority
alarm per module is
the most productive
approach.
The module is
shown once
displaying the
critical alarm.
Systems with a
larger number of
alarms per operator.
Operators need an
overview of the
plant from the alarm
banner. Showing
only the highest
priority alarm per
unit is the most
productive
approach.
When multiple
alarms are active on
the same module,
multiple alarms are
shown in the alarm
banner for that
module.
When multiple
alarms are active on
the same module,
only the highest
priority alarm is
shown in the alarm
banner for that
module.
3. Show alarms by
unit (All alarm
priorities
configured to
Unit.)
112
System Configuration
Alarm
Presentation
Methods
Alarm Banner
Behavior
Typical Use
Alarm
Philosophy
What if a module
has one alarm
that is critical
and another
alarm that is
not? What do I
see in the alarm
banner?
4. Show critical
(high priority)
alarms always,
other (lower
priority) alarms by
module
Critical Alarms
Systems with a
medium number of
alarms per operator,
with some very
critical alarms.
113
Alarm
Presentation
Methods
Alarm Banner
Behavior
Typical Use
Alarm
Philosophy
What if a module
has one alarm
that is critical
and another
alarm that is
not? What do I
see in the alarm
banner?
5. Show critical
(high priority)
alarms always,
other (lower
priority) alarms by
unit
Critical Alarms
Systems with a
larger number of
alarms per operator,
with some very
critical alarms.
114
System Configuration
Alarm
Presentation
Methods
Alarm Banner
Behavior
Typical Use
Alarm
Philosophy
What if a module
has one alarm
that is critical
and another
alarm that is
not? What do I
see in the alarm
banner?
6. Show critical
(high priority)
alarms by module,
other (lower
priority) alarms by
unit
Critical Alarms
Systems with a
larger number of
alarms per operator,
with multiple
critical alarms on
modules.
Note You can customize the priority of the alarms displayed in the alarm banner using the UserSettings file.
UserSettings contains one setting for device alarms and one setting for process alarms. By default, all process alarms
are shown, and only HART and fieldbus device alarms of priority eight and above are shown.
Alarm Thresholds
The workstation alarm threshold determines what priority of alarms are shown in the alarm banner and sound the
horns. By default, workstations are defined to show and annunciate all process alarms (priorities 4 -15) and a subset
115
of device alarms (priorities 8 - 15). This means that device alarms with priorities below 8 will not be shown in the
alarm banner and will not sound the horn. The device alarm defaults were selected because many low priority device
alarms do not represent a potential impact on the process and are primarily intended for maintenance personal.
However, these alarms are still visible to the operator in the Alarm Summary display, in user-defined graphics and in
the Event Chronicle.
The default alarm threshold setting may be modified for one or more workstations in the UserSettings.grf file. The
workstation variables used for alarm thresholds are
frsVariables.gn_ProcessAlarmThreshold.CurrentValue
frsVariables.gn_DeviceAlarmThreshold.CurrentValue
These variables can also be changed dynamically while in run mode. For example a button can be configured to
modify the alarm banner to only show and annunciate process alarms of priorities above 12, for use during an upset.
Menu Commands
Acknowledge All - This command acknowledges all of the alarms in the selected picture provided the picture has
datalinks referencing each module down to its ALARMS[1] parameter, for example, DVSYS.LIC-101/
ALARMS[1].A_ATTR. If there is not an ALARMS[1] datalink on the picture, or if the Alarm Banner or toolbar area
is selected, no alarms are acknowledged.
Acknowledge One (Ctrl-K) - This command acknowledges a single selected alarm.
Make sure that the referenced alarm parameter (for example, HI_ACT parameter in a function block) is not 0.
Make sure that the module is executing. If the module is executing, the MSTATE parameter value for the module
will be In Service.
Make sure that the alarm is enabled. The value of ENAB for both the alarm parameter and the module ALARMS
parameter must be YES. For example: FIC-101/ALARM-HI.ENAB=YES and FIC-101/ALARMS.ENAB=YES.
Check the value of NALM (the acknowledged status). The alarm might be auto-acknowledged. The value of
NALM is determined by the alarm priority (for example, ALARM-HI.PRI) and can be overridden by the
ALARMS.PRIAD field. If the alarm priority is configured as auto-acknowledged in the DeltaV Explorer and
PRIAD is not overriding the value, the alarm is auto-acknowledged.
Make sure that the necessary data has been downloaded. You must download the module in the controller. You
must also download setup data to all affected nodes (workstations and controllers) whenever the alarm type or
alarm priority configuration is changed.
Determine how many active alarms you have. If there are more than five active alarms, the alarm banner will not
show them.
When an alarm should be in THISUSER/ALARMS but is not, perform the following steps:
1
Make sure that the plant area determined in step 1 is the workstation's Alarms and Events subsystem. If it is not,
assign the area and download the workstation.
Check to see if there are any active alarms in THISUSER/ALARMS. If there are, compare them with the ones
that are missing. This might suggest the problem with the alarms that are not in THISUSER/ALARMS.
116
System Configuration
Make sure that the controller is communicating. Use the DeltaV Diagnostics application to check the
communications status.
Review the steps in the above procedure, "When something should be in alarm but is not..."
When alarm state change records are missing from the Event Chronicle, perform the following steps:
1
Use DeltaV Diagnostics to make sure that the Event Chronicle is active on this workstation. The following
indications could account for missing alarm state change records:
DirBad = BAD - The specified directory for the event data could not be found, or the database could
not be created.
DskFul = FULL - The configured limit of records that can be stored in the event database has been
reached.
RecWrR = -1 - The Event Chronicle on this workstation has not been configured to be active.
Make sure that the module that contains the alarm is in an area assigned to the workstation.
Check to see if there are any alarm state change records in the Event Chronicle. If there are, compare them with
the ones that are missing. This might suggest the problem with the alarms that are missing from Event Chronicle.
Make sure that the controller is communicating. Use the DeltaV Diagnostics application to check the
communications status.
Review the steps in the above procedure, "When something should be in alarm but is not..."
When alarms do not activate the horn, perform the following steps:
1
Follow the steps in the above procedure, "When an alarm should be in THISUSER/ALARMS but is not..."
Alarms must be in THISUSER/ALARMS before a horn can be active for them.
Determine the effective priority of the horn. Alarms with a priority of Log do not sound the horn. Also,
remember that the ALARMS.PRIAD value can change the effective priority of an alarm.
Make sure that a .WAV file has been specified for the alarm priority. Make sure that the file specified is in the
\SOUND directory. Also, note that SILENCE.WAV must be in the directory for the sound card to work.
Make sure that DeltaV Operate is using the standard DeltaV alarm banner. This banner provides access to the
HORN parameters. Make sure that the horn is enabled (THISUSER/HORN.HENAB=1).
117
Custom Alarms
Inside this topic
Custom Alarm Calculation
Custom Alarm Detection
Custom Alarm Presentation
Adding Custom Alarms
Creating a Custom Calculation for the Alarm
Defining the Alarm Detection
The following sections detail the calculation, detection, and presentation aspects for the DeltaV custom alarms. For
more information on how to configure different alarms, refer to the Alarm Configuration topic.
The alarm state calculation typically uses logical and relational operators to: test the values in one or more
parameters, compute a Boolean result (0 or 1), and write it to a new state parameter.
118
System Configuration
In the Alarms view window, click the right mouse button, and then click Add.
Select the alarm, click the right mouse button and select Properties.
In the Alarm properties dialog - General tab, name the alarm and specify the Alarm type and a Priority.
In the Alarm parameter field (still on the Alarm properties dialog - General tab), enter the parameter that triggers
the alarm.
Click OK.
Drag an Analog Input block onto the diagram. The Analog Input block is in the I/O function block category.
Drag a Condition block onto the diagram. The Condition block is in the Logical function block category.
Browse to find the HI_ACT parameter and the CV field in the AI block within this module.
Click OK.
10 Click Parse.
11 When the expression parses without any errors, click OK.
This sets up an expression to see if the HI_ACT parameter is greater than or equal to 70. For this module, the value of
the expression is the value of the OUT_D parameter.
119
Using the example in Creating a Custom Alarm Calculation (HI_ACT > 70), define the alarm detection by following
these steps:
1
Click the right mouse button in the Alarms View window, and then click Add.
Select the alarm, click the right mouse button and select Properties.
Select an Alarm type. For this example, the Any Alarm works.
Select the Priority. The Priority of 'Log' only sends the event to the Event Journal and does not display it to the
operator.
Note This step sets the alarm presentation. Refer to the Alarm Presentation topic for more details.
7
In the Related Parameters section, select the Alarm parameter for OUT of the Condition block.
Use the Advanced tab to enable or invert the alarm characteristics or change the alarm message parameters (if
available).
Click OK.
The alarm detection is now defined for the parameter OUT of the Condition block. When the condition of HI_ACT >
70 for the AI block is reached, the output of the Condition block is set to True and the alarm is triggered.
Note If the alarm was inverted, then the alarm is triggered when OUT of the Condition block is set to False.
120
System Configuration
for alarms with equal acknowledgment status, the priority (CRITICAL, WARNING, ADVISORY)
determines the importance. CRITICAL is the most important priority. ADVISORY is the least important
priority. Alarms can also be assigned the LOG priority. When this happens, all alarm annunciation behavior
is suppressed (for example, the alarm no longer appears in the alarm banner, it does not sound the horn, and
so on).
for alarms with equal acknowledgment status and equal priorities, the controller uses the time stamp. The
most recent alarms are the most important.
The following examples show paths to the ASCII value of the priority for ALARMS parameters associated with the
current user, an area, and a module:
THISUSER/ALARMS[1].A_PRI
AREA_A/ALARMS[1].A_PRI
FIC101/ALARMS[1].A_PRI
121
Note The alarm parameter CUALM (current alarm) can be either zero or non-zero (the non-zero value is determined
by the alarm type and priority used). When CUALM is zero, the parameter is not in alarm. When CUALM is nonzero, the parameter is in alarm.
The alarm parameter NALM (new - unacknowledged - alarm) can be either zero (0) or one (1). When NALM is zero,
there is no new alarm. When NALM is one, there is a new, unacknowledged alarm. When the alarm is acknowledged,
the NALM value returns to zero.
The LAALM (latched alarm) parameter can be either zero or non-zero (the non-zero value is determined by the alarm
type and priority used). When LAALM is zero, the parameter is not in alarm. When LAALM is non-zero, the
parameter is in alarm. Once LAALM is in alarm (represented by a non-zero value), it remains set until both the
condition and NALM return to zero.
The following tables define all the ALARMS parameter fields for modules, areas and users. The Use Example
column assumes a Module named FIC101.
Module ALARMS Parameter Fields
Field
Use Example
Description
Read/Write
A_ (ASCII)
F_ (FLOATING)
FIC101/
ALARMS[1].A_ATTR
alarm
parameter
name
HI_ALM
N/A
CUALM
FIC101/
ALARMS[1].F_CUALM
Current alarm
state
OK/HIGH
0, 1, 2.....
LAALM
FIC101/
ALARMS[1].F_LAALM1
latched alarm
OK/HIGH
0, 1, 2.....
NALM
FIC101/
ALARMS[1].F_NALM
new alarm
NO/YES
0/1
PRI
FIC101/
ALARMS[1].F_PRI
priority
CRITICAL,
WARNING,
ADVISORY,
LOG2
3, 4, 5, 6, 7, 8, 9, 10,
11, 12, 13, 14, 153
TIN
FIC101/
ALARMS[1].A_TIN
timestamp
when it went
into alarm
N/A
122
System Configuration
Field
Use Example
Description
Read/Write
A_ (ASCII)
F_ (FLOATING)
ENAB
FIC101/
ALARMS.F_ENAB
enables or
disables all
alarms in the
module
R/W
N/A
MACK
FIC101/
ALARMS.F_MACK
acknowledges
all the alarms
in the module
N/A
123
Field
Use Example
Description
Read/Write
A_ (ASCII)
F_ (FLOATING)
PRIAD
FIC101/
ALARMS.F_PRIAD
adjust
effective
priority of all
alarms in
module
R/W
N/A
0 alarm priority as
configured 1 lowers
all alarms by one
priority (CRITICAL
alarms become
WARNING, and so
on).
2 lowers all alarms
by two priorities
(CRITICAL alarms
become
ADVISORY;
WARNING and
ADVISORY alarms
become LOG).
3 lowers all alarms
by three priorities
(all alarms become
LOG), for example:
FIC101/
ALARMS.F_PRIAD
= 0 resets all
effective alarm
priorities to be that
of the individual
alarm priorities.
1 Information about the five most important alarms in a module is accessed through ALARMS [1-5].
2 These are default priority names.
3 Active alarms that have been suppressed (OPSUP is 1 (YES)) also appear in the module's ALARMS
parameter, but their priority value is forced to the value 3 (LOG) so that they will appear only after unsuppressed
active alarms.
The following table lists the plant area level ALARMS parameter fields (used to show the top 5 active alarms in
current user's operating plant area). The Use Example column assumes a plant area named AREA_A.
Area ALARMS Parameter Fields
Field
Use Example
Description
A_ (ASCII)
F_
(FLOATING)
CUALM
AREA_A/
ALARMS[1].F_CUALM
current alarm
state
OK/HIGH
0, 1, 2.....
MODULE
AREA_A/
ALARMS[1].A_MODULE
module name
FIC101
N/A
LAALM
AREA_A/
ALARMS[1].F_LAALM
latched alarm
OK or HIGH
0,1,2,....
124
System Configuration
Field
Use Example
Description
A_ (ASCII)
F_
(FLOATING)
CV
AREA_A/
ALARMS[1].A_CV
module name
(same as the
MODULE
field)
.../FIC101
N/A
NALM
AREA_A/
ALARMS[1].F_NALM
new
(unacknowled
ged)
NO or YES
0 or 1
PRI
AREA_A/
ALARMS[1].F_PRI
priority
CRITICAL,
WARNING,
ADVISORY,
or LOG
0, 1, 2, or 3
ATTR
AREA_A/
ALARMS[1].A_ATTR
mod/param
name
FIC101/
HI_ALM
N/A
TIN
AREA_A/
ALARMS[1].A_TIN
time into
alarm
N/A
The following table lists the THISUSER level ALARMS parameter fields (used to show the top 5 active alarms in all
of the current user's system-wide operating plant areas):
THISUSER ALARMS Parameter Fields
Field
Use Example
Description
A_ (ASCII)
F_
(FLOATING)
MODULE
THISUSER/
ALARMS[1].A_MODULE
module name
FIC101
N/A
CUALM
THISUSER/
ALARMS[1].F_CUALM
current alarm
state
OK/HIGH
0, 1, 2.....
LAALM
THISUSER/
ALARMS[1].F_LAALM
latched alarm
state
OK or HIGH
0,1,2,....
CV
THISUSER/
ALARMS[1].A_CV
module name
(same as the
MODULE
field)
FIC101
N/A
NALM
THISUSER/
ALARMS[1].F_NALM
new
(unacknowled
ged)
NO or YES
0 or 1
PRI
THISUSER/
ALARMS[1].F_PRI
priority
CRITICAL,
WARNING,
ADVISORY,
or LOG
0, 1, 2, or 3
125
Field
Use Example
Description
A_ (ASCII)
F_
(FLOATING)
ATTR
THISUSER/
ALARMS[1].A_ATTR
mod/param
name
FIC101/
HI_ALM
N/A
TIN
THISUSER/
ALARMS[1].A_TIN
time into
alarm
N/A
Use Example
Description
Read/Write
A_ (ASCII)
F_
(FLOATING)
CUALM1
FIC101/
HI_ALM.F_CUALM
Current alarm
state
OK/HIGH
0, 1, 2.....
LAALM2
FIC101/
HI_ALM.F_LAALM
Latched alarm
state (active until
acknowledged)
OK/HIGH
0, 1, 2.....
CV
FIC101/
HI_ALM.F_CV
(same as
LAALM)
OK/HIGH
0, 1, 2.....
NALM3
FIC101/
HI_ALM.F_NALM
new alarm
(unacknowledged)
used for Blink on
New Alarm
R/W
NO/YES
write NO to
acknowledge
0/1
PRI
FIC101/
HI_ALM.F_PRI
Priority
R/W
CRITICAL,
WARNING,
ADVISORY,
LOG4
3, 4, 5, 6, 7, 8, 9,
10, 11, 12, 13,
14, 15
ENAB
FIC101/
HI_ALM.F_ENAB
Enables or
disables the
alarms
R/W
NO/YES
0 (NO) causes
the alarm to be
disabled.
1 (YES) causes
the alarm to be
enabled.
126
System Configuration
Field
Use Example
Description
Read/Write
A_ (ASCII)
F_
(FLOATING)
OPSUP
FIC101/
HI_ALM.F_OPSUP
Enables alarm
suppression
R/W
NO/YES
0 (NO) has no
effect on alarm
behavior.
1 (YES) prevents
activation of the
alarm. The
Alarm Suppress
picture shows all
of the suppressed
alarms.
SUPTMO
FIC101/
HI_ALM.F_SUPTMO
Alarm suppression
timeout
R/W
Time in
minutes
Time in minutes
SUPTMR
FIC101/
HI_ALM.F_SUPTMR
Alarm suppression
timer
R/W
Time in
minutes
Time in minutes
INV
FIC101/
HI_ALM.F_INV
R/W
NO/YES
0/1
1 The alarm parameter CUALM (current alarm) can be either zero or non-zero (the non-zero value is determined
by the alarm type and priority used). When CUALM is zero, the parameter is not in alarm. When CUALM is nonzero, the parameter is in alarm.
2 The alarm parameter NALM (new - unacknowledged - alarm) can be either zero (0) or one (1). When NALM is
zero, there is no new alarm. When NALM is one, there is a new, unacknowledged alarm. When the alarm is
acknowledged, the NALM value returns to zero.
3 The LAALM (latched alarm) parameter can be either zero or non-zero (the non-zero value is determined by the
alarm type and priority used). When LAALM is zero, the parameter is not in alarm. When LAALM is non-zero,
the parameter is in alarm. Once LAALM is in alarm (represented by a non-zero value), it remains set until both the
condition and NALM return to zero.
4 Using the DeltaV Explorer, you can add additional alarm priority names and map them to any value (3 through
15).
The HORN parameter is intended to be used only by the operator's alarm banner. Its use in other displays or by
applications other than DeltaV Operate might interfere with the operation of the alarm banner and is not
recommended.
127
Operator
Span of
Control
Recommended Areas in
the Alarms and Events
Subsystem
ProfessionalPlus
na
Area_1
Area_2
Area_3
Area_4
Area_5
Operator Station 1
Area_1
Area_2
Area_3
Area_1
Area_2
Area_3
Operator Station 2
Area_4
Area_5
Area_4
Area_5
128
System Configuration
Drag the areas for which you want to record events and alarms to the Alarms and Events subsystem using DeltaV
Explorer.
500,000 records
.
.
n records
.
.
<=20,000
500,000 Kb
.
.
n Kb
.
.
20,000 Kb
After gaining experience with the typical number of events being recorded in an Event Chronicle database each day,
adjust the Maximum Chronicle size x records and Remove records older than y days values with the goal that upon
129
completing the daily maintenance cycle, inserting a typical day's worth of event records will not cause the maximum
chronicle size to be reached before the next daily maintenance cycle. This assures optimum file space management;
avoiding excessive disk storage usage.
130
System Configuration
History data capture and storage as determined by the History Collection configuration for that workstation
Any automatic history data management services that have been configured (such as automatic data
discarding, moving to offline storage, etc.)
History data services (browsing/reading/writing) for local and remote client applications
Presentation of the data through the Process History View application or client applications
131
132
System Configuration
Terminology
Following is a list of terms and their definitions.
Active History Data Set - Holds the most recent history data captured for all history tags configured for the
Continuous Historian. The data set holds the contiguous history record from the time it was created until the present.
Continuous Historian - A collection of features and applications that provide capture of, access to, and management
of time-series parameter values from the run-time DeltaV system.
Current History Data Set - Data set created by rollover of the active history data set in the Continuous Historian. A
current history data set is a former active history data set that has been completed by hitting the time or size limit
rules or by direct creation of a new active data set. A current history data set holds history data for a collection of
history tags within the time span of the data set. One or more current history data sets may exist in primary storage.
Extended History Data Set - A history data set that has been placed back online through the use of the Continuous
Historian Administration tools. Such data sets may be for any history tags for any period of time (without continuity
with the active and current history data sets).
Legacy Historian - A third-party historian product that has been replaced by the Continuous Historian. Use of the
legacy historian is limited to existing users of that historian application.
Primary Storage - A storage area on each workstation with a Continuous Historian history server installed. This area
holds a collection of history data sets, including one active history data set, zero or more current data sets, and zero or
more extended history data sets.
133
Define history collection for module and node parameters. Refer to Configuring History Collection for more
information.
Note If you do not assign the module to an Application Station or a commissioned controller, history will not be
collected for the module.
3
Enable the Continuous Historian subsystem for each workstation that collects history and configure the
Continuous Historian properties. Refer to Configuring Continuous Historian Properties for more information.
Assign specific area folders and nodes to the Continuous Historian subsystem.
Note After the initial download of the history collection subsystem there may be a short period of time before the
overall integrity of the subsystem reports GOOD.
On Application Stations, if the Legacy Historian is already installed, there will be a check box for selecting the
Legacy Historian if you wish to continue using that historian on that particular workstation.
Workstations
Continuous Historian data servers are available on all DeltaV workstation types (local or remote). Continuous
Historian performance using slow network connections will not be as fast as when using fast network connections.
The Continuous Historian is the only historian supported on the ProfessionalPLUS workstation and Operator Station
nodes. On Application Stations, existing users are allowed to continue using the Legacy Historian or switch to the
Continuous Historian. The choice is offered only in DeltaV software upgrades and then only if the Legacy Historian
is installed on the workstation being upgraded. (The default selection is the Continuous Historian.) Only the
Continuous Historian is available for use on new DeltaV installations.
Continuous Historian client support is available on DeltaV local or remote workstation nodes (including remote
terminal sessions hosted by a DeltaV workstation). Communications between client application nodes and
Continuous Historian data serving nodes is provided by .Net remoting facilities.
134
System Configuration
The table below summarizes the node support for the Continuous Historian and the Legacy Historian.
Professional
PLUS
Operator
Station
Application Station
Continuous
Historian only
Continuous
Historian only
Remote workstation
---
Continuous
Historian only
135
The historian to be used (The Legacy Historian choice will only be available on Application Stations.)
The target maximum historian size for the Primary storage area
136
System Configuration
value is 50 MB. The value is constrained to always be less than or equal to the primary storage current history size
target.
Enable data set time span - The rollover occurs to create a current history data set that represents the desired time
span. Options include:
Calendar month periods - creation occurs at local time midnight on the first day of each month
Weekly periods - creation occurs at local time midnight on each Sunday morning
None - creation occurs only when the data set size target is exceeded. This is the default setting.
137
Select an Area or a module, click the right mouse button, and select History Collection from the context menu.
On the History Collection dialog, click the Add button to configure the History Collection for that object. (To
modify or delete an existing history collection, select a parameter and click the Modify or Delete button,
respectively.)
Fill in the Modify History Collection dialog. Use the Help button on the dialog for specific instructions.
There are two ways to configure history collection in Control Studio. To add or modify history collection for a
module:
1
Open a module and select History Collection from the File menu.
On the History Collection dialog, click the Add, Modify, or Delete buttons to configure the History Collection
for that object. (To modify or delete an existing history collection, select the parameter and click the Modify or
Delete button, respectively.)
Fill in the Modify History Collection dialog. Use the Help button on the dialog for specific instructions.
Right-click the parameter and select Add History Recorder from the context menu.
Fill in the Add History Collection dialog. Use the Help button on the dialog for specific instructions.
To confirm your entire History Collection configuration in the DeltaV Explorer, select the workstation's Continuous
Historian subsystem, click the right mouse button, and select History Collection from the context menu. This presents
a read-only view of all values to be historically collected for this workstation's Continuous Historian.
138
System Configuration
139
The following properties are available for adding or modifying history collection:
Sampling period
For more detailed information on the choices available, refer to the online help for the dialog.
140
System Configuration
The item will be added to the History Collection list as FP_ARRAY[2,1]. However, when downloaded to the
Continuous Historian, the parameter is specified as FP_ARRAY[2][1].CV. When downloaded to the Legacy
Historian, the parameter is specified as FP_ARRAY(2)(1).CV, because the Legacy Historian does not support the use
of square brackets.
These syntax distinctions are important when you are configuring a Process History View trend for the array
parameter. When configuring a pen in PHV for the Continuous Historian, specify the array parameter path as Module/
ArrayParameterName[row][col]. When configuring a pen in PHV for the Legacy Historian, specify the array
parameter path as either Module/ArrayParameterName[row][col] or Module/ArrayParameterName(row)(col).
141
History Samples
When data is collected for a history tag, a "history sample" is produced. A history sample is the basic unit of history
data for a history tag. A history sample is composed of:
a timestamp -- the date-time when the history tag had this value
a Continuous Historian status value -- with information such as whether the continuous history stream was
broken and the type of break
The Continuous Historian supports the following data types for history sample values:
32-bit float
32-bit signed integer (smaller DeltaV signed integer parameter field are converted to this type)
32-bit unsigned integer (smaller DeltaV unsigned integer parameter field are converted to this type)
Byte-enum -- holds both number and state name for DeltaV name set parameters
Active
Current
Extended
142
System Configuration
To assist in data management, the Continuous Historian can be configured to automatically "roll over" the active
history data set. The active history data set is "closed" and becomes a "current" history data set. A new (empty)
active history data set is started. The configuration rules for performing a rollover can be based on:
the approximate history data file size limit (so that the current history data sets will usually fit on long-term
storage media)
calendar/time targets (so that current history data sets will represent convenient time spans; for example,
days starting at midnight, weeks starting on Sundays at midnight, and so forth)
A new active history data set can also be created directly using the Create New Active Data Set tool in the
Continuous Historian Administration application. Refer to the topic Continuous Historian Administration for more
information.
Current History Data Sets
Current history data sets are created by active history data set "rollover" operations. They hold history data for a
collection of history tags within the time span of the data set. They provide a means to manipulate history data
captured in manageable "chunks," while keeping as much of the recently captured data accessible to history client
applications as possible.
For the current history data sets, the user may configure (on the Advanced tab of the Continuous Historian Properties
dialog):
a time span
If a time span is configured, it is applied to each current history data set as it is created. If automatic export has been
configured, once the time span has expired on a current history data set or the size limit has been reached, the
Continuous Historian will perform the export and remove the data set from primary storage.
Users can manually export data from and/or discard current history data sets using Continuous Historian
Administration tools.
Extended History Data Sets
Extended history data sets provide a means to bring history data that has been exported and no longer online, back
online (that is, again made accessible to history data client applications).
Continuous Historian Administration tools provide means to create extended history data sets from history data files.
Once created, history data in the extended history data set is accessible in the same way as the data in the active and
current history data sets. There are no assumptions about continuity of the data in an extended history data set with
any of the other data on-line. The history tags in the extended history data set need not match (nor are they
constrained by) the other history tags available on-line.
The Continuous Historian performs no automatic data management for extended history data sets. They remain
online (and occupy storage) until the user manually removes them.
143
HDS_ACTIVE
HDS_EXPORT
HDS_DELETE
HDS_EXTENDED
HDS_BACKUP
HDS_RESTORE
144
System Configuration
Read raw samples - This provides access to the individual history samples stored in the history data sets. If
data compression is enabled, the number of samples stored per unit of time could vary a great deal. The
number of raw samples available online for a history tag that has a frequently changing value and with little
or no compression could be quite large.
Read processed data - This tells the server to return information for a history tag, derived by "processing"
the raw history samples; it usually involves a substantial reduction in the volume of data returned, but the
data is still useful for a specific purpose (drawing charts, performing analysis, looking for missing data, and
so forth). Processing involves:
1
Subdividing the time span bounded by the start and end time into one or more, evenly sized subintervals
(for example, 24-hour subintervals for the last month)
Computing one or more "aggregate functions" for each subinterval. Refer to Aggregate Functions for
more information on the aggregate functions supported.
In either type of request, a time span (ultimately resolved as a start time and an end time) is specified in the request to
establish the time boundaries for the request. Timestamps that exactly match the start time are considered within the
time span. Timestamps that exactly match the end time are not within the time span.
Start and end times from a client application will often not exactly "hit" the timestamps for raw samples stored in the
history server, so the following options exist for specifying how the server should handle the boundary sample
situations:
No boundary sample - specifies that no samples should be returned/used outside of the start and end times.
The first sample to be used would be the first raw sample stored after the start time, and the last one used
would be the last raw sample stored before the end time
Outside of span - specifies that the time span should be increased to include the first raw sample beyond the
specified start and/or end time
Interpolate - specifies that a sample should be "derived" for the start and/or end time by interpolation (as
appropriate for the data type) from the raw samples that are immediately before and after the boundary time
specified.
A complicating factor for history data retrieval is that there may be discontinuities (holes) in the history record.
Reading raw samples should return "hole start" samples that indicate the starting time and the reason for the hole (for
example, the parameter cannot be read, the historian shut down, the tag was not configured to collect at that time, and
so forth). Reading processed data should return sufficient information to let the client know if the requested aggregate
was adversely affected by any holes in the history record within each subinterval.
Another kind of discontinuity in the history record involves requesting history data for time spans up to and including
the present. It is usually convenient for clients if the history server would, in this case, return a raw history sample
representing what the history server currently considers "now." It is expected that a client repeating the same request
for a "now" sample some time later would see different, that is, more current, results.
Data Compression
Data compression can be enabled when configuring history data collection for a history data tag, by enabling data
compression and entering a deviation amount. The user can also select the type of display representation (Step, Line,
or Automatic). Step representation displays the values as step changes on the trend and is usually used for discrete
values (such as pumps) and for values that change in a step-like manner (such as setpoints). Line representation
145
displays values with point-to-point connections and is usually used for values such as process data. It is
recommended that either Step or Line be specifically selected when configuring the Display Representation and that
the plot method used to display the data in Process History View be set to the default setting. If the Display
Representation is left as Automatic, then it will set a floating point value to Line, and an integer to Step. Refer to the
Configuring History Collection topic for more information on enabling data compression when configuring history
data collection.
When data compression is disabled for a history tag, a sample (value, status, timestamp) is captured in the history
database for each scan cycle (determined by the configured scan period). Even if the value of the history tag remains
the same, a sample will be stored with the same value/status for each scan cycle.
When data compression is enabled for a history tag, the only samples stored are those that are needed to represent the
history record for the tag to the desired degree of accuracy. Clients reading archived data for a compression-enabled
history tag should expect the request to return a variable number of unevenly spaced samples. Enabling data
compression reduces storage requirements and improves performance when retrieving the history record for tags that
change infrequently or by insignificant amounts.
It determines the default behavior for displaying the data in Process History View (PHV)
It affects the interpolation algorithm behavior that determines how to represent a value for a point in time
between raw samples
Along with the data type, it determines the compression technique used
Note The Process History View application allows the user to select a Line or a Step plot method for a given trend,
regardless of the display representation configured for the tag's history collection and regardless of the compression
technique used for gathering the data. Mixing the configured display representation and the PHV trend plot method
can result in misleading trend graphing outputs. For example, if a history tag is configured for Line display
representation, data collection and compression are optimized for producing sloping line rendering of history data. If
the user overrides the default and chooses Step plotting in PHV, the trend may indicate that changes occurred in
abrupt steps, when actually the trended parameter changed gradually (at a nearly constant slope). Conversely, if a
history tag is configured for Step display representation and the user chooses Line plotting in PHV, the trend may
indicate the values of a parameter changed gradually, when they did not.
In summary, optimal rendering results will be achieved when the trend plot method in PHV matches the display
representation configured for the tag history collection. It is therefore recommended that the default plot method be
used in PHV, rather than selecting a plot method that might conflict with the configured display representation.
Changing the display representation and downloading will affect the subsequent behavior of the system, but it does
not change the history data already collected for a history tag. No attempt is made to track changes of display
representation. The current configuration is interpreted as the preferred choice for rendering and interpolating values
in all previous history data stored on-line for the tag.
146
System Configuration
Bad
Uncertain
GoodCascade
GoodNonCascade
Substatus
NonSpecific
Limits
Constant
HighLimited
LowLimited
NotLimited
The composite Ff status value returned is a value representing the "worst" of individual Ff status values seen.
Specifically, each part of the composite Ff status is computed separately as follows:
Quality - The composite Quality value is the worst of Quality values of all the raw sampled involved. As such:
Substatus - If the Quality value AND the Substatus value of all the raw samples involved are exactly the same, the
Substatus is that same value; otherwise a Substatus value of NonSpecific is returned.
Limits - The composite Limit value is a "Limit value OR" function of all the individual Limit values from the raw
samples involved.
147
status bits set. Composite historian status values for interpolated history samples or history aggregates are obtained
by bit-ORing the individual historian status values that were involved in computing the interpolated sample or
aggregate.
The individual historian status bits defined are:
History data unavailable (** No Data **) - When set, indicates a type of "hole" in the history record. This status
would let history clients know that the history server has no history data set mounted that includes this history tag for
this point in time. Situations would include the period of time before the oldest history sample currently online for a
history tag or gaps in the online history record due to history data sets being removed.
History collection not configured (Not Configured) - When set, indicates a type of hole in the history record. This
lets history clients know that the hole is intentional, that is, caused by the configuration engineer deciding to no
longer have history captured for this tag on this node, or configuring the historian to be disabled.
Historian/scanner shutdown (Historian shut down) - When set, indicates a type of hole in the history record. This
status lets history clients know that the hole was a temporary outage due to the historian not operating or due to
planned or unplanned DeltaV shutdowns. (It is likely that no other history tags have data available from this server at
this point in time.)
History data unreadable (Not Readable) - When set, indicates a type of hole in the history record. This lets history
clients know that the history tags became unreadable for whatever reason (source node crash, communication
problems, configuration changes partially distributed, and so forth).
Aggregate value invalid (Bad Aggregate) - This status bit is set for aggregate values (requested using "read
processed" calls) that could not be produced. Situations where it is impossible to compute a requested aggregate value
might include:
A minimum, maximum, or average is requested for an interval that is entirely within a hole in raw data
samples, so there are no useful values that can be used in computing the aggregate.
An aggregate is requested that is not supported on a history tag of that type (for example, requesting a timeweighted average for a string type history tag).
Value
Timestamp
Composite Ff
(DeltaV) Status
Composite
DvCH (Archive)
Status
First
Last
Count
Number of raw
samples (including
holes)
Always constant
value: Bad ,
NonSpecific,
NotLimited (0)
Composite of all
raw samples in
interval
148
System Configuration
Aggregate
Value
Timestamp
Composite Ff
(DeltaV) Status
Composite
DvCH (Archive)
Status
Interpolated
Interpolated value
at start of interval
% Available
% of time in
interval where
history data is
present (0-100)
Timestamp of first
hole (start) in
interval
Composite of all
non-hole samples in
interval and
interpolated
boundary samples
Composite of all
samples in interval
and interpolated
boundary samples
The aggregate functions in the table below are supported for Float, 32-bit signed integer, and 32-bit unsigned integer
history data types.
Aggregate
Value
Timestamp
Composite Ff
(DeltaV) Status
Composite DvCH
(Archive) Status
Minimum
Timestamp
corresponding with
Value
Ff status
corresponding with
Value
DvCH status
corresponding with
value
Maximum
Timestamp
corresponding with
Value
Ff status
corresponding with
Value
DvCH status
corresponding with
value
Time-weighted
average
Time-weighted
average of non-hole
raw samples in
interval and
interpolated
boundary samples
Composite of all
non-hole samples in
interval and
interpolated
boundary samples
Composite of all
samples in interval
and interpolated
boundary samples
149
150
System Configuration
In workstations where the Legacy Historian is installed, the current PHIST subsystem will continue to exist,
unchanged.
In local workstations where the Continuous Historian is installed, a new CHIST subsystem will exist (while
DeltaV services are running).
Type
Usage
EXIST
Boolean
SWREV
String
OINTEG
Boolean
SERVER
Boolean
ITEMS
Int32
ONSCAN
Int32
ITEMPSEC
Int32
READPSEC
Int32
DCLOAD
Float32
BADREAD
Int32
151
Name
Type
Usage
BADWRITE
Int32
DCSTOP
Boolean
Data storage disk has too little free space for normal
operation
Float32
PRIXSMB
Int32
EXPFAILS
Int32
ERLACTIVE
Int32
HSLOAD
Float32
HSWRITES
Int32
152
System Configuration
Name
Type
Usage
SILOAD
Float32
SIWRITES
Int32
153
Reconverting an Archive
If you select an archive for conversion that has already been converted, you will get a message saying that the
converted file already exists and are given the option to overwrite the existing file.
154
System Configuration
155
storage. Files may be brought back online as needed using the Create Extended Dataset or Restore features of the
Continuous Historian Administration application.
When different versions of DeltaV software are used to create these files, users should be aware that, in general, older
.xfc files will be readable by versions of DeltaV software newer than the one that created them. They will not,
however, be readable by versions of DeltaV software that are older than the version that created them. Users who
have more than one DeltaV system operating at different version levels need to take this into consideration if they
plan to move historian data between their systems.
156
System Configuration
157
If the Restore operation is interrupted using the Abort button, any data sets restored before the abort is confirmed are
not affected. Restoration of a data set that is in progress will not be completed; it may take some time to delete the
partially restored data set.
This feature requires the user to have the DeltaV security key for the HDS_RESTORE function.
Note that the extended data sets are not included in the storage size. (The user is responsible for creating and deleting
extended data sets, and therefore for managing their storage within the capacity of the disk drive.) The total size of
extended data sets is displayed in the status bar at the bottom of the Continuous Historian Administration window.
Diagnostics
This feature lets a user review the diagnostics for the Continuous Historian. It can be accessed from the Tools menu
or the toolbar icon. It provides information on the historian server such as the last number of writes, the total number
of cache writes, the total number of writes, and the percent busy. It also provides information on the Primary storage
area, such as the current status, whether the disk is full, the percent of the storage area in use, and the free disk space.
It also tells whether early creations of new Active data sets have been done and how many automatic exports have
failed. For early creations of new active data sets, it doesn't show creations initiated by the user or creations initiated
on a timed (for example, Daily) basis.
158
System Configuration
Backing up all Extended (as well as Current) data sets to local/networked storage
Deleting backed up data sets in the target directory according to their age
Syntax
The Automated Backup Utility is located in the DeltaV/bin directory on the DeltaV workstation, The filename is
HistorianBackup.exe. The syntax for the Automated Backup Utility is:
HistorianBackup Directory [/CreateNewActive] [/Extended]
[/BackupIfLTDays:n] [/Retries:n] [/DeleteIfGTdays:n] [/OnlyIfModified]
where the parameters in brackets are optional. The parameters are:
Directory
is the directory to which the data sets will be backed up (in either
UNC or drive letter directory format)
/CreateNewActive
/Extended
/BackupIfLTDays:n
/Retries:n
retries on exclusive use error for "n" retries, where "n" is in the range of 0 to
720; the default is 5 retries
/DeleteIfGTDays:n
deletes off line data sets greater than "n" days old
/OnlyIfModified
Data sets are backed up in alphabetic order. Oldest data sets are backed up first. Any data set being backed up will
have its "Backup Status" in the Continuous Historian Administration application set to "Backing Up" while the
159
backup is in progress. When the data set is backed up, its status is set to "Backed Up." If the data set is modified
during or after the backup, its status is set to "Modified." If the data set is modified during or after the backup, a
backup file will still exist for the data set; however, the backup file will not be up-to-date.
Note that the Continuous Historian Administration application only updates every 60 seconds, so there may be a
slight delay in the backup status display immediately after a backup is performed.
The results of the backup procedure are recorded in the Windows Event Log.
Examples
The following command backs up all the current data sets to the DeltaVBackups directory on the c: drive. If
the directory does not exist, it will be created as part of the backup process.
HistorianBackup c:\DeltaVBackups
A UNC path may also be defined for the backup directory. The shared folder should have full control
permissions.
HistorianBackup \\server\share
The following command creates a new active data set and backs up all the current data sets to the
DeltaVBackups directory on the c: drive.
HistorianBackup c:\DeltaVBackups
The following command backs up all current and extended history data sets.
HistorianBackup c:\DeltaVBackups
/DeleteIfGTDays:15
The following command backs up all current data sets whose Backup Status is "Modified." If the /Extended
switch had also been used, the same criterion would have been applied to the Extended data sets. In the
Continuous Historian Administration application, the Backup Status field changes from "Modified" to
"Backed Up."
HistorianBackup c:\DeltaVBackups
/BackupIfLTDays:3
The following command backs up all current data sets and deletes all backed up data sets whose end times
are prior to 15 days before the backup and which do not have a corresponding data set still in the Continuous
Historian data base. If the /Extended switch had also been used, the same criterion would have been applied
to the Extended data sets.
HistorianBackup c:\DeltaVBackups
/Extended
The following command backs up all current data sets for which the end times fall within the last 3 days.
HistorianBackup c:\DeltaVBackups
/CreateNewActive
/OnlyIfModified
The following command backs up all current data sets and allows for retries if certain error conditions exist.
The error conditions addressed by the /Retries:n switch include: a) The DeltaV Continuous Historian Server
is not running, b) the DeltaV Continuous Historian Server fails during the backup, or c) the DeltaV
Continuous Historian Server is unavailable due to being locked out by another application's access to the
DeltaV Continuous Historian database. The retry rate is once per minute and must be greater than or equal to
0 and less than 721. If the switch is not specified, Historian Backup defaults to 5 retries. If the database does
not become available during the retry period, an error will be logged stating that the retry period was
exceeded.
HistorianBackup c:\DeltaVBackups
/Retries:20
160
System Configuration
file. The log file may be overwritten or appended each time the backup procedure is run. Using the operator ">"
before the directory path and file name overwrites the current log file, while using the operator ">>" appends the
current log file. For example:
HistorianBackup c:\Backups >directorypath\logfile.log
will create a new log file in the specified directory, or
HistorianBackup c:\Backups >>directorypath\logfile.log
will append the current log information to an existing log file.
If you schedule the backup to create a log file automatically, the first example above will result in the log file being
overwritten each time the scheduled task runs; it may be preferable to use the second format (using >>), which
appends the backup information to the existing file.
To use this option with the Windows Task Scheduler, you must create a batch or command file and add the log file
option to the command file. The log file option is not available if the HistorianBackup.exe file is called directly from
the Windows Task Scheduler. It is also recommended that you specify the full path for the log file; otherwise the log
file will be placed in the same directory as the batch/command file, which may not be the desired location.
For example:
c:\DeltaV\bin\HistorianBackup d:\histbackup >>d:\histbackup\backup.log
will append the backup procedure details to the existing log file backup.log in the d:\histbackup directory (the same
directory as the backup files).
Backed up data sets that are no longer in the Continuous Historian database, that are located in
\\Siteserver\CHBackups, and that are greater than 30 days old will be deleted.
A log file, CHBackup.log, will be created the first time the scheduled backup runs and appended each time
thereafter.
161
Note The user creating the Scheduled Task must have the appropriate Windows and DeltaV security privileges to run
the Scheduled Task, access the Continuous Historian backup feature, and write the log file.
Warning During a Scheduled Task backup, a command line window will open briefly with information about the
backup if the logged on user is one who has privileges to run the Scheduled Task. Do not close this window. If this
window is closed, the backup will be cancelled.
Unsuccessful Backups
If the DeltaV Continuous Historian Database is unavailable due to access by another applications and does not
become available again during the retry period, an error will be logged stating that the retry period was exceeded. The
error message is available for viewing in the Windows Event Viewer or the backup log file (if this option was
selected). The applications that may "lock" the Continuous Historian Database are:
DeltaV Continuous Historian Administration when performing a Backup, Restore, Export, Create Extended,
or Delete operation
DeltaV Continuous Historian Server when performing an Automatic Export or Delete operation
If the operation completes with the retry period, the backup will start and complete normally.
Description
Multiple instances of Historian Backup utility running. The user should probably try to
run the batch/command file at regular intervals until successful or until a more severe
error occurs.
Invalid parameter. The command line's syntax is incorrect. The user should correct the
problem and rerun the batch/command file.
162
System Configuration
Error Level
Description
The directory specified is a special folder (such as COM or AUX). Change the
directory name and rerun the batch/command file.
The local directory is one to which the user performing the backup does not
have write access. Change the directory name and rerun the batch/command
file.
The directory specified is a local/separate node's shared folder to which the user
does not have write access. Change the directory name and rerun the batch/
command file.
Wrong History Installed. Either there is no DeltaV Continuous Historian installed or the
legacy Continuous Historian is installed. Contact the System Administrator.
No DeltaV. DeltaV is not installed or the DeltaV service is not running. Contact the
System Administrator.
Can't Create New Active Data Set. The user does not have the privileges necessary to
create a new Active Data Set. Contact the System Administrator.
Backup Exception. Analyze the Exception text shown in the Event Log/batch/command
file output. Contact Emerson Process Management for help.
163
In the Office 2003 Setup dialog, choose Add or Remove Features and click Next.
In the next dialog, check "Choose advanced customization of applications" and click Next.
In the DeltaV bin directory, double-click the file DvCHXLASetup.Office2003.msi, the installer for the
Continuous Historian Excel Add-In. (Alternatively, you can right-click and select Install from the context menu.)
On the Select Installation Folder screen, accept the default directory for installation, and select whether the addin is to be available to others who may use the computer or only yourself.
The .NET Programmability Support must be installed before Excel is used with the DeltaV Continuous Historian
Excel Add-In. If Excel is started without .NET Programmability Support, you should follow the steps above to add
the required support and then reactivate the DeltaV Continuous Historian Add-In by running the ExcelAddIn.reg file
from the Add-In's installation folder (C:\Program Files\Emerson Process Management\DeltaV Continuous Historian
Excel 2003 Add-In\ by default.)
The Continuous Historian Add-In must be uninstalled and reinstalled with each upgrade of the DeltaV System to a
new version. You can uninstall the Add-In using the Windows Control Panel option Add or Remove Programs. You
164
System Configuration
can also uninstall the Add-In by running the DvCHXLASetup.Office2003.msi installer and selecting the Remove
option.
Two other selections are Edit Function, which will bring up the worksheet function dialog for an existing formula for
editing, and Refresh, which will cause all Continuous Historian worksheet functions on the active worksheet to be
refreshed from the historian database.
Worksheet Functions
The Continuous Historian Excel Add-In provides dialogs to help in configuring the worksheet functions. The dialogs
are:
Configure Single Value Function - to configure a worksheet function to retrieve a single sample for a tag at
a specified time (previous sample, next sample, or interpolated)
Configure Raw Data Function - to configure a worksheet function to retrieve available samples for a
single tag within a time period
Configure Calculated Data Function - to configure a worksheet function to retrieve calculated data
relating to a single tag over a time period which is broken down into a number of subintervals of equal
duration
For information on using the dialogs to configure the worksheet functions, refer to the topic Using the Worksheet
Function Dialogs. For details on the functions, including the syntax and arguments, refer to the topic Worksheet
Function Reference.
165
GMT - Dates and times are presented as they were recorded by the Continuous Historian.
Local Time - Dates and times are presented in the user's local time as it applied at the time of the recording.
For example, if the event occurred during daylight saving time, it will be presented showing the daylight
saving local time even when viewed outside daylight saving time.
GMT Offset - Dates and times are presented with a fixed, user-configurable, offset (+/- hh:mm) from GMT.
This offset will be constant, and will disregard daylight saving time. This mode would be useful where data
is viewed in a different locale from where it was recorded. It will allow the data to be viewed in an
approximation of the local time of the plant.
166
System Configuration
A similar, though potentially more serious, problem occurs where you wish to find out data relating to an occurrence
around the time that daylight saving time starts.
Consider a plant in a U.S. state that operates under Central Time. At 2:00 a.m. on October 31, 2004 daylight saving
time ends (Central Daylight Time finishes and Central Standard Time is used). The local time thus goes from
01:59:59 to 01:00:00. This is the second time it has been 01:00:00 that day. If anything goes wrong in the plant during
the next hour, it will not be possible to view that data in the DeltaV Continuous Historian Excel Add-In if local times
are used. This is because, in converting to GMT, the first occurrence of times between 01:00:00 and 01:59:59 on
October 31, 2004 is assumed. You would need to choose to use either GMT or GMT Offset when dealing with such
issues.
In cell B1, enter the start date and time in the format mm/dd/yyyy hh:mm:ss; for example, 10/20/2004 08:15:00.
(Note that the date format required by Excel is dependent on the user's locale.)
In cell C1, enter the end time using a formula, for example "=B1 + 1/24". This sets the end time for the period to
one hour (1/24 day) from the start time.
Select cell A3 as the cell in which to enter the formula for the worksheet function. This will be the top left cell of
the array in which the results are displayed.
Note A range of 61 rows by 5 columns will be needed for the results. (This includes the header row and 60 rows of
data.) Rather than select the entire range, the user may select the top left cell of the range, for example, A3, and then
use the option "Adjust selection to accommodate results" in the worksheet function dialog to automatically extend the
range to the appropriate size.
167
From the menu bar select DeltaV | Continuous Historian | Configure Calculated Data Function. The Configure
Calculated Data Function dialog appears.
168
System Configuration
For Tag, click the cell reference button to the right of the tag field
Click on cell A1 in the worksheet to automatically fill in the cell reference, or type A1 or $A$1 in the dialog box.
For the Period start time, select Cell Reference and enter B1 (or $B$1) to indicate that the start time is stored in
cell B1 (or click the cell reference button and then click on cell B1 in the worksheet).
For the Period end time, select Cell Reference and enter C1 (or $C$1) to indicate that the end time is stored in
cell C1 (or click the cell reference button and then click on cell C1 in the worksheet).
For Intervals, select Interval, enter 1 and select minute(s) from the drop-down list.
Under Display Data, select Header Row to show the column names for the returned data.
Select the Columns by holding the Control key and selecting Minimum Value, Minimum Timestamp, Maximum
Value, Maximum Timestamp, and Average Value.
Click the right arrow button to add the selected columns to the Selected Columns list.
Note As changes are made to the optional fields, the Worksheet Required Range is updated to show the dimensions
of the array that will be yielded.
10 Under Worksheet, make sure the option to "Adjust selection to accommodate results (if necessary)" is selected.
(By default, this option is selected.)
Note Since there is no data below or to the right of the selected cell, there is no need to check the "Insert rows and
columns" checkbox. Also, since the selected dates do not run across the daylight saving change, there is no need to
check the box for Extra rows.
11 Click the "Try It..." button to preview the results.
Note This button opens a grid containing the actual data as queried from the DeltaV Continuous Historian database.
The Try It window shows the row and column at which the data will be inserted. The dialog can be closed before the
query is complete. While the query is being performed, the title bar indicates that it is working. On completion, the
title bar indicates the number of rows and columns and the time taken to perform the query.
169
12 Close the Try It results window and click OK on the main dialog.
The resulting worksheet, after clicking OK (and reformatting the column widths and the date format) is shown
below:
170
System Configuration
Single Value Function (DvCHValue) - a worksheet function to retrieve a single sample for a tag at a
specified time (previous sample, next sample, or interpolated)
Raw Data Function (DvCHRaw) - a worksheet function to retrieve available samples for a single tag
within a time period
171
Calculated Data Function (DvCHIntervals) - a worksheet function to retrieve calculated data relating to a
single tag over a time period divided into a number of subintervals of equal duration
The format for each function, an example, and a description of the function arguments are presented in the remainder
of this topic. Note, in the examples, that some of the arguments (such as strings, column names, tags, dates and times)
must be enclosed in quotation marks, while others (cell references, numbers, and Booleans) are not.
Single Value Function (DvCHValue)
This worksheet function is used to retrieve a single sample for a tag at a specified time. If used to show headers,
timestamps, or status information about the values, this function must be entered as an array formula in a range that
has the appropriate number of rows and columns. Use the DeltaV Continuous Historian "Configure Single Value
Function" dialog to help set up a call to this function.
Syntax
DvCHValue(connection, tag, show_header, columns, time_mode, selection_mode, timestamp)
Example
=DvCHValue("localhost", "DeltaV=MAIN_WORKSTATION CHS250_1S/SGGN1/OUT.CV", TRUE,
"Value;Timestamp", "GMT-06:00", 0, "9/25/04 12:00:00 PM")
Function Arguments
Connection - the node name of the DeltaV Continuous Historian server PC.
Tag - the DeltaV tag for which you want to retrieve data. The tag can be text, such as FIC101.PV, or a cell reference.
In the case of a cell reference (such as $A$1), the contents of the referenced cell must contain a valid tag.
Show_header - A Boolean (TRUE or FALSE) that indicates whether or not you want the returned data to have a
column header row.
Columns - a string that defines the columns that will be included in the results. Column definitions are separated by
semicolons. Each column definition comprises the column name and, optionally, various attributes relating to that
specific column. Column attributes are separated by commas. Supported columns and attributes are as follows:
For INT32, UNIT32, and Float data types, the value stored by Excel is a Variant Double.
For enumerations, the value stored by Excel is the state name in a Variant String.
172
System Configuration
Time_mode - indicates how the timestamp argument should be interpreted. The Historian database records all times
in GMT; the time_mode argument specifies what conversion, if any, should be applied to the supplied timestamp in
order to convert to GMT.
Local - the timestamp is treated as being in the client PC's time zone. Conversion to GMT takes into
consideration whether the timestamp falls within daylight saving time.
GMT+/-hh:mm - the time is adjusted by the specified hh:mm; daylight saving time has no effect.
Selection_mode - indicates how you want to select data in relation to the time(s) specified.
Timestamp - is a single timestamp for which the DeltaV Continuous Historian database is queried. It may be text or a
cell reference. If the timestamp argument is a reference, the contents of the referenced cell must be a valid timestamp.
Raw Data Function
This worksheet function is used to retrieve available samples for a single tag within a specified time period. The
function must be entered as an array formula in a range that has the appropriate number of rows and columns. Use
the Continuous Historian "Configure Raw Data Function" dialog to help set up a call to this function.
Syntax
DvCHRaw(connection, tag, show_header, columns, time_mode, period_start, period_end, start_boundary,
end_boundary, max_num_values)
Example
=DvCHRaw("localhost", "DeltaV=MAIN_WORKSTATION CHS250_1S/SGGN1/OUT.CV", TRUE,
"Value;Timestamp,Local;Parameter Status,IsGood;Collection Status,Text", "GMT", "10/4/04 3:02:05 PM",
"10/5/04 3:02:05 PM", 1, 1, 50)
Function Arguments
Connection - the node name of the DeltaV Continuous Historian server PC.
Tag - the DeltaV tag for which you want to retrieve data. The tag can be text, such as FIC101.PV, or a cell reference.
In the case of a cell reference (such as $A$1), the contents of the referenced cell must contain a valid tag.
Show_header - A Boolean (TRUE or FALSE) that indicates whether or not you want the returned data to have a
column header row.
Columns - a string that defines the columns that will be included in the results. Column definitions are separated by
semicolons. Each column definition comprises the column name and, optionally, various attributes relating to that
specific column. Column attributes are separated by commas. Supported columns and attributes are as follows:
173
For INT32, UNIT32, and Float data types, the value stored by Excel is a Variant Double.
For enumerations, the value stored by Excel is the state name in a Variant String.
Time_mode - indicates how the timestamp argument should be interpreted. The Historian database records all times
in GMT; the time_mode argument specifies what conversion, if any, should be applied to the supplied timestamp in
order to convert to GMT.
Local - the timestamp is treated as being in the client PC's time zone. Conversion to GMT takes into
consideration whether the timestamp falls within daylight saving time.
GMT+/-hh:mm - the time is adjusted by the specified hh:mm; daylight saving time has no effect.
Period_start - the timestamp of the start of the period. If this is a cell reference, the referenced cell must contain a
valid timestamp.
Period_end - the timestamp of the end of the period. If this is a cell reference, the referenced cell must contain a valid
timestamp.
Start_boundary - defines how the start boundary is handled:
174
If 0 (inside), the first sample returned will be the first sample after (or at exactly the same time as) the
period_start.
If 1 (outside), the first sample returned will be the first sample before (or at exactly the same time as) the
period_start.
System Configuration
If 0 (inside), the last sample returned will be the first sample before (or at exactly the same time as) the
period_end.
If 1 (outside), the last sample returned will be the first sample after (or at exactly the same time as) the
period_end.
Max_num_values - the maximum number of values you wish to retrieve. Any samples in the database within the time
period in excess of this number will not be retrieved.
If period_start is an earlier time than period_end, then samples are taken forward from the start time toward
the end time.
If period_end is an earlier time than period_start, then samples are taken backward from the start time
toward the end time.
If max_num_values is set to -1, all samples within the time period are retrieved.
For INT32, UNIT32, and Float data types, the value stored by Excel is a Variant Double.
For enumerations, the value stored by Excel is the state name in a Variant String.
175
Time_mode - indicates how the period_start and period_end arguments should be interpreted. The Historian database
records all times in GMT; the time_mode argument specifies what conversion, if any, should be applied to the
supplied timestamp in order to convert to GMT.
Local - the timestamp is treated as being in the client PC's time zone. Conversion to GMT takes into
consideration whether the timestamp falls within daylight saving time.
GMT+/-hh:mm - the time is adjusted by the specified hh:mm; daylight saving time has no effect.
Period_start - the timestamp of the start of the period. If this is a cell reference, the referenced cell must contain a
valid timestamp.
Period_end - the timestamp of the end of the period. If this is a cell reference, the referenced cell must contain a valid
timestamp.
Samples - one of the following:
The number of samples required (without quotation marks). The start and end of the period each yield a
sample; therefore, this number must be 2 or greater.
The interval between samples (enclosed in quotation marks). This is a positive number followed by a units
string, which must be one of the following: hours, minutes, or seconds. If necessary, the period_end is
automatically adjusted to extend the overall period such that it is a multiple of this interval.
176
System Configuration
Example
=DvCHIntervals("localhost", "DeltaV=MAIN_WORKSTATION CHS250_1S/SGGN1/OUT.CV", TRUE,
"Minimum Value;Minimum Timestamp;Maximum Value;Maximum Timestamp;Average Value", "Local",
"10/6/04 11:33:33 AM", "10/7/04 11:33:33 AM", 50)
Function Arguments
Connection - the node name of the DeltaV Continuous Historian server PC.
Tag - the DeltaV tag for which you want to retrieve data. The tag can be text, such as FIC101.PV, or a cell reference.
In the case of a cell reference (such as $A$1), the contents of the referenced cell must contain a valid tag.
Show_header - A Boolean (TRUE or FALSE) that indicates whether or not you want the returned data to have a
column header row.
Columns - a string that defines the columns that will be included in the results. Column definitions are separated by
semicolons. Each column definition comprises the column name and, optionally, various attributes relating to that
specific column. Column attributes are separated by commas. Supported columns and attributes are as follows:
For INT32, UNIT32, and Float data types, the value stored by Excel is a Variant Double.
For enumerations, the value stored by Excel is the state name in a Variant String.
For INT32, UNIT32, and Float data types, the value stored by Excel is a Variant Double.
For enumerations, the value stored by Excel is the state name in a Variant String.
177
For INT32, UNIT32, and Float data types, the value stored by Excel is a Variant Double.
For enumerations, the value stored by Excel is the state name in a Variant String.
Time_mode - indicates how the period_start and period_end arguments should be interpreted. The Historian database
records all times in GMT; the time_mode argument specifies what conversion, if any, should be applied to the
supplied timestamp in order to convert to GMT.
Local - the timestamp is treated as being in the client PC's time zone. Conversion to GMT takes into
consideration whether the timestamp falls within daylight saving time.
GMT+/-hh:mm - the time is adjusted by the specified hh:mm; daylight saving time has no effect.
Period_start - the timestamp of the start of the period. If this is a cell reference, the referenced cell must contain a
valid timestamp.
178
System Configuration
Period_end - the timestamp of the end of the period. If this is a cell reference, the referenced cell must contain a valid
timestamp.
Intervals - one of the following:
The duration of each interval (enclosed in quotation marks). This is a positive number followed by a units
string, which must be one of the following: days, hours, minutes, or seconds. If necessary, the period_end is
automatically adjusted to extend the overall period such that it is a multiple of this interval.
179
DeltaV limits
Legacy Historian
limits
32-bit
unsigned
integer
Max 4,294,967,295
Min 0
Max 2,147,483,647
Floating point
Max 3.40282e+38
Min -3.40282e+38
Max 1.70141e+38
Min -1.70141e+38
32-bit signed
integer
Max 2,147,483,647
Min -2,147,483,648
Max 2,147,483,647
Min -2,147,450,880
180
System Configuration
Operating details involving the DeltaV OPC History Server (startup, shutdown, client interaction, etc.) are written to
the Windows Event Log.
References
Users should be familiar with the following specifications, available from the OPC Foundation:
OPC Foundation - OPC Historical Data Access Specification - Version 1.20 Released December 10, 2003
OPC Foundation - OPC Historical Data Access Automation Interface Standard - Version 1.0 Released
January 26, 2001
OPC Foundation - OPC Common Definitions and Interfaces - Version 1.0 - October 27, 1998
Users who develop clients using Visual Basic or Excel with VBA may find the Automation Interface Standard most
helpful.
DeltaV OPC History Server Functional Overview
The DeltaV Application Station acts as a gateway between the DeltaV Continuous Historian and other applications
and networks. The DeltaV OPC History Server runs on this workstation, providing DeltaV historical data access to
applications that are running either on the Application Station or on a machine with a network connection to the
Application Station. The DeltaV OPC History Server also runs on the ProfessionalPLUS workstation.
181
Note In order to run an OPC HDA client on a non-DeltaV workstation, first install the OPC Remote application. To
install the OPC Remote application, use the setup file located in the OPC Remote directory on the DeltaV Installation
CD (in the directory DVExtras\OPCRemote). The version must be the same as the installed version of the DeltaV
software.
OPC Interfaces
Properties and Methods
The DeltaV OPC History Server incorporates all the required interfaces and methods of the OPC HDA Specification.
It also incorporates the optional "ReadProcessed" method under the IOPCHDA_SyncRead interface. See "OPC
HDA Custom Interfaces and Methods" in the topic DeltaV OPC History Server for more information on the custom
interfaces and methods.
182
System Configuration
The DeltaV OPC History Server provides a timestamp and quality value associated with each history data value. For
raw data values, the timestamp is the time the value was recorded by the DeltaV Continuous Historian. For processed
data values, the timestamp is the start of the interval, with two exceptions, minimum and maximum, which can be
requested with actual timestamps or interval timestamps. The OPC HDA quality value makes use of the parameter
and collection status quality information that is available from the DeltaV Continuous Historian.
The DeltaV OPC History Server presents time to client applications in UTC. Client applications are responsible to
make any necessary timestamp modifications (such as conversion to local time).
Browser
The DeltaV OPC History Server has a browser that exposes all parameters stored in the DeltaV Continuous Historian.
The browser supports the use of "wild cards" for string filters to assist in finding the stored parameters. A single
character may be filtered using the question mark character (?). For example, requesting TIC-100?/PID1/PV.CV will
return TIC-1000/PID1/PV.CV, TIC-1001/PID1/PV.CV, etc.
Multiple characters may be filtered by the asterisk character (*). For example, requesting TIC-1001/PID1/*.CV will
return TIC-1001/PID1/OUT.CV, TIC-1001/PID1/PV.CV, and TIC-1001/PID1/SP.CV.
In addition, the logical operators equal to (=) and not equal to (!=) may be used with the wild card filters to further
refine the parameter search.
Performance
The DeltaV OPC History Server loading is determined by the client request loading. Client applications should be
designed and tested to ensure that history collection performance is not degraded. The frequency of requests and the
amount of data requested can both affect loading. Each request also imposes a load on the DeltaV Continuous
Historian Server, and care should be taken to avoid loading it to the point that data collection would be affected.
Sample Client Applications
Two client applications are provided that allow browsing the items in the DeltaV OPC History Server and displaying
raw data for individual items for a fixed time span or start/end time with a fixed number of samples. The applications
can write the returned data to a file in a common file format (csv, xml) that can be used by third-party applications.
One sample client application (OPCHDAClient.exe), located in the DeltaV\bin directory, allows the user to create an
XML input script file that is used as a command line argument and writes output to text files. Several example script
files are available in the DeltaV\samples directory. The functions of this client are documented in the topic OPC
Historical Data Access Clients. A second client application, HDAprobe.exe, located in the DeltaV\bin directory, may
be used for testing and troubleshooting purposes and to help understand the operation of the DeltaV OPC History
Server. This client is not documented or supported.
To use the OPCHDAClient.exe sample client provided with the DeltaV software, it is assumed that the user is
familiar with XML and has access to an XML schema tool, such as XML Spy.
183
0x20040 "Interpolated,
Uncertain"
184
System Configuration
185
IOPCCommon::SetLocaleID
The only supported locale is English with a sublanguage of US English.
IOPCCommon::GetLocaleID
The value returned from this method corresponds to English with a sublanguage of US English.
IOPCCommon::QueryAvailableLocaleIDs
The available locale is returned by this method.
IOPCCommon::GetErrorString
This method may be used to convert from an HRESULT returned by any of the methods or the HRESULT
for an HDA Item into a user friendly description of the error.
IOPCCommon::SetClientName
This method may be used by a client to set the name of the client. The client name is used in some of the
events recorded in the Windows Event Log.
IConnectionPointContainer
The IConnectionPointContainer is a Microsoft defined interface used to obtain call back interfaces. The DeltaV OPC
History Server implements this interface in support of the client providing an IOPCShutdown interface. The methods
making up this interface are:
IConnectionPointContainer::EnumConnectionPoints
Only the IOPCShutdown interface is included in the IEnumConnectionPoints enumerator.
186
System Configuration
IConnectionPointContainer::FindConnectionPoint
This method may be used to obtain the interface corresponding to the IID_IOPCShutdown.
IOPCShutdown
This is a client-side interface used by the DeltaV OPC History Server to notify clients when the supporting DeltaV
services are shutting down. The single method provided by this interface is:
IOPCShutdown::ShutdownRequest
This method is invoked by the DeltaV OPC History Server to notify the client that the DeltaV services are
shutting down.
IOPCHDA_Server
This interface is the primary interface for the DeltaV OPC History Server. The IOPCHDA_Server interface provides
a method for setting up access to historical data values. The methods that make up this interface are:
IOPCHDA_Server::GetItemAttributes
This method returns the list of attributes supported by the DeltaV OPC History Server. These are:
Data Type
Stepped
ItemID
Maximum Time Interval
Minimum Time Interval
Exception Deviation (expressed in Engineering Units)
Current DeltaV Module Description
Current DeltaV Engineering Units
Current DeltaV Engineering Units 100% Value (default is 100)
Current DeltaV Engineering Units 0% Value (default is 0)
IOPCHDA_Server::GetAggregates
This method returns the list of aggregates supported by the DeltaV OPC History Server. These are:
Interpolative
Time Average
Count
Minimum Actual Time
Minimum
Maximum Actual Time
Maximum
Start
End
IOPCHDA_Server::GetHistorianStatus
This method may be used to obtain the status of the DeltaV OPC History Server.
IOPCHDA_Server::GetItemHandles
This method returns associations between server handles and client handles for specific HDA items.
IOPCHDA_Server::ReleaseItemHandles
This method releases associations between server handles and client handles for specific HDA items.
IOPCHDA_Server::ValidateItemIDs
This method validates that specific HDA Item IDs are known to the server.
187
IOPCHDA_Server::CreateBrowse
This method returns a pointer to an OPCHDA_Browser interface. The Item ID filtering is specified as part
of the creation of a new browser.
IOPCHDA_Browser
This interface provides a method to access the list of OPC HDA Item IDs that pass the filter criteria set when this
browser was created. It should be noted that the DeltaV Continuous Historian provides a flat list of historical
parameters. Thus, the DeltaV OPC History Server provides a flat list of OPC HDA Item IDs.
IOPCHDA_Browser::GetEnum
This method returns an enumeration containing all of the OPC HDA Item IDs provided by the DeltaV
Continuous Historian that pass the filter criteria.
IOPCHDA_Browser::ChangeBrowsePosition
This method may be used to move up and down the list of OPC HDA Item IDs or to move directly to a
particular OPC HDA Item ID.
IOPCHDA_Browser::GetItemID
This method provides a way to obtain the current OPC HDA Item ID.
IOPCHDA_Browser::GetBranchPosition
This method provides the current OPC HDA Item ID.
IOPCHDA_SyncRead
This interface provides access to the data held by the DeltaV Continuous Historian.
IOPCHDA_SyncRead::ReadRaw
This method reads the values, qualities, and timestamps from the DeltaV Continuous Historian database for
the specified time domain for one or more OPC HDA Items.
IOPCHDA_SyncRead::ReadProcessed
This method requests an aggregate value or values to be computed by the DeltaV Continuous Historian for
one or more OPC HDA Items, providing values, qualities, and timestamps. See
IOPCHDA_Server::GetAggregates for a list of supported aggregates.
IOPCHDA_SyncRead::ReadAtTime
This method is not supported by the DeltaV OPC History Server at this time.
IOPCHDA_SyncRead::ReadModified
This method is not supported by the DeltaV OPC History Server at this time.
IOPCHDA_SyncRead::ReadAttribute
This method reads the attribute values and timestamps for the specified time domain for an item. The DeltaV
OPC History Server only supports current values for attributes. See IOPCHDA_Server::GetItemAttributes
for a list of supported attributes.
188
System Configuration
Copy the file OPCHDAauto.dll from the DeltaV workstation to %WINDIR%\SYSTEM32\ on the client
machine.
189
Definition
Value/Comment
LogFileDirectory
LogFileName
OpcHdaLog by default
OutputDirectory
OutputFileName
Must be specified
OutputFileFormat
HostName
TimeSetting
LOCAL(default), UTC
<Execution> Tag
The Execution tag defines the data to be retrieved from the DeltaV OPC History Server.
<Execution> has one complex tag:
<Execution>
<Steps> </Steps>
</Execution>
<Steps> Tag
<Steps> contains a list of <Step> tags. The steps will be executed in sequence.
190
System Configuration
<Step> Tag
The <Step> tag defines the configuration of one data item to be retrieved from the DeltaV OPC History Server,
detailed in its subtags.
<Step> has the following single value tags.
Tag Name
Definition
Value/Comment
Interface
IOPCHDA_SyncRead
Method
ReadRaw
ReadProcessed
ReadAttribute
ItemID
AggregateID
OPCHDA_Interpolative
OPCHDA_TimeAverage
OPCHDA_Count
OPCHDA_MinimumActualTime
OPCHDA_Minimum
OPCHDA_MaximumActualTime
OPCHDA_Maximum
OPCHDA_Start
OPCHDA_End
AttributeID
OPCHDA_DataType
OPCHDA_Stepped
OPCHDA_ItemID
OPCHDA_Max_Time_Int
OPCHDA_Min_Time_Int
OPCHDA_Exception_Dev
StartTime
"10-Jan-2001 + 1 MO",
"25 January 1996",
"8:30:00",
"20:30:00",
"July 25, 1996 8:30:00" ,
"8:30:00 Jan 25, 1996",
"1/25/1996 8:30:00"
EndTime
"10-Jan-2001 + 2 MO",
25 January 1996,
9:30:00,
21:30:00,
July 25, 1996 9:30:00,
9:30:00 Jan. 25, 1996,
"1/25/1996 9:30:00"
NumValues
1, 2, (1 by default)
Bounds
191
Tag Name
Definition
Value/Comment
ResampleInterval
0 by default
FileSuffix
Many of these parameters can be understood by reading the OPC HDA specification, Section 4.4.3, for the ReadRaw,
ReadProcessed, and ReadAttribute methods.
192
System Configuration
<StartTime>NOW - 1 D</StartTime>
<EndTime>NOW</EndTime>
<NumValues>1</NumValues>
<Bounds>TRUE</Bounds>
</Step>
</Steps>
</Execution>
</DeltaVOpcHdaClient>
OpcHdaProcessed.xml
The OpcHdaProcessed.xml sample script provides an example of how to obtain processed (also known as
interpolated or calculated) data from the DeltaV OPC History Server. In the following example, the goal is to read
one day's interpolated values of "FIC-101/PID1/SP.CV" before current time, at 10-minute intervals. The data is to be
read from the local DeltaV OPC History Server, with output to a tab-delimited text file named FIC-101.TXT.
The script file (OpcHdaProcessed.xml) contains the following:
<DeltaVOpcHdaClient>
<Configuration>
<OutputFileName>FIC-101</OutputFileName>
<OutputFileFormat>TXT</OutputFileFormat>
</Configuration>
<Execution>
<Steps>
<Step>
<Interface>IOPCHDA_SyncRead</Interface>
<Method>ReadProcessed</Method>
<ItemID>FIC-101/PID1/SP.CV</ItemID>
<StartTime>NOW 1 D</StartTime>
<EndTime>NOW</EndTime>
<ResampleInterval>600000</ResampleInterval>
<AggregateID>OPCHDA_INTERPOLATIVE</AggregateID>
</Step>
</Steps>
</Execution>
</DeltaVOpcHdaClient>
OpcHdaAttr.xml
The OpcHdaAttr.xml sample script provides an example of how to obtain attribute data from the DeltaV OPC History
Server. In the following example, the goal is to read current data type and exception deviation of "FIC-101/PID1/
SP.CV". The attribute data is to be read from a remote server machine called PROPLUS, with output to XML files
named FIC-101_CurrentType.XML and FIC-101_ExecDev.XML. T
The script file (OpcHdaAttr.xml) contains the following:
<DeltaVOpcHdaClient>
<Configuration>
<OutputFileName>FIC-101</OutputFileName>
<HostName>PROPLUS</HostName>
</Configuration>
<Execution>
<Steps>
193
<Step>
<Interface>IOPCHDA_SyncRead</Interface>
<Method>ReadAttribute</Method>
<ItemID>FIC-101/PID1/SP.CV</ItemID>
<StartTime>NOW</StartTime>
<EndTime></EndTime>
<AttributeID>0x01</AttributeID>
<FileSuffix>_CurrentType</FileSuffix>
</Step>
<Step>
<Interface>IOPCHDA_SyncRead</Interface>
<Method>ReadAttribute</Method>
<ItemID>FIC-101/PID1/SP.CV</ItemID>
<StartTime>NOW</StartTime>
<EndTime></EndTime>
<AttributeID>OPCHDA_EXCEPTION_DEV</AttributeID>
<FileSuffix>_ExecDev</FileSuffix>
</Step>
</Steps>
</Execution>
</DeltaVOpcHdaClient>
Output File
The following is the table of keywords that are used in the output files. The keywords will be column names in text
output files and tag/attribute names in XML output files.
Data Value
TimeStamp
Quality
AtrtributeValue
Item
XML only
Attribute
XML only
ItemID
XML only
AttributeID
XML only
AggregateID
XML only
194
System Configuration
The following is a partial output from the OpcHdaRaw.xml sample script in comma-delimited output file format
(*.csv).
DataValue,TimeStamp,Quality
12.345,December 23 2004 8:30:00,192
12.346,December 23 2004 8:31:00,192
12.347,December 23 2004 8:32:00,192
12.348,December 23 2004 8:34:00,192
The following is a partial output from the OpcHdaProcessed.xml sample script in tab-delimited output file format
(*.txt).
DataValue TimeStamp Quality
12.345 December 23 2004 8:30:00 192
12.446 December 23 2004 8:40:00 192
12.547 December 23 2004 8:50:00 192
12.648 December 23 2004 9:00:00 192
The following is the output from the OpcHdaAttr.xml sample script showing a comma-delimited output file of the
current data type:
AttributeValue,TimeStamp
5,December 24 2004 8:30:00
XML Output
The XML output file uses a very simple schema that can be loaded into Internet Explorer or into a Microsoft Word
document using the XML capabilities in MS Office.
Item tag has the following properties:
It contains a list of DataValue tags, each of which has the following properties:
195
196
System Configuration
Controller Considerations
Nodes are physical devices or pieces of equipment on the LAN, such as a controller or a console. You control your
process by downloading modules and defining I/O blocks and other configuration elements in the nodes. The
configuration tells the node how to act and what information you want to receive or save from the process.
You can define a node using the Configuration Assistant application or the DeltaV Explorer. To look at the status of a
node, use the Diagnostics application.
Note Unless specifically noted otherwise, all references to a workstation in the Books Online refer to one of these
DeltaV workstation types: Professional, ProfessionalPLUS, Operator or Base.
Auto-Sense Feature
When you connect controllers and I/O cards to an operational DeltaV control network, the system automatically
senses the controller and cards, as well as the card types. You do not have to type in all the I/O card types connected
to a controller because the DeltaV system does it for you.
Commissioning
An automatically sensed controller must be commissioned in order to be fully functional in the system. When the
system first senses a controller on the network, the controller is displayed in the Decommissioned Controllers section
of the Explorer. A decommissioned controller does not have an ID, an address, or a name. It is not bound to any
controller definition in the database. Commissioning is the process of dragging the controller icon from the
Decommissioned Controllers section to the Control Network section within the Explorer. Commissioning a controller
assigns an address and ID to the controller, and prompts you to supply a name and description.
Decommissioning
Decommissioning a controller takes it out of service. When you decommission a controller, all the information in the
controller is erased. You should not unassign modules when you decommission a controller because these
assignments can be restored through a download after you commission the controller.
Note Whenever you need to remove or a controller for service, or to move it to a new location on the control network,
you should decommission the controller.
When you decommission a controller, the controller icon and all its database information remains visible in the
Explorer. Database information includes all the configured cards, card types, channel types, and all the modules
assigned to the controller. You can restore all of this information by commissioning the controller and selecting the
Download Controller Node.
Controller Considerations
197
Note You can potentially lose online data if it is different from the information in the controller. For example, if you
have made online changes to a module from Control Studio, you lose this data when you decommission the controller
unless you first upload that data into the database. Refer to Uploading Recorded Parameter Changes for more
information.
198
Reading data is preferable to writing data, both for loading reasons and for communications status reasons.
A read operation has the appropriate status, depending on the state of communications. At the destination, a
written value holds the last value and last status and does not indicate communications problems if they
exist. If there is a communication failure between nodes, a written value does not reflect the current value
and status of the source data.
Normal situations occur in which both reads and writes fail. Partial downloads, overload, redundancy
switches, and other operations can all cause a read or write operation to fail (possibly without any indication
of failure) at some instant.
System Configuration
Unsolicited send operations contain a maximum of 2000 parameters per second for the MD controller. This
total is enforced. If the same parameter is being requested by multiple nodes, that parameter is counted
multiple times against this maximum. If there are more than 2000 unsolicited parameters to be sent through
an unsolicited send operation within a second, the excess parameters are held until the next second. This
means that, although the parameter data eventually arrives at the receiving node, the date may be slightly
older than expected. Develop configurations using a limit of 1000 parameters per second for the controller
and remote I/O node. Exceeding these recommended limits may affect system performance. In general, 2000
parameters per second cannot be sustained to another single node due to receive limitations and overhead
and handshaking limitations.
Write operations of either type are recommended to be no more than 20 per second per node.
The scan rate of modules configured with asynchronous writes must be greater than 100 ms to allow
processing time between write operations.
Reading any or all array elements from one controller to another is supported. Write operations of arrays
from node to node are not supported. An error is returned to the caller.
Due to normal system dynamics, a group of buffered asynchronous writes (such as multiple actions in a
single SFC step) does not necessarily act on the destination parameters in a predictable order.
Due to the relative priority of the various read and write operations versus other tasks in each node, in cases
of overload situations, reads and writes may not occur when expected.
A pulse action that writes to a parameter in another controller will retry the write as necessary while the step
is active. With the step active, this continues until the write gets confirmation from the destination node of
success. Possible write failures that will set ERROR and RERROR to TRUE include the write being rejected
due to a wrong mode or the value being invalid for the data type. In these cases, the write will be retried on
the next execution of the module. Between executions of the module, ERROR and RERROR will be TRUE,
but will toggle back to FALSE while the action status is PENDING. If the next attempted write again fails,
the cycle repeats.
In cases of communications failure, the retry mechanism will continue to attempt the write as long as the
step remains active. In a communications failure scenario, feedback is not available from the destination and
ERROR and RERROR will remain false. The write continues to be retried as long as the step is active.
If controllers are heavily loaded, the write may be re-buffered if necessary until there is feedback of success
or failure.
When a write fails, the action gets an error, which rolls up to the step, composite, and SFC level in
parameters called ERROR and RERROR. The phase's failure monitor can examine these parameters at the
run logic level and actions can be taken to inform the operator that a write has failed or other actions can be
performed as appropriate for the users implementation.
Keep inter-module and inter-controller communications to a minimum. Place I/O references within the
control module, not in a separate I/O module. Keep related modules with inter-module references in same
controller.
Controller Redundancy
The DeltaV system supports redundant controllers. A redundant controller consists of a pair of standard controllers
on separate 2-wide power/controller carriers connected together. Each controller requires a separate power supply
mounted on its carrier. One of the controllers in the pair is the active controller. The other controller is the standby
controller. The standby controller contains the same configuration as the active controller. When an active controller
Controller Considerations
199
fails, the standby controller takes over providing uninterrupted control operation without user intervention. The
standby controller gets updates of certain parameter values in the active controller over the redundancy link, but does
not execute control logic. When the switchover occurs, the new active controller reads back I/O data and the modules
begin to execute. A limited amount of re-initialization occurs in order to resume control without disruption. For
example, certain control and output function blocks begin executing in out-of-service mode and climb to their target
mode in order to force handshaking with other blocks. In most cases control actions resume on the first scan after a
switchover. For complex modules, one or a few scans of handshaking may be required. The apparent mode change on
a switchover is expected and has no adverse effect on control.
Even though each controller in a redundant pair does have its own MAC address and node address, a redundant
controller counts as a single node on the DeltaV control network in terms of network capacity.
A redundant controller requires a redundant controller license. Downloading a redundant controller without a license
results in a description of "Redundancy Not Licensed" in Process History View. In addition, the RedEnb diagnostics
parameter has a value of NO if no license is present.
Switchovers
A switchover from the active to the standby controller can occur for the following reasons:
Communications failure between the active controller and the I/O subsystem
Communications failure of both the primary and secondary network connections in the active controller
When a switchover occurs, the node status area on the Alarm Banner indicates the status change to the operator. The
system regenerates active, unacknowledged and suppressed alarms. The system does not regenerate alarms that are
both inactive and acknowledged. Alarm states are maintained during a switchover but General I/O Failure (IOF)
Alarms may change state momentarily.
The system stores a record of each switchover and the reason it occurred (if known). The switchover is logged in the
Process History event chronicle.
If the standby controller should fail, the software disables switchovers until you replace the failed unit.
Generally, there is no user impact related to a controller switchover. However, there are certain situations that the user
should be aware of when configuring control. These relate to HART digital variables, external references to other
controllers, and forced debug parameter values.
HART digital variables will have a value of zero with Bad status for six or more seconds after a controller switchover.
If you access a HART digital variable in an expression (Calc, Condition, or Action function block; SFC transition or
action), be sure to also consider the status of the variable in the expression. For example, use the value only when the
status is Good. Accessing HART digital variables in AI function blocks or by external reference parameters should be
done for monitoring, not control purposes.
When a controller switches over it can take several seconds to re-establish communication with other controllers.
External reference parameters that reference parameters in another controller will have BadNoCommNUV status
during this brief period following a switchover. Understand how downstream function blocks and expressions will
react to this bad status on a switchover so that your configuration will not create an output disruption. Refer to the
'status handling' subtopic of specific function blocks for this information.
200
System Configuration
A Condition function block that references a parameter in another controller has the potential to change its OUT_D
parameter when the referenced controller switches over. You can prevent this by selecting the 'Abort on Read Errors'
option in ALGO_OPTS. This is recommended unless you want OUT_D.ST to be BadNoCommNUV during the
switchover. In this case leave the Abort option deselected and change ERROR_OPT to 'Use Last'.
Forced debug parameter values (that is, those set in Control Studio's debug mode) are not retained following a
controller switchover. The value of the parameter is set to the default value as configured.
In general, the system regenerates process and device alarms during a controller switchover. This includes all active,
unacknowledged and suppressed alarms. Inactive and acknowledged alarms are not regenerated. General I/O Failure
(IOF) alarms may change state momentarily. The Time In values (displayed in the alarm list) and the alarm states are
not affected by the regeneration. The Time Last values on the alarm list are updated. Alarm strings may not be
maintained.
Manual Switchovers
Users with the Diagnostic Key can initiate a switchover from DeltaV Diagnostics. In Diagnostics, a redundant
controller has a Redundancy subsystem. To perform a manual switchover, select the Redundancy subsystem, click the
right mouse button, and then click Redundancy switchover.
Controllers have three parameters that determine whether a manual switchover can occur:
PAvail -- indicates whether the standby controller has received a download and is ready to take over
RedEnb -- indicates whether redundancy has been enabled for the pair. In order for redundancy to be
enabled, the active controller must have received a download.
In order for a manual switchover to occur, all three of the above parameters must have a value of Yes. If not, the
Status parameter provides additional details about why the controller cannot switch over.
Creating a Controller Placeholder
To create a placeholder for a redundant controller in DeltaV Explorer, add a controller node, and then click the
Redundant Controller option on the node's properties.
Installing a Redundant Controller
Installing a redundant controller is as simple as installing a single controller. The auto-sense feature in the DeltaV
system recognizes two controllers on adjacent, connected carriers as a redundant controller.
Refer to Installing your DeltaV Digital Automation System for physical installation instructions.
After installation, drag the controller from the Decommissioned Controllers section to the control network or to a
redundant placeholder. Assign an appropriate redundant license to the controller and download the controllers to
enable redundancy.
Installing a Standby Controller
You can connect a second controller to an existing controller's carrier to introduce redundant control without
interrupting your process. The system automatically commissions a standby controller when you install it. It is not
necessary to remove or decommission the active controller. The active controller continues to operate without
interruption. The system automatically assigns the standby with an address and downloads the standby controller
with the latest download and with any online changes made to the active controller. To install a standby controller
follow these steps:
Caution Follow the steps in the order shown. Do not install a second 2-wide carrier that already has a power supply
and controller installed. Doing so will result in a loss of configuration data for the active controller.
Controller Considerations
201
Using the DeltaV Explorer, assign an appropriate redundant controller license to the controller node that you
want to make redundant in DeltaV Explorer.
Install a second 2-wide carrier to the left of the current 2-wide carrier.
Insert the appropriate Power Supply in the left slot of the 2-wide carrier plug in the power cord.
Connect a controller to the carrier. The version of the controller you connect must match the existing controller's
version.
The DeltaV Explorer displays a redundant controller icon in place of the simplex icon.
If you are changing a simplex controller to a redundant pair, there is a one-time step required. In the DeltaV
Explorer, click the right mouse button on the controller, click Download, and then click Setup Data. This turns on
redundancy for the pair but does not disrupt any existing process control.
202
System Configuration
Controller Performance
Inside this topic
Module Scan Rate
Execution Order within the Module
Scan Rate Multiplier
Scan Rate of Interacting Modules
The DeltaV controller balances memory and CPU capacity with Device Signal Tag (DST) licensing limits. It is
possible to exceed a controller's memory and CPU capacity even if the controller license supports the number of
DSTs in the control strategy. However, for a typical application in a wet process industry, the configuration engineer
should be able to implement the required control strategies up to and including the DST license limit of the given
controller.
Following are some guidelines to help deliver the maximum controller CPU performance.
Controller Considerations
203
For example, consider the INTERLOCK_D input of the Device Control function block or the TRK_IN_D input of
the PID function block. These values might be used by the blocks to stop a motor or close a control valve. If the
Device Control or PID block executes before the block(s) that determine the value of the input, the module loses a
scan before acting on the input. For more information, refer to the section entitled Set the Execution Order of
Function Block in the Control Studio help system.
204
System Configuration
Controller Considerations
205
Floating Point
Boolean
Boolean W/Status
Discrete W/Status
Mode
Internal Reference Parameters (this functions only when one parameter that supports the restore parameter
values feature directly references another parameter that also supports the feature.
To restore a value for a parameter that is not a user-defined, module-level parameter, you can set up an internal
reference for the parameter and designate that its value be restored on restart.
The following energy metering function blocks (AGA_SI and AGA_US) parameters support the restore feature
automatically:
206
CURR_VOLUME
CURR_ENERGY
CURR_HRS_ON
LAST_VOLUME
LAST_HRS_ON
LAST_ENERGY
VOL_ACCUM
PCT_CURR_VOLUME
PCT_CURR_ENERGY
PCT_LAST_VOLUME
PCT_LAST_ENERGY
PCT_CURR_HRS_ON
PCT_LAST_HRS_ON
PCT_VOL_ACCUM
System Configuration
CURR_VOLUME_GOOD
CURR_ENERGY_GOOD
CURR_HRS_ON_GOOD
VOL_ACCUM_GOOD
Check the Restore parameter value after restart checkbox in the user-defined parameter properties.
Check the Restore parameter values after restart checkbox on the module properties dialog.
Set the controller cold restart feature for the associated controller as described below.
Note The loss of power to a controller and a subsequent cold restart or user restart can be disruptive to the process.
An uninterruptible power supply (UPS) is highly recommended as a means to prevent process disruption during a
short power loss. For example, if you specify 1 hour in the Controller Node properties box and the controller loses
power and regains power in an hour or less, the controller downloads itself using the configuration stored in
nonvolatile memory. However, if the controller regains power after 61 minutes or more, you must perform the
equivalent of a restart by downloading the controller node.
total download
Controller Considerations
207
The local cold start database (controller nonvolatile memory) is cleared (that is, made unusable) by any of the
following operations:
controller upgrade
decommission/commission
partial download
upload
If the local database is unusable and a non-zero cold restart time is configured, the controller receives its download
scripts from the ProfessionalPLUS workstation cold start database in the event of a restart that occurs before the cold
restart time has elapsed.
The hardware used for storing the parameter values supports unlimited write cycles. However, the amount of space
allocated for the restore parameter values after restart feature is 390 kilobytes. Consider the following to avoid
exceeding the 390 kilobyte limit:
Each parameter configured with Restore parameter values after restart uses 8 bytes of controller NVM.
There is an additional overhead of 12 bytes for modules: a module with one parameter uses 20 bytes of
controller NVM.
To determine how much free NVM is available, check the controller's FreNVM parameter in DeltaV Diagnostics.
208
System Configuration
COLDSTRTSRC is the source from which the controller receives its download data during a cold restart.
The possible values are Controller (that is, controller nonvolatile memory), Workstation (that is,
ProfessionalPLUS download scripts), or Not Configured (if Cold Restart Perform Within is equal to zero).
SECSLASTPF is the number of seconds since restarting from the last power failure.
FRENVM (Free Non-volatile Memory) is the amount of memory (in bytes) that can be allocated to
parameters for which the user has checked the Restore parameter value after restart feature.
COLD RESTART DATA SIZE is the size of the local configuration (that is, the configuration stored in
nonvolatile controller memory). This parameter is only available through the controller maintenance port.
COLD RESTART SPACE REMAINING is the free nonvolatile memory space. This parameter is only
available through the controller maintenance port.
Controller Considerations
209
I/O Configuration
The DeltaV I/O subsystem supports multiple types of I/O cards, including analog and discrete input and output cards,
HART output and input cards, serial cards, the H1 Fieldbus card, AS-Interface card, Profibus DP card, RTD, ohms,
Thermocouple, mV, Multifunction, and the SOE (Sequence of Events) card. The I/O subsystem consists of a terminal
block that snaps onto the carrier to provide screw termination for field wiring and the actual I/O card that snaps over
the terminal block and onto the carrier. The I/O card converts field signals to the appropriate format for control and
communications.
Channel or
Port Types
Description
Analog Input
Card
Analog Input
Channel
HART Analog
Input Channel
RS232 port
RS422/485 half
duplex port
RS422/485 full
duplex port
Serial Card
210
System Configuration
I/O Card
Channel or
Port Types
Description
Analog Output
Card
Analog Output
Channel
HART Analog
Output Channel
Discrete Input
Channel
Discrete Input
Card
I/O Configuration
211
I/O Card
Channel or
Port Types
Description
Discrete
Output Card
Discrete Output
Channel
Momentary
Output Channel
Produces a momentary
pulse by driving the
output active for a
specified time period
each time the controller
writes a value of TRUE
(1, On). Upon receiving a
new pulse value, the
existing pulse is allowed
to terminate normally
before the new value is
written. Upon receiving a
configuration that
indicates a change from
one type of output to
another, the outputs
switch to the off state.
Continuous Pulse
Output Channel
Produces a continuous
pulse by driving the
output active for a
percentage of a specified
time period. Upon
receiving a new
continuous pulse value,
the existing pulse is
allowed to terminate
normally before the new
value is written. Upon
receiving a configuration
that indicates a change
from one type of output
to another, the outputs
switch to the off state.
212
System Configuration
I/O Card
Channel or
Port Types
Description
Isolated Input
Card
Thermocouple
Uncharacterized
thermocouple
RTD, ohms
Resistance
mV
Voltage
RTD Channel
Resistance
Channel
User
Discrete Input
Channel
SOE Discrete
Input Channel
RTD, ohms
Card
SOE Card
(Sequence of
Events)
I/O Configuration
213
I/O Card
Channel or
Port Types
Description
Thermocouple,
mV* Card
Thermocouple
Uncharacterized
Thermocouple
DI or Pulse Input
(PIN) Channel
DI or Pulse Input
(PIN) Channel for
pulse input gating
Multifunction
Card
214
System Configuration
I/O Card
Channel or
Port Types
Description
AS-Interface
Card
2 ports
H1 Fieldbus
2 ports
DeviceNet
one port
Supports polled
communication as the
DeviceNet master and
acts as the interface
between the DeviceNet
network and the DeltaV
system. Supports up to
61 slave devices and
supports the online
addition of devices.
Profibus DP
one port
* Note When the Thermocouple, mV card is plugged into a Thermocouple terminal block, it functions as a
Thermocouple card. When it plugs into an I/O terminal block, it functions as an mV card.
I/O Configuration
215
Card Parameters
The properties associated with I/O cards are described by card parameters. These values give you information about
the I/O card; they are not configurable. The following are the card parameters displayed in the DeltaV Diagnostics:
EXIST - Boolean value that shows if a card is physically present at the given path (TRUE = card is present, False =
card is not present).
HWREV - Text string containing the hardware revision level of the card at the given path. The card reports a zero if
it does not support hardware revision reporting.
MODEL - Text description of the card model at the given path.
OINTEG - Represents the overall integrity of the card (0 = Good, 1 = Bad).
SNUM - Text string containing the serial number of the card at the given path. The card reports a zero if it does not
support a serial number.
STATUS - Text description of the current condition of the card.
The conditions are analyzed in the following order and if any of them exist, the appropriate integrity is determined
and the appropriate status is displayed. If none of the below conditions exist, then the integrity is set to 0, and the
status is set to Good.
Condition
Status
OINTEG
Value
No Card
No Card
No Card
Good
SWREV - Text string containing the software revision level of the card at the given path.
Channel Parameters
The properties associated with the I/O channel types are described by channel parameters. You modify the channel
parameters through DeltaV Explorer. All channels have the following non-configurable parameters:
OINTEG - Represents the overall integrity of the channel (0 = Good, 1 = Bad).
STATUS - Text description of the current condition of the channel.
216
System Configuration
Channel Parameter
Can
Configure?
Description
Analog Input
Channel
FIELD_VAL_PCT
No
FILTER
Yes
NAMUR_ENA
Yes
OVERRANGE_PCT
Yes
UNDERRANGE_PCT
Yes
HART_FIELD_VAL
No
FIELD_VAL_PCT
No
HART Analog
Input Channel:
Analog Process
Values
I/O Configuration
217
Channel Type
Channel Parameter
Can
Configure?
Description
HART Dynamic
Variables
HART_PV
No
HART_SV
No
HART_TV
No
HART_FV
No
NO_COMM
No
HART Analog
Input Channel:
System Status
Values
218
System Configuration
Channel Type
Channel Parameter
Can
Configure?
Description
HART Analog
Input Channel:
DEV_MALFUNC
No
DEV_CFG_MISMATCH
No
MORE_STATUS
No
NPV_PAST_LIM
No
PV_FIXED
No
PV_PAST_LIM
No
PV_SAT
No
HART Field
Device Status
Values
I/O Configuration
219
Channel Type
Channel Parameter
Can
Configure?
Description
HART Analog
Input Channel:
Other Values
FILTER
Yes
HART_ERRORS
Yes
NAMUR_ENA
Yes
OVERRANGE_PCT
Yes
UNDERRANGE_PCT
Yes
HINTEG
No
220
System Configuration
Channel Type
Channel Parameter
Can
Configure?
Description
Analog Output
Channel
FAIL_ACTION_MODE
Yes
FAIL_ACTION_VAL
Yes
INIT_VAL
Yes
OUT
No
HART_PV
No
HART_SV
No
HART_TV
No
HART_FV
No
HART Analog
Output Channel:
Dynamic Variables
I/O Configuration
221
Channel Type
Channel Parameter
Can
Configure?
Description
HART Analog
Output Channel:
Device Variables*
HART_DV_SLOT0
No
HART_DV_SLOT1
No
HART_DV_SLOT2
No
HART_DV_SLOT3
No
DV_SLOT_CONFIG
Yes
DV_SLOT0_CODE
Yes
DV_SLOT1_CODE
Yes
DV_SLOT2_CODE
Yes
DV_SLOT3_CODE
Yes
NO_COMM
No
HART Analog
Output Channel:
System Status
Values
222
System Configuration
Channel Type
Channel Parameter
Can
Configure?
Description
HART Field
Device Status
Values
DEV_MALFUNC
No
NPV_PAST_LIM
No
PV_FIXED
No
PV_PAST_LIM
No
PV_SAT
No
I/O Configuration
223
Channel Type
Channel Parameter
Can
Configure?
Description
HART Analog
Output Channel:
Other Values
HART_ERRORS
Yes
FAIL_ACTION_MODE
Yes
FAIL_ACTION_VAL
Yes
INIT_VAL
Yes
OUT
No
HINTEG
No
224
System Configuration
Channel Type
Channel Parameter
Can
Configure?
Description
Discrete Input
Channel
FIELD_VAL_D
No
FILTER
Yes
LINEFAULT_DETECT
Yes
COUNTER_IN
No
LINEFAULT_DETECT
Yes
I/O Configuration
225
Channel Type
Channel Parameter
Can
Configure?
Description
Pulse Input
Channel
COUNTER_IN
No
FILTER
Yes
FREQUENCY
No
RESET_COUNT
Yes
FAIL_ACTION_MODE
Yes
FAIL_ACTION_VAL
Yes
INIT_VAL
Yes
LINEFAULT_DETECT
Yes
OUT_D
No
Discrete Output
Channel
226
System Configuration
Channel Type
Channel Parameter
Can
Configure?
Description
Continuous Pulse
Output Channel
FAIL_ACTION_MODE
Yes
FAIL_ACTION_VAL
Yes
INIT_ON_TIME
Yes
LINEFAULT_DETECT
Yes
ON_TIME
No
PULSE_PERIOD
Yes
I/O Configuration
227
Channel Type
Channel Parameter
Can
Configure?
Description
Momentary Output
Channel
FAIL_ACTION_MODE
Yes
FAIL_ACTION_VAL
Yes
LINEFAULT_DETECT
Yes
OUT_D
No
FIELD_VAL
No
FIELD_VAL_PCT
No
FILTER
Yes
OVERRANGE_PCT
Yes
UNDERRANGE_PCT
Yes
All RTD,
Thermocouple,
Voltage, and mV
Channel Types
228
System Configuration
Channel Type
Channel Parameter
Can
Configure?
Description
RTD Channel
Types Only
COMPENSATION
Yes
NUM_WIRES
Yes
CHATTER_CONTROL
Yes
FIELD_VAL_D
No
FULLSCALE
Yes
Maximum temperature.
ALPHA
Yes
DELTA
Yes
ZERO
Yes
User-defined RTD
Channel Type
* When using the DV_SLOT variables to read the instrument mode from a HART output device, the DeltaV
system treats these values as floating point values. Therefore, the DV_SLOT variable associated with the
instrument mode contains the following values for instrument mode:
Out of service = 0
In service = 1.4013E-045
When using an AI function block to reference these values, the scale of the block must be set appropriately to
prevent seeing a 0 value for both instrument modes.
The DeltaV system also treats the control mode read from the HART output device as a floating point value. Each
HART output device has its own definition for control mode. Following are the DV_SLOT values that correspond
to the possible control mode integer values:
0 (Test) = 0
1 = 1.4013E-045
2 (Digital) = 2.8026E-045
3 (Analog RSP) = 4.2039E-045
When using an AI function block to reference these values, the scale of the block must be set appropriately to
handle these values.
I/O Configuration
229
Serial
Fieldbus H1
Series 2, redundant capable cards are configured, auto-sensed, upgraded, and operated just like the Series 1 cards.
Series 2 simplex cards can function as drop-in replacements for Series 1 simplex cards of the same type. With the
exception of the Series 2 simplex H1 card, which requires the Series 2 H1 terminal block, no wiring change is
required to replace a Series 1 card. Series 2 cards report their operating mode (simplex or redundant) to the DeltaV
controller based on the type of terminal block on which they are installed. New redundant terminal blocks provide
wiring terminations for the redundant cards. If a card is installed on a redundant terminal block, it reports itself as
operating in redundant mode; otherwise, it reports itself as operating in simplex mode. If all cards are redundant, the
controller can support up to 32 redundant pairs.
Refer to Example Switchover Situations for some scenarios that are intended to help you to know when a switchover
has occurred and to diagnose and solve the problems that caused the switchover.
The lower slot number in a redundant pair must be an odd number, and the upper slot number must be the
next higher even number. For example, you can install redundant pairs in slots 1 and 2, 3 and 4, and 9 and
10. You cannot install redundant pairs in slots 6 and 7 or 24 and 25. In this example from DeltaV Explorer,
the redundant pair, C07, occupies slots 7 and 8. Notice that the next available slot, C06, was not used; this is
because the lower slot number in a redundant pair must be odd.
230
Other than redundant terminal blocks, no additional software or hardware is required to support redundancy.
A redundant terminal block spans two adjacent slots on the I/O carrier. A redundant I/O card consists of two
Series 2 cards installed in a redundant terminal block. Both cards access the same set of channels in the
terminal block.
System Configuration
The double-wide redundant terminal blocks require only a single set of wires for each redundant channel or
fieldbus segment. (The exception is the Redundant Interface terminal block that uses two sets of wires for
the Series 2 Serial card. One set of wires is for each interface, such as a computer.) The redundant terminal
blocks contain screw terminals appropriate for the card type, and signals from the screw terminals are
connected to both cards in a redundant pair.
The Series 2 DI, 8-Channel, 24 VDC, Dry Contact and the Series 2 DO, 8-Channel, 24 VDC, High-Side
cards support line fault detection. (For DI cards, modify the wiring to include a series and parallel resistor at
the sensor.) This capability can be enabled or disabled by configuration changes.
After resolving line fault errors, use the Clear Saved Fault Information command in DeltaV Diagnostics to
re-enable switchovers if the same problems are detected again. Refer to the information on clearing saved
fault information in the Identifying and Troubleshooting Series 2 Redundant Cards topic for more
information.
Manual Switchovers
Always use the DeltaV Diagnostics program to perform a manual switchover. Removing the active card in a
redundant pair can cause a disruption in the output signal. To perform a switchover in Diagnostics, select the
card, click the right mouse button, and select Redundancy Switchover.
Redundant Discrete
Redundant H1
Redundant Interface
Check the key settings on the corresponding Series 2 cards and set the keys on the terminal block to match. Refer
to I/O Interface Keying for information on key settings.
Locate the assigned slot location on the I/O interface carrier. Remember that the lower slot number must be odd,
and the upper slot number must be the next higher even number. Place the tabs on the back of the redundant
terminal block through the slots on the carrier and push the terminal block up to lock it into place.
Connect the field wiring for the redundant terminal blocks. as shown in the Series 2 card wiring diagrams and
redundant terminal block figures. Click the above links for terminal block port and channel assignment and click
the links in Redundant I/O Cards for wiring diagrams for the Series 2 cards in redundant mode.
I/O Configuration
231
Align the connectors on the Series 2 card with the connectors on the I/O carrier and the redundant I/O terminal
block and push to attach.
Switchover Causes
The DeltaV controller constantly scans both the active and standby cards and directs a switchover from the active to
the standby card when a failure occurs. Switchover is very smooth and occurs in a matter of milliseconds. The last
known good values of the output are held during switchover. A redundancy switchover can occur under the following
circumstances:
Open and short circuit faults in the channels during installation or operation
Card errors due to external noise near the system or noise on the carriers, cards, or channels
Improper grounding that might cause some channels to draw huge currents and high voltages
Fatal condition on the active card (for example, the active card cannot communicate with the controller)
Non-fatal condition on the active card. These conditions are dependent upon the card type (for example, a
failure of the A/D converter on an AI card)
Refer to Example Switchover Situations for some scenarios that are intended to help you identify when a switchover
has occurred and diagnose and solve the problems that caused the switchover.
232
System Configuration
Note The Auto-Sense Cards dialog presents information about installation errors in red text and informational
messages in blue text. However, auto-sense cannot always detect an incorrectly installed terminal block when at least
one of the cards is in the correct slot. (For example, auto-sense will not detect a problem if a terminal block is
incorrectly installed in slots 3 and 4 and a card exists in slot 3 but no cards are in slots 2 and 4.) For this reason, it is
recommended that you verify your installation with DeltaV Diagnostics.
Configuring Series 2 Cards Offline
Adding and configuring Series 2 I/O offline in the DeltaV Explorer is performed in much the same way as pre-Series
2 I/O. The Add Card dialog box includes a Card class selection field (such as the Discrete Input class of cards), a
Card type field (such as 24 VDC, Dry Contact), and a Card series field (Series 1 or Series 2 if Series 2 is supported by
the card class and type). Click the down arrows to expand the list boxes and make your selections for card class, type,
and series.
I/O Configuration
233
234
System Configuration
the same fault occurs, the new active card does not switch over. (If both cards detect the same problem, it is
probably a field error.)
a subsequent fault occurs, the cards do not switch over until the saved fault information command is issued.
Refer to the information on clearing saved fault information in the Identifying and Troubleshooting Series 2
Redundant Cards topic for more information.
Note If ENABLE_AUTO_SWBK is False and the controller detects a new card in the redundant pair, a switchover
will be allowed to the new card if the active card has a fault. For example, if you replace the standby card or if
communications is lost and then reestablished with the standby card, a switchover can occur even if
ENABLE_AUTO_SWBK is False.
The decision to enable or disable automatic switchback depends on the requirements of your process and the
importance of the card. Disabling ENABLE_AUTO_SWBK requires manual intervention for switchovers to occur
I/O Configuration
235
but prevents cards from frequently switching over. On the other hand, enabling ENABLE_AUTO_SWBK causes
cards to switch over but, under certain circumstances, can result in frequent switchovers.
The procedure for enabling and disabling ports or channels on redundant Series 2 cards is the same as that for preSeries 2 cards: select the channel or port, click the right mouse button, select Properties, and then select Enabled. To
enable multiple channels or ports, select the I/O subsystem, click the right mouse button, and then select Configure
I/O.
LEDs
The LEDs on the Series 2 cards show basic operating data. The correct operating conditions for the green Power/
Active LED is solid for the active card and flashing for the standby card. The red LED (continuous on or flashing)
indicates fault conditions. Refer to the LED checklists in the Checking the LED Indicators on Each Device topic for
complete information on each Series 2 card. Use DeltaV Diagnostics to diagnose problems. (Scroll through the topic
and find the appropriate table for your card.)
Diagnostics
The left pane in DeltaV Diagnostics presents a redundant pair of cards slotwise. In the following image, a redundant
AI, 8-channel, 4-20 mA HART card is installed in slots 7 and 8 (C07 and C08).
236
System Configuration
The active card is depicted with the black half of the image in the foreground (C07), and the standby card is depicted
with the grey half of the image in the foreground (C08).
Diagnostic Parameters
The right pane in DeltaV Diagnostics shows diagnostic parameters for the selected card in the redundant pair. The
following image shows the diagnostic parameters for a standby redundant Series 2 Serial card.
I/O Configuration
237
The online help for the Diagnostics program provides descriptions of all the parameters. To access the help, select the
parameter, click the right mouse button, and then select What's this. Following are descriptions of the SwitchAvail,
Pstatus, POInteg, and State parameters:
SwitchAvail (Switchover Available) - Indicates if the redundant pair is available for switchover. Possible
values include:
Available
Disabled
Available - common faults (resolve problem and clear saved fault information)
Unavailable - both cards faulty (resolve problem and clear saved fault information)
PStatus (Pair Status) - Shows the status of the redundant pair. Possible values are:
No Card
Good
Integrity Error
Not Operational
POInteg (Pair Integrity) - Overall integrity (good or bad) of the redundant pair
State (Redundant cards) - Indicates whether or not the selected card is active. A state of Standby means not
active; it does not mean that the card is necessarily available to take over as active.
To view parameter values for channels or ports, select the active card. The values are shown for the active card only;
Diagnostics displays "Not Available on Standby" if the standby card is selected. If the channels or ports are disabled,
Diagnostics shows "@@@@@" for the channel or port's Value parameter and "No installed configuration" for the
Status parameter.
Clearing Saved Fault Information on Redundant Cards
Use the Clear Saved Fault Information command in DeltaV Diagnostics after any problems reported by the redundant
card pair are identified and resolved. Redundant cards hold back previous error information to prevent switching back
and forth. Users must acknowledge the problem and then clear the saved fault information. The Clear Saved Fault
Information command re-enables switchovers if the same problems are detected again. One way to determine if you
need to use this command is to look at the card's SwitchAvail parameter. If the value for the SwitchAvail parameter
reads "Available common fault" or "Unavailable - both cards faulty," send the Clear Saved Fault Information
command.
238
System Configuration
For example, suppose a wire becomes loose on an Analog Input termination block. As soon as the active card detects
the open loop, the controller records the fault, and the redundant pair switches over. Then, the new active card detects
the open loop, and the controller records the fault again. In such a situation, detection of the same open loop will not
cause a switchover. Once you find and secure the loose wire, use the Clear Saved Fault Information command to
enable switchover if the condition is detected again.
Note If switchovers are not occurring as expected, be sure that the ENABLE_AUTO_SWBK parameter is enabled.
Refer to The Enable Auto Switchback Parameter topic for more information.
To access the Clear Saved Fault Information command:
1
Select the redundant I/O card that is reporting either of the above values in the SwitchAvail parameter.
Click the right mouse button and select Clear Saved Fault Information.
I/O Configuration
239
For each situation, read the information in the table and then click the link in the Possible Problem column for
suggestions of how to fix the problem.
Card type and LED
indications
Diagnostics shows an
integrity error on the card and the
following parameter values:
Possible Problem
240
System Configuration
Diagnostics shows an
integrity error on the card and the
following parameter values:
PStatus = No Card
Possible Problem
Status = No Card
I/O Configuration
241
Diagnostics shows an
integrity error on the card and the
following parameter values:
PStatus = Termination Block
Incorrectly Installed
Possible Problem
For each card, select the card, click the right mouse button, and then select Clear Saved Fault Information.
Remove the redundant cards and check for bent or broken pins.
Straighten any bent pins and re-insert the card into its slot on the carrier. Replace the card if a pin is broken or
bent beyond repair.
For each card, select the card, click the right mouse button, and then select Clear Saved Fault Information.
242
System Configuration
Reset the cards by removing each card from the carrier and then re-inserting it into its slot.
For each card, select the card, click the right mouse button, and then select Clear Saved Fault Information.
Determine if there is any electrical noise near the carrier and, if so, remove the noise source.
Flashing red LEDs and loss of communication between the card and the carriers indicate the existence of noise.
Noise can be caused by electrical activity (such as welding), the use of devices (such as 2-way radios), or natural
causes (such as lightning), occurring close to the DeltaV installation.
Reset the serial cards by removing each card from the carrier and then re-inserting it into its slot.
For each card, select the card, click the right mouse button, and then select Clear Saved Fault Information.
Select the card from the I/O subsystem in the left pane in Diagnostics.
In the right pane, read the Status and OInteg parameter values for all channels to determine if there is an open
connection. Look for values, such as Status = Bad Hardware Error and OInteg = Bad, Pair Status Possible
Field Problem.
In Diagnostics, select each card, click the right mouse button, and then select Clear Saved Fault Information.
Replace the card with the blinking red LED as it is probably damaged.
Use a multimeter or other measurement device to determine if any of the channels are drawing 24 VDC without
current limit protection and fix this problem.
Reset the cards by removing each card from the carrier and then re-inserting it into its slot.
For each card, select the card, click the right mouse button, and then select Clear Saved Fault Information.
I/O Configuration
243
Scroll through the parameters for the standby card and determine if there is a port problem.
Remove the redundant cards and check for bent or broken pins.
Straighten any bent pins and re-insert the card into its slot on the carrier. If a pin is broken or bent beyond repair,
replace the card.
For each card, select the card, click the right mouse button, and then select Clear Saved Fault Information.
244
System Configuration
I/O Configuration
245
information on the configuration options. Similarly, configuring a Remote I/O card is similar to configuring standard
DeltaV I/O cards. However, Remote I/O cards have a configurable scan rate. The scan rate controls how often the
card data is moved between the controller and the Remote I/O Node. Valid scan rates are 100 ms, 200 ms, 500 ms,
and 1 second. The default value is 500 ms. Increasing the scan rate increases the loading on the network, controller,
and Remote I/O Node.
Note Do not confuse a remote I/O card's scan rate, the rate at which the card data is moved between the controller
and the Remote I/O node, with a module's scan rate (also called module execution time). A module's scan rate is the
rate at which the module executes. For modules configured to read signals from remote I/O channels, the module's
scan rate should be twice as slow as the Remote I/O scan rate. For example if the Remote I/O scan rate is 100 ms, the
module's scan rate should be 200 ms; if the Remote I/O scan rate is 200 ms, the module's scan rate should be 500 ms.
(Remember that valid scan rates are 100 ms, 200 ms, 500 ms, and 1 second.) A module scan rate of 100 ms is not
supported by remote I/O cards and will negatively affect the card's performance.
Supported Cards
Zone 1
A Remote I/O Node installed in Zone 1 supports the following types of I/O cards:
For card specifications refer to the HART Analog Input Channel Specifications, HART Analog Output Channel
Specifications, Discrete Input Channel Specifications, and Discrete Output Channel Specifications topics in the
Installing Your DeltaV Zone 1 Hardware manual.
Zone 2
A Remote I/O Node installed in Zone 2 supports the following types of I/O cards. For card specifications refer to the
I/O Cards topic in the Installing Your DeltaV Digital Automation System manual.
Note Only HART Passthrough for use with AMS Device Manager and Valvelink is available for Remote I/O. No
other HART functionality is supported.
Analog Input Cards
246
System Configuration
Millivolt, 8-channel
RTD, 8-channel
Thermocouple, 8-channel
I/O Configuration
247
248
System Configuration
DST Counting for Classic I/O, Profibus DP, AS-Interface I/O, DeviceNet I/O, and
DeltaV SIS I/O
For licensing, DSTs are counted in the following ways:
Each output from a function block to the I/O subsystem counts as one DO DST if it is a discrete signal, or
one AO DST if is an analog signal.
An input referenced by one or more function blocks in a module counts as one DI DST if it is a discrete
signal, or one AI DST if it is an analog signal.
An input signal referenced by function blocks in multiple modules, counts as a DI DST or an AI DST in
each module.
Any input that is referenced in a graphic or a history collection and is not referenced in a function block is
not counted as a DST instead, it is counted as a SCADA value.
The total number of DSTs in a controller is equal to the total number of DSTs in all of its modules. In the figure, the
controller has two modules and five DSTs: three input DSTs (either discrete or analog depending on signal type) in
Module 1 and one input and one output DST (either discrete or analog depending on signal type) in module 2 adding
to a total of five DSTs.
I/O Configuration
249
Input A is referenced by one function block and is therefore counted as one input DST (either analog or
discrete depending on signal type).
Input B is referenced by two function blocks, but the function blocks are in the same module so it is counted
as one input DST, either analog or discrete depending on signal type.
Input C is referenced by function blocks in two modules so it is counted as two input DSTs.
Output D is counted as one output DST, either analog or discrete depending on signal type.
DSTs
FFAI
FFAI_RMT
250
System Configuration
Function Block
DSTs
FFAO
FFAO_RMT
FFDI
FFDO
Each occurrence of the following blocks adds to the DST count as shown:
Function Block
DSTs
FFMAI
FFMAI_RMT
FFMDI
FFMDO
For example, two FFAI blocks, contained in the same module and referencing the same transmitter signal, count as
two AI DSTs. Similarly, two FFMDI blocks, contained in the same module and referencing the same device, count as
16 DI DSTs.
I/O Configuration
251
252
the total system DST count exceeds the ProfessionalPLUS license size, or
the number of any of the DSTs categorized as AO, AI, DO, or DI exceeds the system-wide Control license
size for that type of DST and enough unused DSTs of a higher type are not available to make up the
difference.
System Configuration
If the system contains class-based units, one more check is made before download is permitted. This check counts
DSTs configured and associated with class-based units and compares this quantity with the DST size of the systemwide Advanced Unit Management license. A download will not occur if the DST count exceeds the size of the
Advanced Unit Management license.
License Enforcement Example
A configuration has 20 AO DSTs and 27 AI DSTs. The system is licensed for 25 AO DSTs and 25 AI DSTs. Though
the configuration exceeds the licensed AI DST limit, the download is permitted because there are enough licensed,
but unused, AO DSTs to make up the difference.
SCADA Tags
Many values brought into a DeltaV system by way of OPC and Serial are used for monitoring purposes. Because of
this, the DeltaV system allows you to host these values as SCADA (Supervisory Control and Data Acquisition) tags
instead of DSTs. SCADA tags are values that come into the DeltaV system by way of OPC and Serial and are not
used in a control strategy. They are inexpensive, lightweight values that can be passed around the system quickly and
efficiently. SCADA tags can be easily displayed to the operator, saved in the historian, or displayed in a trend.
To get SCADA tags from OPC into the DeltaV system you must create modules that contain input parameters and
assign these modules to the Application Station. You can then use OPC mirror to map the incoming OPC values from
a third party interface to the input parameters in the modules running in the Application Station. These modules are
considered SCADA tags and are not counted as DSTs.
You can also have modules running in the Application Station with input parameters referencing parameters in a
module running in a controller. These input parameters are also considered SCADA tags and are not counted as
DSTs.
I/O Configuration
253
Physical Layer - receives messages from the Communication Layer (Stack) and converts them into signals
on the fieldbus segment; receives signals on the fieldbus segment and converts them into messages
Communication Layer - (Communication Stack made up of the Data Link Layer, Fieldbus Access Sublayer,
and Fieldbus Message Specification). The Data Link Layer controls transmission of messages on the
fieldbus segment.
User Application Layer - DeltaV applications, such as Control Studio and Explorer
Note The User Application Layer is not defined by the OSI model. The Fieldbus Foundation specified a User
Application Model that Fisher-Rosemount used to develop DeltaV software applications.
Physical Layer
Refer to the Fieldbus Installations in a DeltaV Digital Automation System manual for information on installing the
H1 card, wiring the fieldbus segment, and cabling and power requirements.
Communication Layer
The transmission of messages across the fieldbus is managed through a deterministic centralized bus scheduler called
the Link Active Scheduler (LAS). The H1 card functions as the LAS. Some of the Link Active Scheduler's
responsibilities are:
254
System Configuration
Note The H1 card is the only primary Link Master allowed on the fieldbus segment. No other Link Master is allowed
on the segment or unpredictable results can occur. DeltaV software supports one backup Link Master device on each
fieldbus segment.
Scheduled Transfers
Scheduled transfers are typically used for the regular, cyclical, exchange of control loop data between devices on the
fieldbus segment. The LAS maintains a schedule called the Compel Data schedule, which is a list of transmit times
for all the data buffers that need to be cyclically transmitted. The data buffers are in the fieldbus devices. When it is
time for a fieldbus device to send a data buffer, the LAS issues a message called a Compel Data message to the
device. When the fieldbus device receives the Compel Data message, it broadcasts or publishes the data in the buffer
to all devices on the fieldbus and any device that is configured to receive the data receives it. The devices that are
configured to receive the data are called subscribers. Although scheduled transfers are the highest priority activity
performed by the LAS, it requires the smallest portion of a macrocycle. (A macrocycle is a single iteration of a
schedule.)
A link, or Virtual Communication Relationship (VCR), is defined as a connection between a fieldbus parameter in
one device on the segment and a fieldbus parameter in another device on the segment. Some devices support
publisher and subscriber VCRs and other devices support Free VCRs.
Publisher and Subscriber VCRs
A subscriber VCR is an output from a fieldbus device to an input in another device on the segment. The input device
can be another fieldbus device or a DeltaV controller. A publisher VCR is an output from a DeltaV controller to the
input of a parameter in a fieldbus device. Here are a few examples of publisher and subscriber VCRs:
The link between a function block running in a controller to a function block running in a device is a
publisher VCR.
The link between a function block running in a device to a function block running in a controller is a
subscriber VCR.
The link between a function block running in a device to a function block running in another device is a
subscriber VCR
The H1 card supports as many as 35 H1 publisher VCRs and 50 fieldbus device subscriber VCRs per port as long as
the total number of VCRs does not exceed 50. For example, the card can support 35 H1 publisher VCRs and 15
fieldbus device subscriber VCRs per port or five H1 publisher VCRs and 45 fieldbus device subscriber VCRs. Refer
to the VCR Specifications topic for the maximum number of subscriber and publisher links supported by fieldbus
devices that use these types of links.
Note: Many backup Link Master devices cannot support these limits. This means that the configuration can exceed
the capacity of the backup Link Master device. If communication is lost between the H1 card and the segment, the
backup Link Master device may be unable to handle the segment scheduling and the schedule download may fail. If
the backup Link Master device indicates Schedule Download Failure in DeltaV Diagnostics, the device cannot
function as a backup Link Master. If an H1 card configuration has more than 25 publisher/subscriber VCRs per port,
test the configuration before going online to ensure that the backup Link Master device can support the configuration.
To avoid a Schedule Download Failure due to lack of capacity in the backup Link Master consider the following
options:
Upgrade to a backup Link Master that supports the segment's publisher and subscriber VCRs.
Do not configure any device as a backup Link Master.
Reduce the number of publisher and subscriber VCRs on the segment.
I/O Configuration
255
Free VCRs
A Free VCR can function as a publisher link, a subscriber link, or a device alarm. Device alarms require one VCR.
For example, if a device can support a maximum of five VCRs, and one VCR is used for a device alarm, the
remaining four VCRs can be used for any combination of publisher and subscriber links. Each port on the H1 card
can support a maximum of 50 input links and 35 output links as long as the total number does not exceed 50 VCRs.
Refer to the VCR Specifications topic for the maximum number of Free VCRs supported by devices that use these
types of links.
Unscheduled Transfers
Unscheduled transfers are typically used for user initiated changes such as setpoint changes, tuning changes, and
downloads and uploads. Unscheduled transfers require the greatest portion of a macrocycle. The LAS gives all
devices on the fieldbus a chance to send unscheduled messages between transmissions of scheduled messages. The
LAS grants a device permission to use the fieldbus for unscheduled messages by issuing a Pass Token (PT) message
to the device. When the device receives the PT, the LAS allows it to send unscheduled messages until it has finished
or until the maximum token hold time has expired; whichever is the shorter time. The device can send unscheduled
messages to a single destination or it can multicast the message to multiple destinations. The LAS maintains a list of
the devices that are properly responding to the PT message. This list is called the Live List.
Live List Maintenance
New devices can be added to the fieldbus at any time. Between the times it sends out Compel Data messages, the
LAS sends out Probe Node (PN) messages to the addresses not in the Live List. If a new device is present at that
address, it receives the PN and answers with a Probe Response (PR) message. When the LAS receives the PR
message from the device, it adds the device to the Live List. Whenever a device is added or removed from the Live
List, the LAS broadcasts the change to all devices. This allows each device to maintain a current copy of the Live
List.
256
System Configuration
Basic device - sends and receives messages on the fieldbus but does not control when devices have access to
the fieldbus.
Link Master - controls when devices access the fieldbus and executes the link schedule which synchronizes
communications with function block execution on the fieldbus. Link Master devices are capable of taking
over as LAS if the Primary Link Master device fails. The backup Link Master must use address 20.
Bridge - links multiple fieldbus segments. This device class is not currently supported. The DeltaV system
supports one backup Link Master on each segment.
Note Link Master devices should always be Commissioned. Unpredictable behavior could occur if a Link Master
capable device is in Standby or Offline and the Primary Link Master device fails. Any temporary device should only
be connected to the fieldbus as a Basic device.
For more information, refer to the Commissioning and Decommissioning Fieldbus Devices topic.
I/O Configuration
257
interoperability among fieldbus devices. Interoperability, a key benefit of fieldbus technology, is the ability of a host
system to operate multiple devices, independent of manufacturer, on the same fieldbus segment without loss of
minimum functionality.
The DeltaV system supports a number of fieldbus devices from different manufacturers. The device description files
necessary to support these devices are included in the DeltaV install image. If a fieldbus device is not included in the
DeltaV install image, you must install the device description for that device. The device description is specific to the
device type and revision. Download the device description files from www.easydeltav.com The device description
files must include a file with an .fhx extension to work with the DeltaV system. You can download the device
description files to a disk, CD, or directory on your system and then use the DeltaV Explorer to add the device
descriptions to the DeltaV Explorer library. Install the device description files on the ProfessionalPLUS workstation
and the DeltaV system will automatically synchronize the device descriptions on the other workstations. To install a
device description:
1
Insert the device description disk or CD into the drive. (The device description can also be on a local shared hard
drive.)
Click the right mouse button and select Add Device Definition.
Browse for the location of the drive or directory where the device definition files are stored and click OK. You
are not required to select each file individually. The device definition files are automatically selected when you
select the drive. (If the directory contains more than one file of a needed file type, an error is displayed. The
duplicate file types must be removed before attempting to add the device.)
Read the Warning message. If you want to proceed with the installation, click Yes.
Methods
Device Descriptions can also include a set of processing routines called Methods. Methods provide a way to access
and manipulate parameters within a device. For example a DD for a Valve Controller might include methods for
automatically calibrating valve travel, manually calibrating travel, restarting a device, and calibrating the internal
pressure sensor information for display. In the DeltaV system, the methods reside in the Transducer and Resource
blocks. Some methods, such as calibration methods are available through the context menus for the Transducer block.
Other methods such as the restart method, are available through the context menu for the Resource block.
To access a calibration method for a Digital Valve Controller, perform the following steps:
1
Click Start | DeltaV | Engineering | DeltaV Explorer to open the DeltaV Explorer.
Select the device's Transducer block from the Contents of pane, right-click, select Calibration, and then select the
desired calibration method.
258
System Configuration
To access the restart method for a Digital Valve Controller, perform the following steps:
1
Select the device's Resource block from the Contents of pane, right-click, and then select Restart DVC.
I/O Configuration
259
260
System Configuration
In the second form, the command line provides all the device information so the AMSMenu application does not
connect to the DeltaV database and is therefore faster.
For example, if your configuration includes a device named FY-101 that has the following characteristics:
Revision Level: 7
The following script opens a menu when the object the script is attached to is clicked:
Private Sub Rect1_Click()
frsruntask "AMSMenu", "-n FY-101 -m 5100 -t 5900 -r 7 " _
& "-i 0051000100FisherDVC0112461319931 -bt TRANSDUCER -bi 450"
End Sub
The menu that it opens is:
These are the same methods that appear if you right click the device's Transducer block in DeltaV Explorer.
See Working with Other Applications in the DeltaV Operate manual for more information.
I/O Configuration
261
State Transitions
262
System Configuration
A commissioned device is decommissioned to Spare. The device is usually removed from the segment after
doing this. A Spare device loses its address and device tag. Note that a commissioned device automatically
changes to a Spare if its placeholder is deleted.
A decommissioned device that has not been removed from the segment is placed in Standby. This might occur if
a Mismatch device had been made Spare and you want to put it in Standby without taking it off the segment.
A Standby device is dragged to an available placeholder that matches the manufacturer, device type and device
revision and is commissioned. Another way to commission a Standby device is to select Commission from the
device's context menu.
A commissioned device is taken Off-line - the device retains its tag and address. This is normally done when the
device is to be temporarily removed from the segment and reattached in the same service. The device must be
removed from the segment after it is taken Off-line.
A device can transition from Off-line to Standby when it is attached to a segment other than the one from which
it was removed.
A commissioned device is removed from a segment and attached to a segment other than the one from which it
was removed. The device might have been inadvertently attached to the wrong segment.
An Off-line device is made Spare. This is done if a device is placed on a segment with another device with the
same tag as this device. Making the device spare allows you to clear the device tag without removing the device
from the segment.
A Standby device can transition to Spare if it was previously in the Spare state before it was in the Standby state.
10 A Standby device can transition to Off-line if it was previously in Offline state before it was in the Standby state.
11 A device can transition from Mismatch to Off-line.
12 A Mismatch device is dragged to an available placeholder that matches the manufacturer, device type and device
revision and is commissioned. Another way to commission a Mismatch device is to select Commission from the
device's context menu.
Fieldbus devices can also go through the following transitional states:
Comm Initializing - The H1 card is establishing communications with the field device.
Unrecognized - The field device has not been commissioned at this address.
Unknown - The field device is transitioning between states.
Typically, a device will be in one of the above states for only a few seconds. If it remains in one of these states it
indicates a problem. Additionally, if a device goes into the Comm Fail state it indicates that the device is
communicating on the bus (it is in the live list) but communications between the H1 card and the device is currently
disrupted.
If a device remains in the Comm Initializing or Comm Fail state, cycle the device power. If a device remains in the
Unrecognized state, it either has not been commissioned or has been attached to the wrong segment. If a device is in
the Schedule Download Failure state, then the segment currently does not have a functional backup LAS. If a device
shows a Device Class Mismatch, there is something wrong with the device.
I/O Configuration
263
H1 Fieldbus Card
Communication information between the card and fieldbus devices is available from a visual inspection of the H1
card. The bottom two LEDs on the H1 card reflect communication between the port and fieldbus devices on that port.
A blinking yellow LED indicates that the port is communicating with fieldbus devices but either a communication
problem exists with an attached fieldbus device or no function blocks are configured on the segment. If the LED is
off, either the port is disabled or the H1 card is not communicating with any fieldbus devices on the port. Use the
DeltaV Explorer to enable and download the port and Control Studio to create and download configuration. A solid
yellow LED indicates good communication between the port and devices on that port and at least one function block
is configured on the segment.
DeltaV Explorer
Indicators in the DeltaV Explorer tell you if an H1 port or a fieldbus device needs to be downloaded or
commissioned.
The
on an H1 port or device means that the port or device needs to be downloaded. Select the port or
device, click the right mouse button, and then select Download to open a dialog box that lists the fieldbus
configuration information to be downloaded.
The
on a device means that the device needs to be commissioned. To commission the device, select it
from the Decommissioned device list and drag it to either the port or device placeholder.
Control Studio
Use Control Studio in online mode to diagnose problems with modules running in fieldbus devices. You must assign
and download a module before viewing it in online mode.
1
Click View | On-line to create an online (or debug) session in which you can examine module and block
parameters. A red X on a function block parameter indicates a problem with the function block.
Caution Any online changes affect your process because the changes are made to downloaded modules in the
controller. Use extreme care when changing values or stopping the execution of an algorithm.
3
Select the block with the red X. The Parameter View window in Control Studio displays a full list of parameters
for that block.
Double-click a parameter in Parameter View to open the Parameter Properties dialog for that parameter.
Diagnostics
Use DeltaV Diagnostics to perform the following tasks:
check integrity on the H1 card, backup Link Master device, and ports
check overall port statistics and communication statistics for each device
Open DeltaV Diagnostics and click View | Details or View | Compare to quickly see the device state. If the device is
not commissioned, open the DeltaV Explorer and commission the device. Then, download the port and the device. If
the device is commissioned, check integrity on the port and then check port and device communication statistics.
Port Integrity
Typically, integrity problems originate below the node and then rise to the node level. Integrity problems are
indicated by the
264
System Configuration
hierarchy until you find the root cause of the problem. If a fieldbus card has an integrity problem, expand the card to
see which port has the problem. Select each port and look at the port's status. Possible port status values are:
Duplicate Address on Link - Another device is currently communicating at this port's address.
No Communications on Link
One or more function block problems on link or device problem - Expand the port and check the state of
each fieldbus device on the port. Any state other than Commissioned indicates a potential problem with that
fieldbus device.
Retries
Invalid responses
Stack errors
Timeouts
Note If any of the port statistics and communication statistics are continually increasing, a potential communications
problem could exist on this port. To isolate the problem, investigate the communication statistics on each fieldbus
device. Refer to the following section for information.
Next, look at detailed port statistics. Click the right mouse button on the port and then click Display Port Detail
Statistics. In the Detailed Port Statistics dialog, look for the following:
Identifies
Initiates
Aborts
Tip Clicking the Reset Stats button resets all values to 0 and makes it easier to read the statistics.
Device Communication Statistics
Finally, look at communication statistics for each device. Click the right mouse button on each device, click Display
Communication Statistics, and look for the following:
Pcr Timeouts
I/O Configuration
265
misconfigured parameters) to proactive reporting of upcoming maintenance needed. To view Foundation Fieldbus
device conditions in DeltaV Explorer, right-click the device and select Status/Conditions.
Optionally, device alarms can be enabled on a Fieldbus device. When a device detects a condition, it will generate an
alarm, in addition to setting the appropriate condition on the status or conditions screen. The alarm is reported in the
Event Chronicle, is displayed in alarm summaries, and may be displayed in the DeltaV Operate alarm banner,
depending on user configuration (Series 2 H1 card required). A standard device faceplate shows the active alarms for
a fieldbus device. The detail button on the faceplate accesses the same screen as the Status/Conditions selection in the
DeltaV Explorer.
Device condition functionality is dependent on the device. Foundation Fieldbus devices support either standard
Foundation Fieldbus alerts or PlantWeb alerts.
Standard Foundation Fieldbus alerts - Devices report alerts in a single alarm: abnormal. This alarm is based on the
standard Block Alarm definition.
PlantWeb alerts - Devices report alerts in one of three alarms: failed, maintenance and advisory. The device alerts
have been organized into one of these alarms based on the importance of the alert condition to the health of the
device.
With the DeltaV system, all Foundation Fieldbus devices also have a communications failure alarm. This alarm is
generated when the DeltaV software recognizes that a device is no longer communicating on the H1 segment.
Fieldbus devices that support PlantWeb alerts also allow you to suppress conditions from the Status/Conditions
screen. Suppression from the Status/Conditions screen prevents the device from reporting the condition to the DeltaV
system. It is also possible to prevent reported alarm conditions from appearing in the alarm banner and alarm list.
This type of alarm suppression is described in the Suppressing Device Alarms topic.
266
System Configuration
For an alarm category (failed, maintenance, advisory), use the alarm's faceplate in DeltaV Operate.
For conditions of an alarm category, use the Status/Conditions dialog from the device's context menu.
Because alarms contain multiple conditions, suppressions at the alarm category level will always override
suppressions at the condition level.
Example:
A fieldbus device reports that it is due to be calibrated. The Calibration Due condition appears as a Maintenance
alarm in the Status/Conditions dialog, the DeltaV alarm banner, and Event Chronicle. Because regular service is
scheduled for the following week, the user might choose to suppress all Maintenance alarms from that device using
the Details faceplate. Alternatively, the user could choose to suppress only the Calibration Due condition from
appearing in the alarm banner and the Event Chronicle by checking the box above the condition in the Status/
Conditions dialog for that device. In both cases, the Status/Conditions dialog continues to display the condition as
active.
I/O Configuration
267
Function Blocks
Function blocks provide the control system behavior. The input and output parameters of the function blocks can be
linked over the fieldbus segment. For example, a simple temperature transmitter contains an AI function block; a
control valve might contain a PID function block as well as the AO block. As with other function blocks, you
configure these function blocks in Control Studio and then assign them to run in the fieldbus devices. During a
download, the function block tag that is configured in the DeltaV Explorer is downloaded to the device and the
function block tag in the device is overwritten. Refer to the section "Configuring Fieldbus Function Block Tags" in
Using Fieldbus in the Control Strategy for more information on fieldbus function block tag names.
Transducer Block
The transducer block performs front end processing of data signals received from the I/O and offloads this work from
the function block. For example, a transducer block might read a signal from a sensor and convert the signal to
Engineering Units, thus relieving the function block of the conversion task. The transducer block contains
information, such as calibration date and sensor type. There is usually one transducer block for each AI and AO
function block.
You can access the transducer block in the DeltaV Explorer to do the following:
268
System Configuration
Navigate to the fieldbus ports. The ports are under the fieldbus H1 card. The card is under the I/O subsystem.
Right-click the port to which you want to attach the device placeholder and select New Fieldbus Device. The
Fieldbus Device Properties dialog opens.
Enter the appropriate information about the device in the dialog box. The DeltaV system selects an address. You
can customize this field, but it is not necessary. Select the device type and revision based on the type of device
you want to add. The device properties must match the properties of the device you will commission later.
I/O Configuration
269
Remember that DeltaV Explorer has extensive online help. Click the Help button on this dialog box for help on
any of the fields.
Fieldbus devices often provide error detection for a variety of device conditions. Refer to Device Alarms
Overview and Configuring Device Alarms for more information. Select the Alarms and Displays tab in the
Fieldbus Device Properties dialog to enable Device Alarms to be reported by the device.
Note The alarms and displays tab is only shown when supported by the DeltaV hardware. Device alerts are supported
by Series 2 H1 cards.
Each device can also be configured with a primary control display and faceplate. DeltaV software includes a
standard device faceplate.
5
Click OK to add the device placeholder to the segment. The device appears as a decommissioned device on the
segment.
When device alarms are enabled, alarms become visible in the right pane in DeltaV Explorer when you select the
Fieldbus Device Alarms icon for the device. Select an alarm and right-click properties to enable or disable it or to
change the alarm's priority.
Commissioning a Device
Commissioning a device assigns it an address on the segment and makes the device available to the DeltaV system.
You use the DeltaV Explorer to commission devices. You can reconcile any differences between the device and the
placeholder during the commissioning process. After commissioning a device, you download.
270
System Configuration
Click Start | DeltaV | Engineering | DeltaV Explorer to open the DeltaV Explorer.
The device should appear under Decommissioned Fieldbus Devices. It may take a minute for the device to
appear. Tip: Press the F5 key to update the list.
The device must be in the Standby state before you can commission it. To determine if a device is in Standby,
select Decommissioned Devices, click View | Details from the menu bar, and be sure that the words "Standby
Fieldbus Device" appear under Type in the right pane.
If the device is not in Standby, select the device in the right pane, click the right mouse button, and select
Standby. It may take a minute or so for the device to transition to Standby.
5
Now be sure that the decommissioned device's properties, Device Type, Manufacturer, and Device Revision,
match the placeholder properties. To check the properties, select the item, click the right mouse button, and select
Properties. If necessary, edit the placeholder properties to match the device properties. (For information about
how to create a placeholder, refer to the Create a Device Placeholder topic.)
Select the device from the Decommissioned Fieldbus Devices list and drag it to the placeholder.
I/O Configuration
271
Read the information on the Device Commissioning Wizard - Start dialog and click Next to open the Device
Commissioning Wizard Reconcile Device dialog.
We will use this dialog to reconcile any differences between the placeholder and the device.
8
272
Click the Reconcile Device button. (If you do not click this button and click Next instead, the parameters in the
device will remain as they are and will overwrite the parameters in the placeholder when you commission the
device.) The Reconcile Device dialog shows two sets of fieldbus device configuration parameters: parameters in
the placeholder and parameters in the device. This dialog allows you to transfer parameters from a placeholder to
a device and edit parameters in the device. The following figure shows the dialog for reconciling resource block
parameters.
System Configuration
Click the Help button and read about reconciling device parameters. Click the Transducer block in the
upper left corner of the Reconcile dialog to reconcile the transducer block parameters. Read the device
documentation before reconciling transducer block parameters.
Click OK when you are finished reconciling parameters and then click Finish to commission the device.
It may take a little while to commission the device. Several factors contribute to the time it takes to
commission. Among these are the number of function blocks and devices and the time it takes for devices to
move through the various device states.
I/O Configuration
273
The wizard:
Uploads function block parameter changes from the existing device if it is still on the network
Follow the instructions on the wizard to proceed through the replacement process.
Here are a few guidelines for using the wizard:
274
You must have the key to the lock associated with the VC_DEVICE_CHECKOUT_CHECKIN and
REPLACE_DEVICE functions. By default, these functions are associated with the Can Calibrate lock.
The replacement device must be of the same type and manufacturer as the existing device. The device
revisions can differ as long as the same function blocks are supported between revisions.
The replacement device, which may or may not be physically connected to the fieldbus segment, must be in
Standby or Mismatch.
The existing device, which may or may not be physically connected to the segment, must be commissioned.
If the existing device is connected, it must be disconnected before the new device is selected to replace it.
System Configuration
Two configurations of a single fieldbus device (current to historical or historical to another historical)
Two commissioned fieldbus devices (current to current, current to historical, historical to current, historical
to historical)
A placeholder and a standby fieldbus device during commissioning of the standby device
Two placeholders
Reconciling is the process of comparing configurations before commissioning. When you drop a device onto the
fieldbus port, you are commissioning it. If the configuration differs from the current values, you have the opportunity
to reconcile the values in either configuration to the other. A wizard steps you through the process.
Configuration and configuration comparisons are available from the device context menu.
Uploading Fieldbus Devices
You can upload parameter values from function blocks running in a commissioned fieldbus device to the database.
This is useful if you want to ensure that factory-set parameter values are maintained in the database or that values
modified by a technician in the field are uploaded to the database. Parameter changes to the following function blocks
can be uploaded to the database: AI, AO, DI, DO, Fieldbus Multiplexed AI, Fieldbus Multiple DI, Fieldbus Multiple
DO.
Unlike controllers where the system detects a need to upload changes, the system does not detect a need to upload
changes to fieldbus device parameters. To upload a fieldbus device, select the device in the DeltaV Explorer, and
select Upload Function Blocks. There is no need to download the device after an upload.
Installing Generic Fieldbus Devices
The DeltaV system requires a set of device definition files for each fieldbus device type and device revision. Many
fieldbus device definition files are pre-installed with the DeltaV system. However, when you install a generic fieldbus
device, you must first install the device's definition files from the ProfessionalPLUS workstation. After you install the
device definition files from the ProfessionalPLUS workstation, you synchronize the device definitions on the other
DeltaV workstations in order to make the other workstation's device definitions current with those on the
ProfessionalPLUS workstation.
Use the DeltaV Explorer on the ProfessionalPLUS workstation to load the device definition files. Refer to the DeltaV
Explorer online help for information on installing fieldbus device definition files.
Note Fieldbus devices that are supported on the DeltaV system have been tested for interoperability with the DeltaV
system. Non-supported devices have not been tested for interoperability with the DeltaV system and may not operate
properly.
I/O Configuration
275
Valid Values
Description
Baud rate
Data bits
7 or 8
Determines the number of data bits. Use 7 for ASCII and 8 for RTU
mode.
Description
As many as 256
characters
Describes the use of the port. This description only appears when
you view the port properties from the DeltaV Explorer.
Enabled
Enables the port. If the port is not enabled, the Serial Card does not
scan for input data or transmit output when in master mode and does
not respond to Modbus messages when in slave mode.
276
System Configuration
Property
Valid Values
Description
Message
timeout (ms)
Determines the amount of time the Serial Card waits for a response
from the serial device after sending a request message. More
specifically, this indicates the time from when the Serial Card sends
the last character of the request message until the time the last
character of the response message is received. This property is only
applicable when in Modbus master mode.
Mode
Master or Slave
Parity
Port type
RS-232, RS-422/485
Full Duplex, RS-422/
485 Half Duplex
Retry count
0 through 255
Send outputs
on startup
Checked or unchecked
Determines whether the Serial Card sends all current output values
to the serial devices on power-up, reset, switchover or after a
download. This property is only applicable when in Modbus master
mode.
Stop bits
1 or 2
Transmit
Delay (ms)
Set the device address to match the address of the physical device connected to the serial card.
Repeat steps 1 through 3 for the second device. Set the address of the second device to match the address of the
physical device connected to the serial card.
I/O Configuration
277
Configuring a Dataset
In master mode, the Serial Card exchanges data with the serial device through a dataset. A dataset is a collection of
parameters associated with a serial device. The parameters in the dataset hold data values that correspond to registers
or data in a serial device.
The dataset defines the type and amount of data being sent to or received from the serial device. All the data values
for a dataset have the same properties. Properties include the data type, data direction, and so on. The data values in a
dataset map to a contiguous series of serial device registers or data.
In slave mode, the Serial Card emulates sets of data through datasets. The datasets are used to define the data that the
Serial Card and DeltaV system are to emulate. The dataset in the slave mode defines the type and amount of data the
Serial Card supports. All the data values for a dataset have the same properties.
You can create as many as 16 datasets for each Serial Card port. These 16 datasets can be allocated to the serial
devices in several ways. For example, you can configure one serial device with 16 datasets, or you can have 16
devices on the port with one dataset each.
The DeltaV Explorer help describes how to add a dataset for a Serial Card. Basically, you define the dataset through
the Serial Dataset properties dialog. The following table defines the fields in the dialog.
Serial Dataset Properties
Property
Card Type
Valid Values
Description
Data direction
Standard,
Programmable
Input or output
Dataset Tag
Standard,
Programmable
DeltaV data
type
Standard,
Programmable
DeltaV start
address
Programmable
0 to 65535
Description
Standard,
Programmable
278
System Configuration
Property
Card Type
Valid Values
Description
Number of
values
Standard,
Programmable
Programmable cards: 0 to
100.
Output mode
Standard,
Programmable
Output read
back
Standard,
Programmable
Checked or unchecked
Standard
PLC register
offset
Standard
I/O Configuration
279
Property
Card Type
Valid Values
Description
PLC start
register
address
Standard
Read only
Special Data
Programmable
0 to 65535
For example, the user needs a dataset with the following parameter values:
Number of values: 2
On DeltaV tab select Floating point with status in the DeltaV data type field.
Maximum
Number of
Values
100
50
280
System Configuration
Maximum
Number of
Values
100
Diagnostics
17
Meaning
Description
Diagnostics
15
16
17
Report Slave ID
I/O Configuration
281
Serial device data can be read or written from the Operator Display by referencing the DST/register number
parameter associated with the containing data set in an Operator Display Data Link.
Reading or Writing an Operator Display's Serial Data Using a Serial Dataset DST
1
Drag the Data Link to the desired location on the display and click the left mouse button.
Enter the dataset's DST name followed by the register number in the tagname field (for example:
CTLR101010101/R40101). You can also use the Parameter Browse feature to browse for the DST and register
name.
Set the other Data Link parameters to their desired values and click OK.
You can use serial device data in control modules. For example, use serial data as the I/O reference in standard
function blocks or create module-level parameters that reference the Dataset Tag and parameter associated with the
register with which you want to work.
The following specific examples describe how to read from and write to serial devices using a control module and a
control module reference.
Writing an Operator Display's Setpoint to a Specific Dataset Register
1
Create a module containing an Internal Write parameter (located on the Special Items palette).
Modify the Internal Write parameter properties by selecting a parameter type of External Reference.
For the External parameter path field, click Browse. Click Device Tags in the Type field and All Device Tags in
the Look in field. The list includes dataset tags.
Double-click the dataset tag that contains the parameter (register) that corresponds to the dataset value that you
want to write to.
Double-click the parameter. This parameter can be linked to a display's input data field. The result in Control
Studio looks like this:
Double-click the IO_IN parameter and then click Browse to select a specific analog input channel.
282
System Configuration
If desired, scale the analog input value using the XD_SCALE, OUT_SCALE, and L_TYPE parameters.
Add an Internal Write parameter to the diagram. The Internal Write parameter is on the Special Items palette.
Modify the properties of the Internal Write parameter by selecting a parameter type of External Reference.
For the External parameter path, click Browse. Select Device Tags in the Type field and All Device Tags in the
Look in field. The list include dataset tags.
Double-click the dataset tag that contains the parameter (register) that corresponds to the dataset value to which
you want to write.
Wire the AI block's Out parameter to the Internal Write parameter. The result in Control Studio looks like this:
Note Any value that is on the Output side of the AI block is written to the serial device regardless of the status of the
AI block.
Create a module containing an Internal Read parameter (located on the Special Items palette).
Modify the properties of the Internal Read parameter by specifying a parameter type of External Reference.
To select an External parameter path, click Browse. Click Device Tags in the Type field and All Device Tags in
the Look in field. The list include dataset tags.
Double-click the dataset tag containing the parameter (register) that corresponds to the dataset value that you
want to read from.
Double-click the parameter. This parameter can be linked to a display. The result in Control Studio looks like
this:
To select a device tag, click Browse. Click All Device Tags in the Type field. This shows all the Device Tag
names including the dataset tag name you want to read.
Double-click the Device Tag that contains the parameter (register) from which you want to read.
If desired, scale your input value using the Analog Input block's XD_SCALE, OUT_SCALE, and L_TYPE
parameters. The result in Control Studio looks like this:
I/O Configuration
283
284
System Configuration
devices maintain their values. Refer to the following topic, Using Outputs in Control Modules, for more information
on this option.
Using Outputs in Control Modules
When using serial output data in control modules, remember that the output values are only sent to the Modbus
devices when the value changes. This might cause problems if there is a program running in the Modbus device (for
example, a PLC) that could overwrite a register being used for output data by a DeltaV control module. The DeltaV
control module might think that the output register has one value in it when it actually contains a different value
written by a third party. The control module does not send the output value to the Modbus device until the output
value changes. To prevent this situation, enable the Output Readback option for any output datasets that could be
changed by a third party. When the Output Readback option is enabled, the Serial Card reads the output values from
the Modbus device during its normal input scan and updates the corresponding values in the DeltaV system if they
change. This ensures that the output register values in the DeltaV system always match what is actually in the
Modbus device.
Mapping Method
Boolean
String
Not supported.
I/O Configuration
285
Mapping Method
Boolean
The card sets the Boolean value to 0 if the Modbus register has a value of 0
and to a value of 1 if the Modbus register has a value other than 0.
The card maps the lower 8 bits of the Modbus register to the DeltaV value
with no additional conversion.
The card maps all 16 bits of the Modbus register directly into the DeltaV
integer value.
The card maps two consecutive Modbus registers to the DeltaV value. The
first register is the least significant word, and the second register is the most
significant word.
Floating point
Floating point values are stored on Modbus PLCs in IEEE format in two
consecutive registers where the first is the least significant word and the
second is the most significant word. The Serial Card maps the two
consecutive Modbus registers to the DeltaV floating point value using the
first register as the least significant word and the second as the most
significant word.
String
The Number of values field indicates the size of the string. The Serial Card
maps the specified registers to a single DeltaV string with a length equal to
number of values * 2. The first register specified contains the first two
characters of the string where the high order byte of the register contains
the first character and the low order byte contains the second character. The
remaining registers contain the rest of the string characters in the same
order.
286
System Configuration
Mapping Method
Boolean
The card sets the coil or input status to a value of 0 if the DeltaV
value is 0 and to 1 if the DeltaV value is anything other than 0.
String
Not supported.
Mapping Method
Boolean
The card sets the Modbus register to 0 if the Boolean has a value of 0 and to 1
if the Boolean has a value of 1.
The card maps the DeltaV value to the lower 8 bits in the Modbus register and
sets the upper 8 bits to 0.
The card maps all 16 bits of the DeltaV integer directly into the Modbus
register.
The card maps the DeltaV value to two consecutive Modbus registers. The
first is the least significant word, and the second is the most significant word.
Floating point
Floating point values are stored on Modbus PLCs in IEEE format in two
consecutive registers with the first being the least significant word and the
second being the most significant word. Therefore, the Serial Card maps
DeltaV floating point values to two consecutive Modbus registers. The first
register contains the least significant word, and the second contains the most
significant word.
String
The Number of values field indicates the size of the string. The Serial Card
maps the string to consecutive Modbus registers starting with the start register
configured for the dataset. The first Modbus register contains the first two
characters of the string with the high order byte containing the first character
and the low order byte containing the second character. The card maps the
remaining characters in the string to ascending Modbus registers with the
characters in the same order in the registers.
I/O Configuration
287
Analog - raw 4 to 20 mA signal, Card and channel status are applied, no HART status is applied.
HART Dynamic Variables - digital signal, Card, Channel, and HART status are applied.
HART Dynamic Variables - digital signal, Card, Channel, and HART status are applied.
HART Device Variables - digital signal, Card, Channel, and HART status are applied.
Some multivariable devices have a predefined set of Dynamic Variables; in others, you can assign process values to
the Dynamic Variables through an external device or application. Refer to the vendor's documentation for your HART
device for specific information. Refer to the Link Initialization topic for information on setting up the devices to
communicate correctly with the DeltaV system.
When DeltaV (version 3.3 or later) and AMS Device Manager (version 1.4 or later) are communicating with the same
HART instruments, AMS Device Manager works through the DeltaV system's software and wiring.
288
System Configuration
I/O Configuration
289
Error Conditions
HART field devices report internal self-test status information and indications of signal integrity. This information is
sent in a status byte that is sent with each HART message. The error conditions affect the status associated with
channel data, the channel integrity parameter (OINTEG), and the status text visible in the diagnostics application
(STATUS).
Effect of Error Conditions on Channel Data Status
When an Analog Input function block references a HART channel, error conditions affect the statuses of the OUT
parameter in the Analog Input function block. The following table describes the effect of HART and system-derived
errors on the status of the OUT parameter. (If multiple errors are present, the worst case status is reported.)
HART Error Conditions
Parameter
Field Device
Malfunction
Analog Output
Saturated
NPV Out of
Limits
COLD_START
No effect
No effect
No effect
No effect
CONFIG_CHANGE
No effect
No effect
No effect
No effect
HART_PV
BadNonSpecific(1)
BadDeviceFailure(1)
BadNonSpecific(1)
No effect
HART_SV
No effect
BadDeviceFailure(1)
No effect
BadNonSpecific(1)
HART_TV
No effect
BadDeviceFailure(1)
No effect
BadNonSpecific(1)
HART_FV
No effect
BadDeviceFailure(1)
No effect
BadNonSpecific(1)
HINTEG
True
True
True
True
DEV_MALFUNC
No effect
True
No effect
No effect
MORE_STATUS
No effect
No effect
No effect
No effect
NO_COMM
No effect
No effect
No effect
No effect
NPV_PAST_LIM
No effect
No effect
No effect
True
OINTEG
Bad(1)
Bad(1)
Bad(1)
Bad(1)
PV_FIXED
True
No effect
No effect
No effect
PV_PAST_LIM
No effect
No effect
No effect
No effect
PV_SAT
No effect
No effect
True
No effect
STATUS
Analog Output
Current Fixed
Device Malfunction
Analog Output is
Saturated
Non-Primary
Variable Out of
Limits
BadNonSpecific(1)
BadDeviceFailure(1)
BadNonSpecific(1)
No effect
Only AI
HART_FIELD_VAL
290
System Configuration
Parameter
Field Device
Malfunction
Analog Output
Saturated
NPV Out of
Limits
No effect
No effect
No effect
No effect
OUT
BadNonSpecific(1)
BadDeviceFailure(1)
BadNonSpecific(1)
No effect
HART_DV_SLOT0
No effect
No effect
No effect
No effect
HART_DV_SLOT1
No effect
No effect
No effect
No effect
HART_DV_SLOT2
No effect
No effect
No effect
No effect
HART_DV_SLOT3
No effect
No effect
No effect
No effect
Parameter
FIELD_VAL_PCT
Only AO
PV Out of Limits
Config Changed
Cold Start
More Status
Available
COLD_START
No effect
No effect
True
No effect
CONFIG_CHANGE
No effect
True
No effect
No effect
HART_PV
BadNonSpecific(1)
No effect
No effect
No effect
HART_SV
No effect
No effect
No effect
No effect
HART_TV
No effect
No effect
No effect
No effect
HART_FV
No effect
No effect
No effect
No effect
HINTEG
True
No effect
No effect
No effect
DEV_MALFUNC
No effect
No effect
No effect
No effect
MORE_STATUS
No effect
No effect
No effect
True
NO_COMM
No effect
No effect
No effect
No effect
NPV_PAST_LIM
No effect
No effect
No effect
No effect
OINTEG
Bad(1)
Bad
No effect
No effect
PV_FIXED
No effect
No effect
No effect
No effect
PV_PAST_LIM
True
No effect
No effect
No effect
PV_SAT
No effect
No effect
No effect
No effect
STATUS
Primary Variable
Out of Limits
Device Configuration
has Changed
More status
available (via
Remote Monitor)
I/O Configuration
291
Parameter
Config Changed
Cold Start
More Status
Available
HART_FIELD_VAL
BadNonSpecific(1)
BadConfigError
No effect
No effect
FIELD_VAL_PCT
No effect
No effect
No effect
No effect
OUT
BadNonSpecific(1)
BadConfigError
No effect
No effect
HART_DV_SLOT0
No effect
No effect
No effect
No effect
HART_DV_SLOT1
No effect
No effect
No effect
No effect
HART_DV_SLOT2
No effect
No effect
No effect
No effect
HART_DV_SLOT3
No effect
No effect
No effect
No effect
Only AI
Only AO
Unconfigured or
Unsupported
Digital Var
Loss of
Digital
Comms
5% Digital
Comm Error
Rate
Burst
Mode
COLD_START
No effect
No effect
No effect
No effect
No effect
CONFIG_CHANGED
No effect
No effect
No effect
No effect
No effect
HART_FIELD_VAL
BadConfigError(2)
No effect
No effect
UncertainNonSpecific
No effect
FIELD_VAL_PCT
No effect
No effect
No effect
UncertainNonSpecific
No effect
HART_PV
No effect
BadConfigError(3)
BadNoCommLUV
UncertainNonSpecific
No effect
HART_SV
No effect
BadConfigError(3)
BadNoCommLUV
UncertainNonSpecific
No effect
HART_TV
No effect
BadConfigError(3)
BadNoCommLUV
UncertainNonSpecific
No effect
HART_FV
No effect
BadConfigError(3)
BadNoCommLUV
UncertainNonSpecific
No effect
HART_DV_SLOT0
No effect
BadConfigError(3)
BadNoCommLUV
UncertainNonSpecific
No effect
HART_DV_SLOT1
No effect
BadConfigError(3)
BadNoCommLUV
UncertainNonSpecific
No effect
HART_DV_SLOT2
No effect
BadConfigError(3)
BadNoCommLUV
UncertainNonSpecific
No effect
HART_DV_SLOT3
No effect
BadConfigError(3)
BadNoCommLUV
UncertainNonSpecific
No effect
HINTEG
No effect
No effect
True
No effect
No effect
DEV_MALFUNC
No effect
No effect
No effect
No effect
No effect
NO_COMM
No effect
No effect
True
No effect
No effect
292
System Configuration
Parameter
Unconfigured or
Unsupported
Digital Var
Loss of
Digital
Comms
5% Digital
Comm Error
Rate
Burst
Mode
MORE_STATUS
No effect
No effect
No effect
No effect
No effect
NPV_PAST_LIM
No effect
No effect
No effect
No effect
No effect
OINTEG
Bad
No effect
Bad
No effect
No effect
OUT
BadConfigError(2)
No effect
No effect
UncertainNonSpecific
No effect
PV_FIXED
No effect
No effect
No effect
No effect
No effect
PV_PAST_LIM
No effect
No effect
No effect
No effect
No effect
PV_SAT
No effect
No effect
No effect
No effect
No effect
STATUS
Refer to "Effect of
Error Conditions on
Diagnostics Status
Text"
No effect
"Not
Communicating
with Device"
"Burst
Mode
Enabled" (4)
Table Footnotes
(1) Unless ignored by the configuration.
(2) Unless ignored by the configuration; not all scaling errors can be ignored.
(3) Only the digital variable that is unconfigured or unsupported will have bad status.
(4)Only detected on HART Passthroughs (for example AMS, Scaling).
Non-HART Error Conditions
Parameter
Channel Status:
Hardware Error,
Config Error, or
Not Configured
COLD_START
No effect
No effect
No effect
CONFIG_CHANGED
No effect
No effect
No effect
HART_FIELD_VAL
BadDeviceFailure
BadConfigError
UncertainNonSpecific
FIELD_VAL_PCT
BadDeviceFailure
BadConfigError
UncertainNonSpecific
HART_PV
BadDeviceFailure
BadConfigError
UncertainNonSpecific
HART_SV
BadDeviceFailure
BadConfigError
UncertainNonSpecific
HART_TV
BadDeviceFailure
BadConfigError
UncertainNonSpecific
HART_FV
BadDeviceFailure
BadConfigError
UncertainNonSpecific
HART_DV_SLOT0
BadDeviceFailure
BadConfigError
UncertainNonSpecific
HART_DV_SLOT1
BadDeviceFailure
BadConfigError
UncertainNonSpecific
I/O Configuration
293
Parameter
Channel Status:
Hardware Error,
Config Error, or
Not Configured
HART_DV_SLOT2
BadDeviceFailure
BadConfigError
UncertainNonSpecific
HART_DV_SLOT3
BadDeviceFailure
BadConfigError
UncertainNonSpecific
HINTEG
No effect
No effect
No effect
DEV_MALFUNC
No effect
No effect
No effect
MORE_STATUS
No effect
No effect
No effect
NO_COMM
No effect
No effect
No effect
NPV_PAST_LIM
No effect
No effect
No effect
OINTEG
Bad
Bad
No effect
OUT
BadDeviceFailure
BadConfigError
UncertainNonSpecific
PV_FIXED
No effect
No effect
No effect
PV_PAST_LIM
No effect
No effect
No effect
PV_SAT
No effect
No effect
No effect
STATUS
"Good - No Installed
Config" or "Bad
Configuration Error"
COLD_START
No effect
CONFIG_CHANGED
No effect
HART_FIELD_VAL
No effect
FIELD_VAL_PCT
No effect
HART_PV
No effect
HART_SV
No effect
HART_TV
No effect
294
System Configuration
Parameter
HINTEG
No effect
MORE_STATUS
No effect
SLOT0
No effect
SLOT1
No effect
SLOT2
No effect
SLOT3
No effect
HART_FV
No effect
DEV_MALFUNC
No effect
NO_COMM
No effect
NPV_PAST_LIM
No effect
OINTEG
Bad
OUT
BadDeviceFailure
PV_FIXED
No effect
PV_PAST_LIM
No effect
PV_SAT
No effect
STATUS
Diagnostics in Progress
There has been a problem configuring the HART instrument during initialization.
If any of the conditions below exist, OINTEG will be True (1) except for Good and Good - No Installed
Config.
I/O Configuration
295
296
System Configuration
Device Configuration Cannot be Changed - Device is Busy - The HART channel attempted to configure the analog
output scale information of the attached HART instrument, and the instrument reported that it was busy (AI only).
Device Configuration Cannot be Read - Device is Busy - The HART channel attempted to read the analog output
scale information of the attached HART instrument, and the instrument reported that it was busy.
Device Configuration Cannot be Read - The HART channel attempted to read the analog output scale information
of the attached HART instrument, and the instrument reported a problem.
Device Configuration Units or Range Invalid - The HART channel attempted to configure the analog output scale
information of the attached HART instrument, and the instrument reported that the units or one or both range values
are invalid.
Device Configuration Set to Nearest Possible Value - The HART channel attempted to configure the analog output
scale information of the attached HART instrument, and the instrument reported that it set one or both of the range
values to the nearest possible value.
Configuration Does Not Match Device - The HART channel has not yet attempted to configure or read the analog
output scale information of the attached HART instrument.
Diagnostics in Progress - The HART channel is performing Valve Diagnostics (Valve Stimulus Testing) on a Fisher
Controls valve (AOUT only).
Device is Write Protected - The Analog Input HART channel attempted to write the analog output scale information
to the attached HART instrument and the instrument reported that it is write protected.
Device is Write Protected (In Service) - The Analog Output HART channel attempted to write the analog output
scale information to the attached HART instrument and the instrument reported that it is write protected. For Fisher
Controls DVC valves, this indicates the valve is "In Service".
Device Configuration Access is Restricted (In Service) - The Analog Output HART channel attempted to write the
analog output scale information to the attached HART instrument and the instrument reported that it is write
protected. For Fisher Controls DVC valves, this indicates the valve is "In Service".
Device Configuration Cannot be Read - The Analog HART channel attempted to read the analog output scale
information from the attached HART instrument and the instrument reported that HART command 15 is not
supported.
Device Configuration Cannot be Changed - The Analog HART channel attempted to read the analog output scale
information from the attached HART instrument and the instrument reported that HART commands 35 or 44 are not
supported.
Device Configuration Cannot be Changed (In Service) - The Analog Output HART channel attempted to write the
analog output scale information to the attached HART instrument and the instrument reported a bad instrument status.
For Fisher Controls DVC valves, this indicates that the valve is "In Service".
Reconfiguration in Progress - The HART instrument is in the process of being rescaled.
Configuration Range Does Not Match Device - The HART channel determined there was a lower or upper range
value mismatch between the function block and HART instrument.
Non-HART Device Failure Error STATUS Text Strings
"No Card"
"Bad - Hardware Error"
"Bad - Failstate Active"
"A/D Converter Error"
"Open Loop Detected"
I/O Configuration
297
DEV_MALFUNC is True
PV_FIXED is True
There has been a problem configuring the HART instrument during initialization
If any of the conditions related to the diagnostic status text strings listed above exist, OINTEG will be True
(1) except for Good and Good - No Installed Config.
298
System Configuration
Ignore PV Out of Limits for All PV Status - Primary variable (PV) values that are higher or lower than the
configured limits are ignored when determining PV statuses.
Ignore NPV Out of Limits for All NPV Status - Non-primary variable (NPV) values that are higher or lower than
the configured limits are ignored when determining NPV statuses.
Ignore PV Output Saturated for All PV Status - PV values that are output saturated are ignored when determining
PV statuses.
Ignore PV Output Fixed for All PV Status - PV values that have a fixed output are ignored when determining PV
statuses.
Ignore FLD Device Malfunction for All Status - Values determined during a field device malfunction are ignored
when determining statuses.
Ignore Loss of Digital Comms for FV_PCT Status - Values determined during the loss of digital communications
are ignored when determining the field value in percent (HART_FIELD_VAL) status.
Override Unsupported Device Scale - If a HART device returns Not a Number (NaN) for the signal's Upper or
Lower Scale, the DeltaV system ignores the scale returned by the device and uses the scale configured in the I/O
block's HART_FIELD_VAL parameter.
Note The default value for these actions is disabled (False). That is, these status conditions are not ignored. When you
enable these actions, the block ignores the specified statuses.
Link Initialization
In order for the HART field device to be compatible with the DeltaV system, it must be able to communicate using
the HART commands listed in this section.
In the DeltaV system, HART link initialization is performed by the DeltaV AI-HART card and the controller function
block.
I/O Card Initialization
When a HART card is plugged in, it assumes that all channels are analog only. When you configure the card, you can
set the channel to HART_ANALOG_INPUT (AO also).
The card then tests for an open circuit. If no open circuit is detected, the card sends out HART Command 0 (Read
Manufacturer and Device Type) followed by Command 59 (Write Number of Response Preambles).
Controller Function Block Channel Initialization
The DeltaV Controller also performs HART channel initialization. As soon as the controller is notified that an AIHART card configuration is complete, it sends Command 0 to each HART channel.
If a function block is linked to the HART_FIELD_VAL parameter (for AI) or OUT parameter (for AOUT) of the
HART channel, the first time the function block executes, it sends scaling information (high and low range and units)
to the HART instrument for its analog output signal. The units code is sent via HART Command 44 (Write Primary
Variable Units). The high and low range information is sent via HART Command 35 (Write Primary Variable Range
Values). At this time, the HART instrument sets a bit saying that it has changed its configuration to the new values.
The controller sends HART Command 15 (Read Primary Variable Output Information) to read the range and units
information. This is followed by Command 38 (Reset Configuration Change Flag) to clear the change flag in the
instrument. Note that if command 44 is not supported, command 15 is inserted before command 35 in the description
above.
I/O Configuration
299
You might connect a hand-held device to an instrument in the field to change its scale values. The controller
detects this change in the instrument and sends Command 15 to read the new values followed by command
38.
During loop tuning, you can change the range values in an AI function block. These changes are sent to the
HART instrument.
You might specify range values to a high level of precision and some HART instruments might not be able to
support that precision. The controller sends Command 15 to detect the actual range precision the instrument
is using in the process.
If a HART instrument does not support the HART Commands 44 and 35 (used to set the scale values), the values read
by HART Command 15 are compared to those specified by the function block. If the values are the same, they are
accepted and the link initialization continues. If the values are not the same (or if the HART instrument is writeprotected or blocking access to that configuration information), the controller stops the HART link initialization for 5
seconds, restarts it with cmd 0, and the initialization repeats.
HART Special Units Handling
The HART protocol allows units that might be unique to a particular HART instrument and unknown to the DeltaV
system. To deal with this for a specific function block, select one of the following values for the Engineering unit
descriptor: hyphen (-), blank space ( ), or no units. The DeltaV system then uses the units and scale information that
are currently configured in the HART instrument. If the type of units are known to the DeltaV system, the units are
displayed in the XD_SCALE parameter of the function block. However if they are unknown to the DeltaV system,
the units field in XD_SCALE is blank.
HART Scan Update Rate (AI)
After this card's initialization phase, the card sends out Command 3 (Read Dynamic Variables and Primary Variable)
repeatedly to each HART channel. The HART scan update rate for each input channel configured for HART is 600800 ms. The analog values for each input channel are scanned in much faster than the HART scan update rate.
Passthrough messages sent by AMS Device Manager can cause a card's HART scan rate to be twice the rate without
AMS Device Manager running.
HART Scan Update Rate (AOUT)
After this card's initialization phase, the card sends out Command 3 (Read Dynamic Variables and Primary Variable)
repeatedly to each HART channel. The HART scan update rate for each output channel configured for HART is 600800 ms.
If device variables (DV_SLOT) are configured for a channel, the card sends command 33 to read the configured
device variables. The HART scan update rate for each channel configured for device variables is an additional 600800 ms.
Passthrough messages sent by AMS Device Manager can cause a card's HART scan rate to be as much as twice the
rate without AMS Device Manager running.
If valve diagnostics is running on a channel, the card's HART scan rate can be as much as twice the rate without
diagnostics running.
As an example:
The scan rate for an 8 channel analog output card with all channels configured for HART is 4.8 to 6.4 seconds:
300
If device variables is also running, the scan rate can be 9.6 - 12.8 seconds.
If AMS Device Manager and device variables are running, the scan rate can be 19.2 - 25.6 seconds.
If AMS Device Manager, device variables, and valve diagnostics are running, the scan rate can be 38.4 -51.2
seconds.
System Configuration
The AMS Device Manager software is not installed with the DeltaV software. It is a stand-alone client/server system
that is installed and licensed separately from the DeltaV software. The license file specifies the allowed number of
concurrent users. The AMS Device Manager Audit Trail is installed with AMS Device Manager. Refer to the AMS
Device Manager Installation Guide for complete information.
Note Once AMS Device Manager is launched either from the DeltaV Explorer or the Start menu, only one instance of
it runs on the DeltaV workstation.
Prerequisites for Launching AMS Device Manager from DeltaV Explorer
There are some prerequisites for launching AMS Device Manager from the DeltaV Explorer:
AMS Device Manager must be installed on the same workstation as the DeltaV software.
The user must have an AMS Device Manager user name and password.
The DeltaV DSTs (Device Signal Tags) and the AMS tags must match for each device.
Click Start | DeltaV | Engineering | DeltaV Explorer to open the DeltaV Explorer.
Navigate to the HART channel and ensure that it is enabled. (Select the channel, click the right mouse button,
and select Properties to see if it is enabled.) Refer to the DeltaV Explorer online help if you need assistance in
navigating to an object.
Auto-sense the HART device to create the device tag. (Select the channel, click the right-mouse button, and
select Auto-sense HART device.) The tag appears beneath the channel in the Explorer hierarchy.
Select the device, click the right-mouse button, and select the desired AMS Device Manager command from the
context menu.
Enter your AMS Device Manager user name and password and wait for the AMS Device Manager Tag Search
dialog to open. Once AMS Device Manager is opened, you do not have to re-enter your user name and password.
You remain logged on to AMS Device Manager until you exit the application.
AMS Device Manager displays device information in the Tag Search dialog and then opens the dialog associated with
the selected menu command. Use the Help menu in AMS Device Manager for complete help.
Tip You can access AMS Device Manager commands from the AMS Device Manager Tag Search dialog. Select the
device in the Tag Search dialog, click the right mouse button, and select a command from the context menu.
I/O Configuration
301
302
System Configuration
can reset devices (turn the devices' outputs off and disable data exchange) or continue polling the slave devices. Auto
addressing specifies how an address is assigned when a device is replaced. For more information, refer to the
Communication on the Network topic.
AS-Interface Slave Device Configuration
Device configuration consists of assigning an AS-Interface Device Type to the device and assigning the device
address. An AS-Interface Device Type is a fixed-format description of the device that the AS-Interface master uses to
communicate with the slave device. You create your own AS-Interface Device Type from the device's data sheet. The
AS-Interface Device Type consists of an Identification code and I/O Configuration (taken together these are defined
by the AS-Interface Specification as the device Profile) the Parameters for the device, and the inputs and outputs
supported by the device. (In the DeltaV Explorer, the Profile appears in the format S-[I/O
Configuration].[Identification Code] as defined by the AS-Interface Specification. For example, S-2.0.) The
Identification code and I/O Configuration are designated by the device manufacturer. The Identification code
identifies the type of device and the I/O Configuration identifies the device's input and output bits. The four bit
Parameters are used to customize the device behavior.
Note An AS-i port status value of Mismatch in DeltaV Diagnostics means that the profile for one or more of the
actual devices on the segment does not match that of the configured device.
When a new AS-Interface slave device is created in the DeltaV Explorer, each input and output for the device is
assigned a channel label and a Device Signal Tag (DST). The labels and DSTs appear under the device in the Explorer
hierarchy. A Device Signal Tag is a unique name that represents a specific signal from the device. The signal is used
in the control strategy and counted for licensing. A default DST name is assigned by the system when the device is
created but you can rename it at any time. The channel label is taken from the device's AS-Interface Device Type and
can be modified through the AS-Interface Device Type's property page. Refer to the Port Downloads section for
information on downloading the AS-Interface ports.
Modifying Devices
Use the device's Properties page to modify the description, address, and to enable and disable the device. Select the
device in the DeltaV Explorer and select Properties from the device's context menu to access the Properties page. The
Add New Type button on the Properties page is functional only when adding a new device to the DeltaV system; not
when viewing the properties of an existing device. Use the online help for help on the fields in the Properties dialog.
Addressing
Each slave device connected to an AS-Interface network has an address between 1 and 31. All AS-Interface devices
are shipped from the manufacturer with address 0 a temporary address that prohibits data exchange. A new ASInterface slave device is assigned an address when it is created in the DeltaV Explorer. When a device is replaced, it
can have its address assigned through a hand-held device or it can be automatically set to the original address through
the Auto Address feature on the AS-Interface master.
Auto-Sensing
The auto-sense feature aids in AS-Interface device configuration. Auto-sensing lists the slave devices existing in the
database and those sensed on the port and shows each device's address, name, I/O configuration, and Identification
code. This feature can be used to add devices to the configuration, and to clear and set addresses. You must download
the port to activate slave devices.
Tip Turn off the Auto-address enable feature before attempting to clear an address.
I/O Configuration
303
Port Downloads
The action that the AS-Interface master takes following a new port download depends on the changes included in the
new configuration. Changes to port properties: Auto address enable and Action in the event of controller failure are
copied to the master and there is no effect on the slave devices on the network.
Warning If a slave device is added or removed from the configuration or if a slave address or profile is changed, the
AS-Interface master must restart the port. Restarting the port consists of the master transitioning to the offline state
where it resets all slave devices and reactivates the slaves. Resetting the slave devices causes the slaves to deactivate
their outputs. Once the port restarts, slave outputs return to the controller-driven state.
Diagnostics
Diagnostics displays the slave devices, DSTs, and values and provides advanced diagnostic information that is
supported by the AS-Interface master. Refer to the Diagnostics online help for complete information on diagnosing
AS-Interface slave devices and the AS-Interface master port.
304
System Configuration
I/O Configuration
305
configures signals that describe the I/O that the Slot (Profibus module) provides to the DeltaV system. For more
information, refer to the Profibus Module Signals topic.
Add and configure the Profibus master (the Profibus card's port)
Refer to the DeltaV Explorer online help for detailed information on adding and editing Device Definitions and
configuring Profibus devices.
Configuring the Profibus Master
Profibus master configuration consists of specifying the action the Profibus master takes if the controller fails, setting
the baud rate for all devices on the network, setting the master's address, and specifying network properties. The
supported baud rates, in bits per second (bps), for Profibus devices are 9.6K 19.2K, 93.75K, 187.5K, 500K, and
1.5M. The address for the Profibus master is usually 1. The DeltaV Explorer online help on the port properties dialog
provides detailed information on all the configuration properties for the Profibus master.
Adding and Creating Device Definitions
Adding the Device Definition creates a hierarchy of categories (Profibus Family, Manufacturer, Model, Device
Revision, and modules) under Profibus Devices in the DeltaV Library. You can change the device and module
parameter values and overwrite the default values specified by the manufacturer. You can also create Profibus module
signals in the Library. For more information, refer to the Profibus Module Signals topic.
Tip It is recommended that you change a module or device parameter value at the Library level rather than at the Slot
level to ensure that future instances of the module or device inherit that parameter value.
If you change a device parameter value at the Library level, existing instances of that device are not changed but
future instances of the device inherit the new parameter value. If you change a module parameter value or signal at
the Library level, existing instances of that module are not changed but future instances of the module (Slots) inherit
306
System Configuration
the new parameter value or signal even if the module is added to an existing device. If a device is associated with a
particular Device Definition in the Library, the DeltaV Explorer will not allow you to delete or re-add that Device
Definition. This ensures that the Device Definitions in the Library are consistent with existing devices.
Profibus Module Signals
The Device Definition contains information about data length, it does not contain information about the data itself.
For each Profibus module in the Library, you add Profibus module signals that contain information such as signal
direction, data type and the location of the signal value within the modules data.
You can configure module signals at the library level and at the physical network level.
Library Configuration - To save engineering time for similar devices, create default signals in the library. Configure
the signals that are common to all instances of a module type. When you add a slot for that module type to a device, it
is created with the signals defined for it in the library. (You can also create module signals at the physical device.)
Physical Network Configuration - Complete the configuration of the signal at the physical configuration level.
Provide a description of the signal and associate it with a specific Device Signal Tag (DST). For more information on
DSTs, refer to the Modifying and Assigning Device Tags topic.
Configuring Slave Devices
The Configuration steps vary depending upon whether the slave device is compact or modular. However for both
device types, you can specify if the device is enabled or disabled, assign an address, and set the device's Watchdog
Timer. The Watchdog Timer specifies the amount of time before the device goes into its fail safe mode if
communication on the network stops. The address is automatically assigned for both device types when the device is
created however, you can change the device address. Slave devices can have an address between 2 125. It is
recommended that address 1 be reserved for the Profibus master. Addresses are unique; no two devices, slave or
master, can have the same address on a port.
Configuring a compact device consists of adding the slave device to the Profibus master port and setting the device
properties (enable and Watchdog Timer). When a compact device is added to the Profibus master port, the slots and
parameters defined for that device are automatically created below the device in the DeltaV Explorer hierarchy.
Remember that configuration for a compact device is generated based on a fixed number of Profibus modules in a
particular order. Be aware that you cannot delete compact device slots in DeltaV Explorer; you must delete the device
in order to delete the slot.
Configuring a modular device consists of adding the device to the Profibus master port and setting the device
properties (enable and Watchdog Timer). However, because the configuration for a modular device is generated based
on the number and order of its modules, you configure the device by adding modules (called Slots in DeltaV) in the
correct order. Depending on the type of module, you may have to add signals or adjust parameter values. Unlike
compact devices, modular device slots can be deleted.
Parameters values can affect diagnostics, ground fault detection, failure actions and many other device
characteristics. For devices that have configuration parameters at the device and or the slot level, it is important to
provide parameter values for proper operation of the device.
Note When entering parameter values, note that the values you enter are always in decimal format for Profibus
devices.
I/O Configuration
307
will not inherit this value. For more information on inheritance, refer to the Tip in the Adding and Creating Device
Definitions topic. Slots can be added until the maximum number of bytes and slots specified by the device
manufacturer for that device have been met. When you add a new Slot, the dialog box displays the manufacturer's
limits and shows you the number of used and available bytes and slots.
The .GSD file specifies the number for the first slot. The default is 0. You must number the Slots contiguously to
successfully download the device. The Profibus protocol specifies that there can be no gaps in Slot numbers. The Slot
types and Slot order of the physical device must match the configuration in the DeltaV configuration database or the
device can not establish communication with the master.
Modifying and Assigning Device Tags
When you create a Slot from a Profibus Library module to which a signal was added, the signal and a DST are created
below the Slot in the DeltaV Explorer hierarchy. The DST is marked with a yellow tag. A default DST name (for
example PDT2S000AL1 in the following figure) is automatically assigned but it can be renamed so that it is
meaningful in your control strategy.
A DST is a unique name that represents a specific signal from the device. The signal is used in the control strategy
and counted for licensing. At the Slot level, you can customize the DST name and modify the signal properties for
that device. Remember that any modifications made to the signal at the Slot level do not affect the Profibus Library
module that contains that signal. If you have previously configured a DST, you can browse for it and assign it to a
signal.
Using Profibus DP with DeltaV Function Blocks
Refer to Using Profibus DP, DeviceNet, and AS-Interface with DeltaV Function Blocks for more information.
308
System Configuration
125 k
250 k
500 k
61 m (200 ft.)*
* ODVA specifications allow for a maximum trunk length of 100 m (328 ft.) at 500 k baud; however, testing indicates
that a few device types experience unstable operation at these limits. Emerson Process Management recommends a
maximum trunk length of 61 m (200 ft.) at 500 k baud to maintain a stable DeviceNet system with a wide variety of
devices.
Communication on the DeviceNet Network
Data exchange using polling is the normal method of communication and begins when the port is downloaded. The
port uses the polling connection configured in the device. The port verifies the device's Vendor ID, Device Type, and
Product Code, and I/O polling size attributes and then begins exchanging data with the device. The data is mapped by
the user to signals. Refer to the Adding DeviceNet Signals topic.
Note The change-of-state and strobe methods of communication are not supported by the DeltaV system.
I/O Configuration
309
310
System Configuration
Modifying Parameter Values in the Library and Setting Parameter Download Preferences
There are two types of parameters for DeviceNet devices:
Read only parameters that are used to monitor the current status of devices. Read only parameters are not
configurable and are not downloaded.
You can view and modify default parameters and select the parameters that you want to include in the download at
the DeltaV Explorer Library level. Any changes made to default parameters at the Library level affect the selected
revision and all devices of that type subsequently created from that revision. Follow these steps to modify default
parameters in the Library:
1
Use the Default Parameters dialog box to modify the default parameters and to open the Download Preferences dialog
box. Use the Download Preferences dialog box to select the parameters that you want to include in the download and
to deselect the parameters that you want to exclude from the download. Refer to the DeltaV Explorer online help for
complete help on the fields in this dialog box. It is highly recommended that you refer to the device documentation
and select for download, only those parameters that are needed for the device. In addition, deselect parameters that
have potential side effects such as MAC ID and baud rate. When you click OK in the Download Preferences dialog,
you will see your changes in the Default Parameters dialog box.
Using DeviceNet with DeltaV Function Blocks
Refer to Using Profibus DP, DeviceNet, and AS-Interface with DeltaV Function Blocks for more information.
I/O Configuration
311
Note If there is no match, the connection breaks, and no data is exchanged. Also, the VendorID, Device Type,
Product Code, and input/output sizes cannot be read from the device. The verification only identifies a match in these
items, it does not read back the values. Disable I/O Polling and download the device, and then read back Vendor ID,
Device Type, Product Code, and input/output sizes using DeltaV Diagnostics to troubleshoot communication
problems.
With DeltaV Diagnostics if the device supports the standard method of addressing through setting the MAC
ID parameter of the DeviceNet Object.
Disable I/O Polling for the device in DeltaV Explorer and download the DeviceNet card.
Right click on the device in the left pane, select Set Device Address, and enter an address.
Enable I/O Polling and download the card in DeltaV Explorer to resume data exchange.
Note Set the address before you put the device on the network if the port is operational. Do not attach the device if
you do not know the address or baud rate.
Some devices use switches on the front of the device to configure the baud rate. Consult the device
documentation for information.
The EDS file for some devices supports a baud rate parameter for configuration through DeltaV software.
Some devices support the use of the DeviceNet Object's baud rate attribute to set the baud rate. (Consult the
device's conformance documentation.) Use DeltaV Diagnostics to set the baud rate for this type of device.
Be sure to disable I/O Polling for the device and to reset or power cycle the device for the baud rate to take
effect.
If the device supports neither switches nor the baud rate parameter, use a diagnostics tool to configure the
baud rate. Consult the device documentation for information.
The EDS file for some devices supports an autobaud rate parameter for configuration through DeltaV
software. Enable this parameter and attach the device to the network.
312
System Configuration
device, the value is stored in both the device and in the configuration database. (The value is written to the device and
read back from the device. If the write and read are successful, the value is stored in the database.) Remember that
any parameter modifications made at the device level affect only that device. Any new devices of the same type
inherit the parameter values specified in the device revision. To modify parameters, select the device, click the right
mouse button, and select Modify Parameters.
Offline Devices
If you attempt to modify parameters in an offline device, you will receive a message that the DeltaV system cannot
communicate with the device and you are given the option of modifying parameters offline. When you modify
parameter values in an offline device, the values are stored in the database only. Later, you can download to
synchronize the values in the database with the values in the device. Refer to the Downloading Devices topic for
more information.
NVRAM Button
Some devices require an explicit command to save parameter values in non-volatile memory. If you are modifying
parameter values for a device with this requirement, the NVRAM button is enabled on the Modify Parameters dialog
box. Click this button to save the parameter values to non-volatile memory. If you download the parameters to a
device with this requirement, the save command is sent automatically if the parameter download is successful.
Downloading Devices
You have four download options at the device level: Device, Properties and Signals, Parameters, and Update Device
Download Status. Select download to download the device as well as properties and signals and parameters. Select
Properties and Signals to download these options only and select parameters to download parameters only.
Note If you decide to download a device and during the download you notice a parameter value that is incorrect in the
database, you can deselect the parameter for download, download the device, and then modify the value online. You
cannot modify a value during the download.
I/O Configuration
313
314
System Configuration
If your Profibus DP, DeviceNet, or AS-Interface device goes to a failsafe state due to a failure in the device or a loss
of communication with the DeltaV system, the status of its DSTs in the DeltaV system is Bad. The following shows a
technique for analog outputs using a DeltaV PID function block. A condition function block detects Bad status in the
output DST and, after the failsafe time duration, causes the PID block output to track the failsafe value in the device.
After the failsafe state in the device clears, the PID block initializes from the failsafe value.
The following figure shows a similar technique for a discrete output using the Device Control function block. The
condition block is used in the same way as in the figure. In this case the DC block becomes interlocked to the 0
(passive) state when the device goes to failsafe state. When the failsafe state clears, SP_D and CAS_IN_D are in the
passive state, and can be written to the active state at the appropriate time.
I/O Configuration
315
The previous figure illustrates using the condition block when you are writing the discrete output with boolean or
expression logic. Whether the output is maintained or pulsed, the idea is to be sure the output is the device failsafe
value when the device is in the failsafe state.
Anti-Aliasing Filtering
Hardware and software signal filtering is supported in the DeltaV system:
The analog input card contains hardware filtering that limits the frequency of the input signal seen by the digital-toanalog (D/A) converter to about 3 Hz.
In addition, you can define software filtering to be applied at the analog card when you configure the analog input
channel properties (FILTER channel parameter). This feature prevents aliasing of the signal if the module execution
rate is set slower than twice the highest frequency component of the input signal.
The default setting for the software filter is Filter Disabled. If an input signal is relatively free of process noise and is
contained in a module executing a moderately fast rate, you might not need to apply additional software filtering at
the card.
If you choose to modify the filter, you see a selection of filter time constants in the Named State list. If you follow the
module execution rate guideline (period of control) that is shown in parentheses next to the filter time constant you
select, no aliasing will occur, even if the signal has significant noise.
Note If you modify the filter on an input channel, you might need to retune any control block that uses the channel for
its controller variable.
316
System Configuration
A hardware or software failure in the controller that interrupts communications for more than 2 seconds.
Note I/O cards must be receiving DeltaV power and field power to enter the configured failure action mode.
Failure Action Mode Designates if the channel should HOLD LAST VALUE or OUTPUT FAILURE
ACTION VALUE.
Failure Action Value Specifies the value used if the channel is configured to OUTPUT FAILURE
ACTION VALUE
I/O Configuration
317
.
Card
Analog Output
Hold Last Value: The output is held at the last value received from the controller before the
failure action condition occurred.
Use Configured Failure Action Values: The output is driven to the configured failure action
value when the failure action condition is entered.
Note All outputs values below 1 mA (including failure action values) are clamped to 1mA to
ensure that the open loop detection mechanism of the D/A converter is always operable.
Discrete
Output
Hold Last Value: The outputs continue with the latest configuration and output values. This
applies to all channel types. If the channel is configured to be continuous pulse output type, it
continues with the latest period and duty cycle. If the channel is configured to be a momentary
pulse output type, it continues to process the current pulse. No additional pulses can be
generated.
Use Configured Failure Action Values: In this mode, failure action forces the outputs to go to
predefined levels. If the channel is configured as momentary or continuous pulse output type,
the pulse is aborted for the failure action value.
Redundant Cards
For redundant Series 2 cards, loss of controller communication with both cards causes both cards to take their failure
action, but with slight differences. Both cards illuminate their red Error LEDs, but only the active card drives the field
outputs. Removing the active card will NOT cause failure action output values to remain, since a switchover cannot
occur when a card is removed.
Error Condition
RTD - 2 Wire
Short
Open Wire to Terminal 2
Open Wire to Terminal 3
RTD - 3 Wire
Short
Open Wire to Terminal 2
Open Wire to Terminal 3
Open Wire to Terminal 4
318
System Configuration
Channel Type
Error Condition
RTD - 4 Wire
Short
Open Wire to Terminal 1
Open Wire to Terminal 2
Open Wire to Terminal 3
Open Wire to Terminal 4
Thermocouple
Short
Open Wire to Terminal 2
Open Wire to Terminal 3
mV - Bipolar
Short
Open Wire to Terminal 2
Open Wire to Terminal 3
Volts - Unipolar
Short
Open Wire to Terminal 2
Open Wire to Terminal 3
Volts - Bipolar
Short
Open Wire to Terminal 2
Open Wire to Terminal 3
I/O Configuration
319
320
System Configuration
filename - (filename)
321
Note You can use a hyphen (-) in place of a forward slash (/). Therefore, you can enter /area as area. If there is a
filename, it must be the first argument. After each parameter, there must be a space followed by the value for that
parameter.
The startup command is CHS. This example starts the Process History View application and opens a saved file called
Reactor.phvc. If you do not provide a specific directory, the Process History View application searches for the file in
the default charts subdirectory (DeltaV/Dvdata/Charts). In this example, Process History View opens the file
Reactor.phvc, which resides in the default charts subdirectory (DeltaV/Dvdata/Charts):
CHS Reactor.phvc
The arguments are order independent and uncoupled (except for time options). However, some only affect a specific
type of display. For example, if displaying a Chart, the event-specific arguments are ignored. If a filename is
provided, it must be the first argument after the CHS command.
Avoid combining mutually exclusive searches. For example, you can only pair the event type ALARM with the
category PROCESS. Similar pairings occur for the event types CHANGE and DOWNLOAD.
Note If you combine mutually exclusive options, remember that when you specify the event type ALARM, you can
only specify the category PROCESS. Any other value results in records not being found. Instead, the CLI accepts
these currently mismatched pairs with the result being that records are not found in the chronicle.
Arguments (parameters and qualifiers) are indicated by either a hyphen (-) or forward slash (/) and are not case
sensitive.
Wildcards
You can use the wildcard characters * or ? when specifying an Event Filter argument (area, device, and so on). The
wildcard character '*' represents zero or more of any printable character, and the wildcard character '?' represents a
single printable character. Both wildcard characters can appear multiple times in an argument, and there are no
restrictions on the placement of the wildcard characters. (Wildcard characters can appear at the beginning, end, or
anywhere in an argument.)
The following sections provide details for each argument.
Specifying the Filename
To open a document that was saved using the Process History View application, provide the filename in the command
line. The filename must be the first parameter after the executable name, CHS. If the file exists in the default
directory for Process History View documents (DeltaV/Dvdata/Charts), supply only the filename and .phv_
extension on the command line (FIC101.phvc). If the file exists in a subdirectory (DeltaV/Dvdata/Charts/reactors),
include the subdirectory with the filename and extension (reactors/FIC101. phvc).
In the first example, Process History View opens the file Motors.phvc, which resides in the default directory
(DeltaV/Dvdata/Charts). In the second example, Process History View opens the file MyChart.phvc, which resides
in the subdirectory ../lib.
322
System Configuration
Examples:
CHS Motors.phvc
CHS lib/MyChart.phvc
Specifying a New Document Type
Flag name : new
Type : New Document
Applies to : Events, Chart, and EChart
Acceptable values : One of the character strings (Event, Chart, EChart). Not case sensitive.
Description : This argument opens a new document of the specified type (Chart, EChart, or Events). Chart opens a
new empty document that shows only a graph. EChart opens a new empty document that shows both the graph and
events grid, and Events opens a new empty document that shows only the events grid.
This parameter creates a new Process History View document. Typically, the /new argument can be combined with
other arguments.
Examples:
CHS /new events
CHS /new Chart
CHS /new EChart
Specifying the Area Name
Flag name : area
Type : Event Filter
Applies to : Events and E+Chart
Acceptable values : One or more character strings. Enclose in parentheses or double quotes. If more than one value,
separate with a comma.
Description : This parameter is used to add entries to the Area filter list. The search string can be a single area name,
a list of area names, or the string thisUser. The string thisUser can also appear in a list of areas. If an area name is
repeated in the list, only one instance of it is retained.
If the option is not present on the command line, no filtering of areas is performed.
Example :CHS /new events /area (AREA_1, AREA_2)
Specifying the Device (Node) Name
Flag names : device , dev , node
Type : Event Filter
Applies to : Events and E+Chart
Acceptable values : One or more character strings. Enclose in parentheses or double quotes. If more than one value,
separate with a comma.
323
Description : This parameter is used to add entries to the Node filter list. The search string can be a single Node name
or a list of Node names. If a node name is repeated in the list, only one instance it is retained.
If the option is not present on the command line, no filtering of node names is performed.
Examples:
CHS /new events /node (CTLR1, CTLR2)
CHS /new events /dev (CTLR1)
Specifying the Module (Tag) Name
Flag names : module, tag
Type : Event Filter
Applies to : Events and E+Chart
Acceptable values : One or more character strings. Enclose in parentheses or double quotes. If more than one value,
separate with a comma.
Description : This parameter is used to add entries to the Module filter list. The search string can be a single Module
name, or a list of Module names. If a Module name is repeated in the list, only one instance of it is retained.
If the option is not present on the command line, no filtering of Module names is performed.
Examples:
CHS /new events / Module (InletFlow, OutletFlow)
CHS /new events / Module (OneFlow)
Specifying the Event Type
Flag name : type
Type : Event Filter
Applies to : Events and E+Chart
Acceptable values : One or more of the character strings (EVENT, ALARM, CHANGE, STATUS and
DOWNLOAD). Enclose in parentheses or double quotes. If more than one value, separate with a comma.
Description : This parameter is used to add entries to the Type filter list. The search string can be a single Type, or a
list of Types. If a Type is repeated in the list, only one instance of it is retained.
If the option is not present on the command line, no filtering of Types is performed.
Examples:
CHS /new events /type (EVENT, ALARM)
CHS /new events /type (EVENT)
Specifying the Category
Flag names : category , cat
Type : Event Filter
Applies to : Events and E+Chart
324
System Configuration
Acceptable values : One or more character strings (USER, PROCESS, DEVICE, and SYSTEM). Enclose in
parentheses or double quotes. If more than one value, separate with a comma.
Description : This parameter is used to add entries to the Category filter list. The search string can be a single
Category or a list of Categories. If a Category is repeated in the list, only one instance of it is retained.
If the option is not present on the command line, no filtering of Category is performed.
Example :CHS /new events /Category (USER, PROCESS)
Specifying the Start Time
Flag name : starttime
Type : Time specification
Applies to : Events, Chart, and E+Chart
Format : Same formats as the endtime argument. There are two valid formats. For specifying the absolute start time,
either use the format specified for the workstation ( Start | Control Panel | Regional Settings ) or Continuous
Historian format.
Description : The start time is treated differently for Event displays than it is for Charts and E+Charts.
In Event displays, specifying the start time results in the display of the most recent events, beginning at the specified
time, and ending at the current time. The default display is the most recent hour if not otherwise defined. This
argument is not to be used with the time span arguments for Events. If you provide both a start time and a time span,
the start time is ignored. The start time must be in the format specified in Regional Settings (available in the Control
Panel).
Example :CHS /new events /starttime 10:00
For Charts and E+Charts, the default time range is 8 hours, ending at the current time. If creating a new Chart or
E+Chart with the /new qualifier, use the /starttime argument to select a specific start time. If opening an existing file,
you can use this parameter to change the configured value in the file. If using the Process History View application,
this is the same as clicking Chart | Configure Chart, clicking the Time Scale tab, and entering the value in the Time
Start field.
For Charts and E+Charts, you can use the starttime argument with the other time specification arguments, span or
endtime . The start time argument can be either of the two following types:
1
Same format as defined in the Date and Time tabs of the Regional Settings dialog (available in the Control
Panel).
325
Note The keyword today means today's date at 00:00, and the keyword yesterday means yesterday's date at 00:00.
Other keywords are the days of the week (Monday, Tuesday, Wednesday) and months of the year (January, February,
March). You can also use a format such as Tuesday+14h to mean 2 PM of the most recent Tuesday. Since the time
string can contain forward slashes (12/05/97 08:00:00 PM), enclose the string in double quotes or parentheses.
In this example, the Process History View application opens a new events document that displays events that
occurred four hours prior to the current time.
CHS /new events /span 4
In this example, the Process History View application opens an existing file, and modifies the time span to 2
hours.
CHS motor.phvc /span "2:00"
326
System Configuration
Same format as defined in the Date and Time tabs of the Regional Settings dialog (available in the Control
Panel).
327
Same format as defined in the Date and Time tabs of the Regional Settings dialog (available in the Control
Panel).
328
System Configuration
Examples:
CHS /span 1:00 /trend (MTR101/PID1/PV.CV,
MTR201/PID1/PV.CV)
Specifying Parameter Reference Substitution String
Flag name: sub
Type : Substitution string
Applies to : Chart and E+Chart
Acceptable values : A single character string. If the string contains a hyphen (-) or a forward slash (/), you must
enclose the entire string in parentheses or double quotes.
Description : The argument sub is used to modify the parameter reference strings already defined in an existing
chart, such that the module name portion of the defined parameter reference is replaced with the substitution string. A
parameter reference (such as FIC-101/PID1/PV.CV) is in the form:
MODULE NAME/BLOCK/PARAMETER.FIELD
All characters in the parameter reference up to the first forward slash (/) are replaced by the string sub. For example,
if a document contains the configured parameter references FIC-101/PID1/PV.CV and FIC-101/PID1/SP.CV, and sub
MTR101 is specified on the command line, the chart automatically changes the two parameters to MTR101/PID1/
PV.CV and MTR101/PID1/PV.CV.
If a parameter reference is blank, it will remain blank. If a parameter reference contains no forward slash, the entire
string is replaced with the substitution string.
If a Chart or E+Chart is called with a substitution string, then it is not possible to save the chart. However, it is
possible to modify the existing configuration before exiting.
In this example, the chart Motors.phvc contains the parameter references FIC-101/PID1/PV.CV and FIC-101/PID1/
SP.CV, which are replaced by MTR101/PID1/PV.CV and MTR101/PID1/PV.CV.
Example :CHS motors.phvc /sub MTR101
Note You must supply a filename with the sub argument.
329
330
System Configuration
Specifying a Desc1
Flag name : desc1
Type: Event Filter
Applies to : Events and Echart
Acceptable values : Any string. Wildcards can be used in the string (* is a multi-character wildcard and ? is a single
character wildcard.)
Description : Places the associated string into the Level1 field of the Other Columns page of the Event Filters.
Example : CHS /new events/desc1 HIGH
Specifying a Desc2
Flag name : desc2
Type: Event Filter
Applies to : Events and Echart
Acceptable values : Any string. Wildcards can be used in the string (* is a multi-character wildcard and ? is a single
character wildcard.)
Description : Places the associated string into the Level1 field of the Other Columns page of the Event Filters.
Example : CHS /new events/desc2 LOW
331
Downloading Data
Inside this topic
What Happens during a Download
When To Download
What To Download
The workstations and controllers in your DeltaV system require configuration data from the DeltaV database in order
to operate. Initially, the DeltaV database stores all of the configuration data. You make changes to the configuration in
the database without affecting the operation of the controllers and workstations. When the configuration is complete,
you download that information to the workstations and controllers.
The data that you download allows the DeltaV system to manage your control strategy. For example, workstations
need to know all of the other nodes in the system as well as which areas to monitor and where to record events.
Likewise, controllers must have their assigned modules downloaded so that the modules can run in the controller.
You must also download the I/O card data so that the controller knows the type and enabled status of the channels and
the Device Tag associated with each channel.
You can download any data from within the DeltaV Explorer application. It is possible to download the entire
configuration (entire database) or small parts of the configuration by making the appropriate selections within
Explorer. For example, the Explorer lets you download a single controller, setup data, I/O card, or module by
selecting the icon for that item and choosing Download on the context menu (the menu that appears when you click
the right mouse button). In addition, you can download individual modules from within Control Studio.
A download temporarily disrupts the part of the operation of the controller or workstation that is being downloaded.
Care must be taken to determine if the process can withstand this temporary disruption. To ensure the safety of the
process, it might be necessary to delay the download of the configuration changes until the process can be shut down.
To minimize the effects of such disruption, it is recommended that only those parts of the configuration that have
changed be downloaded. This is particularly important in the case of controllers.
Download Physical Network
To download the entire configuration, perform the following steps:
1
Select the Physical Network icon and then right-click Download | Physical Network.
The workstation downloads all of the configuration data for all of the nodes in the system.
Note Downloading using the Object | Download | Physical Network command also downloads the configuration data.
Download Control Network
Downloading the control network is the same as downloading the physical network. To download the control
network, click the Control Network icon and then right-click Download | Control Network. The workstation
downloads all of the configuration data for all of the nodes in the system.
Note Downloading using the Object | Download | Control Network also downloads the configuration data.
Full (Total) Download (Workstation or Controller)
To download the entire configuration of a workstation or controller, select the item you want to download, right-click,
and then click the Download option from the menu. This downloads the entire configuration for the node selected
(workstation or controller) and is called a full (total) download.
332
System Configuration
Use a full download when the node has not yet been downloaded or has no configuration. Total controller downloads
should be avoided when the process is running. If there is already configuration present in the controller, a total
download will generally cause parameter values in the controller to be replaced with those from the configuration
database. There are some exceptions where matching behavior occurs, such as in controller function blocks directly
connected to output channels and for fieldbus shadow blocks. Depending on your configuration you could experience
an output disruption on a total controller download.
Refer to Preserving Configuration and Controller Data During Power Loss for more information on Restore
parameter values after restart feature.
Partial Download
If only part of the configuration has changed since the last full (total) download, a partial download may be the best
download option. A partial download minimizes disruption to control strategies that are currently running. A partial
download occurs when you select one or more modules and initiate a download.
When you initiate a partial download, the system sends the module changes to the appropriate controller. However,
the new modules will not execute until the running module completes its execution scan. When the scan of the current
module is complete, the controller copies the parameter value/function blocks combinations, as defined in the
following table. For MODE parameters the system copies the target mode field to the new module. The block
calculates the actual mode field when it begins to execute. Output and control blocks generally start in OOS mode on
the first execution after a download (partial and total, and on the first execution after a controller switchover), then
climb to their target mode. This provides proper re-initialization and handshaking with other blocks. The mode
change is expected and has no adverse effect on control.
On a partial download loops initialize to the current setpoint value regardless of whether setpoint ramping is on.
If the partial download fails because of a controller switchover, the controller that becomes the standby due to the
switchover will have a status of No configuration.
The partial download function matches function block parameters (in the old and new versions) by function block
name and type. User-defined parameters are matched by name and type. The partial download copy function supports
module-level, user-defined parameters for both modules and composites.
You can determine partial download behavior on a module-by-module basis using the Parameter download behavior
field on the General tab of the Module Properties dialog. Select one of the following options:
Preserve critical block values The controller copies critical function block values from the executing
module to the new module during a download. This selection typically minimizes disruption to the process.
Critical function block parameters are defined in the table below.
Preserve user-defined and critical block values The controller copies user-defined parameter values from
the completed scan of the current module to the new version of the module during a download. When the
new module executes its first scan, it uses the copied values in order to minimize process disruption. As
shown in the table, only a single field is copied for some of the function block parameters. This is the case
because the other fields (for example, Actual Mode or Target) are recalculated on block execution. For userdefined parameters, the entire parameter is always copied.
Use configured values The controller does not copy any parameter values from the executing module but
uses the values from the configuration database.
The data type of the user-defined parameter is changed. For example, the INPUT1 parameter is changed
from type float to type integer.
Downloading Data
333
User-defined parameters that are not at the top-level of modules or composites (for example, user-defined
parameters that are associated with SFCs or phases inside PLM, SFC, and unit modules).
Analog Input
Pulse Input
OUT, MODE.TARGET
Analog Output
LAST_IN
Bias/Gain
Ratio
MODE.TARGET, OUT
Calculation/Logic
OUT[x]
Condition
DISABLE
Counter
Device Control
Discrete Input
OUT_D, MODE.TARGET
Discrete Output
Integrator
Inspect
334
System Configuration
Function Block
Input Selector
Lab Entry
Neural Network
Splitter
On-Delay Timer
OFF-Delay Timer
Retentive Timer
ELAPSED_TIMER
Reset/Set Flip-flop
Set/Reset Flip-flop
OUT_D
Signal Characterizer
Timed Pulse
Refer to the topics When to Download and What to Download for more details.
Setup Data Download
You also download a subset of configuration data that is not directly related to a module. This data is called setup
data. Setup data includes named sets, parameter security, cold restart information, redundancy information, alarm
preferences, and event chronicle definitions. A download of the setup data sends these changes to all the workstations
and controllers.
You can download setup data alone or with the configuration data. To download setup data alone, select the object in
DeltaV Explorer (for example, a controller) in the left pane. Then, click Object | Download | Setup Data. To download
setup data along with all other configuration data, click Object | Download | Selected Object.
Delete Unused Card Configuration
When you delete an I/O card using DeltaV Explorer, you must download this change to the controller. The Delete
Unused Card Configuration command downloads the deleted card information to the controller configuration without
disrupting control or requiring a download of the I/O subsystem. To use this command, select the I/O Subsystem for
the controller in DeltaV Explorer and then right-click Download | Delete Unused Card Configuration.
Resending Successful Downloads
The Resend Last Known Good Download function sends the last successful total download to a node without going
to the database. If you have performed a total download followed by one or more partial downloads, this function
resends all of the information contained in the total download as well as the partials. For controllers, the function
sends the same download script that would be sent to a controller that restarts after a power failure.
This function is especially useful for situations where a workstation fails due to a disk error. It enables you to bring
the new or repaired node up to the previous operational status without downloading recent edits to the configuration.
Do not use the Resend Last Known Good Download function after decommissioning a controller. Perform a full
download after recommissioning a controller.
Downloading Data
335
Yes -- Click this button to select the parameter changes to upload before downloading.
Cancel -- Click this button to avoid uploading any parameter changes and proceed to the Download
Confirmation dialog.
For more information on uploading parameters, refer to the Uploading Recorded Parameter Changes topic.
Note It is possible for a DeltaV user to make online changes between the time a user requests the download and the
time the system transfers the data. Online changes made within this window of time are not displayed as uploadable
parameter changes. For this reason, it is important for users performing downloads to coordinate the downloads with
those who have permission to make online parameter changes.
If you decide to continue downloading, the system downloads the data to the appropriate nodes and stores a copy of
the data on the ProfessionalPLUS workstation in the Powerup directory (DeltaV\DVData\Powerup). If the download
is a total download involving controllers, the system also stores a compressed version of the relevant portions of the
download in the controllers' nonvolatile memory. This enables the controller to perform a cold restart and download
itself if power fails and is restored. Refer to the topic entitled Preserving Configuration and Controller Data During
Power Loss for more information on how cold restart works.
The download progress log is saved to DeltaV\DVData by default for workstations in the control network. It is saved
to DeltaV\DVData\RemoteSystems\identifier for remote operator stations.
Caution A download can potentially bump the I/O. To prevent accidentally bumping the I/O, place the block
producing the outputs in manual mode before you download. Care must be taken to determine if the process can
withstand this temporary disruption. To ensure the safety of the process, it might even be necessary to delay the
download of the configuration changes until the process can be shut down.
Alarm parameter fields all get initialized to their default (or configured) value as is appropriate, the first execution
cycle of the module establishes the initial alarm state for it's alarms. In practice, this means that inactive,
336
System Configuration
unacknowledged alarms appearing in the alarm list prior to a download will not be in the list after the download
because they are initialized to acknowledged by the download.
Downloading large modules to a controller can use a large amount of system resources. Exact amounts vary
depending on the module being currently run by the controller and the size of the module being downloaded. To
ensure that you do not have a problem with system resources, place the running block in manual mode before you
download.
Large databases require significant amounts of free disk space in order to download successfully. Make sure that there
is a least half the size of the database in free disk space before downloading the database.
When to Download
The DeltaV Explorer marks the physical objects that require a download with the
However, if you are making changes to the setup data, you see the
symbol (blue triangle) next to the
ProfessionalPLUS workstation (at the node level only). The setup data are global data. The changes you make to the
setup data affect all of the controllers and workstations. You must download ProfessionalPLUS setup data (or
changed setup data) in order for the setup data to be distributed to all workstations and controllers.
Caution A download can potentially bump the I/O. To prevent this from occurring, place the block producing the
outputs in Manual mode before you download. Care must be taken to determine if the process can withstand this
temporary disruption. To ensure the safety of the process, you might even need to delay the download of the
configuration changes until the process can be shut down.
Refer to the following table for a complete list of changes that require you to download.
Note A full download of each controller node must be performed before any partial download is allowed.
The following table lists changes you can make in the Explorer that would require a download.
Database Changes and Their Corresponding Downloads
When you make this change
in the database:
Download the module to the controller node. This updates the local
module table in the ProfessionalPLUS station.
Downloading Data
337
Modify a card.
Download the I/O Card. For serial cards, also download control
modules that reference the card.
Modify a channel.
Edit a module.
Commission a controller.
338
System Configuration
Download the setup data to all nodes. Also, stopping and restarting of
services such as the Batch Executive may be required.
Note There are other times when you must download that are not signaled by a change in the database. You only need
to perform a full download for the affected node. A power outage requires that the node without power be
downloaded again after power returns. Refer to the Preserving Configuration and Controller Data During Power Loss
topic for more information. Also, replacing a controller requires a download for the replaced controller. Refer to the
Auto-Sense Feature topic for more information.
What to Download
Controller and I/O
To minimize process disruption, download I/O components at the lowest level that downloads the desired changes.
For example, if you add or modify a card, download only the card rather than downloading the whole I/O subsystem
or the whole controller. By referencing the hierarchy in DeltaV Explorer, you can determine the lowest level object to
download. Expand the hierarchy (click the + next to an object) and download the lowest level object with a
to it.
next
To preserve outputs during a download, a module-level download that includes AO, DO, Loop, and Device Control is
partial.
Caution A download can potentially bump the I/O. To prevent this, place the block producing the outputs in manual
mode before you download. Care must be taken to determine if the process can withstand this temporary disruption.
To ensure the safety of the process, it might be necessary to delay the download of the configuration changes until the
process can be shut down.
Downloading loaded Phases or an SFC that has undergone a structural change can cause the controller memory to
fragment. In this situation FREMEM remains constant but the largest contiguous portion of memory decreases.
Typically, controller performance is not significantly affected unless several downloads of this type are performed. To
prevent any impact on controller performance, do not download to loaded phases.
Workstation
When downloading a node, the other workstations on the network must wait until the download is complete. The
DeltaV system attaches application locks and does not permit any other workstation to modify the data.
Downloading Data
339
If you are uploading multiple modules, the dialog appears as shown. If you are uploading a single module, the dialog
title includes the module name and the Node Name and Modules columns do not appear. The most recent value set
for each parameter (and field) and the user who made the change appears in the list. If two or more changes were
made to the same parameter and field within two seconds, the Same Time column includes a question mark (?).
The present controller configuration, operating parameters and I/O is not necessarily included in the upload process.
Any parameter changes made by the control algorithms in the controller, as is done in SFC processing, are not
included in the upload. You select which parameter values you want to write to the database modules. The Upload
command is available in the DeltaV Explorer and in Control Studio.
Note Upload before download does not capture the present configuration and operating parameters in the controller.
Only manual operator changes from the workstations are recorded. Any settings automatically performed by the
controller are not included in the upload. Use with caution, major process interruption could result from using this
feature if the specific implementation of the users configuration is not taken into account.
When an upload operation is interrupted before it completes, the values that it uploads before the interruption are
retained by the database.
340
System Configuration
Caution Select only the parameter changes that represent desired configuration changes to the module in the
database. Normally, changes to operating parameters (setpoints or operating state parameters that are initialized or
written by the module and many phase logic module parameters as well) would not be selected for upload.
Caution When you request an upload, make sure you select all of the values you want. Parameter changes that are
not selected are discarded, and not uploaded to the database. The download replaces the online values with the values
in the database and discards any recorded parameter changes for the downloaded module.
Note For remote workstations, downloading (total download) the RDS (Remote Data Server) Application Station
sends the configuration, setup data, displays, and charts to all the Remote Workstations (1st and 2nd hop) under that
RDS.
341
Referencing Documents
The integration feature enables you to launch a document from any description field in DeltaV Explorer, Control
Studio, or Recipe Studio. For example, you can enter a field such as C:\Procedures\MainShutdown.htm to point to a
specific HTML file that your organization has created.
To open the document, right-click the address in the Description field and then click Launch. When you click Launch,
the appropriate application opens and loads the file. For html and Microsoft Word documents, if the application is
already open, the control loads the document in the open application. If the document is a text document, the control
opens a new instance of Notepad for each referenced file.
Other examples of valid entries are:
C:\Spreadsheets\reactor1.xls
C:\ModuleDescriptions\FIC101.doc
This feature is only supported on the ProfessionalPLUS station. All referenced documents must be on the
ProfessionalPLUS station as well. The browser used must be the version of Internet Explorer that is included with the
Windows operating system.
342
System Configuration
System Preferences
Inside this topic
Defining System Preferences
Advanced Unit Management Preference
Batch Preference
Fieldbus Preference
Profibus Preference
AS-Interface Preference
DeviceNet Preference
RS3 I/O Preference
PROVOX I/O Preference
Asset Optimization Alarms Preference
Remote I/O
Electronic Signatures
DeltaV SIS
DeltaV System Preferences improve the ease of use of the system by allowing you to tailor the Engineering Tools to
hide any functions that you might not require. Enabling or disabling a function causes the DeltaV applications to
reveal or conceal the applicable menus and choices without adding or removing any application software. Any
configuration that exists for a disabled function becomes inaccessible, but the data is retained in the database.
Enabling/Disabling functionality is independent of licensing.
Defining System Preferences
To enable a function using DeltaV System Preferences, perform the following steps:
1
Select the check box that corresponds with the function that you want to enable.
Click OK.
A popup appears that says for changes to take effect you must restart the DeltaV Database Server.
Open the DeltaV Database Administrator (Click Start | DeltaV | Engineering | Database Administrator).
Select Force shutdown even if clients are connected as shown, then Click OK.
If any applications that have a connection to the database are open, popups appear for each application
saying its database connection will be lost and asking if you want to exit the application.
System Preferences
343
For each popup that appears, click Yes to exit the application and continue shutting down the database server or
click No to keep the application connected.
If you click Yes for all popups, the message in the Database Administrator status line changes to Database
Server is shutdown.
If you click No, the database does not shut down.
You can now restart any applications that closed when you shut down the database server.
Advanced Unit Management Preference
This preference enables or disables the following features of the Advanced Unit Management function:
DeltaV Explorer
Aliases in Control Strategies Unit modules, unit phases, and phase logic modules in process cell creation.
Control Studio
Display of unit classes and phase classes when adding a new module
Operator/Application Station
Batch Preference
This preference enables or disables the following features of the Batch function:
Start menu options
Batch, Recipe Studio, Batch History View, and Batch Operator Interface
DeltaV Explorer
344
Activation of the Recipe Studio and Batch Operator Interface toolbar buttons and menu options
Applications | Recipe Studio and Applications | Batch Operator Interface menu options
System Configuration
Control Studio
DeltaV Operate Activation of the Batch History View, Batch Operator Interface, and Recipe Studio toolbar
buttons
Applications | Batch Operator Interface, Applications | Batch History View, and Applications | Recipe Studio
menu options
Fieldbus Preference
This preference enables or disables the following features of the Fieldbus function:
Control Studio
Profibus Preference
This preference enables or disables the following features of the Profibus function:
DeltaV Explorer
AS-Interface Preference
This preference enables or disables the AS-Interface function as follows:
DeltaV Explorer
DeviceNet Preference
This preference enables or disables the DeviceNet function as follows:
DeltaV Explorer
System Preferences
345
Control Studio
Diagnostics
Interface to PROVOX I/O card files, cards channels and related parameters
Control Studio
Diagnostics
Wizard for synchronizing configuration between the DeltaV system and the asset server
Diagnostics
Remote I/O
This preference enables or disables the following features of Remote I/O:
DeltaV Explorer
346
Interface for adding Remote I/O Nodes under Remote I/O Network.
System Configuration
Diagnostics
Interface to diagnostic parameters for Remote I/O subsystem, Remote I/O Nodes, and cards.
Electronic Signatures
This preference enables or disables the following features of Electronic Signatures:
DeltaV Explorer
Dialogs that allow operators to enter an electronic signature before writing to parameters and fields listed in
signature policies.
DeltaV SIS
This preference enables or disables the following features of DeltaV SIS:
DeltaV Explorer
SIS Module and Module Template choices added to the New dialog.
SIS function block palettes are available when creating SIS modules.
Secure Write mechanism added for making changes from Control Studio online and DeltaV Operate
Diagnostics
System Preferences
347
DeltaV Explorer
In DeltaV Explorer, you can see the hierarchy of objects in your database. Objects include controllers and I/O cards,
workstations, areas, modules, equipment, and many other items.
The Explorer program is modeled after Windows Explorer. The user interface, navigation, and shortcut features in
DeltaV Explorer are similar (if not identical) to Windows Explorer.
The DeltaV Explorer gives you a visual representation of the system hardware and configuration that you can
navigate and modify. You can quickly populate your database with the DeltaV Explorer. The DeltaV Explorer
includes a graphical representation of the library modules that you can use as templates for you own modules. Drag
and drop library modules into areas and then modify these modules in Control Studio. You can also quickly navigate
through your database to learn about its contents.
The DeltaV Explorer allows you to define system characteristics and view the overall structure and layout of the
system. You use a tree-like structure to add, delete, or modify your system. You can perform the following functions
graphically:
import/export
348
System Configuration
349
Definition
Incomplete information - indicates that the downloading node (the workstation) does not have all
the information on the node with this indicator. To clear this indicator, click the node with the
indicator, click the right mouse button, and then click Download Setup Data. This transfers setup
data from the database to the physical node. It also updates the downloading workstation node so
that the workstation has all the information it needs to manage the new node. This indicator can
appear on controllers and workstations that are physically connected to the network or on
controller or workstation placeholders. Note that you cannot download the system data for a
placeholder; the physical node must be connected first.
Integrity - indicates that the node is communicating but has an integrity problem. Controllers can
have this indicator for several reasons.
For example:
There is a mismatch between the I/O configuration and the physical I/O. Compare the controller's
I/O configuration in the Explorer with the actual I/O cards connected to the controller.
The controller is configured for network redundancy but does not have the necessary connections
to support it. Check to see if the node is configured to support network redundancy. If it is, make
sure the controller has a network connection.
Workstations can have this indicator for several reasons.
For example:
The workstation is configured for network redundancy but does not have the necessary
connections. Check to see if the workstation is configured to support network redundancy. If it is,
make sure the workstation has a network connection.
The workstation cannot communicate with at least one controller that it needs to communicate
with.
The event chronicle database has detected an error (such as an invalid directory).
SIL integrity - indicates that the integrity of one or more of the Logic Solvers on the controller's
subsystem is Bad. This indicator has a higher priority than the integrity indicator, but not as high as
the Not communicating indicator.
No configuration - indicates that the node does not have a configuration. This can occur if the
node has never been downloaded. For controllers, this can occur if there is a power failure and cold
restart was not enabled for the node.
Not communicating - indicates that the node is not communicating. This indicator occurs when
there is a bad connection, if the controller is not powered up, or if the controller is
decommissioned. To clear this indicator, go to the node and make sure it is connected, that the
wiring is correct and sound, and that the node is powered up.
The Explorer enables you to launch the Diagnostics application and view diagnostics data for any selected Explorer
object. This can provide useful diagnostic information for nodes that have the
indicator. To investigate integrity
problems for a node, click its icon, click the right mouse button, and then click Diagnose.
350
System Configuration
"Needs
Downloading"
Value
Definition
Yes
Indicates that some of the parameters in the database for this node no
longer match the parameters in the node itself. If you perform a
download, some changes will be made to the node. If this indicator
is not present, no download is required.
Unknown
Indicates that some of the parameters in the database for this node
might not match the parameters in the node itself. Select the node,
click the right mouse button, and then click Download | Update
Download Status to determine if a download is required.
Module Indicators
Indicator
Definition
Library module. You can drag library modules into an area, modify
them, and use them in your configuration strategy.
Module in an area. A module in an area is the database copy of the
module. Area modules can be edited and assigned by reference to a
specific controller.
Module assigned to a controller. The control associated with this
module is placed in the controller when the controller is downloaded.
Module assigned to a controller and downloaded
Downloaded module for which the assignment has been removed
Result
Provides a context menu. This menu changes based on what the selected item is.
Selects the item, whether an icon, a menu option, or a button. When selecting the menu or
button, the function represented by the menu or button is executed.
Double-click
Using the left mouse button, selects the item and executes the function represented by the
item.
351
Action
Result
Enter key
Accepts and executes the selected item. This item can be a button, a menu option, or an
object.
Tab key
Alt + Tab
Toggles between running applications, for example, switching between DeltaV Explorer
and Control Studio.
Alt + underlined
character
Selects the function for that item. This is available in menus, buttons and dialogs,
providing there is a character that is underlined.
Note In some cases, you can press only the underlined character. This is only true when
the menu, button or dialog currently has focus.
Alt + double-click
Using the left mouse button, displays Properties for that item.
F1
F10
Shift + F10
F3
Ctrl + X
Ctrl + C
Ctrl + V
Alt + Enter
F5
F6
Switches panes.
Backspace
Keypad *
Keypad +
Keypad -
Right arrow
Left arrow
352
System Configuration
The following terms are universal in Windows applications. The DeltaV documentation uses these terms.
Special Terms for Navigation
Term
Definition
Collapse
To close the list and hide all the items that make up the list.
Click the next to the item to collapse the list.
Context Menu
Cut + Paste
Drag + Drop
Drill Down
Expand
To open a list and view all the items that make up the list.
Click the next to the top item to expand the list.
Tailor Functionality
You can tailor the Engineering Tools to provide only the required functionality. Run the System Preferences
utility from the Start menu on the ProfessionalPLUS workstation. The choices in the menus and toolbars will
be simplified accordingly.
Split View
You can split DeltaV Explorer into two windowpanes using the View | Split menu option. You can use this
split view to keep the Physical Network onscreen in the lower pane at all times while using the upper pane to
navigate around your configuration. You can even drag and drop between panes.
Module Diagnostics
In DeltaV Diagnostics, if you select the Assigned Modules subsystem of a node, a snapshot of the current
353
status of all modules is displayed in tabular form. You can then select the column headers (for example,
UnResRef, Forced, OOS) to sort the table based on those columns.
354
Unresolved References
In DeltaV Diagnostics, if you expand the Assigned Modules subsystem of a node, all modules and a visual
indicator of integrity problems for each module are displayed. If you right-click a module, a list of
unresolved references within that module is displayed.
Edit Expressions
You can view and edit expressions from DeltaV Explorer by double-clicking the T_Expression parameter.
Operator Diagnostics
Diagnostic information can be shown on operator displays. To determine the parameter path, select the
object in Diagnostics and use the Detail view.
Refresh
When engineering from more than one workstation, make sure that you refresh the view of DeltaV Explorer
periodically. You can do this by pressing the [F5] key.
Download Status
If you are unsure of the download status being displayed by DeltaV Explorer, select the node, right-click,
choose download, and then select UpdateDownload Status. This will verify the correct download status of
the node.
Work in Progress
You can use the Work in Progress flag during configuration to mark a module as being unfinished. This will
have no effect on the operation of the module.
System Configuration
Download a module.
355
The Control Studio window is divided into different sections called views. The following figure shows Control
Studio and the different views.
356
System Configuration
From the Hierarchy View, you view the components of the module and of its composite function blocks.
From the Parameter View, you define specific characteristics of objects on the diagram, such as function
blocks, steps, or modules. You can view the parameters alphabetically or by parameter category.
From the Diagram View, you create function blocks and sequential function chart algorithms graphically on
a diagram that defines how the module behaves.
From the Alarm View, you view the enabled alarms for the block or module. You configure the alarm limits,
priorities, and more from the Alarm View.
From the Palette View, you access the icons that represent function blocks, modules, and SFCs. The Palette
View is discussed in the following topic, The Palette.
The Palette
The Palette in the Control Studio contains all the blocks available in the DeltaV System. These blocks are the
foundation of the modules you use in creating your DeltaV system's control strategy.
357
358
System Configuration
Navigation Tips
Action
Result
Provides a context menu. This menu changes based on what the selected item is.
Selects the item, whether an icon, a menu option, or a button. When selecting the
menu or button, the function represented by the menu or button is executed.
Double-click
Using the left mouse button, selects the item and executes the function
represented by the item.
Enter key
Accepts and executes the selected item. This item can be a button, a menu option,
or an object.
Tab key
Alt + Tab
Alt +
underlined
character
Selects the function for that item. This is available in menus, buttons and dialogs,
providing there is a character that is underlined.
Note In some cases, you can press only the underlined character. This is only true
when the menu, button or dialog currently has focus.
Note The right mouse button is used extensively in Control Studio. You can access all the block, alarm, and
parameter properties by clicking the right mouse button.
The following terms are universal in Windows applications. The DeltaV documentation uses these terms.
Special Terms for Navigation
Term
Definition
Collapse
To close the list and hide all the items that make up the list. Click the
item to collapse the list.
Context Menu
A menu that changes based on what item is selected when the menu is called. The
menu is dependent on the context from which it is accessed.
The context menu is by clicking the right mouse button.
Cut + Paste
To remove (cut) an item from one spot and placing (pasting) it in a new spot.
Drag + Drop
To select an item with a single-click of the left mouse button and, while holding the
mouse button down, move the item on the window. This results in a copy of the
selected item being created.
Drill Down
To double-click an item and expose the layers underneath. You can then drill down
into one of the layers by double-clicking that layer. You can drill down any item that
has layers until you reach the lowest layer.
Expand
To open a list and view all the items that make up the list. Click the
item to expand the list.
next to the
359
setting a breakpoint and have the algorithm execute until it reaches the breakpoint (in debug mode only)
Note The modules that you are viewing in either online or debug view must be downloaded in the controller, and
some of the changes you make can affect the process.
360
System Configuration
Caution Editing online or debugging a function block diagram can affect the process that you are currently running.
361
A Forced IN Input
You cannot force the output of a block to a particular value; you can only force the input to a particular value.
Remember to remove the forced input when you want the algorithm to execute normally.
Running to a Breakpoint
Sometimes it is not practical to advance step-by-step from the beginning of a diagram until you reach the place where
you think the problem is. The solution to this is the breakpoint. Using a breakpoint, you can tell the algorithm where
to stop. The algorithm runs until it reaches a breakpoint, and then it stops.
When you set a breakpoint, a red circle indicates where the breakpoint is set. The following figure shows a function
block with a breakpoint set.
stopping, starting, and resetting embedded and linked composite levels of the algorithm
setting or forcing inputs to desired values. Control Studio only writes out those values that have been
changed.
Caution If you edit an SFC online, you can affect the process that is currently running.
362
System Configuration
Double-click a transition to drill down into it and Control Studio's online view displays a graphical representation of
the expression in a new dialog as follows:
All components of a transition that have correctly evaluated are marked with a green check mark.
Any parameters of the expression that have an error are marked with a question mark (?).
Any element of the transition that has not correctly evaluated is marked with a red X.
An expression that has not entirely been evaluated is marked with a red X while some of the underlying
components (those that have evaluated correctly) display a green check mark.
The expression contains a discrete parameter with a value of 0 is shown with a green checkmark in the
lowest level of the tree next to the parameter name. A red X is displayed when the discrete parameter has
any nonzero value.
The debug view for SFCs allows you to disable transitions, steps, and actions, as well as force transitions. When
actions or steps are disabled, they are displayed as inactive in the diagram even though the active parameter still gives
an indication of active; this way, you can see which actions would be taking place without actually executing the
actions.
Note SFC algorithms do not fully support the online edit of embedded composites containing function blocks. If you
drill into and set a breakpoint in an embedded composite, the breakpoint will not be reached, and execution will not
stop at that breakpoint.
Disabling Steps
By disabling a step, you can stop the execution of an action in the step or prevent the action from executing (if the
step has not become active yet). A disabled step is shown with a red X through the step. This indicates that the step
does not cause actions to be evaluated. The following figure shows a disabled step.
363
364
System Configuration
Note You can disable all of the actions for a step by disabling the step. However, the individual action disables are
not overwritten. That is, when actions 1 and 3 are disabled and the user disables the step, all actions are disabled, but
enabling the step does not cause actions 1 and 3 to become enabled.
Forcing Transitions
The option to force a transition allows you the flexibility to directly influence the flow through a running SFC. Note
that forcing a transition only affects active transitions. If a transition is active and then becomes disabled or its
condition evaluates to False, forcing the transition causes processing to continue through the transition as if it were
enabled and True for the next scan. This is a momentary request. A forced transition is only temporary; the transition
returns to normal operation after the processing is complete.
As a debugging sequence select tool, forcing a transition allows you to force execution of a particular branch of a
sequence select divergence. To do this, disable all of the transitions in the divergence and then force the transition for
the desired path.
Stopping, Starting, and Resetting Levels
You can manipulate portions of the SFC by starting, stopping, or resetting individual levels of an SFC algorithm. For
example, consider an SFC that uses a linked composite containing an SFC for draining the contents from a vessel. If
there is an equipment failure that requires you to drain the vessel manually, you could drill down into the composite
and click Stop Sequence to stop the SFC from trying to drain the vessel. The title for the SFC is displayed as
Sequenced Stopped. If you want to restart the draining, click Start Sequence.
Stopping and Starting Module Execution
You can completely stop all execution in a module by stopping the module. While the module is stopped, the title of
the module is displayed as Stopped, and all action and transition processing for each level of the module stops.
Unlike disabling steps and actions, stopping a module does affect timing values for actions. For example, if a Delay
action is delaying for 30 seconds and you stop the module 15 seconds into the delay, the action will delay another 15
seconds once the module is started again.
Setting Values
You can directly affect values in the SFC while it is processing. For example, if the SFC has a parameter for showing
the setpoint, you can set a value for that parameter and change the setpoint.
Forcing an Input
You can override an input wire and provide the signal value you want for an input by forcing the input. This function
only works on composites that contain SFCs and are referenced from a function block diagram. The inputs to the SFC
that are connected to wires from the function block diagram can be forced to new values.
Using Modules
A module is a reusable control algorithm that focuses around process equipment. Modules link algorithms,
conditions, alarms, displays, and other characteristics together for a particular piece of equipment. The DeltaV system
has a library of modules with all the necessary characteristics already defined. You modify the modules to fit your
needs as you develop your control strategies. For more information on modules, refer to the Modules topic.
365
Composites
The DeltaV system allows you to group control strategies within modules into multiple layers of a diagram. These
layers or groups are called composites. Although many control languages can be contained in a composite, they are
represented on the diagram as a single element.
For example, if you opened a single composite on a function block diagram, you might find that it contains one or
more additional function blocks and composites, or even a sequential function chart. Parameters can be wired to the
composite so that data can pass in and out of it. Composites can be nested to a depth of six levels within the control
module's diagram.
The following figure provides a graphical example of a single-level composite that is in a function block diagram.
The composite in this example contains three function blocks.
improve readability of a large control strategy by allowing you to group the elements into logical control
tasks
allow the various control languages (Function Block Diagrams and Sequential Function Charts) to be
intermixed within the same control module
provide a mechanism to develop control logic segments one time, store them in the library, maintain them in
a single location, and still use that logic in a number of different control modules
The following figure provides a graphical example of how composites appear within a control strategy diagram.
366
System Configuration
367
368
Segment the control logic into logical groupings. This allows improved organization and readability of the
control strategy.
Arrange control strategies hierarchically. Composites can be placed inside other composites.
Intermix various control languages (function block diagrams and sequential function charts) within a single
control module.
System Configuration
You can reference this logic from modules. Modifying the library automatically updates all modules
that reference the composite template in the library. This type of composite is known as a linked
composite.
Use the custom block assistant to put a copy of that logic in a module. This type of usage is known as an
embedded composite. Subsequent changes you make to the composite template do not affect any blocks
previously created from the template.
Connect multiple function blocks or a sequential function chart to form a composite. Composites you create in the
library can be reused repeatedly on diagrams or charts when you want to perform the same function more than once.
The following figure is a representation of a composite function block definition that is used for signal conditioning.
369
You can convert embedded composites to linked and linked composites to embedded by selecting the composite
block and clicking the right mouse button and clicking Convert. For a description of linked and embedded
composites, refer to the Linked and Embedded Composites topic.
Linked and Embedded Composites
When deciding to link or embed a composite, you should know how you want the data to be updated. Composites,
especially linked composites, contain some subtle functional differences that are important to consider when
developing and maintaining control strategies. Among the distinguishing characteristics of composites is the type of
data it contains, which can either be structural information or parameter information.
Structural information for a composite containing a function block diagram includes all the function blocks
contained in the diagram, how they are wired together, and where they are placed on the diagram. For composites
containing SFCs, the structural information includes what steps and transitions are contained on the diagram, how the
steps and transitions are connected together, and where the steps and transitions are placed on the diagram.
Parameter information for a composite containing a function block diagram includes all the parameter names,
parameter data values (including expressions), status information, and filter settings. For composites containing
SFCs, the parameter information includes step actions, step transition conditions, and module parameters.
The following figure shows the relationship of structural and parameter information for both embedded and linked
composites. For a more in-depth discussion on the characteristics of embedded composites and linked composites,
refer to the following two sections.
Relationship of Structural and Parameter Information for Embedded and Linked Composites
Embedded Composites
When you use an embedded composite, both the structural and the parameter data are stored as part of the module
(refer to the previous figure). When you edit the module in the offline view, both types of information can be
modified. Double-click an embedded composite (or click the right mouse button and then click Edit Object) to open
the composite for modification.
Like in any control diagram within the DeltaV system, you can edit the parameter information when in the online
view. If you created the embedded composite from a library composite, an exact copy of the library composite is
370
System Configuration
made and placed within the control module. From that point forward, all links back to the original library composite
are broken.
If your purpose is to create a composite that you can modify without affecting the original block or any other
composite blocks that are linked to the original, embed the composite. An embedded composite is a separate,
standalone object; modifying it does not change the source block, and modifying the source block does not change
the new composite.
Linked Composites
Linked composites also provide some useful features, but a greater understanding of how linked composites work is
essential for you to fully take advantage of these features. With linked composites, you develop and maintain the
control logic once, and that structural information can be used in several different control modules. The structural
information is always maintained in the library, while the parameter information is stored within the control module
itself.
By storing the parameter information in the control module, you can adjust the values of the composite for each
control module that references it. When a library composite is placed on a diagram as a linked composite, all the
parameter information associated with that library composite is copied, with default values, to the control module. To
modify these values for a specific control module, double-click the composite when the composite is selected from
within the control module's diagram. You can then adjust the default values to the values you want to use. The control
module stores all the parameter values that were changed from the library default values.
If, at a later time, you modify the default value in the library for a parameter, any control module that has not had that
parameter modified also receives the updated parameter value. For example, if you modify the default value for
parameter ABC, any module for which that default value has not been set receives the new value as the default.
Modules in which parameter ABC was modified are unaffected by the parameter change in the library.
Note Changes to default parameter values in Linked Composite templates take effect in modules referencing
templates only after a partial download of these modules.
You can also change a default parameter value in a single instance of the composite template by disconnecting (delinking) the parameter from the template. Open the instance of the composite and select the parameter. Right click
and select Properties. Deselect the Use Default Value from Composite Template option. The composite is still linked
to the template, but this parameter's default value can now be changed for this instance of the module.
The structural information of a linked composite is stored in the library. Changing any structural information on the
library composite automatically modifies all control modules that reference the library composite. There are three
ways to edit the structural information of a library composite:
From within the DeltaV Explorer, select the composite in the library, click the right mouse button, and then
click Edit. This launches a Control Studio window.
From within Control Studio, click File | Open and click Objects of Type: Composite Templates. Then select
the desired library composite by name and click OK.
While editing a control module from within Control Studio, select a linked composite, click the right mouse
button, and then click Edit Object. This launches a second Control Studio window with the composite
loaded and ready for editing.
If you want to be able to change the original composite block definition and have that change propagate to all of the
other composites you create from the block, use a linked composite. This way, you can fix or edit a composite in one
place and all of the other linked blocks are changed automatically. When you link a composite block, it gets updated
if you modify the original block or the composite template it was created from. Linked data is stored in the source
block; the block you create from the original stores the location of the source block and displays a representation of
the original block.
371
Note If you have the linked composite open in a copy of Control Studio, go to that copy of Control Studio and press
F5. This refreshes the window and your changes are displayed.
In a function block diagram, you can create an embedded composite by dragging the Custom Block
Special Items palette and clicking Embedded Composite, as shown in the following figure.
from the
372
System Configuration
the composite's control strategy. The number of outputs determines the number of values that can be wired from the
composite back to blocks in the containing FBD. In the composite, these wired output values are output parameters.
All input and output parameters are visible parameters on the composite block in the containing function block
diagram.
In an SFC, you can insert an embedded composite by clicking the right mouse button on the right side of the
Hierarchy View and then clicking Add. A dialog appears, and you click Embedded Composite, as shown in the
following figure.
In a function block diagram, you can create a linked composite by dragging the Custom Block
Special Items palette and clicking Linked Composite, as shown in the following figure:
from the
373
Creating a Custom Linked Composite Block Assistant: Selecting Linked Object Type
Once you select the type of object you want to link to, click Next. Then, you can browse for any existing objects or
define new objects. Once you have identified what the composite is linked to, click Finish.
In an SFC, you can insert a linked composite by clicking the right mouse button on the right side of the Hierarchy
View and then clicking Add. The steps are then like the previous procedure for adding a linked composite to an FBD:
Click Linked Composite and identify what the composite is linked to.
The inputs and outputs are not wired in an SFC diagram. The linked composite appears in the Hierarchy View, but not
on the SFC diagram. You run the algorithm in the composite using a non-boolean action in a step, and you can
reference the parameters in the composite.
374
System Configuration
Converting Composites
Composites can be converted from linked to embedded and vice-versa. There are many reasons that you might want
to convert them from one type to another:
Perhaps you need to make a structural change in a composite that is linked, but you do not want to affect
other composites that are also linked to the same library composite.
Perhaps you created an embedded composite that could be used multiple places in your application. You
would like to be able to use it in multiple algorithms and maintain it in one place.
Perhaps you want to replace a composite's links to a particular library composite with links to a different
library composite.
You can convert composites to different types and establish different links using the Convert command in Control
Studio. The conversion options in Control Studio are as follows:
Convert to Embedded
Convert to Existing
Convert to New
To accomplish a conversion, select the composite in a diagram, click the right mouse button, and then click Convert.
Click To Embedded if you want to change a linked composite to embedded or To New if you want to change an
embedded composite to a new linked composite. Click To Existing to convert an embedded or linked composite to a
linked library composite that exists in the library.
Note If you convert an embedded composite to a linked composite, the embedded composite will no longer exist in
the database.
During any of these conversions, wires to parameters of the same name are maintained. However, the values defined
for those parameters with the same name are inherited from the new block. Parameters that no longer exist after
conversion lose their wired links and the default values.
Convert to Embedded
Use the Convert to Embedded command in Control Studio to change a linked composite to an embedded composite.
The new embedded composite keeps the same structural and parameter information, but the links to the library
composite are broken. This allows you to make changes to the new embedded composite without affecting your other
composites.
Convert to Existing
Use the Convert to Existing command in Control Studio to remove the selected composite and copy an existing
composite in its place. If parameters are named the same in both composites and the parameters have been changed
from the default value, the values of the existing composite's parameters are used.
In other words, if you have modified the default value for a parameter with the same name as a parameter in the new
composite, the value will remain. Any parameter that has not been modified will receive the updated parameter value.
For example, if you have modified the default value for parameter ABC, the value for ABC in the new composite will
remain the same. Any parameter for which the default value has not been set will receive the new value from the
composite as the default. Parameter ABC will be unaffected by parameter changes in the library.
Note If you convert an embedded composite to a linked composite, then the embedded composite will no longer
exist in the database.
375
Convert to New
Use the Convert to New command in Control Studio to put a new composite in the library. If you convert a linked
composite to a new composite, you essentially rename the composite and put a copy of the renamed composite in the
library. The links are then made to the new composite in the library.
If you convert an embedded composite to a new library composite, you put a copy of the composite in the library.
Then links are established to the new composite in the library.
Expressions in the DeltaV System
User-defined expressions in the DeltaV system are used in function blocks to execute calculations, to perform
conditional checks, and to perform system-wide reads and writes. The steps and actions in SFCs also use expressions.
These expressions are based on the IEC 61131-3 Structured Text language. For more information on expression
syntax, refer to the Expressions topic.
Command Languages
You can create algorithms for your modules in the DeltaV system using one of the following command languages:
Function Block Diagrams (FBDs) - typically used for analog control, monitoring, motor control, and
discrete valve control
Structured Text (ST) - used within DeltaV software to create expressions in the condition, action, and calc/
logic function blocks as well as in actions and transitions in SFCs.
376
Extensible Parameters
Certain function blocks allow the number of input/output parameters to be increased or decreased. You can
increase or decrease this number by right-clicking a function block and then selecting Extensible
Parameters.
System Configuration
Show Parameter
Function block parameters that are not visible on the block can be displayed. To select such a parameter for
display, right-click the associated function block and then select Show Parameter.
Phase Requests
It is very important that your phase waits for the Phase Request to be completed, as signified by the
REQUEST register returning to 0, before issuing another request. Always follow any step that writes a value
to REQUEST with a transition expression that waits for 'REQUEST' = 0.
Unfinished Configuration
A Work in Progress flag is available to mark your module as unfinished. This flag has no effect on the
operation of the module. The download procedure will inquire whether modules with this flag set should be
downloaded.
Alarm Priorities
You can write to the PRI parameter of an alarm to adjust the priority of the alarm in run time.
Feedback Wires
Wires that carry feedback signals in function block diagrams are displayed as dashed lines. Feedback wires
are determined when a module is saved or when the function block execution order is set.
377
378
System Configuration
Verify Recipe
After creating a recipe, make sure that you verify it. Verifying a recipe checks each level of the recipe and
determines whether each step is connected and correctly configured.
Recipe Studio
The MAX_RESERVED parameter must be set to zero to allow ten phases to run in parallel in a recipe.
Phase Restart
The type of restart for a phase cannot be modified at configuration time. It can be modified dynamically
from within the phase by writing to the RESTART_TYPE parameter.
Phase Execution
A phase can be made to execute across a transition without stopping the phase. This is useful when another
379
phase has to be started in parallel part of the way through the first phase. Refer to the Using the
DOWNLOAD_REQ Parameter topic in Books Online for more information.
380
Phase Simulation
If a phase has Simulate enabled, the Batch Executive will communicate with the Recipe Simulator instead of
the phase in the controller. Additional configuration (using the REQUEST command) within the Recipe
Simulator is required to fully mimic phase logic interaction with the Batch Executive.
Releasing a Formula
If you forgot to release your formula to production in Recipe Studio, you can do so in DeltaV Explorer by
right-clicking the formula.
Recipe Parameters
Parameters can be created by drilling into any level of a recipe that is open in Recipe Studio. However, a
recipe parameter can only be deleted if the operation, unit procedure, or procedure it belongs to is opened in
Recipe Studio.
Recipe Layout
The layout of a recipe in the PFC view of the BOI follows the layout in Recipe Studio. Configuring recipes
so that they always start in the top left corner of the diagram with the vertical size and spacing of the icons
reduced allows for a better online display.
Unit Aliases
When using a unit alias in any step of a procedure, then all steps (within that procedure) that have classbased equipment assignments should use unit aliases also.
System Configuration
The I/O Configuration application lets you view I/O data in three ways. These views are available under the View
menu.
Control Strategies - Show a hierarchy that includes areas, assigned modules, and I/O reference parameters. For each
parameter, this view displays the parameter type and its associated Device Tag.
From the control strategies view, you can select parameters and edit their properties by clicking the right mouse
button.
381
382
System Configuration
383
Filter By Menu
384
System Configuration
on the toolbar.
385
386
System Configuration
Viewing Alarms
Filtering Alarms
Use the Filter Settings dialog to limit the amount of information shown in the alarms list. You can filter on process
and device alarms by area, unit, and module, and by Logic Solver hardware and device alarms. This dialog is
accessed through the View | Filters command.
Filter Dialog
387
Description
Alarm name
The name of the alarm as it appears on operator displays that reference it. For
example, HI_HI_ALM.
Type
Parameter
The name of the module that contains the alarm and the parameter value that
triggers the alarm.
Limit value
Enable
Inverted
Priority
%P1 Parameter
Represents the first parameter value that appears in the alarm message. (This
parameter is optional.)
% P2 Parameter
Represents the second parameter value that appears in the alarm message. (This
parameter is optional.)
Enable Delay
Shows the time (in seconds) that is delayed before alarm processing begins.
Processing begins immediately after the alarm is enabled (alarm_ENAB
becomes true). The alarm_ACT parameter is forced to 0 for the time specified
(in seconds). The timer resets whenever alarm_ENAB goes from zero to 1.
On Delay
The time (in seconds) that is delayed before alarm_ACT is set to true (1) after
the alarm condition is detected. If the alarm condition clears before the delay
time is reached, the alarm_ACT parameter remains false (0) and the timer is
reset. Every time the alarm condition clears, the timer resets.
Off Delay
The time (in seconds) that is delayed before alarm_ACT is set to 0 (false) after
the alarm condition clears. If the alarm condition reoccurs before the delay time
is reached, the alarm_ACT parameter remains true (1) and the timer is reset.
Every time the alarm condition is detected, the timer resets.
Hysteresis
Used as a deadband when resetting base alarm conditions for analog values. The
block uses the value of alarm_HYS instead of the standard ALARM_HYS.
When conditional alarm detection is enabled, the block uses ALARM_HYS as
the deadband for deviation alarm conditions only.
388
System Configuration
389
version history
download history
alarm priorities
Change the value of a parameter (for example, OUT) in the AI function block template in the library.
From DeltaV Explorer, import the FHX file containing the module AI_TEST.
A dialog appears asking if you want to update the existing AI object in the database (that is, the AI function block
template in the library) with the AI block that is in the file you are importing.
If you click Yes, the AI block function block template in the library is replaced with the AI block from the import
file.
If you click No, the AI function block template in the library will not be replaced.
390
System Configuration
The module AI_TEST retains its AI block parameter values (as defined in the FHX) in either import case.
The standard import and export functions are available using the following DeltaV Explorer commands:
To export, you can also select an object in the DeltaV Explorer hierarchy, right-click, and then click Export from the
context menu.
The DeltaV Explorer also support drag and drop exports and imports. You can drag an item from DeltaV Explorer
onto an application (for example, Windows Explorer, MS Excel, MS Outlook, Notepad, Desktop, MS Word). This
causes the item to be exported and then opened by or attached to the application, depending on how the application
behaves. Dragging an FHX file to the highest level of the tree in DeltaV Explorer causes the file to be imported.
When importing a configuration, a message may appear stating that the database already contains an object with the
same name. This message asks if you want to update the existing object with the import file's object. Replying No to
All typically allows the existing database items to be used (not the ones from the import file). However, there are
certain objects that are always imported (or force updated) from the .fhx file. The force update list includes the
following objects:
ALARM TYPE
ALARM ANNUNCIATION
LOCK
GROUP
USER
DEFAULT LOCK
FIELD SECURITY
PARAMETER SECURITY
FUNCTION SECURITY
NAMED SETS
If VCAT is enabled, this can result in import log errors where the system was not able to overwrite library items that
were not checked out. To recover, run sync-database after importing.
Note When importing a database, any duplicate equipment IDs are renumbered. The equipment being imported is
what gets renumbered. If two or more users are working concurrently on the same database, segment the equipment
into specific IDs (for example, all tanks get 0-99, all agitators get 101-199, and so on). Then, when you combine the
databases through an import, all of the equipment will retain the correct IDs, and your logic will reference the correct
IDs.
391
Editing configuration data exported with User-Defined formats in a text file with an editor that supports
Unicode (Notepad, for example)
Editing configuration data exported with User-Defined formats in a text file with the DeltaV Excel Bulk Edit
Template (limit of 255 parameters and 255 characters per cell)
Editing configuration data exported with User-Defined formats in an ODBC data source with Microsoft
Access
Note It is recommended that you create a backup copy of the configuration database before bulk importing data.
Select, create, or modify a format specification file (.fmt) to define the data to be exported and imported. Use the
Format Specification wizard (from DeltaV Explorer select File | Format Specification) to create or modify a
format specification file.
If you are exporting and importing modules, create a module template from the object you want to bulk edit. For
more information, refer to the Bulk Edit Example - Custom Module topic.
The tasks required to create and edit class-based modules and class-based modules containing class-based modules
are more involved. Refer to Bulk Edit Example - Class-based Modules and Bulk Edit Example - Class-based
Modules Containing Class-based Modules.
392
System Configuration
Note You can specify one object type for each import or export operation. For example, if you build a spreadsheet of
channel data, the associated cards and controllers must already exist in the configuration database for the channel data
to import correctly. The imported file can contain the card and controller names as well as the channel data, but these
items are only used during the import to map the channel data correctly in the configuration database.
You can also export and import using ODBC data. Refer to the Export and Import Using ODBC topic for more
information.
Editing Exported Data
You can edit data exported in User-Defined formats in the following ways:
In a text file with an editor that supports Unicode (Notepad, for example)
Format Specification
Before you can export data to bulk edit, you must have a format specification file to define the data for the object to
export or import. The format specification file defines the format for data exported from and imported to the DeltaV
database. Sample format specification files and some corresponding export files are included in the DeltaV
installation. They are in the directory DeltaV/DVData/BulkEdit. You can use these as is or use the Format
Specification wizard to create new .fmt files and then export data to create your own .txt files.
Note Format specification files that you have created on a previous release of DeltaV software should be reviewed to
incorporate new data fields that may have been added in the current release.
The following table lists the sample format files and output data files included with the DeltaV system. The sample
files may not apply to specific objects you are exporting and importing. Create your own format specification files to
ensure they apply to your needs.
Sample Format Specification and Data Files
Object Type
Aliases
Aliases.fmt
---
AS-Interface Device
ASI_Dev.fmt
---
AS-Interface
Discrete I/O
ASI_Disc_IO.fmt
---
393
Object Type
AS-Interface Port
ASI_Port.fmt
---
Card
Card.fmt
RIO1Card.fmt
RIO2Card.fmt
cards.txt
RIO1Card.txt
RIO2Card.txt
Channel
Channel.fmt,
AIChannel.fmt,
AOChannel.fmt,
DOChannel.fmt
Remote IO Channels.fmt
Channels.txt,
AIChannel.txt,
AOChannel.txt,
DOChannel.txt
Remote IO Channels.txt
DeviceNet Device
DevNet_Device.fmt
---
DeviceNet Port
DevNet_Port.fmt
---
DeviceNet Signal
DevNet_Signal.fmt
---
Fieldbus Device
FF_Device.fmt,
FF_Device with Device Alarms.fmt
ff_devices.txt
Fieldbus Port
FF_Port.fmt
---
Formula
Formula.fmt
---
History Collection
HistoryDataPoint.fmt
HistoryDataPoint.txt
Logic Solver
Logic Solver.fmt
---
Logic Solver
Channels
---
Module
AnalogMonitor_Module.fmt,
DiscreteMonitor_Module.fmt,
Loop_Module.fmt,
Motor_Valve_Module.fmt,
mod_integ.fmt
analog_monitors.txt,
discrete_monitors.txt,
loops.txt,
motors_valves.txt
Process Cell
ProcessCell.fmt
---
Profibus Device
Prof_Dev.fmt
---
Profibus Port
Prof_Port.fmt
---
Profibus Signal
Prof_Sig.fmt
---
Profibus Slot
Prof_Slot.fmt
---
Programmable
Serial Dataset
Prog_Serial_Dataset.fmt
---
Programmable
Serial Port
Prog_Serial_Port.fmt
---
Serial Dataset
Serial_Dataset.fmt
---
Serial Port
Serial_Port.fmt
---
394
System Configuration
Object Type
SIS Module
SISMod.fmt
SISMod.txt
Unit Module
UnitMod.fmt
---
The format specification file defines the object to export and import, including the order of the data fields. The
specification also defines the comment character, separator character, and the use of blank lines and columns. When
you export data the output .txt files follow the field order specified in the .fmt files.
To create or modify a format specification file, follow these steps:
1
From DeltaV Explorer, select File | Format Specification. Then, select New or Edit.
If you selected Edit, select a format file to edit from the Open Format Specification dialog, then click Open.
The Format specification - General dialog opens.
Select or verify the filename of the format specification file you are editing. Then, set the other options on the
dialog as desired.
Click Next.
The Format specification - Select fields dialog opens.
Channel object - Subtypes are channel types: 100 mv input, discrete input, discrete output, and so on.
Module object - Subtypes are either module templates or modules based on module templates.
Module objects require that you enter a subtype so that information on the blocks within the module are
exported and imported. If you do not correctly specify the module subtype, importing creates empty
modules.
For other object types specify a subtype if you need to export information specific to the subtype.
The fields that appear in the Field names area depend on the object type and subtype selected.
Note that for each of the object types, there are required fields (that is, fields the import file must contain to
be successfully imported). For information on required fields, refer to the Object Syntax topic.
5
Click Next.
The Format specification - Field order dialog appears.
If you are creating the format specification to import an existing data file, order the fields and insert skip columns
as required. Use skip columns as placeholders if your import file contains data that you do not want or need to
import. The number and order of fields in the format file must match the import data file exactly. If they do not
match, importing the data results in errors.
Click Next.
The Format specification - Which fields must already exist in the database dialog appears. Depending on the
395
object for which you are creating a specification file, there may be one or more fields listed in this dialog.
Select a field to allow imports only when data in the selected fields already exist in the configuration database.
For example, if you select the ctrlr (controller) field in this dialog, controllers listed in the ctrlr field in the
import file must already exist in the configuration database to import data.
9
Click Finish.
The software saves the format file.
Refer to DeltaV\bin\BitstringTranslations.txt
BitstringTranslations.txt
DeltaV\bin\BitstringTranslations.txt contains a list of parameter options and the corresponding descriptive strings for
the options. For example, the line for CONTROL_OPTS.OPTION5 looks like:
CONTROL_OPTS.OPTION5 CONTROL_OPTS.ActOnIR
If you encounter generic option names in your export files you can refer to the file to find the parameter and the
option to see the descriptive term for the option.
Note The DeltaV software uses BitstringTranslations.txt during configuration and operation. Do not modify
BitstringTranslations.txt in any way. Doing so may cause unpredictable results.
396
System Configuration
Field -- The field name as it appears in the format specification wizard and exported data files
Valid Values -- The syntax of valid field values or a list of valid values
Required for Import -- Indicates whether a field must exist in the import file and contain a value for the data
to be successfully imported
Note You can include fields that are not required for import in your format and text import files. However, for some
objects some fields are interdependent. That is, if a field exists in the format and text import files, other related fields
must also be included and must contain valid values in the import file or the import fails.
Click the following links to see a list of fields that each object contains and information about each field:
Aliases
AS-Interface devices
AS-Interface ports
DeviceNet devices
DeviceNet ports
DeviceNet signals
Fieldbus devices
Fieldbus ports
Formulas
Logic Solvers
Process cells
Profibus devices
Profibus ports
Profibus signals
Profibus slots
397
Serial ports
Serial datasets
SIS Modules
Unit modules
Valid Values
Required for
Import
description
No
unit_mod_class
Yes
area
Yes
unit_mod_name
Yes
alias_name
Yes
alias_path
No
ignore
No
T or F
398
System Configuration
Valid Values
Required for
Import
description
As many as
255 characters
using any
keyboard
characters.
No
ctrlr
Any valid
controller
name. The
controller
must exist in
the database
for the import
to be
successful.
Yes
card_slot
1 through 8
Yes
asi_port_slot
Yes
asi_dev_tag
As many as 16
characters.
The string
must contain
one
alphabetical
character and
can include
the following:
$, -, _
Yes
asi_dev_addr
1 to 31
Yes
asi_dev_type
Sample 2In x
2Out module
Sample
proximity
sensor
Any other
user-defined
type
Yes
asi_dev_enable
True or False
No
asi_dev_param0_enable
True or False
No
asi_dev_param1_enable
True or False
No
399
Field
Valid Values
Required for
Import
asi_dev_param2_enable
True or False
No
asi_dev_param3_enable
True or False
No
Valid Values
Required for
Import
description
No
ctrlr
Yes
card_slot
1 through 8
Yes
asi_port_slot
Yes
asi_dev_addr
1 to 31
Yes
asi_dev_tag
Yes
asi_dev_type
No
No
asi_disc_io_name
Yes
Note that for an import or export of an AS-Interface device to succeed, the AS-Interface port must already exist.
400
System Configuration
Valid Values
Required for
Import
description
No
ctrlr
Yes
card_slot
1 through 8
Yes
asi_port_slot
Yes
enable
True or False
No
ctrlr_fail_action
Reset devices.
Continue polling.
No
auto_addr_enable
True or False
No
Note that for an import or export of an AS-Interface port to succeed, the controller must already exist.
Valid Values
Required for
Import
description
No
ctrlr
Yes
card_slot
1 through 64
Yes
card_type
Yes
redundant
T = redundant
F = not redundant
No
parameter
Card-level parameters
No
401
The sample format specification files for channel objects do not support HART channel types. To export and import
HART channel types you must create your own format specification files using object type Channel and specify the
appropriate subtype.
Field
Valid Values
Required for
Import
description
No
ctrlr
Yes
card_slot
1 through 64 controllers
1 through 4 for Remote I/O Zone 1
1 through 8 for Remote I/O Zone 2
Yes
channel_slot
Yes
channel_type
Yes
device_signal_tag
No
enable
T = enabled
F = disabled
No
No
hart_device_manufacture
No
hart_device_type
No
hart_device_rev
No
enable_alarms
T = enabled
F = disabled
No
primary_display
No
faceplate_display
Faceplate display
No
Parameter List
Channel-level parameters
No
Alarms
Channel alarms
No
402
System Configuration
Valid Values
Required for
Import
description
No
ctrlr
Controller name. Up to 16
characters long
Yes
card_slot
Yes
dev_net_port_slot
Yes
dev_net_dev_enable_io_polling
Polling T or F
No
dev_net_dev_tag
As many as 16 characters.
Must contain one alphabetical
character and any of the
following: $, -, _
Yes
dev_net_dev_addr
Yes
dev_net_dev_manu
Yes
dev_net_dev_model
Yes
dev_net_dev_rev
Yes
dev_net_dev_input_size
No
dev_net_dev_output_size
No
Valid Values
Required for
Import
description
No
ctrlr
Yes
403
Field
Valid Values
Required for
Import
card_slot
Yes
dev_net_port_slot
Yes
enable
T or F
No
baud_rate
No
fail_action
No
Valid Values
Required for
Import
description
No
ctrlr
Yes
card_slot
Yes
dev_net_dev_tag
Yes
dev_net_dev_manu
Yes
dev_net_dev_model
Yes
dev_net_dev_rev
Yes
dev_net_dev_addr
Yes
dev_net_sig_name
Yes
dev_net_sig_tag
No
dev_net_sig_dir
Yes
dev_net_sig_byte_offset
No
404
System Configuration
Field
Valid Values
Required for
Import
dev_net_sig_data_type
Yes
dev_net_sig_use_scaling
T or F
No
dev_net_sig_low_scale_val
No
dev_net_sig_high_scale_val
No
dev_net_sig_start_bit
No
dev_net_sig_num_used_bits
No
Valid Values
Required for
Import
description
No
ctrlr
Yes
card_slot
1 through 8
Yes
card_type
Yes
redundant
T = redundant
F = not redundant
Yes
fb_port_slot
1 through 2
Yes
fieldbus_device_tag
Yes
fieldbus_device_address
20 through 35
Yes
fieldbus_device_manufacture
Yes
fieldbus_device_type
Yes
405
Field
Valid Values
Required for
Import
fieldbus_device_rev
Yes
fieldbus_id
No
fieldbus_device_bklk_master
T or F
No
enable_alarms
T or F
No
primary_display
No
faceplate_display
No
The following fields appear only for Fieldbus devices with device alarms.
ABNORM_ALM.ENABLE
T or F
No
ABNORM_ALM.PRIORITY
No
ADVISE_ALM.ENABLE
T or F
No
ADVISE_ALM.PRIORITY
No
COMM_ALM.ENABLE
T or F
No
COMM_ALM.PRIORITY
No
FAILED_ALM.ENABLE
T or F
No
FAILED_ALM.PRIORITY
No
MAINT_ALM.ENABLE
T or F
No
MAINT_ALM.PRIORITY
No
* The pick lists in the Excel template show the system-defined alarm priorities only. If
these priorities have been renamed or if new priorities have been added then the pick lists
are not updated. You can enter these priorities manually.
Valid Values
Required for
Import
description
No
ctrlr
Yes
card_slot
1 through 8
Yes
406
System Configuration
Field
Valid Values
Required for
Import
card_type
Yes
redundant
T = redundant
F = not redundant
Yes
fb_port_slot
1 through 2
Yes
enable
T = enabled
F = disabled
No
fb_port_sch_macrocycle
Valid value
No
fb_port_min_sch_spacing
No
parameters
No
Valid Values
Required for
Import
description
No
recipe_name
Yes
formula_name
Yes
version
No
release_to_production
T = Released
F = Not released
No
Note that for an import or export of a formula to succeed, batch parameters must already exist.
407
The following table summarizes the values that can appear for hdp_type and use_default based on settings in the Add
or Modify History Collection dialog in the class and in the instance.
HDP defined
in module...
Allow
instance
history data
point to be
configured
(in class)
Use default
value from
module
class (in
instance)
Type field in
History
Collection
dialog
hdp_type in
Bulk Edit
Template
use_default
in Bulk Edit
Template
Class
Checked
Checked
Configurable
Configurable
Class
Checked
Not Checked
Override
Override
Class
Not Checked
NA
Definition
Definition
<NULL>
Instance
NA
NA
Instance
Instance
<NULL>
From the Bulk Edit Excel template, do not modify the hdp_type values. In the use_default field you can change the T
to F for Configurable HDPs and modify other field values. After you import, the hdp_type field for theses HDPs
become Override. You can also edit the Override and Instance HDPs. You cannot edit the field values for HDPs of
hdp_type Definition.
Valid Values
Required for
Import
value_recorded
Yes
enable
No
display_representation
No
No
No
compression_enabled
T = enabled
F = disabled
No
deviation
No
408
System Configuration
Field
Valid Values
Required for
Import
at_least
No
hdp_type
Definition*
Configurable**
Override**
Instance**
No
use_default
No
Valid Values
Required for
Import
description
No
logic_solver
16 characters
Yes
ctrlr
No
card_slot
No
ls_scan_rate
0.05 = 50ms
0.1=100ms
0.15=150ms
0.2=200ms
No
publish_globally
T or F
No
primary_display
No
detail_display
No
faceplate_display
No
test_interval
days
No
409
Field
Valid Values
Required for
Import
remind_days
days
No
ADVISE_ALM.PRIORITY
No
ADVISE_ALM.SUPPRESS_TIMEOUT
No
COMM_ALM.PRIORITY
No
COMM_ALM.SUPPRESS_TIMEOUT
No
FAILED_ALM.PRIORITY
No
FAILED_ALM.SUPPRESS_TIMEOUT
No
MAINT_ALM.PRIORITY
No
MAINT_ALM.SUPPRESS_TIMEOUT
No
* Note The pick lists in the Excel template show only the system-defined alarm priorities. If these
are renamed or if new ones are added then the pick lists will not update but you can enter these
priorities manually.
Valid Values
Required for
Import
description
No
logic_solver
Yes
channel_slot
1 through 16
Yes
ls_channel_type
Yes
device_signal_tag
No
enable
T or F
No
Parameter list
No
410
System Configuration
Field
Valid Values
Required for
Import
description
No
ctrlr
No
area
No**
module_name
16 characters
Yes
work_in_progress
T or F
No
restore_param_vals
T or F
No
param_download_behavior
No
module_type
No
module_subtype
Yes***
scan_rate
0.1 = 100 ms
0.2 = 200 ms
0.5 = 500 ms
1 = 1 second
2 = 2 seconds
5 = 5 seconds
10 = 10 seconds
30 = 30 seconds
60 = 60 seconds
No
primary_display
No
detail_display
No
faceplate_display
No
Parameter List
Depends on subtype
No
411
Field
Valid Values
Required for
Import
Alarms
Depends on subtype
No
Valid Values
Required for
Import
description
No
area
Yes
proc_cell_class
Yes
proc_cell_name
Yes
equip_id
No
max_owners
No
mmi_pic
No
Valid Values
Required for
Import
description
No
ctrlr
Yes
card_slot
1 through 8
Yes
412
System Configuration
Field
Valid Values
Required for
Import
profibus_port_slot
Yes
enable
T = enabled
F = disabled
No
profibus_dev_tag
Yes
profibus_dev_addr
Yes
profibus_dev_family
Yes
profibus_dev_manufacturer
Yes
profibus_dev_model
Yes
profibus_dev_revision
Yes
profibus_dev_watchdog_enable
T = enabled
F = disabled
No
profibus_dev_watchdog_time
No
Note that for an import or export of a Profibus device to succeed, the Profibus card and Profibus port must already
exist.
Valid Values
Required for
Import
description
No
ctrlr
Yes
card_slot
1 through 8
Yes
profibus_port_slot
Yes
enable
T = enabled
F = disabled
No
station_address
No
413
Field
Valid Values
Required for
Import
baud_rate
No
repeater
No
fms_device
No
No
No
min_io_cycle
max_io_cycle
token_rotation_time
slot_time
idle_time1
No
No
No
idle_time2
No
ready_time
No
quiet_time
No
gap_update_factor
No
msg_retry_limit
No
token_retry_limit
No
fail_action
No
Valid Values
Required for
Import
description
No
ctrlr
Yes
card_slot
1 through 8
Yes
profibus_dev_tag
Yes
profibus_dev_manufacturer
Yes
414
System Configuration
Field
Valid Values
Required for
Import
profibus_dev_model
Yes
profibus_dev_revision
Yes
profibus_dev_addr
Yes
profibus_slot_module_num
Yes
profibus_slot_definition
Yes
profibus_sig_name
Yes
profibus_sig_tag
No
profibus_sig_use_diag_chan
No
profibus_sig_diag_channel
No
profibus_sig_stand_net_byte_order
T = Big Endian
F = Little Endian
No
profibus_sig_dir
input or output
Yes
profibus_sig_byte_offset
No
profibus_sig_data_type
Yes
profibus_sig_use_scaling
T or F
No
profibus_sig_low_scale_value
No
profibus_sig_high_scale_value
No
profibus_sig_start_bit
No
profibus_sig_num_bits
No
Note that for an import or export of a Profibus signal to succeed, the Profibus device must already exist.
Valid Values
Required for
Import
description
No
ctrlr
Yes
415
Field
Valid Values
Required for
Import
card_slot
1 through 8
Yes
profibus_port_slot
Yes
profibus_dev_tag
Yes
display_name
Yes
profibus_slot_definition
Yes
profibus_slot_module_num
Yes
Note that for an import or export of a Profibus slot to succeed, the Profibus device must already exist.
Valid Values
Required for
Import
description
No
ctrlr
Yes
card_slot
1 through 8
Yes
card_type
RED_PROG_SERIAL_32DS
(Prog. Serial Card, 2 Ports, RS232/RS485,
Redundant)
PROG_SERIAL_32DS
(Prog Serial Card, 2 Ports, RS232/RS485)
PROG_SERIAL_32DS_SER2
(Prog Serial Card, 2 Ports, RS232/RS485, Series 2)
Yes
redundant
T = redundant
F = not redundant
Yes
device_signal_tag
No
serial_port_slot
1 or 2
Yes
serial_port_pio_name
PIO_CFG_NAME_PORT_PROG_SERIAL_RED
PIO_CFG_NAME_PORT_PROG_SERIAL
Yes
416
System Configuration
Field
Valid Values
Required for
Import
serial_device_index
1 through 16
Yes
serial_device_address
1 through 16
No
dataset_number
1 through 16
Yes
dataset_data_direction
input or output
No
dataset_datatype
No
dataset_num_values
No
dataset_output_mode
No
dataset_output_readback
No
device_data_type
No
data_start_addr
0 to 65535
No
special_data1
0 to 65535
No
special_data2
0 to 65535
No
special_data3
0 to 65535
No
special_data4
0 to 65535
No
special_data5
0 to 65535
No
417
Valid Values
Required for
Import
description
No
ctrlr
Yes
card_slot
1 through 8
Yes
card_type
RED_PROG_SERIAL_32DS
(Prog. Serial Card, 2 Ports, RS232/RS485, Redundant)
PROG_SERIAL_32DS
(Prog Serial Card, 2 Ports, RS232/RS485)
PROG_SERIAL_32DS_SER2
(Prog Serial Card, 2 Ports, RS232/RS485, Series 2)
Yes
redundant
T = redundant
F = not redundant
Yes
serial_port_slot
1 or 2
Yes
serial_port_pio_name
PIO_CFG_NAME_PORT_PROG_SERIAL_RED
PIO_CFG_NAME_PORT_PROG_SERIAL
Yes
serial_master_slave
master or slave
No
serial_retry_count
1 through 255
No
serial_message_timeout
No
serial_transmit_delay
0 through 25500
No
serial_send_outputs
No
serial_port_type
RS232
RS422/RS485 half duplex
RS422/RS485 full duplex
No
serial_baud_rate
No
serial_parity
even
odd
none
No
serial_data_bits
7 or 8
No
serial_stop_bits
1 or 2
No
enable
T = Enable port.
F = Disable port.
No
418
System Configuration
Valid Values
Required for
Import
description
No
rio_node_name
Yes
rio_card_slot
1 through 4
Yes
rioz1_card_type
ZONE_1_AI_AO
ZONE_1_DI_DO
Yes
rio_assigned_to
No
rio_scan_rate
No
Valid Values
Required for
Import
description
No
rio_node_name
Yes
rio_card_slot
1 through 8
Yes
419
Field
Valid Values
Required for
Import
rioz2_card_type
AI_16CH_HART_4-20
TI_4CH_ISOLATED
AI_8CH_1-5V
AI_8CH_4-20
AI_8CH_HART_4-20
AI_8CH_HART_4-20_SER2
MV_8CH
RTD_8CH
TC_8CH
AO_8CH_4-20
AO_8CH_HART_4-20
AO_8CH_HART_4-20_SER2
DI_32CH_HD
DI_8CH_115VAC_DCT
DI_8CH_115VAC_ISO
DI_8CH_240VAC_DCT
DI_8CH_240VAC_ISO
DI_8CH_24VDC_DCT
DI_8CH_24VDC_DCT_SER2
DI_8CH_24VDC_ISO
DO_32CH_HD
DO_8CH_115_240VAC_HSS
DO_8CH_115_240VAC_ISO
DO_8CH_24VDC_HSS
DO_8CH_24VDC_HSS_SER2
DO_8CH_24VDC_ISO
Yes
rio_assigned_to
No
rio_scan_rate
No
Valid Values
Required for
Import
description
No
ctrlr
Yes
card_slot
1 through 8
Yes
420
System Configuration
Field
Valid Values
Required for
Import
card_type
SERIAL_32DS
(Serial Card, 2 Ports, RS232/RS485)
SERIAL_32DS_SER2
(Serial Card, 2 Ports, RS232/RS485, Series 2)
RED_SERIAL_32DS
(Serial Card, 2 Ports, RS232/RS485, Redundant)
Yes
redundant
T = redundant
F = not redundant
Yes
device_signal_tag
No
serial_port_slot
1 or 2
Yes
serial_port_pio_name
PIO_CFG_NAME_PORT_SERIAL
PIO_CFG_NAME_PORT_SERIAL_RED
Yes
serial_device_index
1 through 16
Yes
serial_device_address
1 through 16
No
dataset_number
1 through 16
Yes
dataset_data_direction
input or output
No
dataset_datatype
No
dataset_num_values
No
dataset_output_mode
No
dataset_output_readback
No
421
Field
Valid Values
Required for
Import
dataset_plc_datatype
coils
input status
input registers
holding registers
diagnostics data
No
dataset_plc_reg_addr_offset
0 through 65535
No
* Refer to the Serial Device Configuration topic for details on each field.
Valid Values
Required for
Import
description
No
ctrlr
Yes
card_slot
1 through 8
Yes
card_type
SERIAL_32DS
(Serial Card, 2 Ports, RS232/RS485)
SERIAL_32DS_SER2
(Serial Card, 2 Ports, RS232/RS485, Series 2)
RED_SERIAL_32DS
(Serial Card, 2 Ports, RS232/RS485, Redundant)
Yes
redundant
T = redundant
F = not redundant
Yes
serial_port_slot
1 or 2
Yes
serial_port_pio_name
PIO_CFG_NAME_PORT_SERIAL
PIO_CFG_NAME_PORT_SERIAL_RED
Yes
serial_protocol_type
RTU or ASCII
No
serial_master_slave
master or slave
No
serial_retry_count
1 through 255
No
serial_message_timeout
No
serial_transmit_delay
0 through 25500
No
serial_send_outputs
No
422
System Configuration
Field
Valid Values
Required for
Import
serial_port_type
RS232
RS422/RS485 half duplex
RS422/RS485 full duplex
No
serial_baud_rate
No
serial_parity
even
odd
none
No
serial_data_bits
7 or 8
No
serial_stop_bits
1 or 2
No
enable
T = Enable port.
F = Disable port.
No
Field
Valid Values
Required for
Import
description
No
logic_solver
16 characters
No
area
No
module_name
16 characters
Yes
work_in_progress
T or F
No
module_type
No
module_subtype
Yes
primary_display
No
423
Field
Valid Values
Required for
Import
detail_display
No
faceplate_display
No
risk_red_factor
No
Parameter List
Depends on subtype
No
Alarms
Depends on subtype
No
Valid Values
Required for
Import
description
No
area
Yes
unit_mod_class
Yes
unit_mod_name
Yes
work_in_prog
No
T or F
scan_rate
No
primary_display
No
detail_display
No
faceplate_display
No
equip_id
No
424
System Configuration
Field
Valid Values
Required for
Import
max_owners
No
Parameter List
Depends on subtype
No
Alias
unit_mod_class
area
unit_mod_name
alias_name
AS-Interface Devices
ctrlr
card_slot
asi_port_slot
asi_dev_tag
asi_dev_addr
asi_dev_type
ctrlr
card_slot
asi_port_slot
asi_dev_tag
asi_dev_addr
asi_disc_io_name
AS-Interface Ports
ctrlr
card_slot
asi_port_slot
Card
ctrlr
card_slot
card_type
Channel
ctrlr
card_slot
channel_slot
channel_type
425
Object Type
DeviceNet Devices
ctrlr
card_slot
dev_net_port_slot
dev_net_dev_tag
dev_net_dev_addr
dev_net_dev_manu
dev_net_dev_model
dev_net_dev_rev
DeviceNet Ports
ctrlr
card_slot
dev_net_port_slot
DeviceNet Signals
ctrlr
card_slot
dev_net_dev_tag
dev_net_dev_manu
dev_net_dev_model
dev_net_dev_rev
dev_net_dev_addr
dev_net_sig_name
dev_net_sig_dir
dev_net_sig_data_type
Fieldbus Device
ctrlr
card_slot
card_type
redundant
fb_port_slot
fieldbus_device_tag
fieldbus_device_address
fieldbus_device_manufacture
fieldbus_device_type
fieldbus_device_rev
Fieldbus Port
ctrlr
card_slot
card_type
redundant
fb_port_slot
Formula
recipe_name
formula_name
History Collection
value_recorded
(If compression_enabled is True, deviation
and at_least are also required)
Logic Solver
logic_solver
426
System Configuration
Object Type
logic_solver
channel_slot
ls_channel_type
Module
module_name
module_subtype
Process Cell
area
proc_cell_name
Profibus Device
ctrlr
card_slot
profibus_port_slot
profibus_dev_tag
profibus_dev_addr
profibus_dev_family
profibus_dev_manufacturer
profibus_dev_model
profibus_dev_revision
Profibus Port
ctrlr
card_slot
profibus_port_slot
Profibus Signal
ctrlr
card_slot
profibus_dev_tag
profibus_dev_manufacturer
profibus_dev_model
profibus_dev_revision
profibus_dev_addr
profibus_slot_module_num
profibus_slot_definition
profibus_sig_name
profibus_sig_dir
profibus_sig_data_type
Profibus Slot
ctrlr
card_slot
profibus_port_slot
profibus_dev_tag
display_name
profibus_slot_definition
profibus_slot_module_num
427
Object Type
ctrlr
card_slot
card_type
redundant
serial_port_slot
serial_port_pio_name
serial_device_index
dataset_number
ctrlr
card_slot
card_type
redundant
serial_port_slot
serial_port_pio_name
rio_node_name
rio_card_slot
rioz1_card_type
ctrlr
card_slot
channel_slot
channel_type
rio_node_name
rio_card_slot
rioz2_card_type
ctrlr
card_slot
channel_slot
channel_type
Serial Dataset
ctrlr
card_slot
card_type
redundant
serial_port_slot
serial_port_pio_name
serial_device_index
dataset_number
Serial Port
ctrlr
card_slot
card_type
redundant
serial_port_slot
serial_port_pio_name
428
System Configuration
Object Type
SIS Module
module_name
module_subtype
Unit Module
area
unit_mod_class
unit_mod_name
Export Name
TI_4CH_ISOLATED
ISO_TC_CHAN
ISO_TC_B_CHAN
ISO_TC_E_CHAN
ISO_TC_J_CHAN
ISO_TC_K_CHAN
ISO_TC_N_CHAN
ISO_TC_R_CHAN
ISO_TC_S_CHAN
ISO_TC_T_CHAN
ISO_MV_25_CHAN
ISO_MV_55_CHAN
ISO_MV_100_CHAN
ISO_VOLT_0_5_CHAN
ISO_VOLT_0_10_CHAN
ISO_VOLT_1_5_CHAN
ISO_VOLT_1_CHAN
ISO_VOLT_5_CHAN
ISO_VOLT_10_CHAN
ISO_RTD_RES_CHAN
ISO_RTD_PT100_CHAN
ISO_RTD_PT200_CHAN
ISO_RTD_NI120_CHAN
ISO_RTD_USER_CHAN
ISO_RTD_CU10_CHAN
AI_8CH_1-5V
AI_CHAN
AI_8CH_4-20
AI_CHAN
AI_8CH_HART_4-20
AI_HART_CHAN
AI_CHAN
AI_8CH_HART_4-20_IS
AI_HART_CHAN
AI_CHAN
429
Display Name
Export Name
AI_8CH_HART_4-20_RED
AI_HART_CHAN_RED
AI_CHAN_RED
AI_8CH_HART_4-20_SER2
AI_HART_CHAN
AI_CHAN
AI_16CH_HART_4-20
AI_HD_HART_CHAN
AI_HD_CHAN
AO_8CH_4-20
AO_CHAN
AO_8CH_HART_4-20
AO_DISABLED_HART_CHAN
AO_ENABLED_HART_CHAN
AO_8CH_IS_HART
AO_DISABLED_HART_CHAN
AO_ENABLED_HART_CHAN
AO_8CH_HART_4-20_RED
AO_DISABLED_HART_CHAN_RED
AO_ENABLED_HART_CHAN_RED
AO_8CH_HART_4-20_SER2
AO_DISABLED_HART_CHAN
AO_ENABLED_HART_CHAN
AO_8CH_IS
AO_CHAN
ASI
ASI_PORT
DNIC
DNIC_PORT
DI_16CH_IS
DI_IS_CHAN
PCI_IS_CHAN
DI_16CH_SOE
DI_SOE_REG_CHAN
DI_SOE_EV_CHAN
DI_32CH_HD
DI_HD_CHAN
DI_8CH_115VAC_DCT
DI_CHAN
PCI_CHAN
DI_8CH_115VAC_ISO
DI_CHAN
PCI_CHAN
DI_8CH_240VAC_DCT
DI_CHAN
PCI_CHAN
DI_8CH_240VAC_ISO
DI_CHAN
PCI_CHAN
DI_8CH_24VDC_DCT
DI_CHAN
PCI_CHAN
DI_8CH_24VDC_DCT_SER2
DI_CHAN_SER2
PCI_CHAN_SER2
430
System Configuration
Display Name
Export Name
DI_8CH_24VDC_DCT_RED
DI_CHAN_RED
PCI_CHAN_RED
DI_8CH_24VDC_ISO
DI_CHAN
PCI_CHAN
DO_32CH_HD
DO_HD_CHAN
DO_4CH_IS
DO_CHAN
MPO_CHAN
CPO_CHAN
DO_8CH_115_240VAC_HSS
DO_CHAN
MPO_CHAN
CPO_CHAN
DO_8CH_115_240VAC_ISO
DO_CHAN
MPO_CHAN
CPO_CHAN
DO_8CH_24VDC_HSS
DO_CHAN
MPO_CHAN
CPO_CHAN
DO_8CH_24VDC_HSS_RED
DO_CHAN_RED
MPO_CHAN_RED
CPO_CHAN_RED
DO_8CH_24VDC_HSS_SER2
DO_CHAN_SER2
MPO_CHAN_SER2
CPO_CHAN_SER2
DO_8CH_24VDC_ISO
DO_CHAN
MPO_CHAN
CPO_CHAN
FIC
FIC_PORT
RFIC
RFIC_PORT
FIC_SER2
FIC_PORT
LOGIC_SOLVER
UNDEFINED_CHAN
AI_LS_CHAN
AI_HART_LS_CHAN
AO_HART_LS_CHAN
DI_LS_CHAN
DO_LS_CHAN
431
Display Name
Export Name
LOGIC_SOLVER_RED
UNDEFINED_CHAN
AI_LS_CHAN
AI_HART_LS_CHAN
AO_HART_LS_CHAN
DI_LS_CHAN
DO_LS_CHAN
MV_8CH
MV_100_CHAN
MULTI_14CH
DIN_CHAN
PIN_CHAN
PIC
PIC_PORT
PROG_SERIAL_32DS
PROG_SERIAL_PORT
RED_PROG_SERIAL_32DS
PROG_SERIAL_PORT_RED
PROG_SERIAL_32DS_SER2
PROG_SERIAL_PORT
RTD_8CH
RTD_CU10_CHAN
RTD_NI120_CHAN
RTD_PT100_CHAN
RTD_PT200_CHAN
RTD_PT500_CHAN
RTD_RES_CHAN
RTD_USER_CHAN
SERIAL_32DS
SERIAL_PORT
RED_SERIAL_32DS
SERIAL_PORT_RED
SERIAL_32DS_SER2
SERIAL_PORT
TC_8CH
TC_CHAN
TC_B_CHAN
TC_E_CHAN
TC_J_CHAN
TC_K_CHAN
TC_N_CHAN
TC_R_CHAN
TC_S_CHAN
TC_T_CHAN
432
System Configuration
Display Name
Export Name
ZONE_1_AI_AO
Z1_AI_CHAN
Z1_AI_HART_CHAN
Z1_AO_CHAN
Z1_AO_HART_CHAN
ZONE_1_DI_DO
Z1_CPO_CHAN
Z1_DI_CHAN
Z1_DO_CHAN
Z1_FREQ_CHAN
Z1_MPO_CHAN
Export Name
ISO_MV_25_CHAN
ISO_MV_55_CHAN
MV_100_CHAN
ISO_MV_100_CHAN
ISO_VOLT_0_5_CHAN
ISO_VOLT_0_10_CHAN
ISO_VOLT_1_5_CHAN
ISO_VOLT_1_CHAN
ISO_VOLT_5_CHAN
ISO_VOLT_10_CHAN
AI_HD_CHAN
AI_HD_HART_CHAN
AI_CHAN
AI_CHAN_RED
AO_CHAN
CPO_CHAN_RED
CPO_CHAN
CPO_CHAN_SER2
ISO_RTD_CU10_CHAN
433
Channel Type
Export Name
RTD_CU10_CHAN
DI_CHAN
DI_CHAN_RED
DI_CHAN_SER2
DI_SOE_REG_CHAN
DI_HD_CHAN
DI_IS_CHAN
DI_SOE_EV_CHAN
DIN_CHAN
DO_CHAN
DO_CHAN_RED
DO_CHAN_SER2
DO_HD_CHAN
AI_HD_HART_CHAN
AI_HART_CHAN
AI_HART_CHAN_RED
AO_ENABLED_HART_CHAN
AO_ENABLED_HART_CHAN_RED
AO_DISABLED_HART_CHAN
AO_DISABLED_HART_CHAN_RED
MPO_CHAN
MPO_CHAN_RED
MPO_CHAN_SER2
ISO_RTD_NI120_CHAN
RTD_NI120_CHAN
ISO_RTD_PT100_CHAN
RTD_PT100_CHAN
ISO_RTD_PT200_CHAN
RTD_PT200_CHAN
434
System Configuration
Channel Type
Export Name
RTD_PT500_CHAN
PCI_CHAN
PCI_CHAN_RED
PCI_CHAN_SER2
PCI_IS_CHAN
PIN_CHAN
ISO_RTD_RES_CHAN
RTD_RES_CHAN
ISO_TC_B_CHAN
ISO_TC_E_CHAN
ISO_TC_J_CHAN
ISO_TC_K_CHAN
ISO_TC_N_CHAN
ISO_TC_R_CHAN
ISO_TC_S_CHAN
ISO_TC_T_CHAN
TC_B_CHAN
TC_E_CHAN
TC_J_CHAN
TC_K_CHAN
TC_N_CHAN
TC_R_CHAN
TC_S_CHAN
TC_T_CHAN
TC_CHAN
ISO_TC_CHAN
ISO_RTD_USER_CHAN
RTD_USER_CHAN
435
The following table lists the valid values for the channel_type field in import and export files for Logic Solver
channel objects.
Channel Type
Export Name
AI_LS_CHAN
DI_LS_CHAN
DO_LS_CHAN
AI_HART_LS_CHAN
AO_HART_LS_CHAN
Undefined Channel
UNDEFINED_CHAN
Export Name
Z1_AI_CHAN
Z1_AO_CHAN
Z1_CPO_CHAN
Z1_DI_CHAN
Z1_DO_CHAN
Z1_FREQ_CHAN
Z1_AI_HART_CHAN
Z1_AO_HART_CHAN
Z1_MPO_CHAN
Export Name
ISO_MV_25_CHAN
ISO_MV_55_CHAN
MV_100_CHAN
ISO_MV_100_CHAN
436
System Configuration
Channel Type
Export Name
ISO_VOLT_0_5_CHAN
ISO_VOLT_0_10_CHAN
ISO_VOLT_1_5_CHAN
ISO_VOLT_1_CHAN
ISO_VOLT_5_CHAN
ISO_VOLT_10_CHAN
AI_HD_CHAN
AI_HD_HART_CHAN
AI_CHAN
AO_CHAN
CPO_CHAN
CPO_CHAN_SER2
ISO_RTD_CU10_CHAN
RTD_CU10_CHAN
DI_CHAN
DI_CHAN_SER2
DI_HD_CHAN
DO_CHAN
DO_CHAN_SER2
DO_HD_CHAN
AI_HART_CHAN
AO_ENABLED_HART_CHAN
AO_ENABLED_HART_CHAN_RED
AO_DISABLED_HART_CHAN
AO_DISABLED_HART_CHAN_RED
MPO_CHAN
MPO_CHAN_RED
MPO_CHAN_SER2
ISO_RTD_NI120_CHAN
RTD_NI120_CHAN
437
Channel Type
Export Name
ISO_RTD_PT100_CHAN
RTD_PT100_CHAN
ISO_RTD_PT200_CHAN
RTD_PT200_CHAN
RTD_PT500_CHAN
PCI_CHAN
PCI_CHAN_SER2
ISO_RTD_RES_CHAN
RTD_RES_CHAN
ISO_TC_B_CHAN
ISO_TC_E_CHAN
ISO_TC_J_CHAN
ISO_TC_K_CHAN
ISO_TC_N_CHAN
ISO_TC_R_CHAN
ISO_TC_S_CHAN
ISO_TC_T_CHAN
TC_B_CHAN
TC_E_CHAN
TC_J_CHAN
TC_K_CHAN
TC_N_CHAN
TC_R_CHAN
TC_S_CHAN
TC_T_CHAN
TC_CHAN
ISO_TC_CHAN
ISO_RTD_USER_CHAN
RTD_USER_CHAN
438
System Configuration
In DeltaV Explorer, select the object that you want to export. Then, select File | Export | User Defined...
A wizard appears and leads you through the steps necessary to export the object.
The dialog contains two radio buttons that determine how you select data to export:
Select the Children of selected component button to choose items in and below the selected component.
Refer to the Selecting Items to Export topic for more information.
Select the Search results button to search the DeltaV system for items to export. Refer to the Searching
for Items to Export section for more information.
After you have selected the items to export by either of these methods the Format Source dialog appears.
2
Select the format specification file that defines the items whose data you are exporting. Then, click Next.
The Export Target dialog appears.
Click Browse to open a select Export File dialog. Either select an existing text (.txt) file or enter a new filename
to export data to. Then, click Next.
The Export Results dialog appears.
439
Select, create, or modify a format specification file (.fmt) to define the data to be exported and imported. Use the
Format Specification wizard (from DeltaV Explorer select File | Format Specification) to create or modify a
format specification file.
If you are exporting and importing custom modules, create a template from the object you want to bulk edit. For
more information, refer to the Bulk Edit Example - Custom Module topic.
440
System Configuration
Open the exported data file from the Bulk Edit template. This creates an ASCII version of the file (with _ASCII
appended to the file name). (The output from the user-defined export is Unicode, and some versions of Excel do
not handle Unicode.)
Edit the exported data as required (you can add, delete, or modify data).
Import the _ASCII file using the same format specification file used to export.
Note You can specify one object type for each import or export operation. For example, if you build a spreadsheet of
channel data, the associated cards and controllers must already exist in the configuration database for the data to
import correctly. The imported file can contain the card and controller names as well as the channel data, but these
items are only used during the import to map the channel data correctly in the configuration database.
441
Use the Open data file icon on the DeltaV Bulk Edit menu to open the exported or sample data .txt file. (Do not
use the normal Excel File Open icon or the File | Open menu selection.)
If the file you open is a Unicode file, a pop-up appears telling you that the template creates an ASCII file with
_ASCII appended to its name. Excel cannot work with Unicode files. The template creates an ASCII version for
you to edit, save, and import. The original Unicode file remains unchanged.
Edit the file as desired. You can add rows, delete rows, and modify the data in rows.
Use the Save icon on the Bulk Edit menu to save the data. Remember that the name of the saved file is the
original file name with _ASCII appended to it (if you started with a Unicode file).
Click OK.
The expression is now visible in the cell.
Now you can copy the row, paste it as many times as desired, and edit the copies as required.
Note If you do not make the expressions visible before you copy and paste, # sign characters are pasted into the
copied cells.
Every time you open a file that contains expressions longer than 255 characters, Excel replaces the expressions with #
signs.
On export, Bulk Edit replaces tabs and carriage returns with <tab> and <cr>. It can be confusing to edit these
expressions and keep the formatting as intended. It is much easier to edit expressions after importing because the
formatting is restored.
However, if you edit an expression in Bulk Edit and the resulting expression is greater than 255 characters, the cell is
populated with pound signs when you move off the cell. Before you save the file you must follow the steps above to
make sure the expression is visible. If you do not, the expression does not import properly and errors result.
442
System Configuration
Area Column
Export File
After Editing
AREA_A
AREA_A/PCELL1
AREA_A/EQ1
AREA_A/PCELL1/EQ1
The following table summarizes the kinds of moves you can make with Bulk Edit for Classless Equipment and
Control Modules.
Moving Classless Equipment and Control Modules
If the Module is a...
Is Moving it Under...
Supported
by Bulk
Edit?
Containing Module
Area
Yes
Process Cell
Yes
Unit Module
Yes
No1
Area
No1
Process Cell
No1
Unit Module
No1
No1
Contained Module
Notes:
1. You must delete the module you are moving before you import it to the new
location.
The following table summarizes the kinds of moves you can make with Bulk Edit for Class-based Equipment and
Control Modules.
443
Is Moving it Under...
Supported by
Bulk Edit?
Containing Module
Area
Yes
Process Cell
Yes
Unit Module
Yes
No1
Area
No
Process Cell
No
Unit Module
No
No
Contained Module
Notes:
1. You must delete the module you are moving before you import it to the new
location.
Editing Channel Types
If you use the Bulk Edit template to modify channel types, you must ensure that the channel types you enter are valid
for the cards you are editing. Refer to the Valid Card Types table for information on valid channel types for the
various card types.
Click Browse, select the format specification (.fmt) file that defines the data file you are importing, and then
click Next.
The Import data source dialog appears.
444
System Configuration
Click Browse, select the data (.txt) file to import, and then click Next.
The Import results dialog appears.
Note On import, information from the *.txt file is processed from the bottom up.
Press the F5 key to refresh the DeltaV Explorer.
Click Next.
In the User Defined Export dialog, select the checkbox by the channel.
Click Next.
In the Format source dialog, click Browse and select an appropriate channel format specification file or click
Create to create a new format specification file.
Click Next.
10 Click Browse to locate an existing file to overwrite or enter a new file name.
11 Click Next.
12 Click Export.
13 Open the Bulk Edit template from Excel.
14 Open the data file that you exported.
15 Copy the data from row 2 of the spreadsheet (row 1 contains the column headers) and paste it to rows 3 through
9 (because there are only 8 channels on the I/O card in this example).
16 Edit the data as needed.
Refer to the Editing User-Defined Export Data topic for information on valid channel types for card types.
17 Save the file (note that the file name now has _ASCII appended to it).
18 From DeltaV Explorer, select File | Import | User Defined Import...
19 Select the format file you used to export the data.
20 Select the _ASCII file that you saved from Excel.
21 Run the user-defined import from DeltaV Explorer.
The data in the file is imported into the configuration. If there are any errors, correct them in the _ASCII data file and
import again.
445
Add a Calculation function block to the module and connect the output of the AI block to the input of the Calc
block. The module should look similar to the following:
Select the Calc block, and then select Expressions from the context menu.
446
System Configuration
Note It is a good idea to always start an expression with a remark (REM). If the first line of the expression starts with
a quote mark, the User-Defined export and import may not interpret the expression correctly.
7
Save module TEMP-101 as a module template named TEMPS_F_C under monitoring in the template library.
Specify the Subtype as TEMPS_F_C. Note that this is the same as the name of the module template you created
earlier.
Select items in the Which fields must already exist in the database dialog, if desired.
Click Finish to save the format specification file and close the dialog.
From DeltaV Explorer, select the TEMP-101 module in AREA_A, then select File | Export | User Defined...
Launch DeltaV Bulk Edit by double clicking BulkEditTemplate.xlt in the DeltaV/DVData/BulkEdit folder.
From the Bulk Edit menu, open TEMPS.TXT. The template converts the file from Unicode to ASCII and creates
the ASCII version of the file TEMPS_ASCII.TXT.
In Excel, copy the first data row (row 2, TEMP-101) and paste it to an empty row.
447
Import the data. The Import dialog indicates the progress and notifies you when the import is complete.
From DeltaV Explorer, you can see the module you imported, TEMP-101B. You may need to refresh the view in
DeltaV Explorer.
In the New dialog, name the template MASTER_CAS and make sure the Object type is set to Control Module or
Template.
Click OK.
In the New dialog, name the template SLAVE_CAS and make sure the Object type is set to Control Module or
Template.
Click OK.
448
System Configuration
Note The SubType must be entered in all capital letters. The user-defined import uses the Subtype to identify the
module templates when it creates modules.
10 Right click SLAVE_CAS and select Properties.
11 In the SubType field of the Properties dialog, enter SLAVE_CAS.
Again, use all capital letters.
12 Right click SLAVE_CAS and select Open with Control Studio.
13 Configure the module to look like the following figure.
14 Perform any other configuration required, save the template, and close Control Studio.
15 Right click MASTER_CAS and select Open with Control Studio.
16 Configure the module to look like the following figure.
17 Perform any other configuration required, save the template, and close Control Studio.
18 The MASTER_CAS and SLAVE_CAS templates should look like the following figure.
449
In the Filename field, enter SLAVE_CAS to create a format file for the SLAVE_CAS module.
Click the Apply Filter... button and make sure the appropriate filters are selected for your purpose.
In the Object Type field of the Browse dialog, select Module Templates
In the Select fields dialog, select module parameters you want to bulk edit. You must at least include area,
module_name, and module_subtype.
10 Open the Parameter List and include block parameters you want to bulk edit, if any.
11 Select items in the Which fields must already exist in the database dialog, if desired.
12 Click Finish to save the format specification file and close the dialog.
To create a format file for a containing module:
1
In the Filename field, enter MASTER_CAS to create a format file for the MASTER_CAS module.
Click the Apply Filter... button and make sure the appropriate filters are selected for your purpose.
In the Object Type field of the Browse dialog, select Module Templates
In the Select fields dialog, select module parameters you want to bulk edit. You must at least include area,
module_name, and module_subtype.
450
System Configuration
Exporting Modules
You must export each module in the hierarchy individually.
To export the modules:
1
Click Next.
Click Next.
10 Repeat steps 1 through 9 for MASTER_CAS. When you export MASTER_CAS select only the
MASTER_CAS_1 module in the hierarchy diagram of the User Defined Export dialog. Do not select anything
else.
Editing the Exported Files
To create two new modules you must edit both exported files. Editing the containing module is slightly different than
editing the contained module so both are detailed below.
To begin:
1
Start Excel.
In the DeltaV Bulk Edit menu, click the file open icon.
Copy line 2 of the spreadsheet and paste it back into the spreadsheet into line 3.
In the area column, remove /MASTER_CAS from both lines, leaving only AREA_A.
451
In the module_name field, rename the two modules to SLAVE_CAS2 and SLAVE_CAS3.
Click the file save icon in the DeltaV Bulk Edit menu.
10 Click Save.
11 Click Yes to replace the existing copy of the file.
12 Close the spreadsheet but leave Excel and the bulk edit template open.
To bulk edit a containing module:
1
In the DeltaV Bulk Edit menu, click the file open icon.
Copy line 2 of the spreadsheet and paste it back into the spreadsheet into line 3 of the spreadsheet.
In the module_name column, rename the two modules to MASTER_CAS_2 and MASTER_CAS_3.
Step 6 binds each the MASTER_CAS modules to specific instances of SLAVE_CAS created when you
import the edited files. The tildes (~) at the beginning of each module name cause the bulk edit software to
discard extra modules created during import. If you do not use the tildes an extra copy of all the contained
modules remain in the hierarchy after import.
7
Click the file save icon in the DeltaV Bulk Edit menu.
10 Click Save.
11 Click Yes to replace the existing copy of the file.
12 Close the spreadsheet and close Excel unless you have more files to bulk edit.
Note You can also use Bulk Edit to move existing containing and contained modules, with some limitations. Refer to
Moving Equipment and Control Modules for more information.
452
System Configuration
Click Next.
Click Next.
Note that the SLAVE_CAS modules were imported to the AREA_A level.
8
Note that the MASTER_CAS_n modules are populated with SLAVE_CASn modules.
Importing MASTER_CAS_ASCII.TXT moved the SLAVE_CAS modules created by importing
SLAVE_CAS_ASCII.TXT under the MASTER_CAS modules. The tildes you prepended the
MODULE_BLOCK_BINDING.MNAME values in the MASTER_CAS_ASCII.TXT file caused the import
to remove the extra modules created when MASTER_CAS_ASCII.TXT was imported.
453
In DeltaV Explorer, drag the ANALOG monitoring template in the library to the Example category under
Control Module Classes to create a class.
Add a Calculation function block to the class and connect the output of the AI block to the input of the Calc
block. The class should look similar to the following:
Select the Calc block, and then select Expressions from the context menu.
454
System Configuration
Note It is a good idea to always start an expression with a remark (REM). If the first line of the expression starts with
a quote mark, the User-Defined export and import may not interpret the expression correctly.
8
Note The SubType must be entered in all capital letters. The user-defined import uses the Subtype to identify the
module templates when it creates modules.
9
In DeltaV Explorer, drag the class F_C to a category under Module Templates.
In the Select fields dialog, select module parameters you want to bulk edit. You must at least include area,
module_name, and module_subtype.
Also include any parameter shortcuts you want to bulk edit. Parameter shortcuts consist of the contained block
name and block parameter name separated by a dollar sign. You must at least include AI1$IO_IN.REF so you
can specify the input to the AI block when creating modules during bulk edit. For information on bulk editing
parameters with multiple options refer to Parameter Option Shortcuts.
Select items in the Which fields must already exist in the database dialog, if desired.
Click Finish to save the format specification file and close the dialog.
Note For more information on creating format specification files, refer to Format Specification in the User-Defined
Exports and Imports topic.
455
Start Excel.
From the Bulk Edit menu, open TEMPS.TXT. The template converts the file from Unicode to ASCII and creates
the ASCII version of the file TEMPS_ASCII.TXT.
Note that the fields in the exported file include only those parameters that can be edited.
In Excel, copy the first data row (row 2, TEMP-101) and paste it to an empty row.
In the module_name column of the new row, rename the module to TEMP-102.
Make other changes desired, including entering I/O references for AI1$IO_IN.REF.
Importing Modules
Import the modules you edited in Excel.
1
Import the data. The Import dialog indicates the progress and notifies you when the import is complete.
From DeltaV Explorer, you can see the module you imported, TEMP-102. You may need to refresh the view in
DeltaV Explorer.
456
System Configuration
Create and combine classes for the containing module and contained modules.
Note Throughout the example objects are renamed. This is done to improve the clarity of the example. You do not
need to rename objects you create
Create the totalizer named set as explained in the Batch Tutorial topic Creating a Command-Driven Equipment
Module Class (TOTALIZER).
In DeltaV Explorer, navigate to Library | Advanced Definitions | Equipment Module Classes | General. (You can
create a new category if you want.)
457
In the New dialog, name the class TTLZER_CL (for class), select Command Driven in the Algorithm Type field,
and browse to the totalizer named set in the Named Set Name field.
Click OK.
Click OK.
10 Open the class in Control Studio and add a PID block to it.
11 Save the class and close Control Studio.
12 Right click again and create another control module class.
13 In the New dialog, name the class TTL_FLO_CL.
14 Click OK.
15 Open the class in Control Studio and add an INT block to it.
16 Save the class and close Control Studio.
For this example you do not need to fully configure the classes, but at least put the blocks in the classes so
you can see how to bulk edit parameters of contained blocks.
17 Drag FLO_CTRL_CL and TTL_FLO_CL and drop them onto TTLZER_CL.
The Advanced Definitions hierarchy should now look like the following.
Drag the TTLZER_CL equipment module class to a category under Module Templates.
The Module Templates hierarchy should look similar to the following figure.
458
System Configuration
Note that the text in the parentheses next to the contained modules' name is the name of the contained
modules in the TTLZER_CL class. To determine the class a module or template is based on, right click the
module or template and select Properties. The Class name field contains the class the module or template is
based on.
2
Select TTLZER_TMP.
Note The SubType must be entered in all capital letters. The user-defined import uses the Subtype to identify the
module templates when it creates modules.
5
In the Filename field, enter FLOW_CONTROL to create a format file for the FLOW_CONTROL module.
459
Click the Apply Filter... button and make sure the appropriate filters are selected for your use.
In the Object Type field of the Browse dialog, select Module Templates
In the Select fields dialog, select module parameters you want to bulk edit. You must at least include area,
module_name, and module_subtype.
10 Open the Parameter List and include parameter shortcuts for block parameters you want to bulk edit, if any.
Note Parameter shortcuts consist of the contained block name and block parameter name separated by a dollar sign.
For example, PID1$GAIN is a shortcut to the GAIN parameter of the PID block that FLOW_CONTROL contains.
The column heading for the parameter shortcut in the export file is PID1$GAIN. Parameter shortcuts for parameters
that have multiple options use generic terms for the options. See Parameter Option Shortcuts for more information.
11 Select items in the Which fields must already exist in the database dialog, if desired.
12 Click Finish to save the format specification file and close the dialog.
13 Repeat steps 1 through 12 for the module TOTAL_FLOW, giving the format file a unique name and browsing to
TTL_FLO_TMP for the Subtype field.
To create a format file for a containing module:
1
In the Filename field, enter TOTALIZER.FMT to create a format file for the TOTALIZER equipment module.
Click the Apply Filter... button and make sure the appropriate filters are selected for your use.
In the Object Type field of the Browse dialog, select Module Templates
In the Select fields dialog, select module parameters you want to bulk edit. You must at least include area,
module_name, and module_subtype.
12 If the equipment module contains function blocks, include parameter shortcuts for block parameters you want to
bulk edit.
460
System Configuration
13 Select items in the Which fields must already exist in the database dialog, if desired.
14 Click Finish to save the format specification file and close the dialog.
Note For more information on creating format specification files, refer to Format Specification in the User-Defined
Exports and Imports topic.
Exporting Modules
You must export each module in the hierarchy individually.
To export a class-based module:
1
Click Next.
Click Next.
10 Repeat steps 1 through 9 for TOTAL_FLOW and TOTALIZER. When you export TOTALIZER select only the
TOTALIZER module in the hierarchy diagram of the User Defined Export dialog as shown in the following
figure.
461
To begin:
1
Start Excel.
In the DeltaV Bulk Edit menu, click the file open icon.
Copy line 2 of the spreadsheet and paste two copies back into the spreadsheet into lines 3 and 4.
In the area column, remove /TOTALIZER from all three copies, leaving only AREA_A.
In the module_name field, rename the three modules to FLOW_CONTROL-1, -2, and -3 respectively.
Click the file save icon in the DeltaV Bulk Edit menu.
10 Click Save.
11 Click Yes to replace the existing copy of the file.
12 Close the spreadsheet but leave Excel and the bulk edit template open.
13 Repeat steps 1 through 12 for TOTAL_FLOW.TXT, naming the three modules TOTAL_FLOW-1, -2, and -3.
To bulk edit a containing module:
1
In the DeltaV Bulk Edit menu, click the file open icon.
Copy line 2 of the spreadsheet and paste two copies back into the spreadsheet into lines 3 and 4 of the
spreadsheet.
In the module_name column, rename the three modules to TOTALIZER-1, -2, and -3.
462
System Configuration
Steps 6 and 7 bind each of the TOTALIZER modules to specific instances of FLOW_CONTROL and
TOTAL_FLOW created when you import the edited files. The tildes (~) at the beginning of each module
name cause the bulk edit software to discard extra modules created during import. If you do not use the
tildes an extra copy of all the contained modules remain in the hierarchy after import.
8
Click the file save icon in the DeltaV Bulk Edit menu.
Click Next.
Click Next.
Note that the FLOW_CONTROL and TOTAL_FLOW modules were imported to the AREA_A level.
463
Note that the TOTALIZER-n modules are populated with FLOW_CONTROL-n and TOTAL_FLOW-n
modules.
Importing TOTALIZER_ASCII.TXT moved the FLOW_CONTROL and TOTAL_FLOW modules under
the TOTALIZER modules. The tildes you prepended the MODULE_BLOCK_BINDING.MNAME values
in the TOTALIZER_ASCII.TXT file caused the import to remove the extra modules created when
TOTALIZER_ASCII.TXT was imported.
After you have completed these tasks you can export, edit, and Import configuration data as necessary.
Note This topic does not explain in detail how to use Access and ODBC data sources. Refer to Microsoft
documentation for detailed information on creating and maintaining Access databases and ODBC data sources.
464
System Configuration
In the File New Database dialog select a location, enter a name, and click Create.
The database dialog opens.
Note File DSN is the only valid choice when creating an ODBC source for a user-defined import or export.
4
Click Add.
Select the correct driver, Microsoft Access Driver, and then click Next.
The Create New Data Source dialog opens
Click the Browse button and either accept the default directory (Data Source) or navigate to the directory where
you want to save your DSN.
Enter a name for the data source in the File name field and then click Save.
The Create New Data Source dialog reappears with the DSN path and file name in it.
Click Next.
The dialog changes to show you the file name and driver you selected.
465
Click Finish.
The ODBC Microsoft Access Setup dialog opens.
10 Click Select.
11 In the Select Database dialog, navigate to and select the database file you want to associate with the DSN you
created.
12 Click OK on this and subsequent dialogs.
Exporting to an Access Database Using ODBC
To export the example module to an Access database using an ODBC Data Source:
1
Select the Children of selected component radio button and click Next.
On the User Defined Export dialog, select the module, then click Next.
On the Format source dialog, browse to and select the format file for the example module, then click Next.
Use the Browse button on the dialog to navigate to and select the DSN connected to the database you are using.
From the drop down list, select the Access database table you created previously.
In the Format source dialog, use the Browse button to load the format file you used to export the data, then click
Next.
Use the Browse button to navigate to and select the data source connected to the database you are using.
From the drop down list, select the Access database table that holds the data to import, then click Next.
DeltaV-INtools Interface
An interface is provided to load INtools data into Excel and then save to the DeltaV system. This is achieved using
two add-ins: DeltaV_XL_INtools and DeltaV_XL_Support.
The add-ins are included on the DeltaV installation CDs and they do not require any additional licensing or DeltaV
software. They also do not require any of the other DeltaV Excel add-ins (OPC add-in or Historian add-in, for
example) to function.
466
System Configuration
Note The DeltaV_XL_Support add-in is not intended for general purpose I/O bulk editing. Some features in this addin may be removed or altered to support the INtools interface as it evolves.
This add-in must be used in conjunction with the DeltaV_XL_Support add-in in order to connect to the
DeltaV database.
The add-ins must be run on a DeltaV ProfessionalPLUS or Professional node in order to connect to the
DeltaV database.
The add-ins should only be used with the version of DeltaV software that provided them.
Open Excel.
Note You must manually re-install the add-ins if you install new DeltaV software in order to use the new versions of
the add-ins.
Installing the add-in adds the INtools Interface option to the DeltaV menu as shown in the figure.
467
Name
Redundancy
Type
Series
Slot
Redundancy
Note DeviceNet cards are not supported in this release of the interface.
For Channels and Ports:
Type
Slot
Enabled
468
Name
Manufacturer
Type
Revision
System Configuration
Description
Address
Note ASi-bus, DeviceNet, Profibus, and Serial devices are not supported in this release of the interface.
For Fieldbus Function Blocks:
Tag
Block Index
Select the Open INtools Export... option to load the xml file.
After selecting the file the Select Load Format dialog appears.
469
By default all the columns necessary for the INtools interface are selected.
Note Do not change the default selections in the Select Load Format dialog. Modifying the selections may cause
errors when you attempt to save configurations created in INtools to the DeltaV Database.
470
System Configuration
Select DeltaV | I/O Support | Convert to DeltaV to convert the worksheet so that it can be saved to the DeltaV
database.
Then use the DeltaV | I/O Support | Data Manager dialog to save the data.
471
If card types have changed, you must delete the cards from the DeltaV database before saving the updated
data or the save will fail.
If controllers have been renamed in INtools they must be renamed manually in the DeltaV system before
saving the updated data. Otherwise, the save attempts to create new controllers.
If you have moved cards within a controller or between controllers in INtools, you must physically move
cards to their new slot location or delete the original card slots in DeltaV Explorer. (Bindings of Control
System Tags/DSTs to DeltaV modules are retained and reconnected when the card is added in its new
location as long as the Control System (DSTs) tag has not been changed). Reconciling or saving cannot
change the card class of slot to or from the Fieldbus class. Reconciling or saving cannot move a card to
another controller.
If you move any Fieldbus devices within a card or between cards or controllers you must delete them from
the DeltaV system before performing a reconcile/save from the DeltaV_XL_INtools add-in.
These rules apply because controllers are saved sequentially so it is necessary to remove items from the controller
they were originally located in before attempting to add them to a new controller.
Use the Reconcile... button on the Data Manager dialog to see other differences before you import the configuration.
Merging INtools Data into an Existing Controller that has non-INtools Interface Data
If a controller contains items that are not present in the INtools XML, these items will be marked for deletion when a
Reconcile is performed. To retain these items, perform a Restore on each one before saving. This may happen for
those types of items that are not yet supported in the XML (Profibus devices, for example).
472
System Configuration
Overview
The following figure and explanation are an overview of how this add-in works.
Do not use the Excel delete row function. Always use the DeltaV Add-in context menu options to delete
cards, devices, datasets, IO module slots, and signals.
Always use the DeltaV Add-in context menu options to restore objects.
Regenerate the library after library objects change in the DeltaV database.
Do not:
Add any new rows, other than using the clipboard to copy and paste.
473
The keyboard shortcuts for paste (Ctrl V) does not work when the Add-in is loaded. Paste using the
clipboard.
You must have a workbook open before you can use the Add-in.
DeltaV Add-ins do not work if the workbook is hidden (if you selected Windows | Hide).
Convert to DeltaV Prepares the Excel workbook for use with the DeltaV system.
Data Manager Connects to the DeltaV database and opens the Data Manager dialog.
Load The add-in populates the Excel workbook with I/O configuration information from the Database
Snapshot for the controllers selected in the Data Manager dialog.
Reconcile Use Reconcile to compare the configuration information in the Database Snapshot to the
information in the Excel workbook. Performing a Reconcile does not change the Database or the Excel
workbook. After performing a Reconcile, using the results to determine what action you need to take.
When you click Reconcile:
1
The add-in compares the Database Snapshot to the Excel workbook row by row.
After the add-in compares all rows, it merges the data and repopulates the Excel workbook. Any
cells that differed between the original Excel workbook and the Database Snapshot are annotated
with a comment and highlighted in color. The colors are:
Yellow - indicates changed data. For example, if you change a Boolean value from True to False in
the workbook then that cell is yellow and the Excel comment attached to it is Changed from 'True'
474
System Configuration
Orange - indicates warnings that do not prevent saving but that you should address.
Red - indicates errors that must be corrected before you can save the configuration. If the reconcile
fails, an Error popup appears. Acknowledge the popup and messages appear in the Reconciling...
popup. Close the popup and examine the worksheet for errors. Correct the errors and reconcile
again.
Note If objects exist in the Database Snapshot but not in the Excel workbook then after a Reconcile the objects are
marked for deletion, as indicated by grayed-out rows. To retain these database objects use the I/O Support | Restore
menu choice to populate the workbook with these missing objects.
Save The add-in first performs a reconcile as described above. If there are no errors, the add-in
updates the DeltaV database and then refreshes the Database Snapshot. Select the Log Changes
checkbox to keep a record of changes made to the configuration. Each controller has its own log file in
\DeltaV\DVData\INtools\Logs.
Note If the node you are saving references DSTs that are already in use in the DeltaV database, an error message
appears. If the error message appears, delete the DSTs from the Excel workbook, then click the Save button on the
Data Manager dialog.
Note If you are working with large databases and errors appear when you attempt to save your changes from Excel,
increase the amount of virtual memory on your computer to at least 1 GByte.
Controllers List Lists the controllers whose I/O configuration is currently loaded in the Excel
workbook and the controllers that are in the Database Snapshot. The list of controllers is not
automatically updated. Click the Refresh Controller List... button to update it.
Library Opens the Library Manager dialog. From this dialog you can regenerate selected libraries.
Note If you make changes to the DeltaV database libraries after you install the add-in, regenerate the libraries from
the Library Manager dialog. Open the dialog by selecting DeltaV | I/O Support | Library from the Excel main menu.
475
Delete and Restore Delete and restore objects in the Excel workbook. The available submenus depend on
current context.
Note Do not use the Excel Delete commands to delete cards, devices, datasets, IO module slots, or signals. Use the
DeltaV | I/O Support | Delete command instead. To delete a card, for example, select a cell within the card
configuration, then select DeltaV | I/O Support | Delete | Card. The text changes to gray italic to indicate the
configuration has deleted from the worksheet. Restore can be used to undelete this card. The gray italic text remains
visible until you save the configuration.
Collapse Uses Excel's Outline capability to hide information for some configuration items. To use, select
an item, then select Collapse from the menu. Use the plus signs (+) that appear in the left of a worksheet to
selectively view hidden information.
Find Next Error If the current worksheet contains errors, use this choice to find the next error from the
current location.
476
System Configuration
The first time you load a controller the initial format is <Default>. Unless you have special data editing
requirements, you can accept the <Default> format. You can create, name, and save formats if you want.
Formats you create are saved in the file ...DeltaV\DVData\INTools\XLSupport\formatters.xml. The formats
determine the columns that appear for the row types. If you reload the same controller, the initial selected
format is <Excel> which represents the format that was originally used to load the controller.
Note Only the columns selected appear in the Excel workbook. Make sure that any columns you need to edit as well
as columns dependant on other columns are included, otherwise you may not be able to edit combinations of
columns.
3
Click OK.
Each controller is loaded into a separate worksheet
Note If you change a single cell in a workbook to a value that is not compatible with related data, the cell is not
immediately flagged as an error. Subsequent changes to other cells may result in additional unflagged errors. Perform
a Reconcile or Save to highlight the cells that contain errors, correct the errors, and continue.
Some of these errors may be the result of attempting to change database objects that can only be changed from
DeltaV Explorer. For example, you cannot change a Profibus IO module slot from the workbook.
477
Note The XML generated by INtools does not support the following types of objects:
DeviceNet Cards and Devices
ASi-bus, Profibus, and Serial devices.
478
System Configuration
DeltaV Logger
DeltaV Logger prints DeltaV OPC Alarms and Events data to a dot matrix printer in real time.
Logger can be launched from DeltaV Process History View. When Logger is launched, it will automatically connect
to the DeltaV Alarms and Event Server and start printing alarms and event data as they occur.
Once you are connected to the Alarms and Events server, you will be able to choose which details about the alarms
and events that you would like to be printed. You can also choose to monitor only specific types of events by using
Event Filters.
To access DeltaV Logger directly, click Start | DeltaV | Operator | DeltaV Logger.
DeltaV Logger Printer Options
DeltaV Logger must be connected to a local line (dot matrix) printer. Printer options are available from the main
menu bar by clicking Printer. The Connected Printers menu shows the printer(s) to which your computer is currently
connected.
documents that can be viewed within your browser (for example, word processing documents, spreadsheets,
html files)
Web Server pages are updated in real time. The Web Server does not support DeltaV Operate scripting language.
Script-based buttons and popups as well as any custom scripts cannot be viewed.
Web Server license use is based on TCP/IP addresses. License use is tracked over a 24-hour period. This means that
on a single-user license, only one TCP/IP address can access the server in a 24-hour period. A user at another address
must wait for the period to expire before accessing the server. If a user tries to log on when the license does not permit
it, a message will be displayed stating that the login failed.
In addition, this system requires the use of Microsoft's IIS application. IIS tracks session connections to the DeltaV
Web Server. Each time a user logs into a Web Server session IIS tracks this. If no activity occurs on this session for a
specific time (typically 20 minutes but configurable in the IIS application), IIS times out the connection.
The 24-hour period is started when the user logs off (clicking the LOGOFF button on the Web Server home page) or
when the IIS session timeout occurs.
479
Web Server software and licenses must be installed following the installation of the DeltaV software. Refer to the
Web Server help file on CD #4 (DV_Extras/DVWebserver).
480
System Configuration
481
to be written periodically, the device can stop its normal operation after it reaches its limit or fail to accept new
values. Consult the device documentation to determine if a parameter is static or non-volatile.
Another way to configure your system to avoid burning out non-volatile memory is to link a CALC block or PID
block running in the controller to the AO block running in the device. This method avoids the use of asynchronous
writes by writing to the AO block through a publisher/subscriber mechanism.
To link a CALC block to the AO block
Link the CALC block's OUT parameter to the AO block's CAS_IN parameter.
Link the PID block's OUT parameter to the AO block's CAS_IN parameter.
Link the AO block's BKCAL_OUT parameter to the PID block's BKCAL_IN parameter.
Write a value to the AO block using the TRK_IN_D and TRK_VAL parameters.
Note This step is very important as the FSTATE_VAL and FSTATE_TIME parameters only appear in the parameter
list after the block has been assigned to a fieldbus device.
2
482
System Configuration
Open DeltaV Explorer, select the H1 card, and select Properties from the context menu.
Download any control modules that are flagged with the blue triangle icon
Tip If multiple modules are flagged with the blue triangle icon, you can save time during the download by selecting
the Uncheck All button on the Select Additional Objects to Download dialog box.
6
Download any fieldbus devices flagged with the blue triangle. Blue triangles should not appear on the port or on
any control modules.
483
Naming Controllers
A controller's name can be as many as 16 characters, must contain at least one letter, and may contain only letters,
numbers, and $, -, or _. In addition, the last 9 characters must be a unique string for each controller if you want
DeltaV Explorer to create DSTs for input and output card channels when you add a card. Explorer creates DST names
by taking as many as the last 9 characters of the controller name and adding CnnCHnn. Cnn is the card slot and CHnn
is the channel number where the DST is created. For example, the DST created for channel 4 of the card in slot 3 of a
controller named ABCDEFGH12345678 would be named H12345678C03CH04.
484
System Configuration
General Guidelines
Here is a quick list of recommendations for creating pictures:
We recommend 300 data links per picture. Remember that a data link does not have to be visible on the
picture to count against the total links per picture. Animations can use none, one, or many data links. (10
data links visible on a picture each with 15 data links used in animation produce a picture with 150 data
links.)
Use a 1 second refresh rate. See the next section for more information.
In DeltaV Operate, scripting must be in Visual Basic. An excessive amount of scripting will adversely effect
system performance.
Read the "Optimization Guide" in the Operator Graphics manual for a comprehensive discussion of issues regarding
the impact of operator graphics on system performance.
485
In the Standard folder, open User_Ref.grf and follow the directions to save the picture as UserSettings.grf.
Click the right mouse button in UserSettings.grf, select Edit Script, go to the section called "Reserved Picture
Initialization" and follow the directions to reserve your pictures.
Important Every picture listed in the Reserved Pictures list is open (but not visible) in DeltaV Operate run mode.
The picture is resident on the machine and the datalinks are actively being updated, allowing for faster access to data
when the operator opens one of these pictures. It is important to understand that the pictures on the Reserved Pictures
list place a burden on the system's resources by keeping those datalinks updated. Therefore, testing is required to
validate that the system is behaving as expected (for example, datalinks are updated at the configured scan rate,
FREMEM is at an acceptable level, and so on). Refer to the System Capacities topic for system limitations.
Floating point array parameters can be accessed in graphics by using the following format:
User parameters
dvsys.module_name/parameter_name[X][Z].f_cv
(where [X][Z] are the [row][column] of the array value)
486
System Configuration
Function blocks
dvsys.module_name/SPLTR1/parameter_name[X].f_cv
dvsys.module_name/SGCR1/parameter_name[X].f_cv(
where [X][Z] are the [row][column] of the array value)
487
Value
Description
FULLSCALE
850
Maximum temperature.
ZERO
100
ALPHA
.00385
DELTA
1.50701
488
In DeltaV Explorer, define a named set that defines the states for the associated discrete device.
In DeltaV Explorer, set the channel's properties: make sure the channel type is set to SOE Discrete Input
Channel, that it is enabled and that the named set is defined.
Systems that include the SOE card must have a network time server. Refer to System Time for more
information (IP addresses for the time server are documented in Installing Your DeltaV Digital Automation
System).
Define one of the workstations as the SOE data collector. By default, the events will be collected by the
ProfessionalPlus workstation. Refer to DeltaV Explorer help for information on how to select a different
workstation.
System Configuration
Open the DeltaV Explorer (click Start | DeltaV | Engineering | DeltaV Explorer).
Select the alias, click the right mouse button, and select References.
489
you cannot perform an active step change on that loop or branch. The best approach is to begin the loop or branch at
the third step and put the second step into manual when needed to control the third step.
Refer to these articles for information on active step changes, looping, and branching in the batch system:
Sequence Loops
Campaign Manager
490
System Configuration
Renaming Workstations
If the Batch Historian machine is the Batch Historian Server, you must also change the name of the machine for SQL
Server. Refer to the SQL Server Books Online topic, Renaming a Server, for more information.
491
Archiving Data
To archive batch and chronicle events, perform the following steps:
1
Select the batch and chronicle events you want to archive from the main database (DVHisDB).
With the archive database still selected, click Archive | Copy and choose a copy destination.
If you are using a CDROM burner, make a copy to the hard drive and use the appropriate CD write tool to make
the CD.
Verify that both the [ArchiveName]_Data.mdf and [ArchiveName]_log.ldf files were copied to the target
destination.
At this point, you have two copies of the database files. The backup exists in the copy location just specified, and
the original archive files still exist in the location designated when the archive was initially created. Although
you can delete the original archive database files, we recommend you leave these files on the workstation to
avoid having a single point of failure in the backups.
Reattach any archive database files (step 3) that still need to be viewed and queried by a client to complete the
procedure.
In order to reattach, the files must be located on a writeable media (preferably the hard drive). A burned CDROM
will not work because the Admin tool cannot write back to the archive files. If the files are restored to a different
location, you will be prompted to locate them when you attach the database.
Select the archived batch and chronicle events and click Batches\Events | Delete. This frees up space in the main
database for more batch and chronicle events.
Verify the newly created space by selecting the DVHisDB database, clicking Database | Properties from the main
menu, and looking at the Database Space tab.
You should develop a structure and naming convention for your archive databases to help manage your historical
batch information. The Batch Historian Administration Tool allows you to create folders for your archive databases.
You can easily move the archive database containers to and from these folders.
492
System Configuration
Downloading Data
The data that you download allows the DeltaV system to manage your control strategy. The Downloading Data topic
explains the various types of downloads in the DeltaV system and the concept of download last.
Writing Expressions
Here are some tips for writing expressions:
Minimize the number of CPU-intensive functions, such as EXPT, LOG2, and **.
Minimize the number of CPU-intensive parameter reads and writes by reducing the number of duplicate
reads.
Use the Named Set command instead of the numerical equivalent to improve readability.
493
The following example shows the original expression and the same expression improved through a reduced number
of reads:
Original
IF OUT1 = 1 AND IN2 = 1
'A_UNIT/STEP.CV' :=
ENDIF;
IF OUT1 = 1 AND IN2 = 0
'A_UNIT/STEP.CV' :=
ENDIF;
494
System Configuration
The following example shows the original expression and a more readable and informative version of the same
expression that uses the Named Set Reference:
Original
IF 'UNIT/B_MODE.CV' = 3 THEN
'A_UNIT/STEP.CV' := 7;
ENDIF;
Improved with Named Set Reference
IF 'A_UNIT/B_MODE.CV' = 'Bch_Mode: Auto' THEN
'A_UNIT/STEP.CV' := 'Step_Cmd: Step7';
ENDIF;
Module-Level Parameters
495
Naming Guidelines
To ensure that DeltaV Operate displays all values and faceplates and does not truncate module descriptions on
faceplates, we recommend that you use the following string length limits when you configure modules in DeltaV
Explorer:
Suppressing Alarms
Generally you respond immediately to alarms. However, occasionally you might find that you are distracted by a
nuisance alarm that you cannot immediately respond to. When this occurs, you can temporarily suppress the alarm.
Suppressing an alarm removes it from the Alarm Banner and Alarm List pictures. When you are ready to respond to
it, unsuppress the alarm and respond.
496
System Configuration
Enable version control on large databases at the end of the day because it can take a lot of time.
Remember that the database is locked during the time that version control is being enabled and no
engineering work can be done.
Enable version control after you import a database. If you enable version control before importing, all items
are listed as checked out and you must manually check them in.
Adding Printers
Use the following guidelines when connecting printers to the system. Consult your system administrator for specific
printer and workstation configuration.
Direct printer connection (for machines without a plant LAN connection) - Attach the printer to the
parallel port or USB port of the machine. This is the only way to provide printer support to a machine that
does not have a plant LAN connection. Do not share print resources across the DeltaV control network to
other DeltaV workstations. Sharing print resources across the DeltaV control network can affect system
performance.
Connect printers to the plant LAN - Attach the printer to the plant LAN through HP Jetdirect.
ProfessionalPLUS or Application Stations with a connection to the plant LAN can print directly to printers
on the plant LAN.
Direct printer connection (for ProfessionalPLUS or Application Stations with a plant LAN
connection) - Attach the printer to the parallel port of the workstation. ProfessionalPLUS or Application
Stations with a connection to the plant LAN can print to this printer through the plant LAN. Do not share
print resources across the DeltaV control network to other DeltaV workstations.
Connect printers to an isolated, separate LAN - Create a separate print LAN between DeltaV
workstations using the third NIC card of each machine. Connect workstations that you want to print from to
this print LAN. Use a non-DeltaV machine as the print server or use a printer with a built-in print server.
Do not use a DeltaV workstation as the print server in this arrangement.
The following printer models are recommended for use with the DeltaV system: HP 6127, HP 2300d and HP 4650n.
497
Printing to File
In the DeltaV Engineering tools, such as DeltaV Explorer and Control Studio, you can print reports and configuration
information. You can also sent the output (for example, a report) to a file. You would select this option if there was no
printer available at the time, save the file electronically for historical purposes, or you wanted to send the file
electronically to another person. This is called Print to File and is selected on the Windows printer dialog.
You are prompted to name the file. Normally you will name the file with a .PRN or .PS extension (PRN=printer file
type; PS=Postscript file type).
Note The printer and Print to File dialogs will defer depending on the application from which you are printing.
Once the file is saved, you can send it to a printer. The steps are the same regardless of what type of file it is.
However, most print to file functions save the file in Postscript format and will require a postscript compatible printer
to print the file properly.
498
System Configuration
Change to the directory where file resides (for example, cd printerfiles <enter>).
499
500
System Configuration
Index
Symbols
!
A
accelerator keys
351
57, 78
administration
alarms,types
95
analog input
210
211
153
153
140
AS-Interface
alarm calculation
99
alarm collection
128
alarm detection
101, 119
343
89
alarm priorities
261
155
98
alarm presentation
267
B
backup
111
Batch
343
batch
378
blue triangle
102, 110
Bulk Edit
92
bulk edit
95
alarm system,troubleshooting
alarm types
95
alarm view
356
alarm,calculating
116
155
351
116
140
302, 343
alarm banner,customizing
454
118
99
alarming,conditional
446
440
392
88
alarms,conditional discrete
Bulk Edit,user-defined
101
Index
115
110
alarms, device
155
343
87, 118
alarm system
alarms,thresholds
102
155
alarm states
102
array parameters
118
alarm banner
alarms,modifying
archive,converting historical
302
administration,Continuous Historian
alarms
101
archive
alarming
alarms,conditional low
analog output
142
alarm
101
350
action
alarms,conditional high
440
C
calculation
99, 118
101
501
calculation,alarm
99, 118
calculation,custom alarm
CHANNEL parameter
118
confirm
20
353, 359
454
148
155
448
collapse
153
151
136
205
164
181
353, 359
136
Comm Fail
263
Continuous Historian,properties
commands
116
commands,menu
Continuous Historian,setup
116
composite
198
control recipes
control strategies
Control Studio
147
Control Studio,tips
101
102
controller restart
102
268, 481
Configuring devices,PlantWeb
creating
198
197
197
263
205
controllers,auto-sense
302
502
controllers
205, 302
Configuring devices
376
controller communication
101
configuration, AS-Interface
conditional alarming,example
configuration
13
381
368
conditional alarms
13
378
conditional alarming
134
147
150
135
Continuous Historian,workstations
control function blocks
366
composite Ff status
150
134
Continuous Historian,upgrading
302
198
communications,controller
136
157
145
208
16
78
context menu
16
153
156
156
System Configuration
143
DeltaV Logger
118
DeltaV SIS
118
118
device alarms
111
101
118, 119
257
257
88
88
267
device descriptions
153
device states
142
data sets,history
262
257
309, 343
diagnostics
280
280
360
360
360
362
156
DeltaV applications
156
diagram view
356
discrete input
211
discrete output
351, 359
353
332
264, 348
DeltaV Explorer,tips
158
353
downloading data
302
264
212
double-click
348
151, 158
displays
263
263
diagnostics,Continuous Historian
262
9, 257, 381
dataset,configuration
DeltaV Explorer
158
DeviceNet
35
276
debugging
153
306
254, 257
device tags,fieldbus
142
database explorer
Index
device alerts
deleting
472
device addresses,fieldbus
446
353, 359
data compression
debug
DeltaV_XL_Support add-in
device addresses
446
datasets
467
detection,custom alarm
118
dataset
343
detection,alarm
cut + paste
479
DeltaV_XL_INtools add-in
detection
118
118
custom alarm,detecting
custom modules
119
320
320
332
332
332
332
332
503
332
downloading data,when to
332
drag + drop
drill down
353, 359
Fieldbus
343
fieldbus
230
249, 306
DST, Profibus
306
DST,counting
249
DST,licensing
249
143
353, 359
Drop-in replacements
DST
332
257
88
24
262
262
Electronic Signatures
41
ENABLE_AUTO_SWBK
235
ENABLE_AUTO_SWBK parameter
ENABLE_PI_GATING
Engineering standards
233
262
262
262
51
265
9, 257
Event Chronicle
91, 128
fieldbus devices
event collection
128
472
467
exporting
393
390
29
29
258
Fieldbus methods,accessing
260
fieldbus,channel values
439
504
Fieldbus methods
export,user-defined
478
29
273
261
fieldbus loops,troubleshooting
export,standard
fieldbus devices,autosensing
fieldbus loops
254
353, 359
Explorer
export
350
164
262
262
214
87
Excel add-ins
262
343
electronic signatures
event
273
275
13
System Configuration
fieldbus,valid units
history data,compression
history data,retrieval
393
378
Foundation Fieldbus
254
254
210, 230
254
I/O cards
254
254
230
I/O channels
I/O Nodes
import
275
importing
264
H1 Fieldbus
215
H1 fieldbus card
444
349
Isolated Input
137, 156
158
29
48
138
INtools interface
29
350
Intellectual property
131, 138
145
integrity
history collection,configuring
history data
392
48
348
history collection
444
48
392
indicators
254
Hide command
264
393
390
import,user-defined
Index
381
import,standard
H
H1 card
245
305, 306
467
245
I/O subsystem
275
472
210
34
GSD files
210
210, 381
I/O configuration
360
210
I/O channels,parameters
360
230
230
I/O cards,parameters
254
function block
145
254
Free VCRs
145
48
467
213
K
keyboard shortcuts
351
155
505
Methods,accessing
L_TYPE parameter
Methods,fieldbus
20
260
258
millivolt
LAS
254
254
modifying alarms
359
module
351
131
license,enforcement
249
module,scan rate
254
254
Multifunction
mV
live list
254
35
loops
Nodes
479
245
29
245
M
9
Macrocycle Viewer
macrocycle,actual
macrocycle,scheduled
macrocycle,viewing
master recipes
190
181
464
macrocycle,required
186
184
189
192
184
378
59
59
palette
357
matrix,parameter
59
palette view
menu commands
116
pane
Methods 257
fieldbus device methods
506
359
matrix
281
479
29
macrocycle
281
214
Logger,DeltaV
203
214
navigation
35
203
locks,for parameters
126
Logger
1, 203, 348
module,execution order
locks
281
249
281
102
Legacy Historian
licensing
214
356
348
parameter security
24
parameter values
35, 92
34
System Configuration
PROVOX
34
PROVOX I/O
356
320
Publisher VCRs
343
254
205
214
235
Parameters, ENABLE_AUTO_SWBK
question mark
350
235
205
R
Recipe Studio
19
378
Recipe Studio,tips
19
379
redundant controllers
22
Parameters,XD_SCALE
Redundant I/O
20
199
230
PlantWeb Alerts
88
reference
266
16
Remote I/O
59
343
69
235
59
268, 481
232
245
preferences
343
presentation
118
reports
presentation,custom alarm
primary storage
priority
267
157
92
right-click
321
321
RTD
306
306
Protect command
SAM
343
320
213
213
385
SCADA tag
306
scan rate
51
359
306
306
Profibus,baud rates
157
351
RTD, ohms
215
Profibus master
RS3
RS3 I/O
Profibus DP
resource block
restore
376
Index
136
92
priority,alarm
Profibus
376
required macrocycle
136
printing reports
376
reports, printing
118
273
51
249
203
204
507
scan rate,module
switchover causes
203
scan rate,multiplier
switchovers
204
scheduled communication
scheduled macrocycle
security
system preferences
144
tags
213
Serial Card
tips
serial cards,output
281
230
slave devices
41
351
302
393
351
116
29
29
UNITS parameter
302, 306
302
22
unscheduled communication
uploading
102
340
user interface
265
350
255
64
265
340
254
348
user-defined data
22
254
uploading,parameter changes
95
Status indicators
116
213
status conditions
393
305
508
transferring data
troubleshooting,alarm system
302, 305
states,alarm
379
267
troubleshooting
41
single-click
states
353
transducer block
triangle indicator
362
signatures,electronic
SOE
376
362
SFC,debugging
slaves
353
tips,Recipe Studio
281
signatures
115
tips,DeltaV Explorer
281
SFC
115
tips,Control Studio
284
214
thresholds,alarm
276
284
Thermocouple
thresholds
Serial Card,configuration
serial data
362
276
serial cards
362
343
64
385
343
system preferences,defining
security,Continuous Historian
Sequence Of Events
199
254
SELSTR
232
439, 444
439
444
397
System Configuration
464
35
35
281
V
valid units for fieldbus devices
VCRs
255
VCRs, free
256
VCRs, publisher
255
VCRs, subscriber
version control
255
478
478
W
window pane
348
worksheet functions,
165
165, 167,
X
X
350
X indicator
350
XD_SCALE parameter
20
Y
yellow triangle
Index
350
509
510
System Configuration