Rockwell Automation 1404-M4_M5_M6_M8 Powermonitor 3000 User Manual, Firmware rev. 3.0 or LATER - Manual (Page 17)

Publication 1404-UM001F-EN-P - November 2009 17
Product Description Chapter 2
Communication Options In addition to the native RS-485 communication port, several
factory-installed communication options are also available. These
options make it possible for a user to select Powermonitor 3000 units
to provide power and energy information into a variety of existing or
new control systems and communication networks. Each
communication option supports bi-directional data transfer with
external devices or applications. Metering measurement, logging,
configuration and status data may be accessed via communication.
Communication options are set in the master module. You may
configure communication by using the display module or via
communication to an external application such as RSPower,
RSPowerPlus, or RSEnergyMetrix. Refer to the information later in this
manual on configuration and operation of the communication options.
Refer to the Powermonitor 3000 Installation Manual, publication
1404-IN007 , for installation and wiring information related to your
selected communication options.
The last 3 characters of the catalog number specify the communication
option of the Powermonitor 3000 unit.
RS-485 Native Communication
A catalog number ending in -000 specifies a power monitor equipped
with only a native RS-485 communication port with the following
performance features:
•
Communication rates 1200, 2400, 4800, 9600, 19,200, 38,400, and
57,600 Kbps
•
RS-485 cable length 1219 m (4000 ft)
•
Cable type: two-wire shielded (Belden 9841)
•
Multi-drop capabilities up to 32 nodes (half-duplex only)
•
Update rate: 100 ms minimum
•
Read/Write data table access to all data
•
One user-configurable data table
•
Supports DF1 half-duplex, DF1 full-duplex, and Modbus RTU
communication protocol
•
Used for field firmware upgrades
The serial communication port operates as a responder on a
full-duplex point-to-point link. You must verify that no more
than one message is triggered simultaneously.