
Version : 1.09
48
The object ‘Alarms’ used in a WebForm displays the Event stack. It corresponds also to
the list of Alarms sent to TView.
Alarm stack: is an internal stack used to buffer alarms when there are several to handle at the same
time or when the communication port is not available or when retries are required.
SMTP From: when receiving an e-mail from
TB
OX
LT2
, the field ‘From’ indicates the origin of the e-
mail.
It accepts any text and the following parameters:
%station% : replaced by the name of the station (see General properties)
%email% : replaced by the e-mail address of the RTU
Example: TBox_%station% <%email%>
SMTP subject:
when receiving e-mail from
TB
OX
LT2
, the field 'Subject' can be dynamized like
following:
When sending a message, the field ‘Subject’ contains the message.
In addition, it accepts any fix text and the following dynamic data:
%station% : replaced by the name of the station (see General properties)
%email% : replaced by the e-mail address of the RTU
%time% : the time of the RTU when the e-mail was generated
Example: Report TBox %station% - %time% :
When sending a report, the subject field contains the Title of the report (see Report
Studio); title that can contain the parameter %station% (see above)
GSM & Printer message:
when
TB
OX
LT2
sends SMS, you can add information to the message.
This information is sent in front of the message.
You can type any text and the following parameters:
%station% : replaced by the name of the station (see General properties)
%time% : the time of the RTU when SMS (or printing) was generated
%condition% : It will result in an exclamation mark (!) in the message if the condition
of the alarm is still active when the alarm is sent.
End of Alarm prefix :
allows specifying a text that will be sent in front of the message, when
the alarm condition ends, to indicate it corresponds to the End of the alarm
Example:
END:
Message sent when the condition ends: .
END: Level too HIGH
Check the total length of SMS message according to the coding used (TEXT or UCS-2) as
explained chapter 12.6.1. SMS coding.
Process alarm even when com. port not available:
An alarm corresponds always to a communication (at the exception of "Internal"
alarms). When an alarm condition is activated, by default, it waits the availability of the
com. port to be handled (Ethernet cable connected, GSM present, PSTN line detected,
...) This can lead to problems in handling escalation: if a media is not present, the alarm
process will be stopped.
This option allows carrying on alarms, even when the port is not available.
Содержание TBOX LT2-530 Series
Страница 1: ...User s Guide Cabling Technical Specifications Version 1 09 LT2...
Страница 10: ...Version 1 09 10...
Страница 11: ...Version 1 09 11...
Страница 17: ...Version 1 09 17...
Страница 20: ...Version 1 09 20...
Страница 21: ...Version 1 09 21...
Страница 38: ...Version 1 09 38...
Страница 39: ...Version 1 09 39...
Страница 151: ...Version 1 09 151...
Страница 175: ...Version 1 09 175...