The RED Common Alarm LED will illuminate when any ATevo alarm (legacy alarms and/or advanced alarms) is activated. With the exception of the six (6) legacy alarms mentioned in the previous section, advanced alarms do not have individual LED indicators.
When the Common Alarm LED is – by itself – illuminated, this indicates that one (1) or more of the advanced alarms are active. These advanced alarms are summarized in Section 7.3.
When the Common Alarm is active, the Common Alarm relay on the Main Control Board will change to the alarmed state after a configured time delay. The Common Alarm will also be reported by any installed optional protocol communications board. It may also be configured to activate a discrete relay on optional Auxiliary I/O Boards (A4x). Section 12.4 gives instructions on how to configure relays.
7.2.1 Configuring Common Alarm
By default, all ATevo alarms (when active) are configured to annunciate the Common Alarm. In some applications, it may be desirable to prevent alarm(s) from triggering the common. Section 4.6 describes how any alarm can be individually removed from the list of alarms that, when active, will trigger a Common Alarm.
7.2.2 High Priority Alarm & Low Priority Alarm (v2.7.0+)
The ATevo always had the user configurable “Common Alarm”. Firmware prior to v2.7.0 navigated directly to “Common Alarm” configuration.
Beginning with v2.7.0 firmware which was released 5/3/2021, alarms named “High Priority Alarm” and “Low Priority Alarm” became available to a user who wishes to further customize alarm priority. These alarms can be configured to close a relay on an AUX I/O and are also readable over SCADA.
If your ATevo shipped with, or has been upgraded to v2.7.0+ firmware, you will see the ALARM TRIGGERS icon instead of the COMMON ALARM icon, and will be able to configure the triggers for these new alarms in the same menu that the “Common Alarm” is configured.
The image above shows the display that is typical of when “Common Alarm” has been selected. “High Priority Alarm” and “Low Priority Alarm” displays are similar.
7.2.3 Other Alarm Enhancements with Firmware v2.7.0
Also new in v2.7.0 is that alarms are listed in alphabetical order. In addition, alarm types that depend on optional hardware are only displayed if the respective option is installed. Examples are “Battery overtemp” and “Battery temp probe fail”; these are visible only if a battery temperature probe is installed and enabled.
