Introducing Ethernet/IP (IP stands for Industrial Protocol)

1
Introducing Ethernet/IP(IP stands for Industrial
Protocol)

• Nick Jones and William H. (Bill) Moss
• 6th ODVA Annual Meeting
• Tampa, FL
• March 8, 2000

2
I need Ethernet Why?

• Customers Asking for it
• Other Vendors are doing it
• I think it will be faster, easier and cheaper
• I want to use existing wire
• I think it will give me better connectivity
• I think Ethernet is going to be the Fieldbus
  winner

3
Customers Other Vendors

• Pressure to add Ethernet
• Large companies have used Ethernet at the
  controller level
• Smaller companies are using at the I/O level
• Now users are asking for its use at all levels

4
Some Customer Requirements

• Absolutely no changes shall be required to any
  existing node on DeviceNet to allow accessibility
  from Ethernet!!!
• Should be able to route messages from Ethernet to
  DeviceNet without making any DeviceNet product
  changes
• Where it make sense, reuse the application layer
  architecture that already exists in the DeviceNet
  spec
• Reuse the same Application Objects and same
  Device Profiles
• Expand as required to support any new
  requirements
• Need to use Commercial Off The Shelf technology
• Use standard Ethernet chip sets
• Use standard TCP/ UDP / IP protocol
• Allow for operation of other standard TCP/ IP
  applications like FTP, HTTP, SNMP, DHCP, BOOTP,
  DNS, etc.

5
Device Access Requirements

• Require temporary access to all devices
  (unconnected)
• Access to device resources cant be permanently
  blocked or held by any one device
• Always allow access to devices for intermittent
  one-time services
• Devices should always support a non-reserved
  access point for non-time critical applications
• Example who, get attribute, set attribute
• Example The Hotel has a reservation phone line
  (that is not always busy) to allow room
  reservations to be made or cancelled
• Optionally support persistent access to devices
  (connected)
• This allows customers to make sure that device
  resources can be reserved or guaranteed for
  important / time critical applications
• Example You can make a guaranteed hotel
  reservation before you board a plane

6
Encapsulation Requirements

• Encapsulationgt To put one protocol inside of
  another
• Typically a higher layer protocol in the data
  portion of a lower layer
• Example encapsulate a DeviceNet message inside
  of a TCP/IP packet
• Shall be general enough to support delivering
  both DeviceNet and non-DeviceNet messages over
  TCP/IP to the appropriate network
• Allows connectivity to other open networks
  (e.g.,Modbus)
• Allows connectivity to legacy, proprietary or
  other vendor specific networks
• Support a set of common protocol independent
  services
• Standard way to do a WHO, ping, request/response,
  etc.
• Be able to determine what protocol(s) a device
  supports
• Support vendor specific services
• Support both unsolicited and solicited services
• Support common method for the first hop
• Ability to deliver any encapsulated frame to the
  correct router

7
Explicit Message Requirements

• Need temporary and persistent access to all
  devices
• Need to be able to do upload and download of
  programming information to devices
• Need access to individual parameters within a
  device
• Need to be able to do configuration of HMI,
  DeviceNet scanners, robots, PLCs, weld
  controllers, etc
• Need to be able to collect data from end devices
• Collect status and maintenance information from a
  drive, valve controller, motion controller, etc.
• Needs to support multiple outstanding requests to
  a device
• Needs to support multiple requests to the same
  device in a single TCP/IP packet

8
I/O Message Requirements

• Need to be able to exchange I/O data between
  devices using connected / reserved resources
• In addition, be able to
• Support several different I/O data trigger
  methods COS, Cyclic, etc
• Support rapid I/O timeouts
• Guarantee freshest data is used
• Verify device identity before exchanging data
• Support an Open scanlist configuration method
• Need to allow for multicast data services for
  maximum efficiency and synchronism
• Need to allow scanners to support I/O connections
  across multiple routers

9
Routing Diagram
I/O
(PC) Programming SW
(PC) Data Collection
ENet to ENet
Ethernet
DNet to ENet to DNet
ENET
Router


ENET



ENet to DNet DNet to ENet


Router
I/O

DNET





DNET
DeviceNet

Router
DNET
DeviceNet
DeviceNet
DNET


D N E T
P L C




I/O
I/O
I/O
I/O



DNet to DNet







10
Routing Requirements

• Need to support data routing between networks
  with the application layer
• Enet subnet to ENet subnet
• ENet to DNet
• DNet to ENet
• DNet to DNet
• DNet to ENet to DNet
• Other multi-hop combinations
• I/O and Explicit Messaging available with routing
• Routing support for alternate protocols
• Support generic single hop routing for any
  protocol

11
Layered ENet Product Model
Only implement the functionality you need
Level 4 I/O Client
Level 2 I/O Server
Level 3 Message Client
Level 1 Message Server

• Level 4 (I/O Message - Client / Originator
  Server / Target)
• Adds I/O message origination support to Level 1,2
  and 3
• Acts as a target and an originator for explicit
  and I/O messages
• Example PLCs, I/O Scanners, Logic Controllers

12
TCP/IP Protocol Suite
The DeviceNet Application Protocol
BOOTP DHCP
Process Layer
FTP
HTTP
DNS
The Application Layer
SNMP
TCP
UDP
Host - to - Host Layer
OSPF
IGMP
ICMP
IGRP
Internet Layer
ARP
IP
RARP
Any IP based network (i.e., Ethernet)
Network Access Layer
13
CIP based Industrial Networks share a common
Application and User Layer
SEMI Devices
Pneu Valve
AC Drives
Position Cntrllrs
Other Profiles
User Layer
Application Layer
Transport and Data Link Layer
DeviceNet Physical Layer
ControlNet Physical Layer
Ethernet Physical Layer
Future ?
Physical Layer
ATM, Firewire USB, Blue Tooth, etc
14
This is DeviceNet
Semi Devices
Pneu Valve
AC Drives
Position Cntrllrs
Other Profiles
User Layer
Application Object Library
Application Layer Explicit, I/O, Routing
Application Layer
Future
DeviceNet DLL Transport
ControlNet DLL Transport
Transport and Data Link Layer
DeviceNet Physical Layer
ControlNet Physical Layer
Ethernet Physical Layer
Future
Physical Layer
ATM, Firewire USB, Blue Tooth
15
This is ControlNet
Semi Devices
Pneu Valve
AC Drives
Position Cntrllrs
Other Profiles
User Layer
Application Object Library
Application Layer Explicit, I/O, Routing
Application Layer
Future
DeviceNet DLL Transport
ControlNet DLL Transport
Transport and Data Link Layer
DeviceNet Physical Layer
ControlNet Physical Layer
Ethernet Physical Layer
Future
Physical Layer
ATM, Firewire USB, Blue Tooth
16
This is Ethernet/IP(IP stands for Industrial
Protocol)
Semi Devices
Pneu Valve
AC Drives
Position Cntrllrs
Other Profiles
User Layer
Application Object Library
Application Layer Explicit, I/O, Routing
Application Layer
Future
encapsulation
DeviceNet DLL Transport
ControlNet DLL Transport
Transport and Data Link Layer
UPD
TCP
IP
DeviceNet Physical Layer
ControlNet Physical Layer
Ethernet Physical Layer
Future
Physical Layer
ATM, Firewire USB, Blue Tooth
17
Ethernet/IP has a new logo
18
Technology will be downloadable

• ODVA will make the technology free and
  downloadable from multiple Web Sites
• Specifications (Protocol, Object Library, TCP/IP
  Encapsulation)
• Example (source) Code for a simple I/O server
  (Level2) type product

19
Layered Product Model

• Layered Product Model approach
• Only implement the functionality you need on
  Ethernet

Level 4 I/O Client
Level 2 I/O Server
Level 3 Message Client
Level 1 Message Server

• Level 4 (I/O Message - Client / Originator
  Server / Target)
• Adds I/O origination support to Level 1,2 and 3
• Acts as a target and an originator for explicit
  and I/O messages
• Example PLCs, I/O scanners, logic controllers,
  high end routers

20
Free Technology

• Level 1 (Explicit Message - Server / Target
  only)
• Used for explicit messaging applications only
• Acts as a target for connected and unconnected
  explicit messages
• Example Program upload / download, data
  collection, status monitoring, etc
• Level 2 (I/O Message - Server / Target only)
• Adds I/O messaging support to Level 1
• Acts as a responder for both explicit and I/O
  messages
• Example Simple I/O server devices
• In an effort to give vendors a jump start on an
  EtherNet/IP product development, ODVA will make
  the Level 2 technology available free of
  charge!
• Provide free example code for Level 2
  functionality
• Provide a free copy of the Ethernet/IP
  Specification

Level 2 I/O Server
Level 1 Message Server
21
What Is Example Code?

• The example code is the C source code (or
  stack) that is provided to product developers
  to allow them to embed the application layer
  within their TCP/IP Ethernet product
• The Example code contains the C source code
  required to implement the application layer on
  top of a TCP/IP Ethernet stack
• This includes support for Level 2 required
  objects
• Also include support for a general purpose
  assembly object
• The developer needs to provide the following
  commercially available items
• The appropriate Ethernet hardware platform
• Any optional product or vendor specific
  application objects
• TCP/IP stack with a Berkley Sockets (BSD)
  interface
• A multitasking real time operating system (RTOS)
• The Example code is currently being developed
  with
• VxWorks RTOS from WindRiver Systems
• TCP/IP stack also from WindRiver Systems
• The example code will also be tested on a
  Microsoft PC platform (NT4.0)

22
Technology will be distributed around the world

• ODVA will repackage on CD-ROM...
• Specifications (Protocol, Object Library, TCP/IP
  Encapsulation)
• Example Code
• and distribute through ODVA affiliates around the
  world

• DeviceNet Europe
• DeviceNet UK
• ODVA Australia
• ODVA China

• ODVA Japan
• ODVA Korea
• ODVA New Zealand
• ODVA USA

23
ODVA and ControlNet Intl Joint SIGs will manage
the technology

• Joint SIG will manage enhancements and bug fixes
• ODVA and ControlNet International Members can
  participate
• One company, one vote
• Supermajority (70) required to adopt proposals
• Both TRBs must approve
• Non-obsolescence policy
• Joint Conformance SIG will develop conformance
  testware

24
ODVA Labs will conformance-test EtherNet/IP
Products

• Testing to begin in Fall, 2000
• ASTEM (Kyoto, Japan)
• University of Michigan (Ann Arbor)
• University of Warwick (Coventry, England)

25
ODVA will promote EtherNet/IP

• Multiple organizations will support the rapid
  adoption of Ethernet/IP
• Introductory training for developers and product
  managers
• Next Training is May 2 in Cleveland
• Offer extended 2-3 day fee-paid developer
  training
• Introduce free technical support service - Ask
  Mr. Ethernet
• Sponsor Trade Show Demonstrations
• Speakers Bureau
• Accelerate Joint ControlNet Intl/ODVA Ethernet
  SIG
• Guidelines for Vendors
• Guidelines for Users
• Collect and Publish Performance Benchmarks