TPU2000/2000R Modbus/Modbus Plus/ Modbus TCP/IP Automation Guide
130
Register
Address
Item
Description (Multiplier if any)
42598
All Harmonic Phase B-Winding 3
Unsigned 16 Bit (X 2)
42599
2nd Harmonic Phase B-Winding 3
Unsigned 16 Bit (X 2)
42600
5th Harmonic Phase B-Winding 3
Unsigned 16 Bit (X 2)
42601
All Harmonic Phase B-Winding 3
Unsigned 16 Bit (X 2)
42602
I restraint Phase A-Winding 3 (Ang)
Unsigned 16 Bit
42603
I restraint Phase B-Winding 3 (Ang)
Unsigned 16 Bit
42604
I restraint Phase C-Winding 3 (Ang)
Unsigned 16 Bit
Event Records (11 Registers Defined)
Event Record data is stored in the same manner as the Fault Record Data. Figure 24 illustrates the method of
storage of the Event Record Data. As illustrated, 128 Groups of fault data is stored internal to the
TPU2000/2000R. Each group is comprised of 11 registers of data as defined in Tables 23 and 24 below. The
register for pointing to a group is defined in Register 42049. Fault records are viewed by writing a data word to
42049 as defined in the table below and reading the block of consecutive registers from 42050 through 42059.
If the number of Operation Records exceed 128, then the buffer overwrites the oldest record contained within its
internal stack. Access and control can be accomplished over Modbus in one of two methods.
If 42049 has a value of 1 written to it, Registers 42050 through 42059 will fill with the FIRST Operation record
within the 128 records stored in the unit. 42049 will then reset to a value of 0 when Registers 42050 through
42059 are read.
If 42049 has a value of 2 written to it, Registers 42050 through 42059 will contain the NEXT record of Operation
Record data which was pointed after the write command executed. 42049 will reset to a value of 0 after the record
has entered the buffer and is read by the host.
If 42049 has a value of 3 written to it, Registers 42050 through 42059 will fill with the LAST UNREPORTED
record of Operation Record data in the 128 records of fault data stored in the unit. For example, if two records of
data accumulated between reads, a read LAST UNREPORTED record command would point to the oldest
unreported record of data accumulated in the buffer. The host could then send another value of 3 to the control
register to obtain the newest value of the unreported record. A write of 3 to the fault record also would fill the
buffer with a value of zero to indicate there are no other values to be retrieved from the buffer. The number of
unreported operation records may be read from Modbus register XXXX.
If no data accumulated within the fault record, (such as after a system reset), values of 0 shall be returned in the
buffer. A new fault record entry is indicated via Bit 8 of Register 40129 being set to a 1. Reference Table 5-9 of
this document for a more detailed explanation of the registers bit map.
As with fault records, there are two methods of obtaining the information via the Modbus 23 (Write/Read)
command or a combination of the Modbus 16 (Write Register) and 03 (Read Register) commands.
METHOD 1:
The host writes a Modbus 23 Command (Modbus 4X Register Read/Write) in which a control code (1, 2,
or 3) is written to 42049 and the buffer is filled with fault data in Registers 42050 through 42059 to be
returned in response to the command. A command of 1 = Points to the First Record in the Fault Table. A
command of 2 Points to the next fault in the fault table. A command of 3 points to the last UNREPORTED
fault in the fault table.
METHOD 2:
The host writes a Modbus Command 16 (Modbus 4X Register Write Command) in which a control code
(1, 2, or 3) is written to 42049 and the buffer is filled with fault data in Registers 42050 through 42059.
Within 10 seconds after the 16 command is issued, the host issues a Modbus 03 command (Modbus 4X
Register Read command) in which the fault data is retrieved from the buffer in Register 42050 through
42059.
