Ethernet/Ip Acyclic Operation; Introduction; Device Type 0X22 (Encoder Profile); Cip Object Model - Baumer EA Series Manual

7. EtherNet/IP acyclic operation

7.1. Introduction

As an application layer EtherNet/IP uses the Common Industrial Protocol (CIP) released by the ODVA. CIP
is transmitted as an "encapsulated" protocol in the data section of standard Ethernet frames. Depending on
the assignment and type of the connection the data transmission mechanisms UDP/IP or TCP/IP are used.
CIP is an object-oriented protocol. The device characteristics are described by which have one or more
instances. Each instance has one or more attributes. Attributes describe individual characteristics of objects
such as parameter values.
In device profiles the ODVA defines which CIP objects and attributes have to be supported by a certain
device class. In addition, optional and manufacturer-defined objects and attributes are also possible.
Data transmission of CIP messages in EtherNet/IP networks takes place by means of implicit and explicit
messages. Typically, implicit messages are smaller data packages for time-critical data transmissions. When
transmitting I/O data implicit connections with long-term viability are generally involved. I/O data is
transmitted by means of UDP. Non time-critical data is transmitted by means of explicit messages. Examples
of explicit messages are configuration or information data which use the TCP/IP transmission mechanisms.
More detailed information about the Common Industrial Protocol (CIP) or EtherNet/IP can be obtained from
the ODVA (www.odva.org).

7.2. Device Type 0x22 (encoder profile)

The EAx580 EtherNet/IP encoder family was designed according to profile 0x22 (encoder profile) of the
ODVA.

7.3. CIP Object Model

The object model describes the used object classes of the encoder and their mutual relationship. This is
defined in the device profile 0x22 (encoder profile) of the ODVA. Cyclic and acyclic data communication run
in parallel and independently of each other.

7.4. Standard objects

The encoder supports the following standard objects:
- Identity Object (0x01)
- Message Router Object (0x02)
- Assembly Object (0x04)
- Connection Manager Object (0x06)
- Device Level Ring Object (0x47)
- Quality of Service Object (0x48)
- TCP/IP Interface Object (0xF5)
- Ethernet Link Object (0xF6)

7.5. Profile-specific objects

The encoder supports the following profile-specific object:
- Position Sensor Object (0x23)
Baumer_EAx_EtherNetIP_EN_MNL 36/81 www.baumer.com
02.20