Rockwell Automation 1420 PowerMonitor 500 - Manual (Page 78)

78
Rockwell Automation Publication 1420-UM001D-EN-P - September 2013
Appendix C
PowerMonitor 500 EtherNet/IP Device Profile
Connections
The Assembly Object supports both scheduled (Class 1) and unscheduled
connections (Class 3 and UCMM). Both connections are used to access
instances 100d to 108d of the Assembly Object:
• UDP - Nine Class 1 connections each to the nine assembly instances 100
to 108 at 100 ms RPI ran stable
• TCP - Nine Class 3 connections each to the nine assembly instances 100
to 108 at 200 ms RPI ran stable
• Both - UDP and TCP can run at the same time
Heartbeat Instances
In addition to the Assembly instances shown earlier, the communication module
also recognizes two heartbeat instances. A heartbeat instance is a virtual output
instance that can be specified by devices wishing to establish Input Only and
Listen Only Class 1 I/O connections to the communication module. Data
cannot be read from or written to a heartbeat instance. The heartbeat instance is
merely a programming construct that serves to keep the connection active.
The communication modules's heartbeat instances are Instance 98 for the Input
Only connection and Instance 99 for the Listen Only connection.
Behavior
The purpose of the Assembly Object is to act as a network interface to the
PowerMonitor 500 unit’s data. That data can be accessed by a variety of means:
Class 1 or Class 3 connections and also with UCMM messages.
Technical Notes This section lists additional technical information about Ethernet network
communication.
Parameters
For the EtherNet/IP communication module, set the following parameters by
using Programming mode through the base module front panel:
• IP address
• Subnet
• Gateway
• Modbus TCP port
• Address Conflict Detect (ACD)