EtherCAT communication solutions
The Ethernet-based EtherCAT fieldbus is designed for automation technology and accommodates both hard and soft real-time requirements.
The fieldbus EtherCAT based on Ethernet has been designed for automation technology and thus meets hard as well as soft real-time requirements. EtherCAT (Ethernet Control Automation Technology) was developed by the EtherCAT Technology Group (ETG). In the same way as with comparable protocols, the EtherCAT development aimed for short cycle times of less than 100 µs, low hardware costs, and low jitter for exact synchronization. With this, the EtherCAT technology is based on the international standards IEC 61158 and IEC 61784 with standardization in ISO 15745-4. The speed of the Ethernet system EtherCAT for time-critical applications in the field of motion control is a key feature.
In the past, EtherCAT has set new standards for the evaluation and transfer of data packets on the basis of the Ethernet. Especially noticeable is the fact that the EtherCAT technology performs no step-by-step reception, interpretation, and further copying of the process data.
In contrast, the data intended for EtherCAT slave devices is extracted parallel to the passage of telegrams through the device. The introduction of the input data into the telegram takes place in the same way. The delay of the respective telegrams amounts to only a few nanoseconds. Not least, the payload data rate could be optimized to 90 %, as the sending and the reception direction of the Ethernet frame are used to reach the data of different participants. In this way, the EtherCAT technology can reach data rates in the range close to 200 Mbps by using the full duplex characteristics of 100BASE-TX. Data is exchanged between master and slaves in the form of process data objects (PDO). Each PDO has a separate address referring to one or more slaves. With this, the combination of payload data and address forms an EtherCAT telegram. The telegrams are delayed only a few nanoseconds during processing. The protocol definitions are enabled with EtherCAT for different sectors:
- Clock synchronization
- Easy installation diagnosis
- Acyclic demand rate transfer
- Cyclic I/O data transfer
The EtherCAT Topology
The full-duplex character of Ethernet forms the basis for the transfer procedures of EtherCAT. Star, ring, tree, line, and combinations resulting from them are possible as topologies for EtherCAT. The advantageous characteristics of industrial communication that distinguish EtherCAT result from this:
- Master redundancy with hot stand-by
- Device switching with active network
- Line redundancy
- Hot connect of segments
Because of the combination of different network characteristics and the topology variations, no additional switches are required on one hand, while on the other hand many possibilities result because of the variations, like neighboring or subordinate control concepts. While the E-bus is used exclusively as a physical layer for modular devices, the Fast Ethernet physics permit max. line lengths of 100 m between the individual participants. However, the individual line lengths can be provided with individual signal variants. The almost unlimited net expanse with EtherCAT results from the fact that a maximum of 65535 participants can be coupled to a network segment. With this, optical waveguides can also be used to bridge distances of up to 20 km.
Precise Diagnoses with EtherCAT
The EtherCAT protocol is known to ensure very quick and exact recognition of problems and faults recognition, which is one of the outstanding diagnosis characteristics of the technology. For example, the CRC checksum is responsible for recognition of bit errors in the transfer. The hamming distance with a value of 4 is a characteristic of the 32 bit CRC polynomials. Furthermore, specific quality monitoring of individual transfer lines is possible, which can be traced back to the transfer physics, the topology, and the protocol of EtherCAT. Critical network sections are thus recognized quickly and precisely with the aid of automatic evaExisting device profiles can be combined with different software interfaces. In this way, it is rather easy to enable a migration from fieldbus to EtherCAT by just adapting the firmware as the hardware.
The following software interfaces are possible via EtherCAT:
CAN application layer
- Various device and application profiles with diverse applications and device classes
- Application profiles, proportional valves, and hydraulic controllers (CiA 408)
- Encoder (CiA 406)
- Drive profile (CiA 402), standard in IEC 61800-7-201/301
- Sercos enables real-time communication as an interface
- Suitable for performance-intensive motion control applications
- Standardization of the servo drives in the IEC 61800-7
- Same standardization of the profile to EtherCAT (IEC 61800-7-304)
- Ethernet devices can be connected within EtherCAT with the aid of switch ports
- Tunneling of the Ethernet frames by means of the EtherCAT protocol (standard with VPN, TCP/IP, PPPoE)
- No impairment of the EtherCAT real-time communication
- Similar to the TFTP protocol
- Uniform firmware update possible (no TCP/IP support required)
- Possible access to any data structure in the respective device
- Security protocol independent of the fieldbus
- Available as safety over EtherCAT
- Functional, TÜV-certified safety according to safety integrity level 3 and IEC 61508
- Worldwide standardized since 2010 in IEC 61784-3-12
- No slowing down of cycle time or transfer rate
Black channel (transport medium) is not taken into consideration in the safety analysis.