GE B30 Communications Manual page 31

Ur family
Hide thumbs Also See for B30:
Table of Contents

Advertisement

CHAPTER 2: MODBUS COMMUNICATION
2.3.1.7 Reading fault report files
Fault report data has been available via the UR file retrieval mechanism since UR 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. The last 15 fault reports
are available for retrieval. It starts from 1 to 15, then if you have 18 reports, 3 to 18 are retrieved. A request for a non-
existent fault report file yields a null file. The current value fault report counter is available in "Number of Fault Reports"
Modbus register at location 3020h.
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
polling 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.
2.3.1.8 Reading PMU records
For URs that support PMU, familiarity with the PMU recording feature is required to understand the following description.
For example, see the PMU Recording and later sections in the N60 instruction manual.
The "PMU Recording Number of Triggers" register increments by one every time a new PMU record is triggered (captured)
on any of the PMU units in the relay (depending on the software option in the order code up to six PMUs can be available in
a relay). When a new trigger occurs, the associated PMU record file is assigned a file identifier based on the number of the
PMU module, the incremented value of this register module 1000 and the format of the COMTRADE file, as described here.
This register can be used to determine if any new data has been captured by periodically reading it to see if the value has
changed; if the number has increased then new data can be available.
The file "PMU_Records_List.txt" lists the available PMU records in the relay. This file can be retrieved by TFTP. This file
includes information about the file name for every PMU record in the relay.
The PMU records can be retrieved using the EnerVista software or by TFTP. The file name has the format
PMUp_xxxxn.eee
where
p is the PMU recorder instance
xxxx is the COMTRADE format shown in the following tables
n is the file sequence number in integer format from 1 to 999. The file sequence number is unique among all PMUs.
eee is the extension (cfg, dat, hdr, cff)
For example, to retrieve file 7 from PMU 3 in binary 16 bit CFF format, retrieve the file PMU3_16B7.cff.
Table 2-15: PMU records for IEEE C37.111-2013, by data format
Binary
Multiple files
PMUp_16Bn.cfg
PMUp_16Bn.dat
PMUp_16Bn.hdr
Single file
PMUp_16Bn.CFF
Table 2-16: PMU records for IEEE C37.111-1999, by data format
Binary
Multiple files
PMUp_n.cfg
PMUp_n.dat
PMUp_n.hdr
UR FAMILY – COMMUNICATIONS GUIDE
Binary32
Float32
PMUp_32Bn.CFG
PMUp_32Fn.CFG
PMUp_32Bn.DAT
PMUp_32Fn.DAT
PMUp_32Bn.HDR
PMUp_32Fn.HDR
PMUP_32Bn.CFF
PMUp_32Fn.CFF
ASCII
PMUp_An.cfg
PMUp_An.dat
PMUp_An.hdr
FILE TRANSFERS
ASCII
PMUp_###An.cfg
PMUp_###An.dat
PMUp_###An.hdr
PMUp_###An.cff
2
2-11

Advertisement

Table of Contents
loading

This manual is also suitable for:

D30D60F35F60G30G60 ... Show all

Table of Contents