What is PowerLink?

Ethernet POWERLINK is a real-time industrial Ethernet technology designed for deterministic communication between controllers and automation devices. It can connect PLCs, distributed I/O, servo drives, motor drives, robotics, vision systems and other field equipment while maintaining predictable communication timing.
In simple terms: POWERLINK organises Ethernet communication so that industrial devices do not compete randomly for transmission time. A controller determines when each device is allowed to exchange time-critical data, making communication predictable enough for machine control and synchronized motion applications.
POWERLINK in this article means the industrial Ethernet technology
The name “PowerLink” is also used by unrelated companies and electrical products. In this article, however, POWERLINK refers specifically to the real-time Ethernet communication technology. It is not a brand of transformers, circuit breakers, switchgear or power-distribution equipment.
POWERLINK belongs to the wider field of industrial communication and is based on standard IEEE 802.3 Ethernet. Its distinguishing feature is the way access to the network is scheduled for deterministic real-time operation.
How does Ethernet POWERLINK work?
A POWERLINK network contains two principal node roles: the Managing Node (MN) and Controlled Nodes (CNs). A PLC, motion controller or industrial PC may act as the Managing Node and coordinate the communication cycle.
Devices such as remote I/O, motor drives, servo drives and other field equipment normally operate as Controlled Nodes. Instead of allowing every device to transmit whenever it chooses, the Managing Node coordinates when the nodes may communicate.
This deterministic access method is based on a combination of polling and defined time slots. The approach prevents several nodes from attempting to use the real-time channel unpredictably at the same instant and allows the control system to maintain a repeatable communication cycle.
What happens during a POWERLINK communication cycle?
A POWERLINK communication cycle is divided into several controlled phases. At the beginning of the cycle, the Managing Node sends a SoC — Start of Cycle frame to synchronize the participating Controlled Nodes.
The real-time or isochronous phase follows. The Managing Node communicates with the Controlled Nodes using mechanisms including PReq — Poll Request and PRes — Poll Response. This phase carries the process information whose timing is important for control.
For example, a servo drive may receive motion setpoints and return actual position or status information, while distributed I/O exchanges input and output states with the controller during predictable network cycles.
A later asynchronous phase is reserved for information that is not as time-critical. The Managing Node opens this section using a Start of Asynchronous mechanism and grants access for configuration, diagnostics and other Ethernet traffic.
Does POWERLINK use TCP/IP for real-time control?
Not for the time-critical process cycle. The statement that POWERLINK performs its real-time control simply by transmitting normal TCP/IP traffic is misleading. Deterministic process data is handled by the POWERLINK real-time communication mechanism at Ethernet level.
Standard TCP/IP-based services can still coexist with POWERLINK. Non-time-critical TCP/IP traffic is assigned communication capacity in the asynchronous portion of the POWERLINK cycle, allowing service, configuration and other standard Ethernet functions to operate without being treated as hard real-time process data.
This separation is useful because a control network may need both extremely predictable drive or I/O communication and ordinary service access to devices at the same time.
What is the relationship between POWERLINK and CANopen?
POWERLINK incorporates many application-layer concepts associated with CANopen. These include the Object Dictionary, Process Data Objects, Service Data Objects and network-management concepts.
PDOs — Process Data Objects are used for process information that needs efficient cyclic exchange, while SDOs — Service Data Objects provide access to parameters and device objects that do not need to be transferred during every real-time cycle.
For this reason POWERLINK has sometimes been described as CANopen over Ethernet. That description refers to its application model; it does not mean that POWERLINK runs physically on a CAN bus. POWERLINK uses Ethernet as its network infrastructure.
How fast is Ethernet POWERLINK?
POWERLINK was designed for applications where communication timing matters more than simply quoting a high nominal network bit rate. Its deterministic cycle allows very short control-cycle times and tight synchronization when the network and devices are engineered accordingly.
Actual performance depends on the number of nodes, amount of process data, required update frequency and asynchronous traffic. It is therefore incorrect to assume that every POWERLINK network will achieve exactly the same cycle time.
This distinction is especially important in synchronized motion-control and servo systems. Multi-axis machines require not only sufficient bandwidth but also low jitter and accurate synchronization between axes.
How many devices can be connected to a POWERLINK network?
The old statement that Ethernet POWERLINK is limited to 63 nodes is not a general POWERLINK specification limit. Standard POWERLINK addressing provides Controlled Node IDs from 1 to 239, while Node ID 240 is assigned to the Managing Node.
This does not mean that every real machine should contain 239 Controlled Nodes on one tightly synchronized cycle. The practical network size depends on the required cycle time, process-data volume and communication frequency of each device.
What is an XDD device description?
POWERLINK uses an XML-based device-description system known as XDD — XML Device Description. It provides engineering tools with structured information about a device, its communication capabilities and its object dictionary.
The purpose is similar to the role played by device-description files in other industrial networks, although the formats themselves are different. Adding a POWERLINK device to a control system therefore involves more than connecting an Ethernet cable: Node ID, process-data mapping, object configuration and controller settings also have to match.
Where is POWERLINK used?
POWERLINK is particularly suited to industrial applications that require deterministic or synchronized communication. Examples include production machinery, packaging equipment, printing systems, distributed I/O, robotics, machine vision and multi-axis motion control.
A POWERLINK PLC can coordinate remote I/O while drives exchange operating data and servo axes exchange position or motion information. Field signals originating from industrial sensors can be processed within the same automation architecture.
Machine information may then be displayed locally through an HMI panel or forwarded to a higher-level SCADA system. These supervisory functions should be distinguished from the deterministic POWERLINK process cycle itself.
What is the difference between POWERLINK and standard Ethernet?
Standard Ethernet provides the underlying frame transmission and physical network technology. POWERLINK adds a deterministic access mechanism and an industrial communication model on top of that Ethernet foundation.
A computer having an Ethernet port therefore does not automatically make it a POWERLINK Controlled Node. The device must implement the POWERLINK protocol and the required device model.
POWERLINK is designed to remain compatible with standard Ethernet technology rather than requiring an entirely unrelated physical network. This also allows common Ethernet diagnostic approaches to be useful when troubleshooting the physical network.
Are POWERLINK and EtherCAT the same?
No. POWERLINK and EtherCAT are separate real-time industrial Ethernet technologies. Both can be used for fast machine and motion-control applications, but their communication mechanisms are fundamentally different.
POWERLINK coordinates network access through a Managing Node and scheduled Controlled Nodes. EtherCAT instead uses its own on-the-fly frame-processing architecture as Ethernet frames pass through participating devices.
For a servo or robotic system, protocol selection should therefore be based on controller support, drive interfaces, synchronization requirements and the existing machine architecture rather than simply comparing nominal Ethernet speeds.
Are POWERLINK and EtherNet/IP the same?
No. They both use Ethernet technology but implement different industrial communication architectures. EtherNet/IP is based on CIP — Common Industrial Protocol, whereas POWERLINK uses its own deterministic communication cycle and a CANopen-oriented application model.
An RJ45 connector or ordinary Ethernet link therefore does not indicate which industrial protocol a PLC, VFD or servo drive supports. POWERLINK, EtherNet/IP, EtherCAT and PROFINET capability must be checked separately in the device specifications.
Is POWERLINK still supported?
POWERLINK was first presented publicly in 2001. From 2003, the Ethernet POWERLINK Standardization Group — EPSG coordinated standardization and further development of the technology.
The EPSG was dissolved on 31 March 2023. Since April 2023, B&R Industrial Automation has taken responsibility for continued development, technical support and certification of POWERLINK and makes the specifications and related tools available through its POWERLINK resources.
POWERLINK is specified within the international industrial Ethernet standards IEC 61158-13 and IEC 61784-2. It should therefore not be described as an abandoned proprietary interface simply because the former EPSG organization no longer operates.
What is openPOWERLINK?
openPOWERLINK is an open-source implementation of the POWERLINK protocol stack. It should be distinguished from the POWERLINK protocol specification itself and from individual manufacturers' proprietary POWERLINK software implementations.
For example, B&R states that its products use B&R's own POWERLINK implementation rather than the openPOWERLINK software stack, even though both implement the same POWERLINK communication standard at protocol level.
Why does a POWERLINK network fail to communicate?
Troubleshooting should begin with the physical Ethernet connection. Check device power, cables, connectors and link status before changing controller software. An illuminated Ethernet link LED proves only that a physical link exists; it does not prove that real-time POWERLINK communication has been established.
Next verify the Managing Node / Controlled Node roles, Node IDs, network cycle configuration and device-description data. A duplicate or incorrect Node ID can prevent expected communication even though the physical network appears healthy.
In drive and motion applications, PDO mapping and device-profile configuration should also be checked. A controller and servo drive may be present on the network while motion commands still fail because the expected process-data objects do not match.
Practical POWERLINK troubleshooting checklist
1. Does the controller actually support operation as a POWERLINK Managing Node?
2. Are the field devices configured as compatible POWERLINK Controlled Nodes?
3. Are all Node IDs valid and unique?
4. Does the configured cycle time suit the number of nodes and amount of process data?
5. Are PDO and SDO mappings consistent with the actual device configuration?
6. Are cables, connectors and Ethernet infrastructure suitable for the equipment and installation?
7. Has the device entered normal POWERLINK operation rather than remaining in a basic Ethernet or initialization state?
8. What do the controller diagnostics and device status indicators report before parameters are changed?
Related Industrial Communication Guides
Industrial Communication · What Is Ethernet? · CANopen · EtherCAT · EtherNet/IP
Related Automation Pages
PLCs and Modules · HMI Panels · SCADA · AC Drives and VFDs · Servo Systems · Sensors · Industrial Robotics