User's Manual

COBALT UHF-SERIES CHAPTER 6: ETHERNET/IP INTERFACE
PAGE 100 OF 140
4.
After the PLC has processed the response information, it copies the counter from
EMS_WRITE1 [1] to EMS_READ1 [0] which signals to the Cobalt that the PLC
has retrieved the response data.
5.
The data will then be cleared from EMS_WRITE1. After which the Cobalt will be
ready to receive another command.
6.9 ETHERNET/IP: OBJECT MODEL
The Object Model is the logical organization of attributes (parameters) within classes
(objects) and services supported by each device.
Objects are broken down into three categories: Required Objects, Vendor Specific
Objects and Application Objects.
 Required Objects are classes that must be supported by all devices on
EtherNet/IP. The Cobalt has six Required Objects.
 Vendor Specific Objects are classes that add attributes and services that
do not fit into the Required Objects or Application Objects categories. The
Cobalt has two Vendor Specific Objects.
 Application Objects are classes that must be supported by all devices using
the same profile. An example of a profile is a Discrete I/O device or an AC