Technical Reference Manual - InduSoft

Alarms, Events, and Trends
Option
Custom Messages
System Warning
Description
Events generated by calling the SendEvent
function.
Various runtime warnings and errors, including:
• Errors that occur when sending alarms by email
• Tag was blocked/unblocked
• Division by zero
• Connection/Disconnection of the remote
security system
5. To log changes in specific project tags, select Tags, and then in the table, specify the tags.
Column
Description
Tag Name
Dead Band
The name of the project tag that you want to log to
the history file.
A value to filter changes against, so that only
changes greater than this value are logged.
For example, if you specify a Dead Band value of 5
for a tag value of 50 and the tag value changes to
52, then the system will not register this variation
in the event log, because the change is less than
5. However, if the tag value change is equal to or
greater than 5, then the system will log the new
value to the history file.
Message
A string (message) related to this tag change. You
can specify tags in messages using the {tagname}
syntax.
The Tags option is useful for logging events that are not important enough to be alarm conditions (for
example, Motor On, Motor Off, and so on).
6. Click OK.
By default, the event log is saved as a series of text files in your project's Alarms folder. For more information,
see Format of the event log.
Alternatively, you can save the event log to an external SQL database. For more information, see Saving your
event log to an external database.
Saving your alarm history / event log to an external database
By default, your project's alarm history and event log are saved to proprietary-format text files in your
project's Alarms folder. However, you can change your project settings to save them to an external SQL
database instead.
1. On the Project tab of the ribbon, in the Settings group, click Options.
InduSoft Web Studio Page 251