Alarms are an important part of detecting problems within your system, but they can also become a nuisance if the source of the alarm is unknown.
There are four major areas within StackStudio that can trigger StackVision Alarms:
1. Server Channel Exceedance Alarms
Server Channels are used to calculate extended averages of your existing parameters and can trigger an exceedance alarm if the extended average exceeds a configured limit.
2. Digital Line Alarms
Alarms can be tied to digital inputs and triggered when the digital input is closed. If the digital input is configured to be normally closed, the alarm will trigger when the input is opened.
3. Polling Alarms
Polling Alarms are tied to a particular datalogger channel and will use the flags applied to the channel to set a StackVision alarm.
4. Condition Manager
A Condition Manager script can be set up to run in ProcessNow that triggers an alarm based upon a preset logic condition.
For more detail about each of these alarm types and how they can be set up, view the "Getting Your Alarms Right" webinar from July 2016.
Clint Anderson, Systems Implementation Engineer, ESC Published: 7/13/2016 2:53:35 PM
Receive notices of new articles and free webinars, of training classes being offered, and regular anouncements and offers.
We'd love to answer your questions.
Check out our helpful animation that teaches the basics of