Rockwell Automation Publication 1426-UM001J-EN-P - August 2019 227
Communication Chapter 9
DeviceNet and ControlNet
Object Model
This section provides the object model for a PowerMonitor 5000 device type on
either a DeviceNet or ControlNet network. Tabl e 3 2
indicates the following:
• The object classes present in this device
• Whether the class is required
• The number of instances present in each class
Object Class List
The PowerMonitor 5000 unit supports the following classes.
Explicit Messaging
This section discusses data retrieval and parameter configuration by using explicit
messaging from Rockwell Automation controllers. Explicit messaging provides
the mechanism for users to program a controller to read and write specific data
tables in a power monitor. With explicit messages, you can read real-time
metering values, configure metering and communication parameters, and also
read certain logs.
The PowerMonitor 5000 unit supports PLC-5 Typed, SLC Typed, and CIP
Generic message requests.
Table 32 - DeviceNet and ControlNet Object Model
Object Class Need in Implementation Number of Instances
Identity (1, 1hex) Required 1
Message Router (2, 2hex) Required 1
DeviceNet Object (3, 3hex) Required 1
Assembly Object (4, 4 hex) Required Minimum of 3
Connection Object (5, 5hex) Required Minimum of 1
Parameter Object (15, Fhex) Required Product Specific
Parameter Group Object (16, 10hex) Optional Product Specific
Acknowledge HandleObject (43, 28hex) Required 1
Non-Volatile Storage Object (161, A1hex) Required Product Specific
File Object (55, 37hex) Required Minimum of 1
PCCC Object (103, 67hex) Optional 1
Base Energy Object (78, 4Ehex)
(1)
Required 1
Electrical Energy Object (79, 4Fhex)
(2)
Required 1
Email Object (815, 32Fhex) Optional 1
(1) See CIP Base Energy Object on page 261.
(2) See
CIP Electrical Energy Object on page 262.
To Next Page
Loading...
Need help?
General
