Disabled Alarm not appearing on the Disable Alarm list hence not possible to Re-Enable
I am facing some issues with Disable alarms. The system is 800xA 5.1 FP3 .
A tag was disabled from the Alarm iist by rightclicking and selecting "Disable Selected" option.
The tag needs to be re-Eanbled back, however this tag is not visible in any alarm list not even present in the Disable Alarm list. The tag is a ReUse MA Analog Input Type.
Can anyone suggest me what would be the best approch to Enable the tag back.
Thanks in advance.
Voted best answer
The Alarm Manager service holds the 10.000 latest occurring alarms.
An alarm that stays disabled for longer periods of time risk being flushed out from the FIFO queue. Proper configuration (separation of system vs process categories in storage and NOT having the option "Make New Alarm each time a condition gets active" enabled) significantly reduces risk of FIFO overflow.
If overflow happen (which seem probable since the disabled alarm list is empty) three options remain:
1) Enable from AlarmCond block in AC 800M. As far as I know; REUSE dev team has decided to not expose this input terminal on the alarm block.
2) Force refresh from 800xA by toggling active event collector OFF then ON (force failover to redundant). Refresh can also be induced with AfwApplogViewer tool using an operation on the Alarm Manager service. Refresh need to be enabled in Alarm Collection Definition in Library Structure (its default ON for AC 800M OPC AE server)
3) Cold Start Application holding the disabled alarm (a warm download with some A/E reconfiguration also trigger refresh - noticable as "Refresh is needed!" events from the OPC AE server of AC 800M).
But first go online with the alarm owning application in CBM and use the Alarm Conditions context menu command on the alarm block/owner to verify alarm to be in disabled state (CondState 1). 2 is idle. 0 is error in config, or not enabled in configuration. 3, 4 and 5 are alarm states. 6 is auto disabled.
If the alarm is not in the alarm manager FIFO and you are unable to use any of the methods (1-3) I listed in my response maybe method 4) below can work for you?
Enable from 3rd party OPC AE client connecting directly to the OPC AE server having the disabled alarm
Ask your ABB support center for the OPC AE client in case your current does not support enabling/disabling.