Utilizziamo i cookie per rendere migliore la tua esperienza di navigazione. Per rispettare la nuova direttiva sulla privacy, è necessario chiedere il tuo consenso per impostare i cookie. Per saperne di più.
Analyzing and Decoding of EtherCAT Protocol based on network configuration file (ENI)
The recorded EtherCAT frames are decoded based on what is included in the EtherCAT Network Information (ENI) file. This file contains the definition of the process image, all variables including the data types, as well as the structure of the cyclic frames. The ENI file is part of the EtherCAT specification ETG.2100 and can be generated by any EtherCAT configuration software. Usually the ENI file is required by the EtherCAT master anyway, so this means that there is no additional engineering effort.
A Test Access Point (TAP) must be inserted into the existing EtherCAT network to capture the EtherCAT frames. The TAP is recommended to be placed between the master and the first slave, but it can also be installed between any two slave devices. However, it is only possible to completely analyze all input and output data when the TAP is installed immediately after the master, because some data (LRW commands) are overwritten by the downstream slave's subsequent input data. The TAP device (e.g. Dualcomm ETAP-1000), should have a short propagation delay in order not disturb the overall network timing.
With the EC-Monitor library, there is no need to intervene in the network, control, the EtherCAT master software, or the configuration. EC-Monitor is therefore suitable for new installations (greenfield) as well as for existing systems and machines (brownfield).
The EC-Monitor library can be used on numerous operating systems like Windows, Linux, QNX, and more without any modifications. The network controller is connected via a special driver from acontis known as the link layer. High-performance link layers designed specifically by acontis for use with EC-Monitor are available for numerous Ethernet controllers.
EC-Monitor processes the ENI file and uses it to determine a variety of aspects of the system like the number of slaves, the structure of the process image, the variable names, and the variable offset in the process data image. Based on this data, the application can dynamically adapt to different network configurations.
Use Case: Diagnosis Tool
The EC-Monitor library provides the necessary data from the network for an EtherCAT diagnostic software to be created by the customer. In addition to displaying the topology and process data, this tool can also be used to localize communication faults. As long as the EtherCAT master software is regularly checking the slave error counter register, this data can also be decoded by the EC-Monitor and made available to the application for further processing. For example, the location and cause of possible errors can be determined from the slave, along with port-specific error counters (bad cables or faulty plug connections), and the results can be displayed graphically. The acontis EC-Inspector is an example of such a tool.
Use Case: IIoT Gateway, (Embedded) Edge Device
An important feature of the EC-Monitor library is the lossless recording of all process data. This is a prerequisite for implementing applications for quality assurance (condition monitoring) or for predictive maintenance. The recorded data can then be analyzed and processed with appropriate algorithms, e.g., on a PC or in an embedded device. The information collected may afterwards be forwarded to a central server or to a cloud. The monitoring of the manufacturing process is, among other things, a prerequisite for the complete traceability of a product.
Use Case: Observation of critical applications with a “Supervisor” System
The EC-Monitor library allows the complete investigation of the entire process data of an EtherCAT network in real-time. For safety-critical applications, this data can be validated by an application on another system. This monitoring system thus controls the main application and can take appropriate measures to shut down the main controller in the event of a fault.
- Analyzing and Decoding the EtherCAT Protocol
- Utilizes the EtherCAT Network Information (ENI) file
- Monitoring of Process Data Variables
- Monitoring of Slave States
- Monitoring of Slave Error Counters (ESC registers 0x300 to 0x313)
- Processing of previously captured raw network traffic (Wireshark files)
- Save raw network traffic in a PCAP (Wireshark) file
- No integration with an existing master controller required
- Suitable for New (Greenfield) and Existing (Brownfield) installations
- No specific TAP required, even a regular switch device may be used
- No impact (e.g. timing, load) on the existing application
- No changes to existing software required
- Very small engineering effort: simply use the existing ENI file
- Use the same software to analyze machines operated by controllers from different manufacturers (Beckhoff, Bosch-Rexroth, Omron, Yaskawa, etc.)