Date Code 970103 Event Reporting 4-1
SEL-251, -2, -3 Instruction Manual
SECTION 4: EVENT REPORTING
EVENT REPORT GENERATION
The relay generates a summary and long event report in response to the actions listed in Table
4.1. The summary event report allows a quick review of the information necessary to determine
fault type and location. The long event report displays eleven cycles of information for
analyzing system and scheme performance.
Table 4.1: Event Report Triggering Actions
• Programmable event report triggering variable (ER) assertion
• TRIGGER command execution
• ET (External Trigger) input assertion
• TRIP output contact assertion
The relay generates a second summary and long event report for the same fault if the trip occurs
after the end of the first report.
Relay elements which trigger event reports must drop out for at least four cycles before they can
initiate another event report. This helps to eliminate multiple records for boundary faults.
Triggering is recorded to the nearest quarter-cycle and referenced to the 16th row of data in the
report. All reports trigger at row 16. This system allows you to determine the total duration of a
long fault which triggers two event reports. Simply calculate the time difference between the
report generated at fault inception by ER (the programmable event report triggering variable) and
the report generated by the TRIP.
SUMMARY EVENT REPORT
The summary report is automatically transmitted from port(s) designated AUTOMATIC
regardless of access level, as long as the designated port has not timed out. If automatic
transmissions are monitored by a dedicated channel or printed on a dedicated printer, enter zero
for the timeout setting of the appropriate port.
Due to the length of the full report, it is not automatically transmitted. You can display the full
report with the EVENT command.
To Next Page
Loading...
