An EtherCAT master stack is the software layer that manages communication between a controller and devices on an EtherCAT network. For embedded automation systems, selecting and integrating this layer involves more than exchanging process data: engineers also need to consider the real-time operating system, network configuration, synchronization, diagnostics, and how the application will access master functions.
A modular software development kit can help address these requirements across different processor architectures and operating systems. The EC-Master SDK from acontis, for example, is designed for embedded real-time environments and provides a C/C++ API, configuration through an ENI file, and implementation options for several operating systems and processor families. Its architecture illustrates the main building blocks and engineering considerations involved in an embedded EtherCAT master.
What an EtherCAT master stack does
The master coordinates communication on the network. Its core handles EtherCAT protocol functions, including cyclic process data transfer and mailbox protocols. These services allow the controller to exchange time-sensitive control data as well as access protocol-specific functions supported by connected slaves.
Configuration is another central task. The EC-Master SDK uses an EtherCAT Network Information (ENI) file, following ETG.2100, to describe the network configuration. During startup, a topology check can compare the configured network with the actual network. This gives the application a way to detect a mismatch as the system boots, rather than relying solely on assumptions about the connected devices.
The SDK is described as compliant with the EtherCAT Master Classes Directive, ETG.1500. It also supports multiple cyclic process-data update rates. These capabilities are relevant when designing a controller that must coordinate network communication with its application’s control tasks.
Modular architecture supports integration
A master implementation typically spans several software responsibilities. In the EC-Master architecture, these are divided among modules so that protocol handling, operating-system interaction, Ethernet transport, and application access can be addressed separately.
- Master Core: Implements the principal master functionality, including protocol handling, process-data transfer, and mailbox communication.
- OS Abstraction: Encapsulates operating-system calls. This layer helps adapt the master to supported platforms, with many functions implemented using C-language macros to support performance.
- Ethernet driver: Provides the MAC-specific real-time link layer used to transport EtherCAT frames.
- Wrapper Library: Offers object-oriented access to master functions for applications written in C# or Python.
This separation is useful when evaluating an implementation for a particular controller platform. The master core, operating-system services, and network interface must work together in the target system. Ready-to-run implementations are listed for a range of operating systems, compilers, and Ethernet drivers, while additional porting and integration work may be needed for other environments.
Protocol coverage and network visibility
EtherCAT networks can use mailbox protocols for functions beyond cyclic process-data exchange. The Class B feature set described for EC-Master includes CANopen over EtherCAT (CoE), Servo Profile over EtherCAT (SoE), Ethernet over EtherCAT (EoE), ADS over EtherCAT (AoE), File Transfer over EtherCAT (FoE), and Vendor over EtherCAT (VoE). CoE support includes SDO upload and download, SDO information services, and emergency requests.
Other listed functions include slave-to-slave communication, access to slave EEPROM and registers, and support for Failsafe Safety over EtherCAT (FSoE) slaves. The relevance of each capability depends on the devices and application requirements in a given machine. Confirming required protocols and device functions during system design helps avoid treating the master as a simple cyclic-data interface.
Diagnostics are also part of the engineering picture. The SDK includes error detection and diagnosis functions, providing application developers with tools to identify communication or configuration issues. The available information does not replace system-level validation, but detailed error reporting can help make faults more visible during commissioning and operation.
Distributed Clocks and synchronization
For applications that require coordinated timing, the Class A edition adds synchronization with EtherCAT Distributed Clocks (DC), including different master synchronization modes. Distributed Clocks are a network synchronization capability; their use should be considered alongside the controller’s timing architecture and the needs of the connected devices.
The SDK also lists an optional external synchronization feature for synchronizing multiple network segments operated by multiple controllers. This is distinct from simply configuring one network: it addresses synchronization across segments under separate controllers and should be evaluated when an application architecture calls for that arrangement.
Optional features for changing or redundant networks
Feature packs add functions for specific system needs. Hot Connect supports preconfigured network sections being added to or removed from the network before startup or during operation. Cable Redundancy is designed to compensate for a cable break or slave breakdown. Master Redundancy provides a second, fully redundant master system intended to take over if the primary master fails.
These options address different failure or configuration scenarios and should not be treated as interchangeable. System designers need to determine which network changes or failures their application must handle, then assess the relevant feature and overall system design.
A Remote Access API provides a TCP/IP interface with the same API for remote and local operation, which can be used by diagnostic and configuration tools. The SDK also lists operating-system network drivers for TCP/IP communication between tools and slaves through EoE.
Choosing a platform and planning integration
Processor and operating-system fit are practical selection criteria for an embedded master. The listed CPU architectures include x86, ARM, and PowerPC, and the operating-system options include Linux and real-time Linux, Windows, QNX, VxWorks, Zephyr, FreeRTOS, and other embedded and real-time environments. Ethernet drivers are available for several controller and network-interface families, with additional options available on request.
Before implementation, engineering teams can usefully confirm:
- Whether the target processor, operating system, compiler, and Ethernet interface are supported.
- Which ENI configuration, protocols, update rates, and diagnostics the application requires.
- Whether Distributed Clocks, external synchronization, Hot Connect, or redundancy functions are needed.
- How the application will access master functions and how the network will be commissioned and maintained.
The vendor also describes workshops, consulting, performance analysis and optimization, customer-specific development, porting, and system integration services. Such support may be relevant when an implementation must be adapted to an embedded operating system or a specific target platform.
Conclusion
An embedded EtherCAT master is a combination of protocol software, operating-system integration, Ethernet transport, and application interfaces. Evaluating those elements together helps technical teams align the master with the target hardware, network devices, timing requirements, and maintenance approach. Features such as diagnostics, Distributed Clocks, remote access, and optional redundancy can extend the implementation, but the right configuration depends on the system’s actual communication and availability requirements.