The section provides troubleshooting steps for some possible alarm problems.
When something should be in alarm but is not, perform the following steps:
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 active alarms than buttons on the alarm banner, the alarm banner will not show them.
When an alarm should be in THISUSER/ALARMS but is not, perform the following steps:
Determine which plant area the associated module is in.
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.
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:
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:
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).