Ormazabal ekor.rpa Series, General Instructions Manual, Page: 80 / 116

IG-267-EN versión 01; 07/04/2017
80
Log record General Instructions
ekor
.rpa
10. Log record
The logic equipment is organised into functional modules, as
indicated previously, grouped together in accordance with
their condition, meaning any type of data is represented in
a specific structure with a specific name. The classification for the different types of data is:
• Digital signals: TYPE/GROUP or CLASS/SUBGROUP or
NODE/NUMBER SIGNAL
• Meterings: TYPE/GROUP or CLASS/SUBGROUP or NODE/
METERING
10.1. Fault report
The system stores 10 fault records in a circular buffer,
meaning the last 10 faults seen by the system are always
stored. The fault reports are issued in text format, meaning
they can be displayed in any text-based programme.
A summary of each report is shown in the display with the
most relevant data.
The filename includes:
(System fault number_Name type of record_Date_
Time_Fault number.txt)
aaaa_Faults_dd-mm-aa_hh-mm-ss-ms_vv_.txt
10.1.1. Data capture logic
Starting from idle status, the system opens a new fault
report every time a unit starts up. This new report is correct
if the unit gives a tripping order.
If start-up fails and the system does not generate a trip, the
report is discarded and not saved.
Whenever several units start up during a fault, they are all
entered in the same fault record.
The reasons for closing a report after tripping are:
• Fault open successfully.
• Fault not cleared successfully. In this case, it waits for a
second after the trip before closing the report.
• Loss of system power before fault end.
In any of the cases above, each report will set out the
reason for closing the report.
The entries programmed as "external trip" also generate a
fault report.
Each fault report contains information on the 60 milliseconds
prior to the start-up which opens the new fault report,
meaning we can see the status prior to the start of fault.
1
Fault report capture window
2
Start of capture
3
Start of fault
4
End of capture
Figure 10.1. Faults