Version: 1.06 86
12. Alarms
12.1. Introduction
Alarm module of TB
OX
MS is the gate to the outside world.
An alarm consists in a communication event, not only for sending warning messages but
to establish a connection, like we will see.
Via alarms, you are able to call a SCADA, send SMS or message to Pagers, send e-mail,
send files to a FTP site, dial another TB
OX
MS or send a report to a printer.
Alarms can be used also to send historical data on regular base using e-mail or FTP. The
historical data is sent as the attached file of a report, developed using
Report Studio
(see
from ‘Windows’ the group of programs of ‘Techno Trade’).
TView
, the supervisory software can then be used to collect data from a mail box or a FTP
site.
The initiation of alarms in the TB
OX
MS relies on the variation of digital or analog Tags.
For example, an intrusion contact or a flow level generates a call.
There are two ways of activating an alarm:
By a condition: an edge on a digital Tag or the value of an analog Tag that passes
below a minimum threshold or above a maximum threshold, with adjustable hysteresis.
By the Ladder diagram: a complex Ladder sequence generates an alarm through a
specific function.
The first option affords a simple and quick way to create alarms (a state change of a
digital Tag or the variation of an analog Tag value to activate the alarm).
The Ladder diagram allows you to create a complex automated alarm condition by using
(for example) priorities or a set of analog or Boolean conditions.
Each new alarm is immediately entered into a 32-alarms queue (adjustable) and
processed, according to its severity level. Alarms are generated one by one.
The alarm queue represents an internal buffer of alarms: if several alarms happen at the
same time or if a communication port is not available when the alarm happens.
The Events stack, gives information about alarms status (Started – Stopped –
Acknowledged).
The Events stack is
discussed at chapter 12.7