It is possible to create a deadband in an Alarm Worksheet so that alarms that are listed within the worksheet will not immediately be recognized or recorded. This is available in order to filter out spurious and/or short term events which could trigger an alarm, but are not actually alarms. In the case shown below, the definition of “Alarm” and “Normalization” means that conditions creating an alarm or return to normalization must be present for a minimum of 10 seconds before the event is actually considered to be an alarm or return to normalization by the system.
How the application Works:
The AlarmTest screen has a lot of alarming functionality showing many different ways that alarms can be displayed and changed within an InduSoft application. Deadband times can be changed by entering new time values into the fields.
Even if you're not ready to take the plunge into fire alarm system design and installation just yet, you should still know the fundamentals in order to perform emergency work. This includes knowing how to disarm the control panel of a deranged system and troubleshoot the heads, pull stations, horns, and zone wiring so that the equipment goes back online, restoring fire. Wonderware intouch Alarms and Events Wonderware Intouch. The person or system should then acknowledge the alarm, indicating that is has been seen. Alarm annunciation: Reports and updates of the alarm state are displayed and/or logged via one or more alarm clients.
There are two tags in this application that the alarms are being monitored on: bAlarmTest and iAlarmTest. The first is a Boolean tag, which is set/reset by the orange switch, and the latter is an Integer tag where the various alarm states are set/reset by the defined alarm limits of the tag on an alarm worksheet. They are: LoLo 0-10, Lo 10-20, Hi 80-90, and HiHi 90-100. These alarm properties of the tag iAlarmTest are mapped to individual Boolean Tags that are viewable in the OPC browser. The OPC Server Task is turned on by default in this application. The application has two additional buttons: One will acknowledge all alarms and cease the ringing, and the other button clears the Alarm database and refreshes the screen and the Alarm Display Object. The latter functionality is accomplished using a Database/ERP Worksheet and creating a separate connection to the project Access Database, then a subroutine is called, located in the Global Procedures, which deletes the records in the AlarmHistory Table, sets the Time Actually Set/Time Actually Normalized tags to a null value, then closes and reopens the screen in order to refresh the Alarm Display object.