Instruction Manual

i.LON 100 Internet Server Programmer’s Reference 8-9
Property Description
<UCPThistLogSize>
The size of the historical alarm log file, in kilobytes. The historical alarm
log contains a record for any acknowledged alarm. Each record includes
the description, acknowledgment time and comment entered for the
alarm.
Please note that the total size of the log files for all Alarm Notifiers (and Data
Loggers) on the i.LON 100 can not exceed the size of the flash memory stored in the
i.LON 100. The i.LON 100 will stop writing to the log files when it only has 256 Kb
of flash memory remaining.
<UCPTlogFormat>
Either LF_BINARY or LF_TEXT. This property determines whether the
log file will be generated as a binary file, or as a text file.
<UCPTemailAggregTime>
The time, in milliseconds, to wait after an alarm occurs before using the
email profiles defined for the Alarm Notifier. This may be useful if you
want to prevent multiple e-mails from being sent to the same address at
the same time.
The default value used if you do not define this property is 0. The
maximum value is 65,535 milliseconds.
NOTE: The <UCPTemailAggregTime> counter resets every time an
alarm occurs. Therefore, if multiple alarms occur before the aggregation
period expires, the emails for those alarms will be merged and sent as a
single email notification. The i.LON 100 will send the email
automatically after 100 alarms have been merged. This may be useful if
multiple alarms occur within a few moments of each other, but you
should take it into consideration before setting this property to a high
value.
<Point>
An alarm notification will occur each time any of the input data points
defined for an Alarm Notifier are updated, and the data point’s
<UCPTpointStatus> matches the status defined for any of the Alarm
Notifier’s active or passive alarm condition sets. You can specify as many
input data points as you like per Alarm Notifier.
The input data points for an Alarm Notifier are signified by a list of
<Point> elements in the <Data> parameter. For a description of the
properties that must be defined within each <Point> element, see Input
Data Points on page 8-10. You can specify as many input data points as
you want for each Alarm Notifier.
<Mail>
An e-mail profile contains an e-mail address, message text, subject
heading, and an attachment file. An e-mail message with the subject
heading, message text and attachment will be sent to the address
provided each time the e-mail profile is used.
You will reference these e-mail profiles when you set up the Alarm
Notifier’s active and passive alarm destination sets. You can create as
many e-mail profiles as you want for each Alarm Notifier, but each alarm
destination can reference only one e-mail profile.
The e-mail profiles for an Alarm Notifier are signified by a list of <Mail>
elements. For a description of the properties that must be defined within
each <Mail> element, see E-mail Profiles on page 8-13.