Native rs-485 communication – Rockwell Automation 1404-M4_M5_M6_M8 Powermonitor 3000 User Manual, Firmware rev. 3.0 or LATER User Manual

Page 64

Advertising
background image

64

Publication 1404-UM001F-EN-P - November 2009

Chapter 4 Communication

If you choose to configure communication parameters by using
communication, please refer to the

Native Communication

Configuration

table and the

Optional Communication Configuration

Parameters

table in

Appendix A

.

Native RS-485 Communication

Your Powermonitor 3000 unit is set up to communicate via its native
RS-485 port when you first power it up, except for units with an
optional RS-232 communication port. The communication
configuration includes the following parameters:

Protocol: Allen-Bradley DF1 full-duplex, DF1 half-duplex slave,
Modbus RTU slave, or auto-sense. Default auto-sense

Data communication rate: Range 1.2, 2.4, 4.8, 9.6, 19.2, 38.4, and
57.6 Kbps. Default 9.6 Kbps

Delay: Range 0…75 ms, 10 ms default

Data Format: 8 data bits, 1 stop bit, no parity, odd parity or even
parity. Default no parity

Node address: Range 1…247, default is the same value as the
unit ID listed on the nameplate

Inter-character timeout: Range 0…6553 ms
Default 0 (= 3.5 character times)

Error checking: CRC (default), BCC

The Delay parameter is the time the power monitor waits before its
response to an external request. Certain communication equipment
requires such a delay for reliable operation.

With a half-duplex protocol selected, you may connect your power
monitor into a multi-drop RS-485 network with up to 32 nodes. You
must use a device configured as a master to communicate with this
port. All devices on the RS-485 network must be set at the same data
rate.

With the DF1 full-duplex protocol selected, the power monitor
communicates with another DF1 full-duplex initiator device over a
point-to-point link.

TIP

The native communication port does not support Data Highway 485
(DH-485) communication. Although DH-485 uses the RS-485 physical
media, its protocol is not compatible with the DF1 protocol.

Advertising