| Real Time Automation | ![]() |
Contact Us | ![]() |
Support | ![]() |
Link to Us |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
|
INTRODUCTION We live in a time of major changes to the way electronic Drive System systems are manufactured, integrated, supported and maintained. No longer are our customers willing to accept islands of automation. Instead the trend, if not the demand, is for open systems that seamlessly integrate from the lowest sensor on the factory floor to the Enterprise Manufacturing Execution System. Data which once was unobtainable is now required. Data, once hand collected, now must be effortlessly assembled, sorted and merged. It must be painlessly transferred from the factory floor to the desk of the CEO even if that desk is a continent away. These trends and business requirements are not unique to Drive System end users. They cut across many major vertical markets including medical, automotive manufacturing, military, aerospace, and process control (chemical, food, beverage and many others). These trends are driving major enhancements to both hardware and software controls technology. Costs are falling, speeds are sharply increasing, functionality is greater than ever and integration time is dropping. There are four overriding factors that are driving increased networking of all types of controls including Drive System control: 1. Increased Time-to-Market Pressure It’s no secret that business today is fast paced. Life cycles for specialty foods are short. Medicines, once approved, need to quickly get into distribution. Brewery and other beverage systems are required to quickly meet production goals. Costs to discretely wire a new point with point-to-point wiring continue to rise both for labor and materials. Engineering time to add new points, especially if more hardware is required, is more scarce. Networking is one way machines can be assembled faster, with less overall cost and with fewer errors. In some networks a Drive System controller can be added by simply clamping the controller on the network cable. 2. Shrinking resource allocation Manufacturing staffs are now at staffed at levels that would have been inconceivable just a few years ago. Time for training, planning and documenting is just not available in some companies. More and more manufacturers are depending on their suppliers, distributors and integrators to bring complete solutions that meet their cost and time-to-market pressures. Integrators, under continuous price pressure, are not only staffed lower overall but staff projects with fewer resources than just a few short years ago. The ability to speedily create a solution is more important than ever. In this resource-starved environment, a network Drive System controller supplier that supports multiple drive system networks, delivers clear, concise documentation, exceptional diagnostics and reliable operation is hard for competitors to displace. 3. Demands For Increased Productivity and Uptime Now more than ever, Drive System systems must contribute to an overall increase in quality, productivity and uptime. Market demands include diagnostics data (from simple cycle counts to failure predictions), shorter integration time, seamless integration into the customers chosen control scheme and immediate failure alarming. 4. Massive Technology Enhancements Controls technology enhancements over the last 10-20 years are going to be far outpaced by the enhancements to control technology over the next 3-5 years. Better, cheaper microprocessors with massive storage and outstanding computational capabilities are beginning to revolutionize the controls market. “Pre-wired” for CAN (Control Area Network), Profibus™ or even Ethernet these systems make network enabling your Drive System controllers more important than ever. Networked Drive System control is a primary piece of the puzzle to meet the complex requirements of customers in the Chemical, Beverage, Food, Pharmaceutical and other important Drive System markets. Networked Drive System Controllers must be quickly integrated into a customer’s automation system. They offer reduced wiring saving time, labor and materials. Many have semi-automatic software integration saving even more integration time. Plus a networked Drive System controller can provide diagnostics and operational feedback increasing system quality, productivity and uptime. If it’s not currently a requirement in your specific market today, it soon will be. What else has caused the enthusiasm for Networking? It’s no secret that proprietary fiefdoms have dominated the automation business ever since people started networking sensors. Hundreds of protocols have come and gone, and many of the dominant ones have served to protect the turf of the major control manufacturers. This has resulted in considerable angst from two groups: 1) users, who are tired of being locked into a whole series of decisions just because they bought a DCS, PLC or other control system; 2) smaller vendors, who often make innovative, advanced products, but are locked out by proprietary protocols. Networking is a very important to the Drive System Control industry, not only because it opens markets previously closed to smaller manufacturers but because it is backed by some of the biggest names in process and discrete automation. This gives network-enabled Drive System Controllers an automatic advantage in the marketplace. Traditional, hard-wired Drive System Controllers and field devices can no longer meet the needs of the demanding plant environment in the 2000s. The disadvantages of high installation costs and additional downtime are reinforced by the fact that hardwired field devices are unable to provide detailed operational information. Digitally networked systems are proving inherently more reliable, and offer advanced functionality and diagnostics. The Direction for 2005 and beyond: Ethernet Ethernet is no longer an option for advanced, complicated Industrial Devices like Drives – ETHERNET IS A REQUIREMENT. Ethernet is the fastest growing segment of Industrial Networking for one reason – The Market (Your Customers) Loves Ethernet. The reasons for this are many and obvious:
TCP/IP Quick Summary : TCP/IP is a protocol standard that comprises the two layers present in almost every Internet message. TCP is the Transport Control Protocol. It is the connection-based protocol that verifies that your message was received at the destination. TCP will retransmit messages that aren’t correctly received and report an error if the message can’t be delivered or if the connection is lost. IP is the Internet Protocol. The Internet Protocol routes messages, fragments large messages into multiple packets along with a number of other important tasks. Together, these protocols reliably move your data from a sending station to a receiving station. Unfortunately, the data is meaningless unless the two stations have a prior agreement on the format of the data. It’s like telling someone the score of the basketball game was 97 to 96. The data is received; it’s understood but worthless without a prior understanding of what teams played and who scored 97 and who scored 96. Advantages: TCP/IP is provided in almost every RTOS (Real Time Operating System). There are well-understood programming instructions for creating TCP/IP connections and sending and receiving data over TCP/IP. In short, it’s available, low cost (free if it’s included in your OS) and reliable. Disadvantages : TCP/IP alone provides no additional benefits to the end user. To use TCP/IP device manufacturers must implement some proprietary data protocol that end users must use to access the data in the drive. Drives only implementing TCP/IP are essentially mute as far as most Programmable Controllers are concerned. MODBUS/TCP Quick Summary: Modbus/TCP is the easiest to use, easiest to understand of all the high-level industrial application layer protocols for industrial automation applications. Modbus/TCP combines two extremely popular technologies, TCP/IP and the flat network view of Modbus RTU, to form a simple yet very functional worldwide standard for industrial data networking. Built on top of TCP/IP protocol, Modbus/TCP is compatible with all standard Ethernet hardware and software. Using the flat file structure of Modbus RTU as the network interface gives Modbus/TCP a much more straightforward method of representing device data than EtherNet/IP or PROFInet. TCP/IP, the Modbus RTU command set and the flat network representation make Modbus/TCP an easily understood and not difficult to implement Ethernet protocol. In the flat network representation carried over from Modbus RTU, devices on the Modbus/TCP network are represented as a set of up to 64K words and up to 64K bits (known as coils). Commands, identical to Modbus RTU commands, are issued from a Client device to read or write the data words or bits of a server device. Modbus/TCP is rapidly ground in applications that formerly used Modbus RTU, Modbus Plus and other serial communications protocols. Unlike other application layer protocols, Modbus/TCP communications are stateless. Each Client – Server transaction is totally independent of every other transaction. Advantages: Ease of implementation. Small code size. Easily understood object model. Small, very efficient set of commands. Disadvantages: No capability to abstract data. Little to no standards for device representation (called profiles in other application layers). An identical device from two different manufacturers will use completely different representations on the network. More Information: http://www.rtaautomation.com/modbustcp ETHERNET/IP Quick Summary: EtherNet/IP, promoted by the ODVA (Open DeviceNet Vendor Association), is much more sophisticated protocol than Modbus/TCP. EtherNet/IP classifies EtherNet/IP nodes as predefined device types with specific behaviors. The set of device types and the EIP application layer protocol is based on the Control and Information Protocol (CIP) layer used in both DeviceNet™ and ControlNet™. Building on these widely used protocol suites the CIP-based protocols provides a seamless integrated system from the sensor-actuator network to the controller and enterprise networks. EtherNet/IP uses all the transport and control protocols used in traditional Ethernet including the Transport Control Protocol (TCP), the Internet Protocol (IP) and the media access and signaling technologies found in off-the-shelf Ethernet interface cards. Structuring EtherNet/IP on these standard PC technologies allows EtherNet/IP to work transparently with all the standard off-the-shelf Ethernet devices found in today’s marketplace. It also means that EIP can be easily supported on standard PCs and all their derivatives. Even more importantly, basing EIP on a standard technology platform ensures that EIP will move forward as the base technologies evolve in the future. Advantages: EtherNet/IP devices are easily integrated into the Rockwell Automation Logix family architecture. Disadvantages: EtherNet/IP is complex to implement. More Information : www.rtaautomation.com/ethernetip PROFINET Quick Summary: PROFInet is really three different networking technologies; PROFInet CBA, PROFInet IO and PROFInet IRT. PROFInet CBA is a component model version of PROFInet. In CBA, PROFInet devices are Microsoft COM (Component Object Model) servers that represent device data using COM objects. These COM objects use standard COM Coclass (COM Class) classes, Interface pointers and member functions. Data is transported between a COM client and server at 10msec intervals. The solid infrastructure of COM, its data abstraction mechanisms and the ability to easily build distributed applications are incorporated into PROFInet CBA. PROFInet IO is the I/O version. It is much more like Profibus than like PROFInet CBA. Like Profibus, data is organized and transported over the network as I/O data. Data can be moved from server to client (PLC) at 1msec type speeds. PROFInet IRT is the isochronous version of PROFInet. This version is for coordinating high-speed motion control and is capable of response times in the 250nsec range. Advantages: PROFInet builds on the world-class and highly popular Profibus standard. Disadvantages: PROFInet is not easily ported to other architectures. More Information : www.rtaautomation.com/PROFInet Summary The industrial market is rapidly moving to a point where every single drive will be networked and the network will be some version of Industrial Ethernet. Gradually, serial, CAN and other network implementations will give way to Ethernet. In 2005 end users will no longer tolerate drive islands. Connectivity to provide status, rapid reconfiguration, energy monitoring and exception reporting will be the norm. Drive manufacturers must move quickly in 2005 to position themselves with Ethernet and one or more of the more pervasive application layer protocols; PROFInet, EtherNet/IP and Modbus/TCP. Real Time Automation, Inc. (RTA, Inc.) is a member of the Profibus Trade Organization (PTO), a member of the Open DeviceNet Vendor Association (ODVA), Modbus IDA and an authorized design partner for NetSilicon and a Design Alliance Partner (DAP) for Freescale Semiconductor. For more information see www.rtaautomation.com or contact John Rinaldi or 1-800-249-1612. |
1. Introduction 2. Increased Time-to-Market Pressure 3. Shrinking Resource Allocation 4. Demands For Increased Productivity and Uptime 5. Massive Technology Enhancements 6. What Else Has Caused the Enthusiasm for Networking? 7. The Direction for 2005 and Beyond: Ethernet 8. TCP/IP 9. Modbus TCP 10. ETHERNET/IP 11. PROFINET
» I want this file in PDF Format » I need to Ethernet Drive Network-enable My Product For Your Immediate Needs Call: John Rinaldi Networking Project Manager 1-800-249-1612 1-414-453-5100 |
RTA, Inc. - The Industrial Networking Home for DeviceNet, EtherNet/IP, Ethernet Drive,
Modbus TCP,
Modbus RTU, PROFINET CBA, PROFINET IO, BACnet, IEC 61131-3,
IEEE 1588, AS-Interface and other networks.
© 2009 Real Time Automation, Inc.
Networking in 30 Days or Less
www.rtaautomation.com
Real Time Automation, Inc. 2825 N. Mayfair Rd. Suite 11 Wauwatosa WI 53222 © Real Time Auomation, Inc. All Rights Reserved. | http://www.rtaautomation.com |
(414) 453-5100 (V) (414) 453-5125 (F) www.rtaautomation.com |