Event Type
Overview
Events can be the following types:
-
Occurrence/completion (Entry/Exit): Events which have a defined beginning and end, representing the beginning or end of a system state. The occurrence and completion are both time-stamped and logged in a history. For example, is an occurrence/completion event.
-
Instantaneous (Pulse): Events with no duration. Only the occurrence of the event is time-stamped and logged in a history. For example, a circuit breaker trip is an instantaneous event.
The event type cannot be customized.
Event Status Definition
The status of an event is active, inactive, or held. It depends on the event type and latch mode. The status of all events can be consulted at any time.
Latch Mode
An event can be unlatched or latched:
-
Unlatched: The event status is active while the cause of the event is present. It automatically returns to inactive when the cause of the event disappears or is resolved.
-
Latched: The event status does not automatically return to inactive when the cause of the event disappears or is resolved. It stays in the held state until it is reset by the user.
Activity
Certain events can be disabled so that the event is not taken into consideration by the TS trip system. In this case, the event is not logged in a history and does not generate an alarm.
Unlatched Occurrence/Completion Events
The following graph shows the event status for an unlatched occurrence/completion event:
A Event inactive
B Event active
1 Event occurrence: event is logged in a history and notified, depending on severity.
2 Event completion: event is logged in a history.
Latched Occurrence/Completion Events
The following graph shows the event status for a latched occurrence/completion event:
A Event inactive
B Event active
C Event held
1 Event occurrence: event is logged in a history and notified, depending on severity.
2 Event completion: event is logged in a history.
3 Event reset: reset command is logged in operation history. All held events are reset.
The following graph shows the event status for a latched event where a reset is attempted before completion of the event:
A Event inactive
B Event active
C Event held
1 Event occurrence: event is logged in a history and notified, depending on severity.
2 Event reset: reset command is logged in the operation history but has no effect on TS event 1 as external event is not completed.
3 Event completion: event is logged in a history.
4 Event reset: reset command is logged in the operation history. All held events are reset.
The following graph shows the event status for a latched, recurring occurrence/completion event:
A Event inactive
B Event active
C Event held
1 Event occurrence: event is logged in a history and notified, depending on severity.
2 Event completion: event is logged in a history.
3 Event reset: reset command is logged in the operation history. All held events are reset.
Unlatched Instantaneous Events
The following graph shows the event status for an unlatched instantaneous event:
A Event inactive
1 Event occurrence: event is logged in a history and notified, depending on severity.
Latched Instantaneous Events
The following graph shows the event status for a latched instantaneous event:
A Event inactive
C Event held
1 Event occurrence: event is logged in a history and notified, depending on severity.
2 Event reset: reset command is logged in the operation history. All held events are reset.
The following graph shows the event status for a latched, recurring instantaneous event:
A Event inactive
C Event held
1 Event occurrence: event is logged in a history and notified, depending on severity.
2 Event reset: reset command is logged in the operation history. All held events are reset.
Resetting Latched Events
Latched events can be reset by pressing the button on the front of the TS trip system for 3–10 seconds.
Reset commands do not target specific events. All held event states managed by the TS trip system are reset, and all trip cause LEDs are cleared.