Recent Control & Safety Systems Discussions
Similar Posts
Version control error when trying to commission wireless gateway
"Delete" option greyed out when trying to Delete a Future device placeholder in AMS
Getting Version control error message when trying to modify history from DeltaV explorer
Execute Batch and Failed “Write to REQUEST attribute Failed” when try to access request.cv. (I.g 3404)
Compare the value of a variable with the value that variable had before the change
Share

Has anyone had issues when trying to unsuppress an alarm?

I am running into a growing list of alarms which were suppressed, and for which I cannot unsuppress.

The common thread is that the are device alarms from smart instruments. The parameters for these are Comm_ALM, Advise_alm and Failed_alm.

Not all device alarms have this issue. The majority behave as they should when unsuppressed, yet I have three tags that I cannot remove from the suppression list.

Am I missing something, Any ideas?

MPHymel
  • MPHymel

    In reply to MPHymel:

    FYI, for the benefit of anyone finding this thread in the future, I was able to get rid of the suppressed alarms by running the CHARM firmware update (though firmware was current, the process reset the CHARM in some way, and the alarms were removed from the suppression list. I also discovered that this is a repeatable problem. The steps below detail how the issue sets itself up. Guardian support team is looking into this, while not a show-stopper, the inablilty to remove a suppressed alarm has the effect of disabling the alarm permanently.

    The following steps demonstrate how an alarm can become suppressed, with no means of unsuppressing....

    1. Set up some HART device
    2. Set the alarm suppression timeout for COMM, MAINT, ADVISE, and FAILED to 999 d, 0 hours, 0 minutes
    3. Cause the device to produce a COMM, MAINT, and FAILED_ALM
    4. Suppress all three alarms.
    5. Unsupress MAINT alarm (you will notice that it works)
    6. Change the alarm suppression timeout to 0 days, 4 hours, 0 minutes for COMM alarm
    7. Try to unsupress the COMM alarm (you will notice that you cannot)
    8. Wait 4+ hours for the suppression timeout to occur. (you will notice that alarm is still suppressed)
    9. Change the alarm suppression timeout back to 999 days, 0 hours, 0 minutes for COMM alarm
    10. Try to unsupress the COMM alarm (you will notice that you cannot)

    Nothing will clear the suppression status for the COMM alarm unless the CHARM is reseated or firmware upgrade process repeated.

This is the official online community site of the Emerson Global Users Exchange, a forum for the free exchange of non-proprietary information among the global user community of all Emerson Automation Solution's products and services. Our goal is to improve the efficiency and use of automation systems and solutions employed at members’ facilities by sharing our knowledge, experiences, and application information.

User Groups | World Areas | Community Guidelines | Legal Information | Privacy Policy | Contact Community Manager

Website translation provided by Website Translator

© 2015-2022 Emerson Global Users Exchange. All rights reserved.