Ethernet Powerlink

This article includes a list of general references, but it lacks sufficient corresponding inline citations. Please help to improve this article by introducing more precise citations. (June 2011) (Learn how and when to remove this message)

|

Ethernet Powerlink is a real-time protocol for standard Ethernet. It is an open protocol managed by the Ethernet POWERLINK Standardization Group (EPSG). It was introduced by Austrian automation company B&R in 2001.

This protocol has nothing to do with power distribution via Ethernet cabling or power over Ethernet (PoE), power line communication, or Bang & Olufsen's PowerLink cable.

## Overview

[edit]

Ethernet Powerlink expands Ethernet with a mixed polling and timeslicing mechanism. This provides:

* Guaranteed transfer of time-critical data in very short isochronic cycles with configurable response time
* Time-synchronisation of all nodes in the network with very high precision of sub-microseconds
* Transmission of less time-critical data in a reserved asynchronous channel

Modern implementations reach cycle-times of under 200 μs and a time-precision (jitter) of less than 1 μs.

## Standardization

[edit]

Powerlink was standardized by the Ethernet Powerlink Standardization Group (EPSG) and founded in June 2003 as an independent association. Working groups focus on tasks like safety, technology, marketing, certification and end users. The EPSG cooperates with the standardization bodies and associations, like the CAN in Automation (CiA) Group and the IEC.

## Physical layer

[edit]

The original physical layer specified was 100BASE-TX Fast Ethernet. Since the end of 2006, Ethernet Powerlink with Gigabit Ethernet supported a transmission rate ten times higher (1,000 Mbit/s).

Repeating hubs instead of switches within the Real-time domain is recommended to minimise delay and jitter.[1] Ethernet Powerlink uses IAONA's Industrial Ethernet Planning and Installation Guide for clean cabling of industrial networks and both industrial Ethernet connectors 8P8C (commonly known as RJ45) and M12 are accepted.

## Data link layer

[edit]

The standard Ethernet data link layer is extended by an additional bus scheduling mechanism, which secures that at a time only one node is accessing the network. The schedule is divided into an isochronous phase and an asynchronous phase. During the isochronous phase, time-critical data is transferred, while the asynchronous phase provides bandwidth for the transmission of non time-critical data. The Managing Node (MN) grants access to the physical medium via dedicated poll request messages. As a result, only one single node (CN) has access to the network at a time, which avoids collisions, present on older Ethernet hubs before switches. The CSMA/CD mechanism of non-switched Ethernet, which caused non-deterministic Ethernet behaviour, is avoided by the Ethernet Powerlink scheduling mechanism.

## Basic cycle

[edit]

After system start-up is finished, the Real-Time domain is operating under Real-Time conditions. The scheduling of the basic cycle is controlled by the Managing Node (MN). The overall cycle time depends on the amount of isochronous data, asynchronous data and the number of nodes to be polled during each cycle.

The basic cycle consists of the following phases:

* Start Phase: The Managing Node is sending out a synchronization message to all nodes. The frame is called SoC—Start of Cycle.
* Isochronous Phase: The Managing Node calls each node to transfer time-critical data for process or motion control by sending the Preq - Poll Request - frame. The addressed node answers with the Pres - Poll Response - frame. Since all other nodes are listening to all data during this phase, the communication system provides a producer-consumer relationship.

The time frame which includes Preq-n and Pres-n is called time slot for the addressed node.

* Asynchronous Phase: The Managing Node grants the right to one particular node for sending ad-hoc data by sending out the SoA—Start of Asynchronous—frame. The addressed node will answer with ASnd. Standard IP-based protocols and addressing can be used during this phase.

The quality of the Real-Time behavior depends on the precision of the overall basic cycle time. The length of individual phases can vary as long as the total of all phases remain within the basic cycle time boundaries. Adherence to the basic cycle time is monitored by the Managing Node. The duration of the isochronous and the asynchronous phase can be configured.

Picture 1: Frames above the time line are sent by the MN, below the time line by different CNs.

Picture 2: Time slots for nodes and the asynchronous time slot

Multiplex for Bandwidth Optimization

In addition to transferring isochronous data during each basic cycle, some nodes are also able to share transfer slots for better bandwidth utilization. For that reason, the isochronous phase can distinguish between transfer slots dedicated to particular nodes, which have to send their data in every basic cycle, and slots shared by nodes to transfer their data one after the other in different cycles. Therefore, less important yet still time-critical data can be transferred in longer cycles than the basic cycle. Assigning the slots during each cycle is at the discretion of the Managing Node.

Picture 3: Time slots in EPL multiplexed mode.

Poll response chaining

Mode used mainly for robotics applications and large superstructures. Key is lower number of frames and better data distributions.

## OpenSAFETY

[edit]

Today, machines, plants and safety systems are stuck in a rigid scheme made up of hardware-based safety functions. The consequences of this are cost-intensive cabling and limited diagnostic options. The solution is the integration of safety relevant application data into the standard serial control protocol. OpenSAFETY allows both publish/subscriber and client/server communication. Safety relevant data is transmitted via an embedded data frame inside of standard communication messages. Measures to avoid any undetected failures due to systematic or stochastic errors are an integral part of a functional safety protocol. OpenSAFETY is in conformance with IEC 61508. The protocol fulfills the requirements of SIL 3\. Error detection techniques have no impact on existing transport layers.

## Notes

[edit]

1. ^ "POWERLINK Communication Profile Specification". 2013: 35. `{{cite journal}}`: Cite journal requires `|journal=` (help)

## References

[edit]

* Machine safety Tactical brief (2012), "Machine Safety" (PDF), Automation World, archived from the original (PDF) on 2012-09-07, retrieved 2012-08-23

* Humphrey, David (2012), openSAFETY Initiative Aims to Unify Industrial Safety Protocols, USA: ARC Advisory Group, archived from the original on 2012-08-17

* "POWERLINK Awarded National Standard in China", Control Engineering Asia, 2012, archived from the original on 2013-01-19

* "DDASCA Consortium defines openSAFETY as standard", Automation.com, 2012

* Zezulka, F.; Hyncica, o. (2008), "Průmyslový Ethernet VIII: Ethernet Powerlink, Profinet" (PDF), Automa, 5: 62–66

* Which Ethernet system is the right one?, Control Engineering Europe, 2009

## External links

[edit]

* ethernet-powerlink.org Ethernet POWERLINK Standardization Group website
* sourceforge.net/projects/openpowerlink Open Source Stack

Ethernet Powerlink and OpenSafety Forums on LinkedIn

* Ethernet Powerlink Group
* OpenSafety Group

* v
* t
* e

Automation protocols

Process automation|

* AS-i
* BSAP
* CC-Link Industrial Networks
* CIP
* CAN bus
* CANopen
* DeviceNet
* ControlNet
* DF-1
* DirectNET
* EtherCAT
* Ethernet Global Data (EGD)
* Ethernet Powerlink
* EtherNet/IP
* Factory Instrumentation Protocol
* FINS
* FOUNDATION fieldbus
* H1
* HSE
* GE SRTP
* HART Protocol
* Honeywell SDS
* HostLink
* INTERBUS
* IO-Link
* MECHATROLINK
* MelsecNet
* Modbus
* Optomux
* Process Image Exchange Protocol (PieP)
* PROFIBUS
* PROFINET
* RAPIEnet
* SERCOS interface
* SERCOS III
* Sinec H1
* SynqNet
* TTEthernet

Industrial control system|

* MTConnect
* OPC DA
* OPC HDA
* OPC UA

Building automation|

* 1-Wire
* BACnet
* BatiBUS
* C-Bus
* CEBus
* DALI
* DSI
* DyNet
* EnOcean
* EHS
* EIB
* FIP
* KNX
* LonTalk
* Modbus
* OpenTherm
* oBIX
* VSCP
* X10
* xAP
* xPL
* Z-Wave
* Zigbee

Power-system automation|

* IEC 60870
* IEC 60870-5
* IEC 60870-6
* DNP3
* Factory Instrumentation Protocol
* IEC 61850
* IEC 62351
* Modbus
* PROFIBUS

Automatic meter reading|

* ANSI C12.18
* IEC 61107
* DLMS/IEC 62056
* M-Bus
* Modbus
* Zigbee

Automobile / Vehicle|

* AFDX
* ARINC 429
* CAN bus
* ARINC 825
* SAE J1939
* NMEA 2000
* FMS
* Factory Instrumentation Protocol
* FlexRay
* IEBus
* J1587
* J1708
* Keyword Protocol 2000
* Unified Diagnostic Services
* LIN
* MOST
* SENT (SAE J2716)
* VAN
* Cyphal

* v
* t
* e

Ethernet family of local area network technologies

Speeds|

* 10 Mbit/s
* 100 Mbit/s
* 1 Gbit/s
* 2.5 and 5 Gbit/s
* 10 Gbit/s
* 25 and 50 Gbit/s
* 40 and 100 Gbit/s
* 200, 400, 800 and 1600 Gbit/s

General|

* Physical layer
* Autonegotiation
* EtherType
* Flow control
* Frames
* Jumbos

Organizations|

* IEEE 802.3
* Ethernet Alliance

Media|

* Fiber
* Twisted pair
* Coaxial
* First mile
* 10G-EPON

Historic|

* CSMA/CD
* StarLAN
* 10BROAD36
* 10BASE-FB
* 10BASE-FL
* 10BASE5
* 10BASE2
* MAU
* FOIRL
* 100BaseVG
* LattisNet
* Long Reach

Applications|

* Audio
* Automotive
* Carrier
* Data center
* Energy Efficiency
* Industrial
* Metro
* Power
* Synchronous

Transceivers|

* GBIC
* SFP/SFP+/QSFP/QSFP+/OSFP
* XENPAK/X2
* XFP
* CFP

Interfaces|

* AUI
* EAD
* MDI
* MII
* GMII
* XGMII
* XAUI

* Category
* Commons

*[v]: View this template
*[t]: Discuss this template
*[e]: Edit this template