Industrial Ethernet:Merging the worlds of data and control by building on open standards For years control engineers have imagined a world where every element of a control system is smart... ...where everything is connected Centralized controllers were a good start but they are artifacts of an earlier time Modern architectures overcome the limits of centralized systems The question is how one interconnects all of the devices Some propose that ethernet and TCP/IP link every device Some see ethernet and TCP/IP as unsuitable for use with every device, but ideal for linking clusters of devices What’s the right answer? What are the necessary characteristics of a sensor and actuator network? Low cost Open protocol Robust physical layer and connectorization EMI and EMC (1000-4-2/3/4/5/6 at heavy industrial levels) Support for multiple media Twisted pair (unshielded, shielded, armored, flexible, high temperature, multiple gauges, etc.) Fiber optics, RF, coaxial Option for combination power/data Industrial temperature range How do ethernet and TCP/IP measure up? Low cost – no, not relative to other means Open protocol – TCP/IP, while a data standard, is not a control protocol. If TCP/IP is used as an open transport then a control protocol – an open control protocol - must still be created Robust physical layer – does not meet European susceptibility limits except at very high cost, still has single points of failure in hubs – doesn’t offer multidrop signaling Robust connectorization – must be created Support for multiple media – yes but at high cost if one wished to mix-and-match media types Option for combination power/data – not standard Industrial temperature range – only at high cost And then there’s the issue of a control protocol Open, robust, secure Tailored for distributed control applications Operable on multiple media Routable for wide area connectivity Addressing support for both small and large networks Based on these issues, ethernet and TCP/IP aren’t ideal for connection to every device Could ethernet and TCP/IP be made to work to every device? Probably, with a lot of development work and money Would they offer an advantage over other approaches? They would offer high speed - useful in only the fastest applications Disadvantages? Require development of a new protocol Add cost Single points of failure EMC issues Impose significant physical layer restrictions on wiring, connectorization, and power distribution Is there a better approach? Yes – use ANSI/EIA 709.1 - a robust, low cost control network designed specifically to link together all of the industrial devices + Use ethernet and TCP/IP to link clusters of devices together – or to an HMI or ERP system or the Internet Industrial control networking ANSI/EIA 709.1: the LonTalk® Protocol Robust, field proven standardized protocol More than 13,000,000 devices already shipped Used by 4,000 customers around the world High performance, low cost transceivers available for every application including twisted pair with and without power Includes a robust and comprehensive network management architecture, routers, network interfaces, and a complete suite of development tools Every ANSI/EIA709.1 device is accessible over any TCP/IP network... The i.LONTM 1000 Internet Server Enables millions of existing products to be on the Internet Cisco NetWorks branded: includes Cisco DNA ANSI/EIA709.1/IP Router and Web server Communicates directly with IP-based HMIs Why use ANSI/EIA709.1, ethernet, and TCP/IP? Device Web Servers Device Web Servers High cost, no control Adds significant cost to every device Two connections per device Increases installation, maintenance and training costs and complexity Different tools for local and remote access Poor scalability Gateways Gateway Disadvantages Provide a tiny window into the control system Limits data exchange, diagnostics and maintenance Difficu