Emsa HS500E manual Appendix C ETHERNET/IP Object Model

A P P E N D I X C : E T H E R N E T / I P – O B J E C T M O D E L

APPENDIX C:

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 HS500E has six Required Objects.

ƒVendor Specific Objects are classes which add attributes and services that don’t fit into the Required Objects or Application Objects categories. The HS500E 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 Drive. This ensures that all devices with the same profile have a common look on the network.

Data Type Definitions

EtherNet/IP was designed by the Open Device Vendors Association (ODVA) as an open protocol. The following table contains a description of the data types used by ODVA that are also found in this appendix.

D a t a T yp e	D e s c r i p t i o n
USINT	Unsigned Short Integer (8-bit)
UINT	Unsigned Integer (16-bit)
UDINT	Unsigned Double Integer (32-bit)
STRING	Character String (1 byte per character)
BYTE	Bit String (8-bits)
WORD	Bit String (16-bits)
DWORD	Bit String (32-bits)

H S 5 0 0 E – O P E R A T O R ’ S M A N U A L	P / N : 1 7 - 1 3 0 5 R E V 0 2 ( 1 2 - 0 5 )
	P A G E 6 3 O F 8 2