![Eaton Power Xpert PXR 10 Manual Download Page 77](http://html1.mh-extra.com/html/eaton/power-xpert-pxr-10/power-xpert-pxr-10_manual_4153055077.webp)
9 Modbus RTU – integrated Modbus port specification
9.3 Modbus register map
PXR Electronic trip unit
01/21 MN012005EN
www.eaton.com
73
9.3.7 Remote control
A range of registers is reserved for the remote control of the release, starting
with 402901/425089 to 402903/425091. These three registers should be
written using function code 16, together with a “slave action code” and the
corresponding ones’ complement. The data format registers are shown
below.
Data format for remote control
Register 402901 (0x6200)
Register 402902 (0x6201)
Register 402903 (0x6202)
The “slave action code” and its functioning are listed in
table 34, and
whether it is supported depends on the specific product.
If the “slave action code” and the associated ones’ complement command
are valid, the release will perform the action in question. Check breaker
status to verify if the requested action has been executed successfully. If so,
it will return a normal function code 16 response to the Modbus master.
Since it may take some time for the release to become active, the Modbus
master can also query the release (e.g. by reading its status) to determine
whether the slave action function has been successfully completed following
the normal response. If the “slave action code” and the associated ones’
complement command are invalid, the release will return the exception
code 03.
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Byte 1 (slave action)
Byte 0 (slave action)
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Ones’ complement of byte 0 (slave action)
Byte 2 (slave action)
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Ones’ complement of byte 2 (slave action)
Ones’ complement of byte 1 (slave action)