Date Code 20010518 “Job Done” Examples - (Example 4) 4-37
SEL-2020 Instruction Manual
EXAMPLE 4: ARCHIVE EVENT REPORTS TO NONVOLATILE FLASH MEMORY
I
NTRODUCTION
This example assumes you have SEL relays connected to several of the SEL-2020 ports, as in the
previous examples, and also that the SEL-2020 is equipped with optional nonvolatile Flash
memory. The nonvolatile Flash memory is required for long-term data storage capable of
archiving multiple records. This example demonstrates another unique feature of the SEL-2020:
the ability to count the number of summary event reports received from an SEL relay, and then
retrieve that number of long event reports to store in the SEL-2020 database.
IDENTIFYING THE PROBLEM
In response to summary event reports, you want the SEL-2020 to request long event reports from
all attached relays and archive them as unique records in nonvolatile memory.
DEFINING THE SOLUTION
Set the SEL-2020
Figure 4.6 is a functional model showing how long event reports can be archived in SEL-2020
memory. To accomplish this function, follow these steps:
1. Use the SET U command to enable the pre-defined user-defined command 20EVENT on
Port 1. 20EVENT is a pre-defined string for user-defined commands that asserts the
corresponding CMDx bit when the SEL-2020 receives a summary event report. See
Section 8: Message Strings for a list of pre-defined strings and more detailed information
about strings.
2. On Port 1, use the SET A command to enable archiving of data, and to define the issue
condition CMD1 to trigger event report collection (using the 20EVENT setting).
3. Use the COPY ALL command, as in previous examples, to copy these settings to all ports
where you want event report data collected. If connected IEDs are not identical, auto-
configure the ports. If they are identical, adjust port IDs and check all settings.