Eaton feeder protector modbus RTU communications board - IL026003002E Owner's Manual
Add to My manuals11 Pages
advertisement
Eaton Feeder Protector
Modbus RTU Communications
Board
I.L. 02602002E
Table of Contents
Effective October 2008 Page 1
Eaton Feeder Protector
Modbus RTU Communications
Board
Introduction
The Feeder Protector Modbus RTU Communications
Board can be ordered as an option from the factory to allow the unit to communicate over a Modbus RTU network.
A 4-pin connector is provided for wiring to the RS-485 network. The Modbus RTU Communications Board is installed in place of the INCOM communications Board.
Products Supported
•
FP-4000 (Firmware Revisions 1.00 and 2.00)
•
FP-5000 (Firmware Revisions 1.00 and 2.00)
•
FP-6000 (Firmware Revision 2.00)
These supported products are referred to as “Feeder
Protectors” throughout this document.
Product Compatibility
The Modbus RTU Communications Board is compatible with all Eaton Corporation products. It can be used in conjunction the RS-485 PONI or the mMint, as well as all other Modbus compliant products. Transmission byte order should be consistent between all products.
Features
The Modbus RTU Communications Board provides the following features:
•
A means of communicating using the standard
Modbus RTU Protocol
•
Selectable baud rates for networking flexibility
•
Selectable addresses 0-99 via the front panel
•
Status indicator displays normal operation and also serves as an error indicator
•
Data in IEEE floating point and fixed-point formats
•
Host interface communications indicator
•
RS-485 TX/RX indicators
•
Termination resistor is DIP switch selectable.
Hardware Installation
Simplified Wiring Rules
The Modbus RTU Communications Board provides a halfduplex, EIA/RS-485 network connection. EIA/RS-485 is a multi-drop, industrial-grade communications standard.
It is a “balanced differential“ signal that feeds over a twisted-pair containing “A” and “B” signals and a common.
For this reason, it is very important to carry all three conductors to ensure a high-quality communications network.
Signal Polarity
The data is considered a binary 1 when the voltage level of the “A” signal is less than the voltage level of the “B” signal. A binary 1 is considered a Mark or OFF, whereas a binary 0 is a Space or ON.
I.L. 02602002E
Cabling
The recommended cable for maximum performance of the
RS-485 network is a twisted-pair with 22-AWG stranded 7 x 30 conductors with PVC insulation under aluminum foil polyester tape, a single 24-AWG stranded 7 x 32 conductor with PVC insulation and aluminum foil polyester tape, and an all-over braided shield (Belden 3106A).
Cables with similar shielding and smaller wire sizes (24
AWG) can be used for easier wiring. The cable characteristic impedance should be 120 ohms
RS-485 Bus Termination
Assuming the characteristic impedance of the cable is 120 ohms, each segment of the RS-485 network should be terminated with an end-of-line terminating resistor. A resistor value of 120 ohm should be used at the Master end of the network as well at the end of the line. This terminating resistor is mounted at the factory and can be switched in by changing the SW4 on (“1”). SW1 should always be in the “Off” position. SW1 and SW4 are set to the off position at the factory. In most installations, the
SW4 terminating resistor does not need to be set to the on position.
Connectors
RS-485 Connector
Figure 1 shows a typical Modbus network where the
Modbus RTU Communications Board (Slave) and host devices are connected to the RS-485 Modbus master. The following chart shows the 5-pin connector pin-out assignment. See Figure 2.
Pin
1
2
3
4
Signal Connection
Common
Shield
J5-1
J5-2
RS 485 Com.
RS 485 Shield
Figure 1. Modbus RTU Communications Board Wiring
Effective October 2008 Page 2
Eaton Feeder Protector
Modbus RTU Communications
Board I.L. 02602002E
Effective October 2008
Figure 2. Connector J5 Wiring Connections
Page 3
Eaton Feeder Protector
Modbus RTU Communications
Board
Wiring Notes
1. For maximum noise immunity, the chassis ground terminal should be wired to the closest system chassis ground with at least a 16AWG stranded copper wire.
2. For maximum noise immunity, the shield of the RS-
485 cable should be daisy-chained from one slave device to another and terminated to chassis ground at the Modbus master-end of the network (single-point ground).
System Capacity
The address of the Modbus RTU Communications Board can be set between 0 and 99 (decimal). The maximum number of devices that can exist on a particular network when the feeder protector with Modbus RTU
Communications Board is used is 32.
If Modbus slave devices other than the FP Relay exist within the system, and if their address can be set above
99, the maximum number of slave devices on the network is 32.
LEDs and DIP Switches
As part of the initial setup, the baud rate, address, and termination resistor must be set to their correct settings.
These switches and indicator LEDs are described as follows:
•
Status LED (Green) Indicator
The Status LED indicator shows that the communications microprocessor on the Modbus RTU
Communications Board is operating properly. It alternates from ON for 1 second to OFF for
1 second.
Other blinking patterns may be noticed in the event of an error detected by the Modbus RTU
Communications Board. Refer to the “Error Detection
Using Status LED” section of this manual.
•
RS-485 Transmit LED (TX) (Red) Indicator
This LED is in the bottom row of LEDs on the communications interface board on the rear of the draw-out case. The LED flashes ON when the
Modbus RTU Communications Board is responding to a request. The board only responds to requests to its address.
•
RS-485 Receive LED (RX) (Green) Indicator
This LED is in the bottom row of LEDs on the communications interface board on the rear of the draw-out case. The RX LED flashes when the Modbus
RTU Communications Board detects that a signal is being transmitted to its address.
•
Translator Transmit (Red) Indicator
This LED indicator blinks after a Modbus message has been received, is acknowledged as a legitimate
I.L. 02602002E
request to the unit, and is being transmitted from the communications processor to the Main processor.
•
Main Processor Transmit (Red) Indicator
This LED indicator is in the second row from the top, on the right, next to the operational line. It blinks when responding to a data register request. More specifically, the LED blinks when a message is being sent to the microprocessor on the Modbus RTU
Communications Board.
•
121
Ω
Termination DIP Switch
The 121-ohm termination DIP switch, when switched to the ON position, places a 121-ohm resistor between the “A” and “B” terminals. This resistor is used as an end-of-line terminator.
•
Address Setting
The Modbus address can be set using the front panel buttons. Press the set button and enter the password.
Then select Communications, INCOM, and scroll to the address field to enter the Modbus address.
•
Baud Rate Selector Switch
DIP switch SW5 is used to set the baud rate of the
Modbus RTU Communications board’s RS-485 channel. This switch is on the Modbus RTU
Communications Board. The unit is set to 9600 baud at the factory. To set it to any other baud rate, remove the unit from the draw-out case. Refer to the following chart for the switch settings for various baud rates.
RS-485 Baud Rate Switch (SW5)
Baud A0 A1
1,200 Open Open
9,600 Open Closed
19,200 Closed Open
Modbus Network Communications
Protocol
Function Codes
The Modbus RTU Communications Board responds to a limited number of Modbus functions codes: 03, 04, 08, and
16 (10
16
). Function codes three (3) and four (4) can be used interchangeably, primarily so that both new and older
PLCs can access the Modbus registers.
Function code 3 (or 4) is the primary function code used to retrieve data from the Modbus RTU Communications
Board. The following chart lists an example of the data packet required to read the current in phase, A, B, and C.
Effective October 2008 Page 4
Query Field Name Example
Slave Address
Function Code
Starting Address High Byte
Starting Address Low Byte
Number of Registers High Byte
Number Of Registers Low Byte
Error Check Low Byte
Error Check High Byte
05
16
03
16
12
16
02
16
00
16
04
16
CRC Low
CRC High
The address in the Modbus register map list is the actual address transmitted to the Modbus slave device. Some
Modbus masters may require the register address to be incremented by one and, in turn, the master decrements this number by one, sending the required register address to the slave device. The Modbus master and slave address being one and the same is referred to as zerobased addressing. Refer to Appendix A.
In the example in the following chart, the unit at address
05hex is responding with a value of 100 amps (0x64h) in phase A, and 99 in phase B.
Eaton Feeder Protector Modbus RTU
Communications Board I.L. 02602002E
Floating Point Data Format
The IEEE-754 Floating Point Single Precision Standard is used to format Modbus floating point numbers. The following chart shows the bit assignment for a 32-bit
IEEE-754 floating point number
.
Bit 31 Bits 30……23 Bits 22…………………0
Table 1. Diagnostic Subfunction Numbers Used with Function Code 8
Subfunction
No.
(decimal)
0
Name
Echo Query
In the query, use…
Modbus RTU board address
1 Restart
Communications
Modbus RTU board address
Modbus board address
10
11
Clear Slave Counters Modbus RTU board address
UART Bus Message
Count
Modbus RTU board address
Response Field Name Example
Slave Address
Function Code
05
16
03
16
04
16
Byte Count
Data from High Byte of Register X
(e.g., 406147
10
)
Data from Low Byte of Register X
00
16
64
16
(e.g., 406148
10
)
Data from High Byte of Register
X+1 00
16
(e.g., 404649
10
)
Data from Low Byte of Register
X+1
(e.g., 406150
10
)
Error Check Low Byte
Error Check High Byte
63
16
CRC Low
CRC High
Supported Diagnostic Subfunctions
It is possible to obtain diagnostics from the Modbus RTU
Communication Board using function code 08. Refer to
Table 1.
Byte Count Data Format
A byte count is used in the data field of a message packet that transmits coil or register information. The byte count data field is one byte in length and equals the number of
8-bit bytes of data that follow the byte count field up to the error-checking field. The value is exclusive of all other field contents, including the byte count field.
14
15
16
Error Count address
Modbus RTU board address ption Error Count
Slave Message Count Modbus RTU board address
Slave No Response
Count
Not supported;
Returns 0
Slave NACK Count
Returns 0
Not supported
17
18
Slave Busy Count
Returns 0
UART Over Run Error
Returns 0 Count
Not supported;
Returns 0
Not supported;
Returns 0
Modbus RTU board
Address
26
27
Modbus RTU board
Firmware Version and
Rev
Modbus RTU board
Firmware Month and
Day
Modbus RTU board
Firmware Year
Modbus RTU board address
28 Modbus RTU board address
Each Modbus register is defined in the Modbus protocol as a 16-bit (two byte) entity. The 32-bit floating point data formats are always contained in two consecutive registers.
Modbus protocol defines register information to be transmitted with the high-byte first, followed by the
1
An implied numeral 1 precedes the decimal fractional part.
Effective October 2008 Page 5
Feeder Protector Modbus RTU
Communications Board I.L. 02602002E
low-byte. The protocol, however, does not specify the storage order of multi-register information. The default, adopted by most of the industry, and thus Eaton, places the low order (least significant) 16-bit word in the first
Modbus register space (x) followed by the high order (most significant) 16-bit word in the next Modbus register space
(x+1), as shown in the chart below. The transmission order is 1 st
byte, 0 th
byte, 3 rd
byte and 2 nd
byte, with bit 8 transmitted first.
Bits
15……8
Bits 7……0
1 st byte 0 th byte
Register x
Bits
31……24
Bits
23……16
3 rd byte 2 nd byte
Register x+1
Multi-Register Fixed Point Data Format
Each Modbus register is defined in the Modbus protocol as a 16-bit (two byte) entity. Data fields that require more than 16-bits (32-bit or 64-bit long integers) must occupy consecutive register locations. Modbus protocol defines register information to be transmitted with the high-byte first, followed by the low-byte. The protocol, however, does not specify the storage order of multi-register information.
The default, adopted by most of the industry, and thus
Eaton, places the low order (least significant) 16-bit word in the first Modbus register space (x) followed by the next higher order 16-bit word in the next Modbus register space
(x+1) and so forth. The transmission order is 1 st
byte, 0 th byte, 3 rd
byte, 2
4 th
byte, 7 th nd
byte, and for 64-bit parameters, 5 th
byte,
byte, and 6 th
byte, with bit 8 transmitted first.
Energy Register 18A0-18B8
For better resolution, a set of registers between 18A0 and
18B8 are available. Figure 3 depicts how this data is formatted. Care must be taken when configuring the
Master program. It may otherwise interpret these register incorrectly. The data cannot be read on 32-bit boundaries.
For example, forward energy is read with address 18A0 with a length of 4. Requesting a length of 2 within register range results in an exception code 02 “Illegal Data address”.
Troubleshooting
The most common issues experienced with the installation of a Modbus RTU Communication Board are addressed as follows. If you have any questions or need further information or instructions, contact your local representative or the Power Management Applications
Support group at 1-800-809-2772 (Option 4).
•
Status LED is not flashing.
-- No external power to the Feeder Protector.
Energy Register 0
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Byte1 of Mantissa
Byte0 of Mantissa
Energy Register 1
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Byte3 of Mantissa
Byte2 of Mantissa
Energy Register 2
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Byte5 of Mantissa
Byte4 of Mantissa
Energy Register 3
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Engineering Units
Mantissa Multiplier
Energy = 2
Mantissa Multiplier
* Mantissa * 10
Engineering Units
Figure 3. Energy Register Data Format
•
Modbus Rx LED is flashing, but the Modbus RTU
Communications Board does not respond to master command requests.
-- Verify that the data transfer rate is correctly set using baud rate switches (A0 and A1). connected correctly from the master to the
Modbus slave device.
-- Verify that the Network is terminated properly.
•
Modbus Rx, Translator transmit, Main Processor transmit are all flashing, but the module does not respond to master command requests.
-- Verify that the Modbus address, stored in the
INCOM address entered from the front panel, is the same as the address requested by the
Modbus Master.
-- Verify that the red, termination switch (SW1) is set to "ON" at the last Modbus slave device.
•
Modbus Rx and Tx LEDs are flashing, and the
Translator transmit (Red) LED is flashing excessively, but the Main Processor transmit LED does not blink.
Most likely, the Modbus board is returning an exception code to the master. Refer to the Exception
Codes section. The Modbus (INCOM) address was changed, but the Master is still polling the old address. Make certain that the Modbus (INCOM) address is not set above 100d.
Page 6 Effective October 2008
Error Detection Using Status LED
If the status light blinks twice in rapid ON/OFF cycles, followed by a 1.5-second OFF, the unit is not being recognized by the Modbus RTU Communications Board or that no unit has been detected. This may occur if the
Modbus address is above the highest allowable Modbus address 99 (0x63h).
If three blinks occur in rapid ON/OFF cycles, followed by a
1.5-second off period, an unsupported product has been detected. Contact Eaton's Power Quality Technical
Support department at 1-800-809-2772 (Option 4) for further assistance.
Exception Codes
Exception codes are returned to the master in response to data requests that are erroneous, invalid, or when the product is busy with other more critical processes, such as tripping on a fault condition. The following Modbus standard, and feeder protector specific exception codes may result under these conditions.
Standard Modbus Exception Codes
ILLEGAL_FUNCTION (1)
ILLEGAL_DATA_ADDRESS (2)
ILLEGAL_DATA_VALUE (3)
SLAVE_DEVICE_FAILURE (4)
ACK(5)
BUSY(6)
NACK(7)
Feeder Protector Specific Exception Codes
NO_PRODUCT_DETECTED (0xA0)
INVALID_INCOM_FLOAT_DATA (0xA1)
INVALID_BLOCK_ADDRESS (0xA2)
RQST_HAS_TOO_MUCH_DATA (0xA3)
RQST_HAS_TOO_LITTLE_DATA (0xA4)
RQST_NUM_REGS_BYTES_MISMATCH (0xA5)
Eaton Feeder Protector Modbus RTU
Communications Board I.L. 02602002E
Safety and Compliance Standards
EMC/Safety Standards
•
UL, CSA
•
CE Mark
•
FCC Part 15, Class A
•
EN 61000-6-2; 1999
•
EN 55011; 1998
EMC Susceptibility Standards
•
EN 61000-4-2; 1995
Electrostatic Discharge
•
EN 61000-4-3; 1998
Radiated RF Immunity
•
EN 61000-4-4; 1995
EFT and Burst
•
EN 61000-4-5; 1995
Voltage Surge
•
EN 61000-4-6; 1996
Conducted RF Immunity
•
ANSI C37.90.2; 1995 Radiated RF Immunity
•
ANSI C37.90.1; 1989
Surge Withstand Capability
EMC Emissions Standards
•
FCC Part 15 Class A (10 meters)
Radiated and Conducted Emissions
•
EN 55011; 1998
Radiated and Conducted Emissions
System Ratings
The following chart lists the electrical and environmental specifications of the Feeder Protector.
Operating Temperature
Storage Temperature
Altitude
Operating Humidity
Environment
Transient Over Voltage
Pollution Degree
Equipment Class
Power Requirements
-20
°
C to 60
°
C
-20
°
C to 70
°
C
3,048m (10,000 ft.)
5% to 90% max. non-condensing
Indoor use only
Category 1
2
3
24 V; 50 mA
Effective October 2008 Page 7
Eaton Feeder Protector Modbus RTU Communications Board
I.L. 02602002E
Appendix A
Modbus Register Maps
Definition
404609 406145 1200
404611 406147 1202
404613 406149 1204
1800
1802
1804
Pri/Sec/Cause
IA
IB
404615 406151 1206
404617 406153 1208
1806
1808
IC
IX
404619 406155 120A 180A IR
404621 406157 120C 180C Iavg
404623 406159 120E 180E VAB
404625 406161 1210
404627 406163 1212
404629 406165 1214
404631 406167 1216
1810
1812
1814
1816
VBC
VCA
Vavg L-L
VAN
404633 406169 1218
404635 406171 121A
1818
181A
VBN
VCN
404637 406173 121C 181C Vavg L-N
404639 406175 121E 181E VNG
404641 406177 1220 1820 IA peak demand
404643 406179 1222
404645 406181 1224
1822
1824
IB peak demand
IC peak demand
404651 406187 122A 182A 3-ph Power
404653 406189 122C 182C 3-ph Reactive Power
404655 406191 122E
404657 406193 1230
404659 406195 1232
404661 406197 1234
182E
1830
1832
1834
3-ph VA
3-ph PF displacement
3-ph PF apparent
Frequency (1/10)
404697 406233 1258
404715 406251 126A
1858
186A
Peak Demand
3-ph Power
404717 406253 126C 186C Power Factor
404719 406255 126E
404721 406257 1270
186E
1870
Product ID
Frequency (1/100)
404723 406259 1872 Forward Energy
10
10
1
1
1
100
100
10
1
1
100
1
1
1
10
10
10
10
10
10
10
10
10
10
10
10
10
10
-
10
A
A
W
VAR
VA n/a n/a
Hz
W
W n/a n/a
Hz
KWh
A
A
A
A
V
V
V
V
V
A
A
V
V
V
V
A
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
-
X
Page 8 Effective October 2008
Eaton Feeder Protector Modbus RTU Communications Board
I.L. 02602002E
Modbus Register Maps (Continued)
404725 406261
404727 406263
404729 406265
404731 406267
404733 406269
404735 406271
406305
406309
406313
406317
406321
406325
406329
Definition
1874
1876
1878
187A
187C
187E
18A0-2
18A4-6
18A8-A
18AC-E
18B0-2
18B4-6
18B8-A
Reverse Energy
Net Energy
Leading Varhours
Lagging Varhours
Net Varhours
VAhours
Forward Energy
Reverse Energy
Net Energy
Leading Varhours
Lagging Varhours
Net Varhours
VAhours
KWh
KWh
KVARh
KVARh
KVARh
KVAh
Wh
Wh
Wh
VARh
VARh
VARh
Vah
1
1
1
1
1
1
1
1
1
1
1
1
1
X
X
X
X
X
X
X
X
X
X
X
X
X
Effective October 2008 Page 9
Eaton Feeder Protector Modbus RTU Communications Board
I.L. 02602002E
Eaton Feeder Protector Primary Status, Secondary Status, Cause-of-Status
The products operational status can be read from registers 1200 and 1201h. Register 1200 contains the Primary and
Secondary status. The Primary Status is located in the high byte of register 1200, and the Secondary Status is located in the low byte of Register 1200. Location 1201 is defined as the Cause-of-Status register. In the Eaton Feeder Protection Modbus
RTU Communications Board, the Cause-of-Status register indicates that the unit is in an Alarm or Pick-up condition. See the following charts for the format of this data.
Data format for Primary, Secondary, and Cause-of-Status
Modbus Address Byte
1200
1200
1201
1201
Definition
High
Low
High
Low
Primary Status
Cause-of-Status
Primary Status
The Primary Status indicates the general state of the relay, either a Normal status, where no overload or other protective function is sensed by the relay, or Abnormal status. The Abnormal status can occur when the breaker is open or closed. In the open position, the indication of an abnormal state can occur when the relay has tripped on a protective function. In the case of a 27 under voltage condition, the Primary Status byte will remain abnormal until the under voltage condition ceases to exist. While closed, an abnormal state can occur while a system parameter has exceeded a protective function threshold.
The Primary status and Cause-of Status is dependent on the programming of the output relays. For FP6000 this is configured under the LED Configuration and for FP4000/5000, under output configuration. If the protective function is directed to a specific output relay, this relay must be configured to indicate Trip or Alarm to make use of the “Abnormal” status indicator, and it must be enabled.
Secondary Status
The secondary Status is used to indicate the status of the breaker being controlled by the relay. An Open (2) or Closed (1) state is reported in this byte.
Cause-Of-State
To enable the Pick-up flag in the Cause-of-Status register, a pick-up must be assigned to a group of functions such as the volts, IOC, or TOC. Under normal conditions where system parameters are all below the protective function thresholds, a “1” is returned in this register. The register will toggle from a 1 to a 71 (decimal) or 47 (Hexadecimals) upon the detection of a
Pick-up, or Alarm.
This indicator is only active while the breaker is “Closed”, and will resort back to a “1” once the breaker has opened.
Table of Primary, Secondary and Cause-of-Status indicators
Primary Status
7 = Normal
Secondary Status
2 = Open
Cause-of-Status
1 = N/A
7 = Normal
4 = Alarm
4 = Alarm
1 = Closed
2 = Open
1= Closed
1 = N/A
1= N/A
71* = Alarm or Pick-up
Comments
Status Normal Breaker
Open, But was not the result of a protective function. User may have pushed the “Push to
Trip” Button of Breaker.
Status is Normal
Breaker is closed
No protective functions are picked-up or alarming.
Status is Abnormal
Breaker is Open due to a protective trip function.
Status is Abnormal
Breaker is closed but the cause indicates that an alarm or a Pick-up condition is active.
* Value is in Decimal.
Page 10 Effective October 2008
Eaton Feeder Protector Modbus RTU Communications Board
I.L. 02602002E
Contact Information
1-800-809-2772 (Option 4)
Eaton
1000 Cherrington Parkway
Moon Township, PA 15108-4312
USA www..Eaton.com
Effective October 2008
© 2008 Eaton
All Rights Reserved
Printed in USA
Publication No.
I.L.
02602002E /Style # 66A2268H03
October 2008
Page 11
advertisement
Related manuals
advertisement