About InTouch events
- Last UpdatedJun 25, 2024
- 1 minute read
An event is a detectable occurrence of something happening within the system, which may or may not be associated with an alarm. A transition into or out of an alarmed state is one kind of event. An event might also be an operator action, a change to the system configuration, or some kind of system error.
An event is different than a condition. A condition can persist for minutes, hours, days, or weeks. An event is momentary; it takes place and is immediately over. An alarm is a condition; an alarm notification is an event.
Events represent normal system status messages and do not require an operator response.
When you define a tag to do event monitoring, you can choose to have event messages printed or logged to the alarm system each time the tag value changes. The event message includes how the value changed and whether the operator, I/O, scripts or the system initiated the change.
An event can be one of the following types:
|
Event |
Condition |
|---|---|
|
OPR |
The operator modified the tag value using the Value input. |
|
LGC |
A QuickScript modified the tag value. |
|
DDE |
The tag value was poked from a DDE client. |
|
PROT |
The tag value change was initiated from an Industrial graphic, either from a custom property or from a pushbutton in the Industrial graphic. |
|
SYS |
A system event occurred. |
|
USER |
$Operator changed. |
The SYS and USER events are generated by the system regardless of whether event logging is enabled for any tags. DDE, OPR, and LGC events relate to tag values and are only generated for tags that have event logging enabled.