Getting on the Right Motion Bus
- Created: Friday, 01 February 2008
As modern machines have become more advanced, the complexity involved in motion control has escalated. Today, servos have replaced cams and gears on machines and multiple axis of synchronized motion control have become commonplace. Distributed motion control requires busses able to handle rigid jitter and timing demands including:
- High data throughput and low latency. Motion requires the controller to frequently update the drive with new trajectory setpoints. As a rule of thumb, each drive should get new setpoints at least every 1 μs.
- Tight synchronization. Drives perform interpolation based on trajectory points to close the loop much faster than 1 μs. The interpolation loops must be synchronized to the controller and, for applications such as electronic gearing and camming, to other drives. As a rule of thumb, clocks should be synchronized to 1 μS.
Today busses such as CANopen and SERCOS have become dominant solutions for distributed motion control; however, they have limited options for I/O compared to more dominant busses such as PROFIbus, DeviceNet, and Modbus. With the emergence of industrial Ethernet busses, designers have a number of new options.
To make Ethernet viable for motion control, manufacturers are using new IT technologies such as packet prioritization using IEEE 802.1D/Q for Quality of Service (QoS) to reduce switch induced jitter and IEEE 1588 Precision Time Protocol (PTP) to enable distributed clock synchronization. Manufacturers are also layering other technologies such as Time Division Multiple Access (TDMA) and adding custom hardware.
There are over 30 different “Industrial Ethernet” protocols being marketed today, but four of them stand out as supporting I/O and motion on one bus and have multi-vendor support. Other popular Ethernet busses should also be considered, including SynqNet and Sercos III, but were not included because of limited I/O availability.
EtherNet/IP (ODVA.org) uses unmodified Ethernet with high-end switches that support QoS and 1588 to provide soft real-time performance. While devices supporting EtherNet/IP with CIP Motion are not yet released, Rockwell has demonstrated multi-axis synchronized motion using Ethernet/IP. Ethernet/IP with CIP Motion uses 1588 to synchronize clocks and QoS to prioritize packets and reduce the jitter on the network. Because it is impossible to eliminate all switch jitter using QoS, EtherNet/IP drives also implement an extrapolation algorithm to allow devices to ride through late data conditions. EtherNet/IP with CIP Motion is stated to provide less than 200-ns clock jitter and a cycle time of 100 axes at 1 ms.
PROFINET (Profibus.com) defines three levels, non real-time (NRT) used for slower updates (100 ms), real-time (RT) used for I/O updates (10 ms), and Isochronous real-time (IRT) used for motion control (1 ms). PROFINET IRT uses a combination of 1588, TDMA, and specialized switches to achieve hard real-time performance. When the network is configured, the master analyzes the network topology and the data required from each device and configures the network so each cycle has a real-time period and a non-real-time period. Each IRT device is assigned a time slot to communicate during the real-time period. Because all the IRT devices are synchronized using 1588, only one IRT device at a time sends packets. Switches with special ASICs buffer packets sent from non-IRT devices during the real-time period and transmit them during the non-real-time period. During the non-real-time period, any RT and NRT data as well as any standard TCP/IP traffic can be communicated. PROFINET IRT is stated to provide less than 1 μs clock jitter and a cycle time of 150 axes at 1 ms.