B.3 FILE TRANSFERS
d) READING DATA LOGGER FILES
Familiarity with the data logger feature is required to understand this description. Refer to the DATA LOGGER section of
Chapter 5 for details. To read the entire data logger in binary COMTRADE format, read the following files.
To read the entire data logger in ASCII COMTRADE format, read the following files.
To limit the range of records to be returned in the COMTRADE files, append the following to the filename before writing it:
To read from a specific time to the end of the log: <space> startTime
To read a specific range of records: <space> startTime <space> endTime
Replace <startTime> and <endTime> with Julian dates (seconds since Jan. 1 1970) as numeric text.
e) READING EVENT RECORDER FILES
To read the entire event recorder contents in ASCII format (the only available format), use the following filename:
To read from a specific record to the end of the log, use the following filename:
EVTnnn.TXT (replace "nnn" with the desired starting record number)
f) READING FAULT REPORT FILES
Fault report data has been available via the UR file retrieval mechanism since firmware version 2.00. The file name is
faultReport#####.htm. The ##### refers to the fault report record number. The fault report number is a counter that
indicates how many fault reports have ever occurred. The counter rolls over at a value of 65535. Only the last ten fault
reports are available for retrieval; a request for a non-existent fault report file will yield a null file. The current value fault
report counter is available in "Number of Fault Reports" Modbus register at location 0x3020.
For example, if 14 fault reports have occurred then the files faultReport5.htm, faultReport6.htm, up to
faultReport14.htm are available to be read. The expected use of this feature has an external master periodically poll-
ing the "Number of Fault Reports' register. If the value changes, then the master reads all the new files.
The contents of the file is in standard HTML notation and can be viewed via any commercial browser.
The COMMAND password is set up at memory location 4000. Storing a value of "0" removes COMMAND password protec-
tion. When reading the password setting, the encrypted value (zero if no password is set) is returned. COMMAND security
is required to change the COMMAND password. Similarly, the SETTING password is set up at memory location 4002.
These are the same settings and encrypted values found in the
menu via the keypad. Enabling password security for the faceplate display will also enable it for Modbus, and vice-versa.
To gain COMMAND level security access, the COMMAND password must be entered at memory location 4008. To gain
SETTING level security access, the SETTING password must be entered at memory location 400A. The entered SETTING
password must match the current SETTING password setting, or must be zero, to change settings or download firmware.
COMMAND and SETTING passwords each have a 30-minute timer. Each timer starts when you enter the particular pass-
word, and is re-started whenever you "use" it. For example, writing a setting re-starts the SETTING password timer and
writing a command register or forcing a coil re-starts the COMMAND password timer. The value read at memory location
4010 can be used to confirm whether a COMMAND password is enabled or disabled (0 for Disabled). The value read at
memory location 4011 can be used to confirm whether a SETTING password is enabled or disabled.
COMMAND or SETTING password security access is restricted to the particular port or particular TCP/IP connection on
which the entry was made. Passwords must be entered when accessing the relay through other ports or connections, and
the passwords must be re-entered after disconnecting and re-connecting on TCP/IP.
L90 Line Differential Relay
GE Power Management