EVENT REPORTING
INTRODUCTION
The SEL-267D relay transmits a summary event report in response to several events and
saves a full event report in its memory. The summary report includes the identifier message
entered at the beginning of the setting procedure as well as date, time, and type of event. If
the event is a fault, the report displays fault location in miles, secondary ohms, fault duration,
and a maximum fault current measurement. The report includes fault targets if the fault
caused a trip (a setting permits disabling the fault locator).
The summary report is automatically transmitted from the designated automatic port (refer to
AUTO setting) regardless of access level, as long as that port has not timed out. If the
automatic transmissions are monitored by a dedicated channel or printed on a dedicated
printer, enter zero for the timeout interval of the appropriate port (refer to TIME1, TIME2
settings).
The full report contains current and voltage information from which phasor diagrams of the
prefault, fault, and postfault conditions may be constructed. It also contains status points
spanning the states of all relay elements, inputs, and outputs. These are useful in reviewing
fault duration, relay element responses, arrival time of transfer-trip signalling with respect to
local relay response, etc.
The full report is not transmitted automatically due to its length (about one page). You may
request a full report with the EVENT command, e.g., EVENT 1.
The twelve most recent events are stored in relay volatile memory. These data are retained as
long as the control power remains on. This differs from the relay settings, which are retained
in nonvolatile memory. Settings are retained until changed by the SET command, regardless
of control power cycling. You may quickly review stored events with the HISTORY
command.
Event reporting is triggered by any of the following:
Fault in any zone
Input Assertion of DIRECT TRIP input
Assertion of BLOCK TRIP input
Assertion of PERMISSIVE TRIP input
Assertion of EXTERNAL TRIGGER
Execution of OPEN command
Execution of TRIGGER command
Another event report is triggered for the same fault if the trip occurs after the end of the first
report.
Date Code 920326
Event Reporting
SEL-267D/167D Instruction Manual
4 - l
Summary of Contents for SEL-167D
Page 3: ......
Page 6: ......
Page 8: ......
Page 9: ......
Page 10: ......
Page 11: ......
Page 51: ...LOGIC DIAGRAMS Date Code 920326 Specifications SEL 267D 167D Instruction Manual 2 31 ...
Page 52: ...Date Code 920326 Specifications 2 32 SEL 267D 167D Instruction Manual ...
Page 53: ...Date Code 920326 Specifications SEL 267D 167D Instruction Manual 2 33 ...
Page 54: ...Date Code 920326 Specifications SEL 267D 167D Instruction Manual 2 34 ...
Page 88: ...SAMPLE EVENT REPORT ...
Page 114: ......
Page 115: ......