Implementation strategies for POWERLINK

Among a large number of Ethernet-based communication systems that are suitable for automation due to their real-time capability, nowadays solutions such as PROFINET, EtherNet/IP, EtherCAT, POWERLINK or Sercos III set the standards. Although all of the above-mentioned systems are based on Ethernet, they vary considerably in terms of their specific features and areas of application. When selecting a suitable protocol, not only criteria such as performance, availability and hardware costs play a decisive role but also the possibilities for optimum implementation.

read the whole article…

By Christian Schlegel, IXXAT Automation GmbH

Today, the industrial automation market for Ethernet-based communication is increasing in demand. As with classical field busses, several protocol standards are available for Industrial Ethernet, which have to be supported by device manufacturers. Since these different Ethernet standards vary in their hardware and software requirements, a specific protocol solution for their integration into a device is required.

Despite the efforts of IAONA to find a common solution for industrial communication over Ethernet, disparate protocols emerged that were sponsored and promoted by a number of classic field bus suppliers. Eleven concepts to achieve Ethernet relevant for industrial communication are currently standardized within IEC 61158. Similar to the so-called “field bus wars” in the eighties, in the end, some of the eleven Industrial Ethernet solutions will be accepted in the market.

… read more

By Christian Schlegel, IXXAT Automation

One solution circumventing the limitations of CANopen (limited bandwidth, limited system extension) would be switching completely to Ethernet POWERLINK. However, for many systems this would be like the tail wagging the dog since the POWERLINK technology is more expensive than the CANopen technology (e.g. cabling costs, hardware costs, system integration costs). Instead of converting a system completely from CANopen to POWERLINK, it often makes sense to build a new system structure using several subsystems. The following two system architectures are possible…

… read more

By Dr. Martin Merkel, Christian Schlegel, IXXAT Automation GmbH

Already in the early days of CAN, Philips Medical Systems noticed the advantages of CAN and decided to use this network protocol as communication network for interconnecting various components such as collimators, generators, and patient tables in their x-ray systems. To achieve a modular and open approach, a group within Philips Medical Systems, managed by Tom Suters, developed the first higher layer protocol for CAN, the CAN Message Specification – CMS, which was presented to the public in 1992.
CMS provided the framework for the first official CAN based communication protocol specified by CAN in Automation, the CAN Application Layer (CAL). One of the reasons that may have lead to the limited market penetration was that CAL did not provide the functionality necessary for a straight-forward description of generic device or application profiles…

… read more

Integration of FlexRay-based control units in existing test benches by using a FlexRay/CAN gateway

Today, measuring and control technology in vehicle test benches is connected to the control units via CAN interfaces.
read more…