IL01301034E
IL01301034E
IL01301034E
Disclaimer of warranties
and limitation of liability Effective August 2009
Instructional Leaflet IL01301034E Supersedes March 2008
The information, recommendations, THE ENTIRE OBLIGATION OF EATON.
descriptions, and safety notations in THE CONTENTS OF THIS DOCUMENT
this document are based on Eaton
Corporation’s (“Eaton”) experience
and judgment, and may not cover all
SHALL NOT BECOME PART OF OR
MODIFY ANY CONTRACT BETWEEN Installation instructions for Series NRX
THE PARTIES.
contingencies. If further information is
required, an Eaton sales office should In no event will Eaton be responsible to
the purchaser or user in contract, in tort
Modbus communications adapter
be consulted.
Sale of the product shown in this literature
(including negligence), strict liability, or
otherwise for any special, indirect,
module (MCAM)
is subject to the terms and conditions incidental, or consequential damage or
outlined in appropriate Eaton selling loss whatsoever, including but not limited
policies or other contractual agreement to damage or loss of use of equipment,
between Eaton and the purchaser. plant or power system, cost of capital,
loss of power, additional expenses in the The MCAM communicates to a master
THERE ARE NO UNDERSTANDINGS,
AGREEMENTS, WARRANTIES, use of existing power facilities, or claims WARNING on a Modbus network using the Modbus
EXPRESSED OR IMPLIED, INCLUDING against the purchaser or user by its (1) ONLY QUALIFIED ELECTRICAL PERSONNEL RTU (remote terminal unit) protocol.
WARRANTIES OF FITNESS FOR customers resulting from the use of SHOULD BE PERMITTED TO WORK ON THE Information is exchanged through the
A PARTICULAR PURPOSE OR the information, recommendations, and EQUIPMENT. MCAM between the Modbus master
MERCHANTABILITY, OTHER THAN descriptions contained herein. (2) ALWAYS DE-ENERGIZE PRIMARY AND and the Series NRX trip unit using
THOSE SPECIFICALLY SET OUT IN ANY The information contained in this manual SECONDARY CIRCUITS. assigned registers.
EXISTING CONTRACT BETWEEN THE is subject to change without notice. (3) DRAWOUT CIRCUIT BREAKERS SHOULD BE
PARTIES. ANY SUCH CONTRACT STATES REMOVED FROM THEIR DRAWOUT CASSETTE.
(4) ALL CIRCUIT BREAKERS SHOULD BE
SWITCHED TO THE OFF POSITION AND
MECHANISM SPRINGS DISCHARGED.
FAILURE TO FOLLOW THESE STEPS FOR
ALL PROCEDURES DESCRIBED IN THIS
INSTRUCTION LEAFLET COULD RESULT
IN DEATH, BODILY INJURY, OR PROPERTY
DAMAGE.
Section 1: General
information
The Series NRX姠 Modbus姞
communications adapter module
(Figure 1) is an accessory that will
operate as a communicating device in
conjunction with a compatible Series Figure 1. Series NRX Modbus
NRX trip unit/breaker in a master Communications Adapter Module
communications network (Figure 2).
Eaton Corporation
Electrical Sector
The catalog number of this module
1000 Cherrington Parkway is MCAM.
Moon Township, PA 15108
United States
877-ETN-CARE (877-386-2273)
Eaton.com
Figure 3. Step 1
Table 12. Cause-of-Status Code Definitions Step 2: Carefully slide the alignment
bracket out from between any mounted
Code Definition Code Definition
terminal blocks and put it aside with its
0 Unknown 65 Reverse power mounting hardware for re-installment after
1 Normal operating mode 66 Fixed instantaneous phase overcurrent #2
the communications adapter module is
connected to the DIN rail.
3 Instantaneous phase overcurrent 67 Reverse phase
11 Overvoltage 68 Reverse sequence
12 Undervoltage 69 Phase current loss
15 Underfrequency 71 Alarm active
16 Overfrequency 72 Bad frame
17 Current unbalance 73 Phase currents near pickup
Mounting Screw
18 Voltage unbalance 75 Making current release
Figure 6. Step 4
19 Apparent power factor 76 Fixed instantaneous phase overcurrent #3
26 Power demand 77 Set points error Step 5: Tilt the communications module
27 VA demand 78 Over-temperature Figure 4. Step 2 forward to engage the upper part of the
DIN rail, and then snap it back into the
30 Total harmonic distortion 80 Long delay neutral overcurrent DIN rail for complete engagement.
Step 3: Remove the terminal block
31 Operations count 82 Historical data in location 19/20 by inserting a small
screwdriver in the recessed area in the
33 Control via communications 84 Ground fault (instantaneous or delay)
top front of the terminal block as shown,
37 Coil supervision 85 Earth fault (instantaneous or delay) and gently pry down to release and
39 RAM error 146 Frequency out of range
remove the block from the DIN rail.
2. The maximum system capacity is Table 9. Diagnostic Table 10. Primary Status
4,000 feet of communications cable Sub-Function Numbers Code Definitions
and 247 devices on the Modbus
Sub-Function Code Definition
RTU network. No. (Decimal) Name
0 Unknown
3. Make sure there is twisted-pair wire 0 Echo query
that is recommended for Modbus RTU 1 Open
network use. Use shielded twisted- 1 Restart communications
2 Closed
pair wire to connect each slave to the 4 Force listen
Modbus RTU network, daisy-chain 3 Tripped
style. The polarity of the twisted pair 10 Clear MCAM/slave product counters
4 Alarmed
Figure 8. Step 6 is CRITICALLY important. 11 Modbus UART bus message count
13 Pickup
12 Modbus UART communication error
Step 7: A mounted communications Section 4: Modbus count
module appears as shown and the communications adapter 13 MCAM exception error count
installation procedure is complete. The Table 11. Secondary Status
module can now be wired in keeping with module connections 14 MCAM message count Code Definitions
the information presented in Section 3. 15 MCAM no response count Code Definition
WARNING 16 MCAM NAK count 0 Unknown
ALL APPLICABLE SAFETY CODES, SAFETY
17 MCAM busy count 3 Test mode
STANDARDS, AND SAFETY REGULATIONS
MUST BE STRICTLY ADHERED TO WHEN 18 Modbus UART over run error count 7 Powered up
INSTALLING, OPERATING, OR MAINTAINING
20 Clear Modbus UART counters 8 Alarm
THIS EQUIPMENT. FAILURE TO COMPLY
COULD RESULT IN DEATH, BODILY INJURY, 21 Slave product checksum error count
OR PROPERTY DAMAGE. 22 Slave product over run count
Table 7. Control ‘Slave Action Number’ Definitions Table 2. Modbus Connector MicroController LED (Status)
Pin-Outs
Control Group Definition Byte 2 Byte 1 Byte 0 This indicator will be flashing green
Pin Number Input Signal whenever the module is powered
Reset Reset trip 0 0 2
1 RS-485 Network-B (non-inverting) up and when the microprocessor is
Reset (peak) demand-watts 0 0 4 executing instructions. When the Series
2 RS-485 Network-A (inverting) NRX Modbus communications adapter
Reset (synchronize) demand watts window 0 0 64 (4016)
3 Common module is connected to a Series NRX
Snapshot command 0 0 128 (8016) trip unit for the first time, this LED will
4 Shield alternately flash red and green to signal a
Reset (peak) demand-currents 0 1 1
This 4-pin connector provides the interface to the learning process between both units. This
Reset all min./max. values 0 1 4 Modbus network. automatic process will take approximately
Unlock waveform buffer (clear upload-in-progress) 0 1 5 Connect shield wire to ground at master device end only. 15 seconds and occurs only once during
Interconnect shielding where devices are daisy-chained. the initial startup. The LED will also flash
Reset min./max. currents 0 1 13 red if the module is not connected to or
Reset min./max. PF-apparent 0 1 16 unable to communicate with a Series NRX
Circuit breaker Open request 1 0 0
Section 5: Jumpers and trip unit.
open-close indicator LEDS Modbus RS-485 network Tx LED
Close request 1 0 1
Refer to Figure 10 to become familiar (Transmit)
Enable Maintenance Mode 1 0 8
with specific jumper and LED locations This LED will be lit whenever the
Disable Maintenance Mode 1 0 9 on the Modbus communications module is transmitting on the Modbus
adapter module. RTU network.
Table 8. Date and Time Register Definitions Modbus RS-485 network Rx LED
(Receive)
Register Number Register Address Data Range
Definition (Decimal) (Hexadecimal) (Decimal) This LED will be lit whenever the
module is receiving from the Modbus
Month 402921 0B68 1–12 RTU network.
Day 402922 0B69 1–31
Modbus control jumper
Year 402923 0B6A
This jumper provides the user with a
Day of week 402924 0B6B 1=Sunday...7=Saturday
means of enabling or disabling remote
Hour 402925 0B6C 0–23 communication control commands to the
LEDs Series NRX trip unit. With jumper placed
Minute 402926 0B6D 0–59
in the ENABLE position, remote Open
Second 402927 0B6E 0–59 and Close Breaker commands can be
acted upon. With the jumper in the
1/100th second 402928 0B6F 0–99
DISABLE position, these commands
will not be accepted.
Jumper
Plug for
Source
Source/residual ground
Sensing selection jumper
Jumper Plugs for This jumper selects the protection
Communicaton Control configuration for Series NRX trip units
with ground fault protection or ground
Figure 10. Modbus Communications fault alarm functionality. Consult Series
Adapter Module (Front View Closeup) NRX trip unit instructions (IL 70C1619)
for further information on ground sensing.
This jumper is not applicable and does
not function for non-ground fault style
trip units.
Shield
24 Vdc –
NW +
Open
NW –
COM
Close
Comr
Figure 11. Series NRX Modbus Communication with Digitrip 520M Invalid object access configuration R/W 42001 425345 07D0 6300 1
Floating Pt data word order configuration R/W 42002 425346 07D1 6301 1
Fixed Pt data word order configuration R/W 42003 425347 07D2 6302 1
Supervisory control query R/W 42901 425089 0B54 6200 3
Date and time registers R/W 42921 0B68 8
Com
Open
Close
Cause 404610 or 406146 1201 or 1801 x x
Current IA A 404611 406147 1202 1802 10 x x
Address
communications protocol Modbus Register Modbus Register Modbus
SP00 Objects (Complete List) Number Address Products
Range In order to satisfy the MCAM
001–247 Fixed
communications needs, please refer
Fixed IEEE Point FP Series Series
to the following reference material: IEEE Point Float (FP) Scale NRX NRX
“Modicon Modbus Protocol” Name Numeric Units Float (FP) (Hex) (Hex) Factor 520M 1150
http://www.modicon.com/techpubs/toc7. Frequency Freq Hz 404661 406197 1234 1834 10 x
html
Power Peak demand W 404697 406233 1258 1858 1 x
Baud Rate The contents of Modbus registers
SP01 Real 3-phase W 404715 406251 126A 186A 1 x
00–03 are product objects (for example, IA—
phase A current). The MCAM ensures (power)
that unique objects reside in identical Power pf pf 404717 406253 126C 186C 100 x
registers independent of Eaton products. factor
Consequently, Eaton products use a
single register map of objects (Table 4 Product ID Prod ID 404719 or 406255 126E or 186E x x
or Table 5). Frequency Freq Hz 404721 406257 1270 1870 100 x
SP02 Parity
00–02
Objects occupy two registers except (K) Energy Forward KWh N/A 406259 N/A 1872 1 x
for certain energy (real and reactive)
objects. These energy objects occupy Reverse KWh N/A 406261 N/A 1874 1 x
four registers. The MCAM can support a Total KWh N/A 406263 N/A 1876 1 x
maximum of 122 registers within a single
Modbus transaction. Apparent KVAh N/A 406271 N/A 187E 1 x
To accommodate Modbus masters that Energy Forward Wh N/A 406305 N/A 18A0 1 x
can only access to register 9999, some (four reg.
SP03 Stop Bit Reverse Wh N/A 406309 N/A 18A4 1 x
objects)
00–01 Eaton registers initially assigned above
Total Wh N/A 406313 N/A 18A8 1 x
9999 have been assigned dual access,
both at the original register (to provide Apparent VAh N/A 406329 N/A 18B8 1 x
compatibility) and at a new register
Figure 13. Setting Sequence Note: Objects are two registers in length unless specified otherwise.
assignment below 9999. The format
Programming Flow Chart for is given as low/high register numbers The primary and secondary codes are mapped to the high and low bytes, respectively, of registers 404609 (1200 ) and 406145
16
Series NRX 520M Trip Unit followed by (low16/high16 Modbus register (180016). The primary status codes are shown in Table 10. The secondary status codes are shown in Table 11. The cause-of-
status codes are mapped to registers 404610 (120116) and 406146 (180116). The cause-of-status codes are shown in Table 12.
addresses). An example is: 4xxxx/4yyyyy The primary/secondary and cause-of-status must be read as a single two register object.
Table 3. MCAM Communications (XXXX+116/YYYY+116). Refer to Table 6. These numeric entries have specific definitions dependent on the particular Eaton product.
Setting Ranges Only the RTU communications mode is
recognized by the MCAM.
Setting Allowable
Number Range
Function codes
Communication SP00 001–247
address The MCAM responds to a limited number
of Modbus function codes. These are
Baud rate SP01 00 = 1200 function codes 03, 04, 06, 08, and 16
01 = 4800 (1016). Function codes 03 and 04 are
02 = 9600 used interchangeably to obtain register
03 = 19200 data. Function code 06 can only be
Parity SP02 00 = None used to set the few single configuration
01 = Odd registers (Section <Register Access
02 = Even Configuration>).
Stop bit SP03 00 = 1 bit
01 = 2 bits
Table 4. Modbus Register Map in Register Number Order Block of registers Register access configurations
Modbus Register Modbus Register Modbus A block of registers (from the register Non-volatile register 42001/425345
Objects (Complete List) Number Address Products column of Table 4 or Table 5) can be (07D016/630016) is used to configure the
Fixed established in the MCAM to remap the MCAM to respond to a group of data
IEEE Point FP Series Series object registers of an Eaton product. objects, of which some objects are invalid
IEEE Fixed Float (FP) Scale NRX NRX The block of registers list is stored in within that group. When non-zero (factory
Name Numeric Units Float Point (FP) (Hex) (Hex) Factor 520M 1150 non-volatile memory. default value), any attempt to access
Status Primary 404609 or 406145 hi byte 1200 or 1800 hi byte x x Function code 16 (1016) is used to load a group of data objects that contain an
cause the object assignments for the block of invalid object will result in an illegal data
Secondary 404609 or 406145 lo byte 1200 or 1800 lo byte x x object exception code 02. Refer to a later
registers. The block assignments are
Cause 404610 or 406146 1201 or 1801 x x stored beginning at register 41001/420481 section entitled “Exception codes.”
Control of product If the ‘slave action number’ and it 1’s All products reporting energy (independent Supported diagnostic sub-functions
complement are valid, the MCAM issues of energy units) support the energy
Since a control error could result in the ‘slave action’ control command to objects occupying four registers—Register It is possible to obtain diagnostics from
unwanted actions initiated by a device, the product. If the slave action request 3 through Register 0. Register 3 is the the MCAM or an attached product using
the MCAM requires a specific protocol is successfully acknowledged by the high order register and Register 0 is the function code 08. Refer to Table 9.
by the Modbus master in order to product, the MCAM returns a normal low order register.
perform control-related functions within Exception codes
function code 16 (1016) response to the Register 3 high byte contains a value
the product. Modbus master. The Modbus master Under certain circumstances, the MCAM
corresponding to engineering units (power
A set of registers is reserved for the may further determine if the product of 10 signed exponent). Register 3 low will return an exception code.
control protocol. completed the slave action function byte contains a mantissa multiplier value • If the function in the query is not
They begin at register 42901/425089 successfully by interrogating the product, (power of 2 signed exponent). supported by the MCAM, exception
(0B5416/620016) and extend through for example, by reading its status. code 01 is returned in the response
Register 2 through Register 0 contains
42903/425091 (0B5616/620216). These If the product does not acknowledge a 48-bit energy mantissa in units of • If the data (object) register is illegal,
three registers are written with a ‘slave the slave action request, the MCAM watthours. Net and total energy objects exception code 02 is returned in
action number’ and its 1’s complement returns an exception code 04. If the ‘slave are signed values. All other energy objects the response
using function code 16 (1016). The current action number’ and its 1’s complement are unsigned values.
‘slave action numbers’, their support being are invalid, the MCAM responds to the • If the data in the query is illegal,
product dependent, are listed in Table 7. Modbus master with a data value illegal The data format of these four registers is exception code 03 is returned
The format of the data is shown in exception code 03. Refer to a later section given in Figure 15. • If the attached product fails (usually a
Figure 14. These three registers, and entitled “Exception codes.” Energy = 2Mantissa Multiplier x (48-bit energy value) x 10 Engineering Units timeout), exception code 04 is returned
only these three registers, must be
written in one Modbus transaction. Date and time registers • In certain circumstances, an exception
code 05 (NAK) is returned
Access to date and time registers provide Energy Register 0
Register 42901/425089 (0B5416/620016) the opportunity for a Modbus master 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 • If the MCAM cannot perform the
to set up and/or read real-time clock requested function, exception code 07
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
information within an Eaton product. Eight (NAK) is returned
Byte 1 of Mantissa Byte 0 of Mantissa
registers, beginning at register number • If only a partial register is used in the
Slave Action Byte 1 Slave Action Byte 0 402921 (i.e., holding register address query, exception code 84 is returned
0B6816), are reserved for this information, Energy Register 1
as defined in Table 8. Registers are read 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Register 42902/425090 (0B5516/620116)
using function code 03 or 04 and written
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 using function code 16 (1016).
Byte 3 of Mantissa Byte 2 of Mantissa
Energy format
1’s Complement of Slave Action Byte 2
Slave Action Byte 0 Energy objects in the MCAM are Energy Register 2
supported in two-register fixed point 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Register 42903/425091 (0B5616/620216) object format and a four-register power/
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
mantissa format. These objects do not
support IEEE floating point format. Byte 5 of Mantissa Byte 4 of Mantissa
rollover values.
Figure 15. Four-Register Energy
Data Format