Introduction; Ethernet/Ip Overview - Lenze SMVector Reference Manual

2

Introduction

EtherNet/IP just like its close siblings DeviceNet and ControlNet, uses CIP (Common Industrial Protocol
a.k.a. Control and Information Protocol) to exchange data between devices on an Ethernet network. AC
Tech implementation of CIP follows the standard supported by the ODVA (governing organization) and
supports the two main types of EtherNet/IP communication: Explicit Messaging and I/O Messaging.
The purpose of this document is to describe the EtherNet/IP implementation specifics for the SMV drive
as well as provide the necessary information and examples for users and network programmers. This
document assumes the reader is familiar with the general concept of CIP and has a basic knowledge of
Ethernet TCP/IP communication principles.
2.1 EtherNet/IP Overview
EtherNet/IP implements network protocol using the seven layer Open Systems Interconnection (OSI) model
as illustrated in Figure 1. Ethernet has an active infrastructure and as such EtherNet/IP can support an
almost unlimited number of point-to-point nodes. The EtherNet/IP system requires just one connection for
configuration and control. An EtherNet/IP system uses peer-to-peer communication and can be setup to
operate in a master/slave or distributed control configuration.
Layer
7 Application
6 Presentation
CIP: Data Management - Explicit Messages, I/O Messages
5 Session
CIP: Connection Management - Message Routing
4 Transport
DeviceNet
Transport
3 Network
CAN
2 Data Link
CSMA/NBA
DeviceNet
1 Physical
Physical Layer
Figure 1: OSI Model
Introduction
CIP: Application Layer - Object Library
Encapsulation
ControlNet
TCP
Transport
ControlNet
CTDMA CSMA/CD
ControlNet
Physical Layer
Physical Layer
3
UDP
IP
Ethernet
Ethernet
CMVETH01B