beautypg.com

Appendix a: ethernet/ip object model, Device object model – B&B Electronics GW-7472 - Manual User Manual

Page 42

background image

GW-7472 User Manual, Version 1.0, Dec 2010

--- 42

Appendix A: EtherNet/IP Object Model

1. Device Object Model

The Device Object Model is the logical organization of attributes, classes and services

supported by a device. Objects are composed of attributes and services. There are three

types of objects in any CIP device: Required Objects, Application Objects and Vendor

Specific Objects.

Required Objects are object classes that must be supported by all devices on EtherNet/IP.

Applications 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 Drive. This ensures that

devices from different vendors but with the same profile have a common interface to

EtherNet/IP Client devices. For example, every AC Drive device must have a motor object

among its required application objects. The attribute numbers for the maximum motor

frequency and other motor data are predefined by the AC Drive profile to simply access to

any device supporting the AC Drive profile.

Vendor Specific Objects are classes that add attributes and s

ervices that don’t fit into the

Required or Application Objects.

The required objects of the GW-7472 are list as below:

 Identity Object (0x01)
 Message Router Object (0x02)
 Assembly Object (0x04)
 Connection Manager Object (0x06)
 TCP Object (0xF5)
 Ethernet Link Object (0xF6)