Introducing EthernetIP IP stands for Industrial Protocol Nick

Introducing Ethernet/IP (IP stands for Industrial Protocol) Nick Jones and William H. (Bill) Moss 6 th ODVA Annual Meeting Tampa, FL March 8, 2000 Feb 11, 2000

I need Ethernet – Why? l l l Feb 11, 2000 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

Customers & Other Vendors l l Feb 11, 2000 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

Some Customer Requirements l Absolutely no changes shall be required to any existing node on Device. Net to allow accessibility from Ethernet!!! – l Where it make sense, reuse the application layer architecture that already exists in the Device. Net spec – – l 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 – – – Feb 11, 2000 Should be able to route messages from Ethernet to Device. Net without making any Device. Net product changes 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.

Device Access Requirements l Require “temporary” access to all devices (“unconnected”) – – Access to device resources can’t 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 – l Optionally support “persistent” access to devices (“connected”) – – Feb 11, 2000 Example: The Hotel has a reservation phone line (that is not always busy) to allow room reservations to be made or cancelled 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

Encapsulation Requirements l l l Feb 11, 2000 Encapsulation=> To put one protocol inside of another – Typically a higher layer protocol in the data portion of a lower layer – Example: encapsulate a Device. Net message inside of a TCP/IP packet Shall be general enough to support delivering both Device. Net and non. Device. Net 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

Explicit Message Requirements l l l 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, Device. Net scanners, robots, PLCs, weld controllers, etc Need to be able to collect data from end devices – l l Feb 11, 2000 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

I/O Message Requirements l l Need to be able to exchange I/O data between devices using connected / “reserved” resources In addition, be able to; – – – l l Feb 11, 2000 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

Routing Diagram (PC) Programming SW (PC) Data Collection I/O ENet to ENet Ethernet DNet to ENet to DNet to ENet ENET Router DNET I/O Device. Net Router DNET Device. Net P L C Feb 11, 2000 D N E T Device. Net DNET I/O I/O DNet to DNet I/O

Routing Requirements l Need to support data “routing” between networks with the application layer – – – l l I/O and Explicit Messaging available with routing Routing support for alternate protocols – Feb 11, 2000 Enet subnet to ENet subnet ENet to DNet to ENet DNet to ENet to DNet Other multi-hop combinations Support “generic” single hop routing for any protocol

Layered ENet Product Model Level 2 “Only implement the functionality you need ” I/O Server l Level 1 (Explicit Message - Server / Target only) – – Level 1 Message – l Server Level 2 (I/O Message - Server / Target only) – – Level 3 – l – Client – – – I/O – Feb 11, 2000 Adds Client support to Level 1 explicit messaging applications only Acts as a target and an originator for messaging applications Example: Computer interface cards, HMI and MMI devices Level 4 (I/O Message - Client / Originator + Server / Target) Level 4 Client Adds I/O messaging support to Level 1 Acts as a “target” for both explicit and I/O messages Example: Simple I/O devices, Pneumatic Valve, AC Drive Level 3 (Explicit Message - Client / Originator + Server / Target) Message l 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 – 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

TCP/IP Protocol Suite “”The Device. Net Application Protocol Process Layer FTP HTTP Host - to - Host Layer TCP OSPF Internet Layer Network Access Layer Feb 11, 2000 “The Application Layer ” DNS IGRP ARP SNMP BOOTP DHCP UDP ICMP IP IGMP RARP Any IP based network (i. e. , Ethernet)

CIP based Industrial Networks share a common Application and User Layer SEMI Devices User Layer Pneu Valve AC Drives Position Cntrllrs Other Profiles Application Object Library Application Layer Explicit, I/O, Routing Application Layer Transport and Data Link Layer Device. Net DLL & Transport Control. Net DLL & Transport Physical Layer Device. Net Physical Layer Control. Net Physical Layer encapsulation TCP UPD Future ? IP Ethernet Physical Layer Future ? ATM, Firewire USB, Blue Tooth, etc Feb 11, 2000

This is Device. Net Semi Devices User Layer Pneu Valve AC Drives Position Cntrllrs Other Profiles Application Object Library Application Layer Explicit, I/O, Routing Application Layer Transport and Data Link Layer Device. Net DLL Transport Control. Net DLL Transport Physical Layer Device. Net Physical Layer Control. Net Physical Layer ecapsulation TCP UPD Future IP Ethernet Physical Layer Future ATM, Firewire USB, Blue Tooth Feb 11, 2000

This is Control. Net Semi Devices User Layer Pneu Valve AC Drives Position Cntrllrs Other Profiles Application Object Library Application Layer Explicit, I/O, Routing Application Layer Transport and Data Link Layer Device. Net DLL Transport Control. Net DLL Transport Physical Layer Device. Net Physical Layer Control. Net Physical Layer encapsulation TCP UPD Future IP Ethernet Physical Layer Future ATM, Firewire USB, Blue Tooth Feb 11, 2000

This is Ethernet/IP (IP stands for Industrial Protocol) Semi Devices User Layer Pneu Valve AC Drives Position Cntrllrs Other Profiles Application Object Library Application Layer Explicit, I/O, Routing Application Layer Transport and Data Link Layer Device. Net DLL Transport Control. Net DLL Transport Physical Layer Device. Net Physical Layer Control. Net Physical Layer encapsulation TCP UPD Future IP Ethernet Physical Layer Future ATM, Firewire USB, Blue Tooth Feb 11, 2000

Ethernet/IP has a new logo Feb 11, 2000

Technology will be downloadable ODVA will make the technology free and downloadable from multiple Web Sites l l Feb 11, 2000 Specifications (Protocol, Object Library, TCP/IP Encapsulation) Example (source) Code for a simple I/O server (“Level 2”) type product

Layered Product Model Level 2 l “Layered Product Model” approach – “Only implement the functionality you need on Ethernet” I/O Server l Level 1 (Explicit Message - Server / Target only) – – Level 1 Message – l Server Level 2 (I/O Message - Server / Target only) – – Level 3 – l – Client – – – I/O – Feb 11, 2000 Adds Client support to Level 1 explicit messaging applications only Acts as a target and an originator for messaging applications Example: Computer interface cards, HMI and MMI devices Level 4 (I/O Message - Client / Originator + Server / Target) Level 4 Client Adds I/O messaging support to Level 1 Acts as a “responder” for both explicit and I/O messages Example: Simple I/O devices, simple router (ENet side) Level 3 (Explicit Message - Client / Originator + Server / Target) Message l 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 – 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

Free Technology Level 2 l – I/O – Server Level 1 (Explicit Message - Server / Target only) – l Level 2 (I/O Message - Server / Target only) – Message – Server – l 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 Ether. Net/IP product development, ODVA will make the “Level 2” technology available free of charge! – – Feb 11, 2000 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 Provide free example code for “Level 2” functionality Provide a free copy of the Ethernet/IP Specification

What Is Example Code? l 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 – – – l The developer needs to provide the following commercially available items; – – l 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; – – – Feb 11, 2000 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” Vx. Works RTOS from Wind. River Systems TCP/IP stack also from Wind. River Systems The example code will also be tested on a Microsoft PC platform (NT 4. 0)

Technology will be distributed around the world ODVA will repackage on CD-ROM. . . l l Specifications (Protocol, Object Library, TCP/IP Encapsulation) Example Code and distribute through ODVA affiliates around the world: l l Feb 11, 2000 Device. Net Europe Device. Net UK ODVA Australia ODVA China l l ODVA Japan ODVA Korea ODVA New Zealand ODVA USA

ODVA and Control. Net Intl Joint SIGs will manage the technology l Joint SIG will manage enhancements and bug fixes – – – l Feb 11, 2000 ODVA and Control. Net 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

ODVA Labs will conformancetest Ether. Net/IP Products Testing to begin in Fall, 2000 l l l Feb 11, 2000 ASTEM (Kyoto, Japan) University of Michigan (Ann Arbor) University of Warwick (Coventry, England)

ODVA will promote Ether. Net/IP Multiple organizations will support the rapid adoption of Ethernet/IP l Introductory training for developers and product managers – l l l 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 Control. Net Intl/ODVA Ethernet SIG – – – Feb 11, 2000 Next Training is May 2 in Cleveland Guidelines for Vendors Guidelines for Users Collect and Publish Performance Benchmarks