Operating with a DeltaV System
December 2009
F-15
Note
1. For devices with multiple inputs or
outputs (such as the 848), you need to
decide which area is best for device
alarm reporting and be sure to assign
the correct control module to the
lowest index number function block. If
there is no module assigned to this
function block, then the device will
always be assigned to the same area
as the controller.
2. With controller area default of AREA
A, and the default of AREA A being
assigned to all workstations, you need
to evaluate the alarm settings when
commissioning a new fieldbus device
with device alarms enabled. If the
device detects a FAILED or COM FAIL
alarm prior to being assigned to a
control module, this device alarm will
be reported and annunciated to all
workstations. This is because all
workstations have Area A assigned.
Consider lowering the priority of these
alarms to ADVISORY until the end of
the commissioning process.
Reporting Alarms and Events to a
Workstation
Device alarm and event reporting is no different than
control module reporting. Alarm and event reporting to
workstations is determined by assigning areas to
workstations. The workstation area assignment is all
you need to do to ensure that you have all of the
information (device and process) for that area.
This is important so that ALL of the information about
an area
−
both the process and device information
−
is
available at any workstation that is responsible for that
area. That way the Event Chronicle has a complete
record for that area, and any user can drill into a
graphic or tag and access all of the information.
This DOES NOT determine WHO views the device
alarms. Who views the alarms is determined by
filtering at each workstation.
Now that all of the device (and process) information is
assigned to a workstation, the next step is to decide
what priority of device and process alarms cause
alarm annunciation to the users on that workstation.
Setting up WHO Sees Device Alarms
The priority of the alarms, and the settings at that
workstation determine what alarms are annunciated
on a particular workstation. Annunciated means sound
the horn and shown in the alarm banner, Alarm List
display, etc.
There are two different approaches that can be used
to adjust the device alarm filtering for a particular
workstation:
Adjust the default DeltaV Operate alarm settings
in the UserRef/UserSettings file
Adjust the individual device alarm priorities
By default, DeltaV Operator Stations have all process
alarms are annunciated, and show up on the Alarm
Banner, Alarm List, graphical displays, etc. on all
operator workstations. Also by default, the device
alarms with priority settings below WARNING (8) are
NOT annunciated or shown in the alarm banner. The
low priority device alarms can be shown in graphics
and on summaries defined to not be limited by the
alarm settings.
The DeltaV Maintenance Station uses the same
DeltaV Operate alarm setting for device alarm
annunciation. This license only shows device alarms
on Maintenance Station graphics. NO process alarms
are shown in the alarm banner or ANY alarm
summary.
Thus, device alarms and process alarms can be
either combined and/or separated for specific user
installations, based on their operating philosophy.
Setting DeltaV Operate Device Alarm
Annunciation Defaults
DeltaV Operate has default settings in the UserRef.grf
file for what priority of device alarms will annunciate
and show in the alarm banner. The default DeltaV
Operate alarm settings annunciate device alarms that
are of the priority WARNING (8) or higher. Device
alarms below this priority will not sound the horn or
show up in the alarm banner.
Operator Station displays can be configured to show
any alarms reporting to that workstation. Along with
typical display configuration, alarm summaries can be
configured to display alarms that match the alarm
banner settings, or user specified ranges. The
standard AlarmSum display is configured to show all
alarms reporting to that workstation (see figure F-8).
F
Summary of Contents for Fisher FIELDVUE DVC6000f
Page 54: ...DVC6000f Digital Valve Controllers December 2009 2 30 2 ...
Page 62: ...DVC6000f Digital Valve Controllers December 2009 4 2 4 ...
Page 127: ...Transducer Block December 2009 4 67 4 ...
Page 141: ...AO Function Block December 2009 4 81 4 ...
Page 207: ...MAI Function Block December 2009 4 147 4 ...
Page 219: ...DO Function Block December 2009 4 159 4 ...
Page 231: ...DI Function Block December 2009 4 171 4 ...
Page 302: ...DVC6000f Digital Valve Controllers December 2009 8 16 8 ...
Page 306: ...DVC6000f Digital Valve Controllers December 2009 A 4 A ...
Page 350: ...DVC6000f Digital Valve Controllers December 2009 E 6 E ...
Page 368: ...DVC6000f Digital Valve Controllers December 2009 F 18 F ...
Page 372: ...DVC6000f Digital Valve Controllers December 2009 Glossary 4 Notes G Glossary ...
Page 382: ...DVC6000f Digital Valve Controllers December 2009 Index 10 F Index ...