I’m an intern working on a project originally set up by another intern a few years ago. To give a quick run down, we have a bunch of power meters monitoring substations through out our plant and we use these meters to keep track of voltage, current, etc.
I’m having an issue with alarms being triggered inside setpoints or below them. For example, I’ve had overcurrent alarms go off at 0 amps when the setpoint is 1080 or voltage alarms going off at 7000 volts with bounds of 5950 and 8050. All of these alarms are also being set off if I do something like changing the name of the alarm.
The alarms are configured through UDT’s and are being viewed with an alarm status table. I’ve tried creating new alarms and they all have the same issue. If anyone has any suggestions, I would greatly appreciate them. I’ll attach screenshots of what I think is helpful please let me know if additional info is needed.
Also, is it possible to clear an alarm status table and start fresh? I have over 100 alarms that I can’t get rid of and they are meaningless.
Your screenshot appears to be of the UDT, not the individual tags, which may have different limits overriding the initial UDT setting.
Also, you mentioned renaming alarms. Did you do this while the alarms were active? Are your logs complaining about unable to acknowledge alarm IDs that dont exist? Have you restarted the gateway? This topic on how to delete alarms may be of help:
Some of the individual tags have overcurrent parameters set to 2000 or 3000, but the majority are 1200 and there’s none less then that.
I only changed the names of alarms that were cleared and acknowledged, and this triggered them again and then instantly cleared and acknowledged. I haven’t had any issues acknowledging alarms, and I haven’t tried restarting the gateway yet. I will do that as soon as I can get someone from IT to allow me to run command prompt as admin.
I think the topic you provided will answer my question about deleting alarms so thank you for that.
