Download  Print this page

Hart Alarms/events Processing - Honeywell Experion PKS User Manual

Profibus gateway module.
Hide thumbs


Device Revision Mismatch (HREVMISM): Used for indicating whether the existing device revision is
different from the installed device.
Device ID Mismatch (HDEVIDFL): Used for indicating whether the configured device ID is different
from the connected device ID.
Supported HART version (HARTVERSION): Used for displaying the supported HART version, like
HART 6.0 and HART 7.0.
Universal Command Revision (HUCMDREV): Used for displaying the supported HART command
Software Revision (HSWREV): Used for indicating the software revision.
Hardware Revision (HHWREV): Used for indicating the hardware revision.
Device Profile Code (HDEVPROFILE): Used for displaying the HART device profile information.
Private Label Distributor (HPVTLDST): Used for displaying the label as received in the command 0.

8.6.5 HART alarms/events processing

HART alarms/events are processed periodically in the PBHCHANNEL, which is associated with the
There are two types of HART alarms/events that are used for monitoring the HART devices.
Device status
Command 48
The following operations are periodically performed for processing the HART alarms/events.
1. Check if there is a change in the DD template or HART notifications," then
a. disable all existing alarms/events
b. re-report all the existing alarms/events so that alarms/events are updated in the station with the new
strings defined in DD file or based on new HART notifications configuration.
2. Check whether the ALMENBSTATE/JOURNALONLY state is changed. The alarms/events must be enabled
or disabled based on the ALMENBSTATE/JOURNALONLY state.
3. Check whether the new alarms/events are reported from the previous scanning for both Device status and
command 48 alarm/events. If yes, then report all the new alarm/events.
If there is any PGM switch-over, then the status of all existing alarms/events is RTN and the alarms/events are
regenerated with new timestamp in the station.
Device status alarms
PBHCHANNEL supports 32 HART device status alarms (that is, 4 bytes). Each bit defines an alarm.
Byte 0 represents field device status, which is updated periodically for every HART command response data.
Byte 0 defines the following alarms.
Bit 7: Field device malfunction alarm
Bit 6: Configuration has changed
Bit 5: Cold Start (device has reset/power cycled)
Bit 4: More Status Available
Bit 3: Loop current fixed
Bit 2: Loop current saturated (PV out of limits)
Bit 1: Non-primary variable out of limits
Bit 0: Primary variable out of limits


Comments to this Manuals

Symbols: 0
Latest comments: