EasyManua.ls Logo

Eaton Power Xpert Release PXR 20 - Date and Time; Event Registers

Eaton Power Xpert Release PXR 20
58 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
46
9. Modbus register map
POWER XPERT® RELEASE TRIP UNIT FOR MAGNUM PXR CIRCUIT BREAKERS MN013015EN January 2022 www.eaton.com
Table 28 shows the list of commands available. The PW
column indicates if the password must be written before
issuing the command.
Table 28. Modbus remote control commands.
Register number 402901 402902 402903
Address (hex) 0B56 0B55 0B54
Definition PW Command (hex)
Reset trip No 0x0002 0xFD00 0xFFFF
Reset powered up indication No 0x0003 0xFC00 0xFFFF
Reset peak demand watts Yes 0x0004 0xFB00 0xFFFF
Reset energy Yes 0x0008 0xF700 0xFFFF
Reset operations count Yes 0x0102 0xFD00 0xFFFE
Reset runtime Yes 0x0103 0xFC00 0xFFFE
Reset min/max currents Yes 0x010D 0xF200 0xFFFE
Reset min/max line-to-neutral
voltages
Yes 0x010F 0xF000 0xFFFE
Reset min/max line-to-line
voltages
Yes 0x010E 0xF100 0xFFFE
Reset all min/max values Yes 0x0104 0xFB00 0xFFFE
Reset trip count Yes 0x0501 0xFE00 0xFFFA
Reset temperature Yes 0x0502 0xFD00 0xFFFA
Reset all diagnostics
information
Yes 0x0503 0xFC00 0xFFFA
Open breaker - activates the
relay mapped to open breaker
pulsed
Yes 0x0000 0xFF01 0xFEFF
Close breaker - activates the
relay mapped to close breaker
pulsed
Yes 0x0001 0xFE01 0xFEFF
Enable maintenance mode No 0x0008 0xF701 0xFEFF
Disable maintenance mode No 0x0009 0xF601 0xFEFF
Activate relay 1 (if relay 1 is
mapped to remote control)
No 0x0101 0xFE04 0xFBFE
Deactivate relay 1 (if relay 1 is
mapped to remote control)
No 0x0201 0xFE04 0xFBFD
Activate relay 2 (if relay 2 is
mapped to remote control)
No 0x0102 0xFD04 0xFBFE
Deactivate relay 2 (if relay 2 is
mapped to remote control)
No 0x0202 0xFD04 0xFBFD
Activate relay 3 (if relay 3 is
mapped to remote control)
No 0x0103 0xFC04 0xFBFE
Deactivate relay 3 (if relay 3 is
mapped to remote control)
No 0x0203 0xFC04 0xFBFD
9.6 Date and time
The date and time are available via registers. The Modbus
client can synchronize the clock in the trip unit by writing the
time at regular intervals. The entire block of registers should
be written in a single command. A time change event is only
generated when the time difference between old and new is
greater than 60 seconds.
Table 29. Modbus date and time data.
Function
code
Register
number
Address
(hex)
Definition Value range
3, 4, 6, 16 2921 0x0B68 Month 1-12
3, 4, 6, 16 2922 0x0B69 Day 1-31
3, 4, 6, 16 2923 0x0B6A Year 2015 - 2099
3, 4, 6, 16 2924 0xB6B Day of week 1 = Sunday,
7 = Saturday
3, 4, 6, 16 2925 0x0B6C Hour 0-23
3, 4, 6, 16 2926 0x0B6D Minute 0-59
3, 4, 6, 16 2927 0x0B6E Second 0-59
9.7 Event registers
The triggering of an event in the trip unit can provide histori-
cal data object values at the instant in time the event occurs
or occurring around the time of the event. The trip unit
categorizes the event information into summary, alarm, and
trip event data. A maximum of 200 summary events, 10
alarm events, and 10 trip events are stored. A single event
may place information into multiple objects. For example,
the occurrence of an event triggered by a circuit breaker trip
may provide both summary and trip information.
Access to event information is based on the selection of
event type and event ID. When the event type selection is
written in register 8193, the earliest and latest event ID can
be obtained in registers 8194 and 8196 respectively to deter-
mine the range of events saved for the selected event type.
Register 8198 is used to select the requested event ID. If
the request event exists in the trip unit, registers 8200
and 8202 provide the Previous Event ID and Next Event ID
respectively. If the requested event does not exist in the trip
unit, exception code 0x87 is returned.
The date and time when the requested event happened is
read in registers 8204 through 8211. This value corresponds
to the time of occurrence of the historical event.
Register 8212 provides an indication of the selected event
type’s data content. This is a constant value for the three
event types Modbus port supports.
Event data also provides a validity bit for each data object,
starting from register 8213. Bit 0 set to be 1 indicates that
the first data object is valid, bit 1 is used to indicate the
second data object is valid, and so on.

Table of Contents

Related product manuals