Page 18
Reference manual FOUNDATION Fieldbus Control module
DOC.RM.BQC54.E Rev: 1
February, 2016
Preliminary Field Trial
Documentation
4.1.4.2 Alert parameter describtion.
1 Alerts - Enabled
These parameters are used to enable the indica-
tion and reporting of each corresponding alert.
When a alert is disabled, the device shall not
detect that particular alert, it shall not be indicated
in the (FAILED_ACTIVE, MAINT_ACTIVE or
ADVISE_ACTIVE parameters or be reported via
respectively Failed Alerts, Maintenance Alerts or
Advisory Alerts.
If an alert enable parameter is changed to ‘dis-
abled’ while the alert is active, it shall clear the
alert and re-evaluate the alert. (Writable, only
affectstheapplicableconditionmodied.Whenset
theconditionwillnotbeindicatedorreported).
2 Alerts - masked:
These parameters will mask any of the failed con-
ditions listed in respectively Failed Alerts, Mainte-
nance Alerts or Advisory Alerts.
Setting a bit to true, will cause the correspond-
ing alert to be indicated in the (FAILED_ACTIVE,
MAINT_ACTIVE or ADVISE_ACTIVE parameters
but it will not be reported to the host via Failed
Alerts, Maintenance Alerts or Advisory Alerts.
If an alert mask is changed while the alert is ac-
tive, the alert is cleared and all the conditions are
reevaluated. (Writable, only affects the applicable
conditionmodied.Whensettheconditionwillbe
indicatedhowever,itwillnotbereported).
3 Alerts-Priority:
Designates the priority of the Failed, Maintenance
or Advisory Alerts. The default is 2 and the recom-
mended value is between 10 and 15. (Writable,
changesthepriorityoftheapplicablealert).
4 Alerts - Active:
These parameters displays which of the condi-
tions within the Failed, Maintenance or Advisory
Alerts is active. When a device detects a condition
has become active, it shall set the corresponding
bit in the Failed, Maintenance or Advisory Alerts
- Active parameters. If it is not suppressed, it will
be reported using the associated alert parameter.
(ReadOnly)
5 Alert Alarm:
These parameter are used to report the particu-
larfailedconditiontothehost.(ReadOnly).For
parameter structure see table 4.2.
4.1.5 NAMUR NE- 107 Alarms
This section describes the parameter interaction to
implement a Bettis Q-Series™ QC54 Control module
to the NAMUR NE-107 requirements as a parameter
group in the Resource Block. There are four alarm
categoriesdenedaspertheNE-107specication,
Failed,OffSpecication,Maintenance,andCheck
function.
Maintenance Although the output signal is valid,
the wear reserve is nearly ex-
hausted or a functions will soon be
restricted due to operational condi-
tions e.g. build-up of deposits
Off
Specication
Off-spec means that the device is
operatingoutsideitsspeciedrange
or an internal diagnostic indicates
deviations from measured or set
values due to internal problems in
the device or process characteris-
tics(e.g.bubbleformationinow
meteringorvalvesticking).
Check Func-
tion
Output signal temporarily invalid
(e.g.frozen)duetoon-goingwork
on the device.
Failed Output signal invalid due to mal-
functionintheelddeviceorits
peripherals.
Each of these categories share 32 conditions that can
bedenedbythedevicemanufacturer.
Each condition may be mapped or not mapped for
each category. If a condition is mapped then it is
indicated in the* ACTIVE parameter. If the condi-
tion in the * ACTIVE parameter is not masked by the
corresponding bit in the *_MASK parameter then the
condition will be queued for broadcast using the cor-
responding *ALM parameter at the associated priority
indicated by *PRI parameter. The 4 categories are
denedbelow.
The conditions are not expected to identify explicitly
the root cause of the condition, but rather to identify it
in terms of:
• Replace the device
• Replace a part of the device
• Correctacongurationproblem
• Fix something outside of the device
The above list is all that the operator needs to know
to restore his process functionality and if there are
more than 31 device conditions they should be
groupedbydenitionintothesebits.