Beckhoff EPP6228-0022 User manual

Documentation | EN
EPP6228-0022
IO-Link master
2022-08-25 | Version: 1.3

Table of Contents
EPP6228-0022 3Version: 1.3
Table of Contents
1 Foreword....................................................................................................................................................5
1.1 Notes on the documentation .............................................................................................................5
1.2 Safety instructions.............................................................................................................................6
1.3 Documentation issue status ..............................................................................................................7
2 Product group: EtherCATPBox modules..............................................................................................8
3 Product overview ......................................................................................................................................9
3.1 Introduction .......................................................................................................................................9
3.2 Technical data.................................................................................................................................10
3.3 Scope of supply...............................................................................................................................11
3.4 Process image ................................................................................................................................12
4 IO-Link basics..........................................................................................................................................13
4.1 IO-Link system layout......................................................................................................................13
4.2 Establishment of IO Link communication ........................................................................................15
4.3 Device description IODD.................................................................................................................16
4.4 Parameter server ............................................................................................................................16
4.5 Data transfer rate ............................................................................................................................16
5 Mounting and cabling .............................................................................................................................17
5.1 Mounting .........................................................................................................................................17
5.1.1 Dimensions ......................................................................................................................17
5.1.2 Fixing................................................................................................................................ 18
5.2 Functional earth (FE) ......................................................................................................................18
5.3 Cabling ............................................................................................................................................19
5.3.1 EtherCATP ......................................................................................................................20
5.3.2 IO-Link.............................................................................................................................. 24
5.4 UL Requirements ............................................................................................................................26
5.5 Disposal ..........................................................................................................................................27
6 Commissioning and configuration........................................................................................................28
6.1 Integrating into a TwinCAT project..................................................................................................28
6.2 Configuration of the IO link master..................................................................................................29
6.3 Configuration of the IO-Link devices ...............................................................................................30
6.3.1 Open the IO link configuration tool................................................................................... 30
6.3.2 Integrating IO-Link devices .............................................................................................. 31
6.3.3 Removal of IO-Link devices ............................................................................................. 40
6.3.4 Activating the configuration .............................................................................................. 41
6.4 Settings of the IO-Link devices .......................................................................................................42
6.5 EPIxxxx, ERIxxxx - Setting of the IO-Link device parameters ........................................................44
6.6 Access to IO-Link data ....................................................................................................................55
6.6.1 IO-Link system communication ........................................................................................ 55
6.6.2 PDO Assignment.............................................................................................................. 56
6.6.3 Accessing IO-Link parameters ......................................................................................... 57
6.6.4 Parameter data exchange................................................................................................ 58
6.6.5 ADS.................................................................................................................................. 59
6.6.6 Access to events .............................................................................................................. 60

Table of Contents
EPP6228-00224 Version: 1.3
6.7 Restoring the delivery state.............................................................................................................61
6.8 Decommissioning............................................................................................................................62
7 Diagnosis .................................................................................................................................................63
7.1 Status of the IO-Link ports ..............................................................................................................63
7.1.1 Interpretation of the status bytes...................................................................................... 63
7.2 ADS Error Codes ............................................................................................................................65
7.3 Further error diagnosis....................................................................................................................68
8 Appendix..................................................................................................................................................69
8.1 General operating conditions ..........................................................................................................69
8.2 Accessories.....................................................................................................................................70
8.3 Version identification of EtherCAT devices .....................................................................................71
8.3.1 General notes on marking................................................................................................ 71
8.3.2 Version identification of EP/EPI/EPP/ER/ERI boxes........................................................ 72
8.3.3 Beckhoff Identification Code (BIC) ................................................................................... 73
8.3.4 Electronic access to the BIC (eBIC)................................................................................. 75
8.4 Support and Service........................................................................................................................77

Foreword
EPP6228-0022 5Version: 1.3
1 Foreword
1.1 Notes on the documentation
Intended audience
This description is only intended for the use of trained specialists in control and automation engineering who
are familiar with the applicable national standards.
It is essential that the documentation and the following notes and explanations are followed when installing
and commissioning these components.
It is the duty of the technical personnel to use the documentation published at the respective time of each
installation and commissioning.
The responsible staff must ensure that the application or use of the products described satisfy all the
requirements for safety, including all the relevant laws, regulations, guidelines and standards.
Disclaimer
The documentation has been prepared with care. The products described are, however, constantly under
development.
We reserve the right to revise and change the documentation at any time and without prior announcement.
No claims for the modification of products that have already been supplied may be made on the basis of the
data, diagrams and descriptions in this documentation.
Trademarks
Beckhoff®, TwinCAT®, TwinCAT/BSD®, TC/BSD®, EtherCAT®, EtherCATG®, EtherCATG10®, EtherCATP®,
SafetyoverEtherCAT®, TwinSAFE®, XFC®, XTS® and XPlanar® are registered trademarks of and licensed by
Beckhoff Automation GmbH. Other designations used in this publication may be trademarks whose use by
third parties for their own purposes could violate the rights of the owners.
Patent Pending
The EtherCAT Technology is covered, including but not limited to the following patent applications and
patents: EP1590927, EP1789857, EP1456722, EP2137893, DE102015105702 with corresponding
applications or registrations in various other countries.
EtherCAT® is registered trademark and patented technology, licensed by Beckhoff Automation GmbH,
Germany.
Copyright
© Beckhoff Automation GmbH & Co. KG, Germany.
The reproduction, distribution and utilization of this document as well as the communication of its contents to
others without express authorization are prohibited.
Offenders will be held liable for the payment of damages. All rights reserved in the event of the grant of a
patent, utility model or design.

Foreword
EPP6228-00226 Version: 1.3
1.2 Safety instructions
Safety regulations
Please note the following safety instructions and explanations!
Product-specific safety instructions can be found on following pages or in the areas mounting, wiring,
commissioning etc.
Exclusion of liability
All the components are supplied in particular hardware and software configurations appropriate for the
application. Modifications to hardware or software configurations other than those described in the
documentation are not permitted, and nullify the liability of Beckhoff Automation GmbH & Co. KG.
Personnel qualification
This description is only intended for trained specialists in control, automation and drive engineering who are
familiar with the applicable national standards.
Description of instructions
In this documentation the following instructions are used.
These instructions must be read carefully and followed without fail!
DANGER
Serious risk of injury!
Failure to follow this safety instruction directly endangers the life and health of persons.
WARNING
Risk of injury!
Failure to follow this safety instruction endangers the life and health of persons.
CAUTION
Personal injuries!
Failure to follow this safety instruction can lead to injuries to persons.
NOTE
Damage to environment/equipment or data loss
Failure to follow this instruction can lead to environmental damage, equipment damage or data loss.
Tip or pointer
This symbol indicates information that contributes to better understanding.

Foreword
EPP6228-0022 7Version: 1.3
1.3 Documentation issue status
Version Comment
1.3 • Product image updated
• Technical data updated
• Chapter "Commissioning and configuration" updated
• Structure update
1.2 • Dimensions updated
• UL requirements updated
1.1 • Front page updated
1.0 • First release
0.1 • First preliminary version
Firmware and hardware versions
This documentation refers to the firmware and hardware version that was applicable at the time the
documentation was written.
The module features are continuously improved and developed further. Modules having earlier production
statuses cannot have the same properties as modules with the latest status. However, existing properties
are retained and are not changed, so that older modules can always be replaced with new ones.
The firmware and hardware version (delivery state) can be found in the batch number (D-number) printed on
the side of the EtherCAT Box.
Syntax of the batch number (D-number)
D: WW YY FF HH
WW - week of production (calendar week)
YY - year of production
FF - firmware version
HH - hardware version
Example with D no. 29 10 02 01:
29 - week of production 29
10 - year of production 2010
02 - firmware version 02
01 - hardware version 01
Further information on this topic: Version identification of EtherCAT devices [}71].

Product group: EtherCATPBox modules
EPP6228-00228 Version: 1.3
2 Product group: EtherCATPBox modules
EtherCATP
EtherCATP supplements the EtherCAT technology with a process in which communication and supply
voltages are transmitted on a common line. All EtherCAT properties are retained with this process.
Two supply voltages are transmitted per EtherCATP line. The supply voltages are electrically isolated from
each other and can therefore be switched individually. The nominal supply voltage for both is 24VDC.
EtherCATP uses the same cable structure as EtherCAT: a 4-core Ethernet cable with M8 connectors. The
connectors are mechanically coded so that EtherCAT connectors and EtherCATP connectors cannot be
interchanged.
EtherCATP Box modules
EtherCATP Box modules are EtherCATP slaves with degree of protection IP67. They are designed for
operation in wet, dirty or dusty industrial environments.
EtherCAT basics
A detailed description of the EtherCAT system can be found in the EtherCAT system documentation.

Product overview
EPP6228-0022 9Version: 1.3
3 Product overview
3.1 Introduction
FE
FE
Tx+ / GND
Rx+ / GND
Rx- / U
Tx- / U
1 |
2 |
3 |
4 |
S
S
P
P
EtherCAT P
downstream connection
EtherCATP
input
1 |
2 |
3 |
4 |
5 |
L+
Input
L-
C/Q
n.c.
IO-Link Ports
Class A
IO-Link-Master
The EPP6228 IO-Link module enables connection of up to eight IO-Link devices, e.g. IO-Link box modules,
actuators, sensors or combinations thereof. A point-to-point connection is used between the module and the
device. The EtherCAT P Box is parameterised via the EtherCAT master. IO-Link is designed as an intelligent
link between the fieldbus level and the sensor, so that parameterisation information can be exchanged
bidirectionally via the IO-Link connection. The parameterisation of the IO-Link devices with service data can
be done from TwinCAT via ADS or very conveniently via the integrated IO-Link configuration tool. In addition
to the IO-Link channels, the EPP6228 features eight digital inputs on pin 2 of the respective M12 socket. In
the standard setting, the IO-Link channels C/Qx of the EPP6228 accept both IO-Link devices and standard
sensors with 24 V DC.
Quick links
Technical data [}10]
Process image [}12]
IO-Link connection [}24]

Product overview
EPP6228-002210 Version: 1.3
3.2 Technical data
All values are typical values over the entire temperature range, unless stated otherwise.
EtherCATP
Connection 2xM8 socket, 4-pin, P-coded, red
Distributed Clocks yes
Supply voltages
Connection See EtherCATP connection
US nominal voltage 24VDC (-15%/ +20%)
US sum current: IS,sum max. 3A
Current consumption from US100mA
+ Current consumption of the connected IO-Linkdevices
Rated voltage UP24VDC (-15%/ +20%)
UP sum current: IP,sum max. 3A
Current consumption from UPNone. UP is only forwarded.
IO-Link Ports
Number 8x ClassA
Connection 8x M12 socket
Cable length max. 20m
Specification IO-Link V1.1
Data rate COM1: 4.8kbit/s
COM2: 38.4kbit/s
COM3: 230.4kbit/s
Device power supply 24VDC from the control voltage US
max. 1.4A per port, short-circuit proof
max. 3.0A in total
Digital input (pin2): characteristic Type3 according to EN61131-2, compatible with type1
Digital input (pin2): input filter 10µs
Digital input (pin2): input current 3.0mA
Housing data
Dimensions WxHxD 60mmx 126mmx 26.5mm (without plug connectors)
Weight approx. 250 g
Installation position variable
Material PA6 (polyamide)
Environmental conditions
Ambient temperature during operation -25 … +60°C
-25 … +55°C according to cULus
Ambient temperature during storage -40 … +85°C
Vibration resistance, shock resistance conforms to EN60068-2-6/ EN60068-2-27
Additional checks [}11]
EMC immunity / emission conforms to EN61000-6-2/ EN61000-6-4
Protection class IP65, IP66, IP67 (conforms to EN60529)
Approvals/ markings
Approvals/ markings*) CE, cULus [}26]

Product overview
EPP6228-0022 11Version: 1.3
*) Real applicable approvals/markings see type plate on the side (product marking).
Additional checks
The boxes have been subjected to the following checks:
Verification Explanation
Vibration 10 frequency sweeps in 3 axes
5Hz<f<60Hz displacement 0.35mm, constant amplitude
60.1Hz<f<500Hz acceleration 5g, constant amplitude
Shocks 1000 shocks in each direction, in 3 axes
35g, 11ms
3.3 Scope of supply
Make sure that the following components are included in the scope of delivery:
• 1 x EPP6228-0022 EtherCAT P Box
• 2x protective cap for EtherCATP socket, M8, red (pre-assembled)
• 10x labels, blank (1 strip of 10)
Pre-assembled protective caps do not ensure IP67 protection
Protective caps are pre-assembled at the factory to protect connectors during transport. They may
not be tight enough to ensure IP67 protection.
Ensure that the protective caps are correctly seated to ensure IP67 protection.

Product overview
EPP6228-002212 Version: 1.3
3.4 Process image
Assignment of IO-Link ports to process data
Process image in TwinCAT IO-Link
port
Status variable Process data of
the IO-Link device
Digital input
1
Module 2
DeviceState Inputs
State Ch1
Module 3 1) Module 11
Digital Inputs
Pin2 Ch1
2
Module 2
DeviceState Inputs
State Ch2
Module 4 1) Module 11
Digital Inputs
Pin2 Ch2
3
Module 2
DeviceState Inputs
State Ch3
Module 5 1) Module 11
Digital Inputs
Pin2 Ch3
4
Module 2
DeviceState Inputs
State Ch4
Module 6 1) Module 11
Digital Inputs
Pin2 Ch4
5
Module 2
DeviceState Inputs
State Ch5
Module 7 1) Module 11
Digital Inputs
Pin2 Ch5
6
Module 2
DeviceState Inputs
State Ch6
Module 8 1) Module 11
Digital Inputs
Pin2 Ch6
7
Module 2
DeviceState Inputs
State Ch7
Module 9 1) Module 11
Digital Inputs
Pin2 Ch7
8
Module 2
DeviceState Inputs
State Ch8
Module 10 1) Module 11
Digital Inputs
Pin2 Ch8
1) The modules "Module 3" to "Module 10" only exist in the process data if the corresponding IO-Link ports
have been configured.

IO-Link basics
EPP6228-0022 13Version: 1.3
4 IO-Link basics
IO-Link is a communication system for connecting intelligent sensors and actuators to an automation system.
The IEC61131-9 standard specifies IO-Link under the designation "Single-drop digital communication
interface for small sensors and actuators" (SDCI).
Both the electrical connection data and the communication protocol are standardized and summarized in the
IO-Link Spec.
4.1 IO-Link system layout
An IO-Link system consists of an IO-Link master and one or more IO-Link devices, i.e. sensors or actuators.
The IO-Linkmaster provides the interface to the higher-level controller and controls communication with the
connected IO-Linkdevices.
The IO-Linkmasters from Beckhoff have several IO-Linkports, to each of which one IO-Linkdevice can be
connected. IO-Link is not a fieldbus, but rather a point-to-point connection.

IO-Link basics
EPP6228-002214 Version: 1.3
CAUTION
Risk of device damage
The IO-Linkdevices must be supplied from the 24V power supply of the IO-Linkmaster provided for this
purpose. Otherwise, damage to the IO-Linkport is possible.

IO-Link basics
EPP6228-0022 15Version: 1.3
4.2 Establishment of IO Link communication
The establishment of the IO-Link communication is illustrated in Fig. Establishment of IO-Link
communication. This illustrates in particular the sequence when automatically scanning [}35] the IO-Link
port.
Fig.1: Establishment of IO Link communication
• If an IO-Link device is connected to a master port, the master attempts to establish communication. A
defined signal level, the wake-up pulse, signals to the device that UART bytes are to be sent from now
on.
From this point on, all data will be interpreted by the IO-Link device as UART bytes.
• The master runs through all baud rates [}16], starting with the fastest baud rate
(COM3=230kbaud). A successful connection has been established when the slave responds to the
wake-up pulse.
• First of all the master reads the basic parameters (Vendor ID, Device ID, process data length,
telegram type and cycle time) and compares them with the existing configuration.
• If no connection could be established to the device, or if the saved parameters differ from those read,
the corresponding error is output.
• If the saved parameters differ from those read, the IO-Link device changes to the PREOP state.
If the IO-Link device specification is V1.1, the parameter server [}16] is now executed. If the IO-Link
device specification is V1.0, this step is omitted and the device changes directly to OP.
• Finally the cycle time is written and the device changes to OP. After that the master cyclically
exchanges data with the device.

IO-Link basics
EPP6228-002216 Version: 1.3
4.3 Device description IODD
IO-Link devices possess individual system information in the form of an IO device description (IODD), which
contains:
• Communication features
• Device parameters with value range and default values
• Identification, process and diagnostic data
• Device data
• Text description
• Picture of the device
• Vendor's logo
If the IODD is imported, then the device data are automatically detected during automatic scanning [}35]
with TwinCAT and adopted in the System Manager.
4.4 Parameter server
In order to be able to use the functionality of the parameter server, both the IO-Link master and the IO-Link
device must be specified to V1.1. The IO-Link revision of the device can be read for the individual port under
Settings [}42]. All IO-Link masters from Beckhoff with current firmware support the IO-Link specification
V1.1.
• The parameter server in the IO-Link master contains parameter data that are saved in the IO-Link
device. The memory capacity is max. 2kbyte (including header).
If the IO-Link device is exchanged, then the data are loaded from the parameter server into the new
device. The requirement for this is that the device is of the same type (VendorID and DeviceID must be
the same).
• If a new IO-Link device is configured, then the IO-Link master loads the parameters from the IO-Link
device into the parameter server when starting for the first time.
Data from other IO-Link devices that are already configured (VendorID and DeviceID do not
correspond to the configured device) are overwritten.
• At each further start the IO-Link master uses a checksum to check whether the data in the parameter
server correspond to those on the IO-Link device and if necessary downloads them to the device.
• If the parameters change during the device runtime, this can be reported to the Master via the store
button [}50] (ParamDownloadStore [}51]). The master then starts the parameter server with an
upload.
• By default the event is not set each time the parameters are written, therefore the end of the
parameterization procedure has to be reported to the IO-Link device via the store button [}50]
(ParamDownloadStore [}51]).
The IO-Link device then sends the corresponding event to the master. The data are loaded into the
parameter server.
• In the case of a pre-programmed IO-Link device, no download takes place from the parameter server
to the device.
4.5 Data transfer rate
An IO-Link master according to specification V1.1 supports all three transmission methods and automatically
adjusts the baud rate to that of the IO-Link device.
An IO-Link device usually supports only one baud rate. IO-Link devices with different baud rates can be
connected to the various ports of the master.
• COM1 = 4.8 kbaud
• COM2 = 38.4 kbaud
• COM3 = 230.4 kbaud

Mounting and cabling
EPP6228-0022 17Version: 1.3
5 Mounting and cabling
5.1 Mounting
5.1.1 Dimensions
117
26.560
Ø 4.5
126
14
All dimensions are given in millimeters.
The drawing is not true to scale.
Housing features
Housing material PA6 (polyamide)
Sealing compound polyurethane
Mounting two mounting holes Ø4.5 mm for M4
Metal parts brass, nickel-plated
Contacts CuZn, gold-plated
Installation position variable
Protection class IP65, IP66, IP67 (conforms to EN 60529) when screwed together
Dimensions (H x W x D) approx. 126 x 60 x 26.5 mm (without connectors)

Mounting and cabling
EPP6228-002218 Version: 1.3
5.1.2 Fixing
NOTE
Dirt during assembly
Dirty connectors can lead to malfunctions. Protection class IP67 can only be guaranteed if all cables and
connectors are connected.
• Protect the plug connectors against dirt during the assembly.
Mount the module with two M4 screws in the centrally located mounting holes.
5.2 Functional earth (FE)
The mounting holes also serve as connections for the functional earth (FE).
Make sure that the box is grounded to low impedance via the functional earth (FE) connections. You can
achieve this, for example, by mounting the box on a grounded machine bed.
FE
FE
Fig.2: Connection for functional earth (FE)

Mounting and cabling
EPP6228-0022 19Version: 1.3
5.3 Cabling
Tightening torques for plug connectors
Screw connectors tight with a torque wrench. (e.g. ZB8801 from Beckhoff)
Connector diameter Tightening torque
M8 0.4Nm
M12 0.6Nm

Mounting and cabling
EPP6228-002220 Version: 1.3
5.3.1 EtherCATP
WARNING
Power supply from SELV/PELV power supply unit!
SELV/PELV circuits (Safety Extra Low Voltage, Protective Extra Low Voltage) according to
IEC61010-2-201 must be used to supply the EtherCATP Power Sourcing Device (PSD).
Notes:
• SELV/PELV circuits may give rise to further requirements from standards such as IEC60204-1etal, for
example with regard to cable spacing and insulation.
• A SELV (Safety Extra Low Voltage) supply provides safe electrical isolation and limitation of the voltage
without a connection to the protective conductor,
a PELV (Protective Extra Low Voltage) supply also requires a safe connection to the protective conduc-
tor.
CAUTION
Observe the UL requirements
• When operating under UL conditions, observe the warnings in the chapter UL Requirements [}26].
EtherCATP transmits two supply voltages:
•Control voltage US
The following sub-functions are supplied from the control voltage US:
◦ the fieldbus
◦ the processor logic
◦ typically the inputs and the sensors if the EtherCATPBox has inputs.
•Peripheral voltage UP
The digital outputs are typically supplied from the peripheral voltage UP for EtherCATPBox modules
with digital outputs. UP can be supplied separately. If UP is switched off, the fieldbus function, the
function of the inputs and the supply of the sensors are maintained.
The exact assignment of US and UP can be found in the pin assignment of the I/O connections.
Redirection of the supply voltages
The supply voltages are passed on internally from the "IN" connection to the "OUT" connection. Hence, the
supply voltages US and UP can be passed from one EtherCATPBox to the next EtherCATPBox in a simple
manner.
NOTE
Note the maximum current.
Ensure that the maximum permitted current of 3A for the M8 connectors is not exceeded when redirecting
EtherCATP.