How it Works
Beckhoff
Loading...
EPP6228-0022
User manual
39 pgs2.48 Mb0
Table of contents
Loading...

Beckhoff EPP6228-0022 User manual

Download
Documentation | EN
EPP6228-0022
IO-Link master
2020-09-22 | Version: 1.1

Table of Contents

Table of Contents
1 Foreword ....................................................................................................................................................5
2 Product group: EtherCATP Box modules ..............................................................................................8
3 Product overview.......................................................................................................................................9
3.2 IO-Link master principles.................................................................................................................10
3.3 Technical data .................................................................................................................................11
3.4 Scope of supply ...............................................................................................................................12
3.5 Process image.................................................................................................................................13
4 Mounting and cabling..............................................................................................................................14
4.1 Mounting..........................................................................................................................................14
4.1.1 Dimensions ...................................................................................................................... 14
4.1.2 Fixing ............................................................................................................................... 15
4.2 Functional earth...............................................................................................................................15
4.3 Cabling ............................................................................................................................................16
4.3.1 EtherCATP...................................................................................................................... 16
4.3.2 IO-Link ............................................................................................................................. 19
4.4 UL Requirements.............................................................................................................................21
5 Commissioning and configuration ........................................................................................................22
5.1 Integration in TwinCAT ....................................................................................................................22
5.2 IO-Link configuration .......................................................................................................................23
5.2.1 Opening the configuration tool......................................................................................... 23
5.2.2 Assigning devices to ports ............................................................................................... 24
5.2.3 Supplementing the device catalog................................................................................... 24
5.2.4 Parameterizing a port ...................................................................................................... 25
5.2.5 Parameterizing a device .................................................................................................. 25
5.2.6 Configuring a port as a digital input/output ...................................................................... 25
5.2.7 Activating the configuration.............................................................................................. 25
5.3 Diagnosis.........................................................................................................................................26
5.3.1 IO-Link Events ................................................................................................................. 26
5.3.2 ADS Error Codes ............................................................................................................. 27
6 Appendix ..................................................................................................................................................29
6.1 General operating conditions...........................................................................................................29
6.2 Accessories .....................................................................................................................................30
6.3 Version identification of EtherCAT devices .....................................................................................31
6.3.1 Beckhoff Identification Code (BIC)................................................................................... 35
6.4 Support and Service ........................................................................................................................37
EPP6228-0022 3Version: 1.1
Table of Contents
EPP6228-00224 Version: 1.1
Foreword

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®, 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.
EPP6228-0022 5Version: 1.1
Foreword

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.
EPP6228-00226 Version: 1.1
Foreword

1.3 Documentation issue status

Version Comment
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
Further information on this topic: Version identification of EtherCAT devices [}31].
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
EPP6228-0022 7Version: 1.1
Product group: EtherCATP Box modules
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 IP67 protection. They are designed for operation in wet, dirty or dusty industrial environments.
Fig.1: EtherCATP
EtherCAT basics
A detailed description of the EtherCAT system can be found in the EtherCAT system documentation.
EPP6228-00228 Version: 1.1

3 Product overview

3.1 Introduction

Product overview
Fig.2: EPP6228-0022
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 [}11] Process image [}13] IO-Link connection [}19]
EPP6228-0022 9Version: 1.1
Product overview
IO-Link Master
...
IO-Link Port
IO-Link Port
IO-Link Port
...
...
IO-Link Device
IO-Link Device
IO-Link Device

3.2 IO-Link master principles

3.2.1 Topology

The IO-Link master serves as a gateway between an automation system (EtherCAT) and the IO-Link devices. It has several IO-Link ports, to each of which an IO-Link device can be connected.
Fig.3: IO-Link topology

3.2.2 Parameter memory

The IO-Link master has a parameter memory. The parameter memory can save a non-volatile copy of the parameters of connected devices.
If a device fails, its parameters remain in the parameter memory.
If a defective device is replaced by a new, identical device, the master can automatically parameterize the new device with the stored parameters.
EPP6228-002210 Version: 1.1
Product overview

3.3 Technical data

All values are typical values over the entire temperature range, unless stated otherwise.
Technical data EPP6228-0022
Fieldbus
Fieldbus EtherCAT Connection EtherCAT P: Combined connection for EtherCAT and supply
voltages
Input: 1 x M8 socket, 4-pin, P-coded Downstream connection: 1 x M8 socket, 4-pin, P-coded
Supply voltages
Connection See Fieldbus connection Control voltage U Nominal voltage 24VDC (-15%/ +20%) Sum current max. 3A Consumer • Module electronics: 100mA
Peripheral voltage U Nominal voltage 24VDC (-15%/ +20%) Sum current max. 3A Consumer -
IO-Link
Number of ports 8x Class A Connection 8x M12 socket Cable length max. 20m Specification IO-Link V1.1 Data rate COM1: 4.8 kbit/s
Device power supply 24VDC from the control voltage U
Digital input I/Q Characteristics Type 3 according to EN 61131-2, compatible with type 1 Filter 10µs Input current 3.0mA
Environmental conditions
Ambient temperature during operation
Ambient temperature during storage
Vibration / shock resistance conforms to EN 60068-2-6 / EN 60068-2-27 EMC immunity / emission conforms to EN 61000-6-2 / EN 61000-6-4 Protection class IP65, IP66, IP67 conforms to EN 60529
S
1)
• IO-Link devices
P
1)
COM2: 38.4 kbit/s COM3: 230.4 kbit/s
S
max. 1.4A per port, short-circuit proof max. 3.0A in total
-25 .. +60°C
-25 .. +55°C according to cURus
-40.. +85°C
1)
Sum current of consumers and power transmission.
EPP6228-0022 11Version: 1.1
Product overview
Technical data EPP6228-0022
Mechanics
Weight approx. 250g Installation position variable
Approvals and conformity
Approvals
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
CE, cULus [}21]

3.4 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.
EPP6228-002212 Version: 1.1

3.5 Process image

Assignment of IO-Link ports to process data
Product overview
Process image in TwinCAT IO-Link
port
1
2
3
4
Status variable Process data of
the IO-Link device
Module 2
Module 3
DeviceState Inputs
State Ch1
Module 2
Module 4
DeviceState Inputs
State Ch2
Module 2
Module 5
DeviceState Inputs
State Ch3
Module 2
Module 6
DeviceState Inputs
State Ch4
1)
1)
1)
1)
Digital input
Module 11
Digital Inputs
Pin2 Ch1
Module 11
Digital Inputs
Pin2 Ch2
Module 11
Digital Inputs
Pin2 Ch3
Module 11
Digital Inputs
Pin2 Ch4
5
Module 2
Module 7
DeviceState Inputs
State Ch5
6
Module 2
Module 8
DeviceState Inputs
State Ch6
7
Module 2
Module 9
DeviceState Inputs
State Ch7
8
Module 2
Module 10
DeviceState Inputs
State Ch8
1)
The modules "Module 3" to "Module 10" only exist in the process data if the corresponding IO-Link ports
1)
Module 11
Digital Inputs
Pin2 Ch5
1)
Module 11
Digital Inputs
Pin2 Ch6
1)
Module 11
Digital Inputs
Pin2 Ch7
1)
Module 11
Digital Inputs
Pin2 Ch8
have been configured [}23].
EPP6228-0022 13Version: 1.1
Mounting and cabling
117
6014
26.5
126
Ø 4.5
13.5

4 Mounting and cabling

4.1 Mounting

4.1.1 Dimensions

Fig.4: Dimensions
All dimensions are given in millimeters.
Housing features
Housing material PA6 (polyamide) Sealing compound polyurethane Mounting two fastening 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 Weight approx.250g
EPP6228-002214 Version: 1.1
Mounting and cabling
FE
FE

4.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 fastening holes.

4.2 Functional earth

The fastening 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.
Fig.5: Connection for functional earth (FE)
EPP6228-0022 15Version: 1.1
Mounting and cabling
1
2
3
4

4.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
4.3.1 EtherCATP
4.3.1.1 Connectors
NOTE
Risk of damage to the device!
Bring the EtherCAT/EtherCATP system into a safe, powered down state before starting installation, disas­sembly or wiring of the modules!
NOTE
Pay attention to the maximum permissible current!
Pay attention also for the redirection of EtherCATP, the maximum permissible current for M8 connectors of 3A must not be exceeded!
EtherCATP is supplied and forwarded via two M8 sockets at the upper end of the modules:
• IN: left M8 socket for EtherCATP power supply
• OUT: right M8 socket for EtherCATP forwarding
Fig.6: Connectors for EtherCAT P
Fig.7: M8 socket, P-coded
Contact Signal Voltage Core colors
1 Tx + GND 2 Rx + GND
S
P
3 Rx - UP: Peripheral voltage, +24V 4 Tx - US: control voltage +24V
DC
DC
yellow white blue orange
1)
Housing Shield Shield Shield
1)
The core colors apply to EtherCATP cables and ECP cables from Beckhoff.
EPP6228-002216 Version: 1.1
Mounting and cabling
4.3.1.2 Status LEDs
4.3.1.2.1 Supply voltage
Fig.8: Status LEDs for the power supply
EtherCAT P Box Modules have two LEDs that display the status of the supply voltages. The status LEDs are labelled with the designations of the supply voltages: Us and Up.
A status LED lights up green when the respective supply voltage is present.
A Status LED lights up red if the respective supply voltage is short-circuited.
4.3.1.2.2 EtherCAT
Fig.9: Status LEDs for EtherCAT
L/A (Link/Act)
A green LED labelled "L/A" or “Link/Act” is located next to each EtherCAT/EtherCATP socket. The LED indicates the communication state of the respective socket:
LED Meaning
off no connection to the connected EtherCAT device lit LINK: connection to the connected EtherCAT device flashes ACT: communication with the connected EtherCAT device
Run
Each EtherCAT slave has a green LED labelled "Run". The LED signals the status of the slave in the EtherCAT network:
LED Meaning
off Slave is in "Init" state flashes uniformly Slave is in "Pre-Operational“ state flashes sporadically Slave is in "Safe-Operational" state lit Slave is in "Operational" state
Description of the EtherCAT slave states
EPP6228-0022 17Version: 1.1
Mounting and cabling
I = 3 A
10 20
5
10
15
20
300
0
25
40
Vert. Faktor: 0,22 cm / V
Voltage drop (V)
Cable length (m)
0.14 mm²
0.22 mm²
0.34 mm²
4.3.1.3 Conductor losses
Take into account the voltage drop on the supply line when planning a system. Avoid the voltage drop being so high that the supply voltage at the box lies below the minimum nominal voltage.
Variations in the voltage of the power supply unit must also be taken into account.
Use the planning tool for EtherCAT P in TwinCAT.
Voltage drop on the supply line
Fig.10: Voltage drop on the supply line
EPP6228-002218 Version: 1.1

4.3.2 IO-Link

1
2
3
4
5
4.3.2.1 Connectors
The IO-Link ports are implemented as M12 sockets.
Fig.11: M12 socket
Mounting and cabling
Contact Function Description Core color
1 L+ Supply voltage (US1) brown
2 DI Digital input white
3 L- GND blue
4 C/Q IO-Link data cable black
5 - - grey
1)
The core colors apply to M12 sensor cables from Beckhoff:
• ZK2000-5xxx
• ZK2000-6xxx
• ZK2000-7xxx.
1)
EPP6228-0022 19Version: 1.1
Mounting and cabling
1 2
4.3.2.2 Status LEDs
Fig.12: Status LEDs of an IO-Link port
1 - IO-Link
LED signal Meaning
off Possibilities:
• Port not configured
• Logic level low
red illuminated
flashes sporadically green
Possibilities:
• IO-Link connection attempt
• No IO-Link device connected
• Incorrect IO-Link device connected
• IO-Link device defective flashing green IO-Link communication active green illuminated Logic level high
1)
1)
1)
Port configured as digital input or output
2 - Digital input DI
The LED lights up when a high level is present on the digital input DI.
EPP6228-002220 Version: 1.1
Mounting and cabling

4.4 UL Requirements

The installation of the EtherCAT Box Modules certified by UL has to meet the following requirements.
Supply voltage
CAUTION
CAUTION!
This UL requirements are valid for all supply voltages of all marked EtherCAT Box Modules! For the compliance of the UL requirements the EtherCAT Box Modules should only be supplied
• by a 24 VDC supply voltage, supplied by an isolating source and protected by means of a fuse (in accor­dance with UL248), rated maximum 4 Amp, or
• by a 24 VDC power source, that has to satisfy NEC class 2. A NEC class 2 power supply shall not be connected in series or parallel with another (class 2) power source!
CAUTION
CAUTION!
To meet the UL requirements, the EtherCAT Box Modules must not be connected to unlimited power sources!
Networks
CAUTION
CAUTION!
To meet the UL requirements, EtherCAT Box Modules must not be connected to telecommunication net­works!
Ambient temperature range
CAUTION
CAUTION!
To meet the UL requirements, EtherCAT Box Modules has to be operated only at an ambient temperature range of 0 to 55°C!
Marking for UL
All EtherCAT Box Modules certified by UL (Underwriters Laboratories) are marked with the following label.
Fig.13: UL label
EPP6228-0022 21Version: 1.1
Commissioning and configuration

5 Commissioning and configuration

5.1 Integration in TwinCAT

The procedure for integration in TwinCAT is described in this Quick start guide.
EPP6228-002222 Version: 1.1
Commissioning and configuration

5.2 IO-Link configuration

5.2.1 Opening the configuration tool

ü Requirement: an IO-Link master has been added in the Solution Explorer under the "I/O" entry.
1. Double-click on the IO-Link master.
ð A device editor for the IO-Link master opens.
2. Click on the "IO-Link" tab.
ð The IO-Link configuration tool opens.
Overview
The configuration tool contains two fields:
• „Ports“
The left-hand field "Ports" shows a list of the ports of the IO-Link master. If a device has been assigned to a port, the device designation is shown next to the port.
• „Catalog“
The right-hand field "Catalog" shows the device catalog. The device catalog contains a list of the IO­Link devices for which a device description exists in the local TwinCAT installation.
Changes in the IO-Link configuration tool only become effective when you activate the IO-Link configuration [}25].
EPP6228-0022 23Version: 1.1
Commissioning and configuration

5.2.2 Assigning devices to ports

There are four ways of assigning devices to ports:
Selecting a device from the device catalog
1. Search for the desired device in the "Catalog" field.
Not available? Supplementing the device catalog [}24]
2. Assign the device to a port. There are two ways to do this:
- Pull the device onto the desired port by drag-and-drop.
- Right-click on the device Click on "Add to Port n" in the context menu.
ð The device is assigned to the port
Importing the device description file IODD
1. Supplementing the device catalog [}24] > "Import from the file system"
2. Select a device from the device catalog [}24]
ð The device is assigned to the port
Scanning devices
ü Requirement: the master and the devices are cabled and supplied with voltage.
1. Click on the "Scan Devices" button.
ð The IO-Link master requests all connected devices to identify themselves. Each detected device is
automatically assigned to the port to which it is connected.
Entering the device description manually
1. Right-click on a port.
2. Click on "Create Device" in the context menu.
ð A dialog box opens.
3. Enter the items of information that describe the IO-Link device.

5.2.3 Supplementing the device catalog

Following the installation of TwinCAT, the device catalog contains only the device descriptions of IO­Linkdevices from Beckhoff. There are two ways of supplementing the catalog:
Importing from the online database "IODDfinder"
ü Requirement: the PC can access the Internet
1. Click on the "IODDfinder" button.
2. Search for the desired device.
3. Click on the image in the "Picture" column.
ð The device description is downloaded and added to the device catalog.
Importing from the file system
1. Click on the "Import device description" button
2. Open a device description file (IODD) in the dialog box that opens
ð The device description is added to the device catalog.
EPP6228-002224 Version: 1.1
Commissioning and configuration

5.2.4 Parameterizing a port

ü Requirement: A device is assigned to the port. Assigning devices to ports [}24].
1. In the "Ports" field, right-click on the port
2. Click on "Settings"
ð The "Settings" tab opens

5.2.5 Parameterizing a device

ü Requirement: The device is assigned to a port. Assigning devices to ports [}24].
1. In the "Ports" field, right-click on the device
2. Click on "Parameters"
ð The "Parameters" tab opens
Buttons
• „Read“
Read the parameter values from the device.
• „Write“
Write the parameter values to the device.
• „Set default“
Set the parameter values to the default values. The default values are adopted from the device description file. Die Standardwerte werden aus der Gerätebeschreibung im Device-Katalog übernommen.
• „Store“
Store the current parameter values in the Parameter Server. „Data Storage“.

5.2.6 Configuring a port as a digital input/output

IO-Link ports can also be configured as digital inputs or digital outputs. This allows digital sensors and actuators having no IO-Link functionality to be connected to IO-Link ports.
1. Expand the "Std-I/O" tree node in the "Catalog" field
ð The operating modes "dig in" and "dig out" appear
2. Configure the desired port. There are two ways to do this:
1. Drag-and-drop: pull "dig in" or "dig out" onto the port in the "Ports" field
2. Right-click on "dig in" or "dig out" and click on "Add to Port n“

5.2.7 Activating the configuration

Changes in the IO-Link configuration tool only become effective when you activate the IO-Link configuration.
There are two ways to activate the IO-Link configuration:
• Click on the "Reload Devices" button
• Activate the TwinCAT configuration:
Click on the "Activate Configuration" button
EPP6228-0022 25Version: 1.1
Commissioning and configuration

5.3 Diagnosis

5.3.1 IO-Link Events

Some of the IO-Link sensors forward events that occur to the master. These events may be items of information, warnings or error messages, e.g. short circuit or overheating. The IO-Link master reports these events by setting the Device Diag bit. Further information on the events can be read via the CoE directory or the DiagHistory tab.
Fig.14: DiagHistory tab
The events are arranged according to type (information, warning, error), flag, occurrence of the event (time stamp) and message (port number & event code). The meaning of the individual messages can be taken from the vendor documentation. The IO-Link device can be directly allocated on the basis of the port number. The events occurring can be managed using the various buttons.
• Update History: if the "Auto Update" field is not selected, then the current events can be displayed via
the "Update History" button
• Auto Update: if this field is selected, then the list of events occurring is automatically updated
• Only new Messages: if this field is selected, then only those messages that have not yet been
confirmed are displayed.
• Ack. Messages: an event that occurs is reported via the Device Diag. Confirming the message will
reset the bit to 0.
• Export Diag History: the events that have occurred can be exported as a "txt" file and thus archived.
• Advanced: this field currently (as at 3rd quarter 2015) has no function.
EPP6228-002226 Version: 1.1
Commissioning and configuration

5.3.2 ADS Error Codes

Error codes are generated in the event of an error during ADS access to an IO-Link device. The error code contains information about the error category, origin and instance. The possible error codes are listed in table „Error Codes“. Additional information about a certain error (S_APP_DEV) is listed in table „Additional Code“:
Example of an AdsReturnCode
AdsReturnCode 0x80110700
80: Device Application Error (IO-Link Spec), 11: Index not Available (IO-Link Spec), 0700: General ADS Error
Error Codes (IO-Link Spec)
Type Origin Name Category Mode Instance Value (Hi
PDU buffer overflow remote S_PDU_BUFFER ERROR SiNGLE
PDU checksum error (master)
PDU checksum error (device)
PDU flow control error remote S_PDU_FLOW ERROR SiNGLE
Illegal PDU service primitive (master)
Illegal PDU service primitive (device)
Communication error remote COM_ERR SiNGLE
Device application er­ror
local M_PDU_CHECK ERROR SiNGLE
remote S_PDU_CHECK ERROR SiNGLE
local M_PDU_ILLEGAL ERROR SiNGLE
local / remote
remote S_APP_DEV** ERROR SiNGLE
S_PDU_ILLEGAL ERROR SiNGLE
SHOT
SHOT
SHOT
SHOT
SHOT
SHOT
SHOT
SHOT
DL 52 Device buffer is too small for
DL 56 Calculated PDU checksum in
DL 56 Calculated PDU checksum in
DL 56 Violation of flow control rule
AL 57 Unknown service primitive or
AL 58 Unknown service primitive e.g.
unknown 10 Negative service response initi-
APP 80 Service PDU transferred, but
Byte, hex)
Comment
storing the complete PDU
master does not match actual received SPDU
device does not match actual received SPDU
during transfer of SPDU be­tween master and device
wrong response e.g. Read Re­sponse on Write Request
different protocol revision
ated by a communication error, e.g.. IO-Link connection inter­rupted
not processed due to device er­ror. See error details in Addi­tional Code**
EPP6228-0022 27Version: 1.1
Commissioning and configuration
Additional Code (IO-Link Spec)
Type Value (Lo
Byte, hex)
No details 00 Device buffer is too small for storing the complete PDU
Index not available 11 Calculated PDU checksum in master does not match actual re-
Subindex not available 12 Calculated PDU checksum in device does not match actual re-
Service temporarily not available 20 Violation of flow control rule during transfer of SPDU between mas-
Service temporarily not available, local control 21 Unknown service primitive or wrong response e.g. Read Response
Service temporarily not available, device control 22 Unknown service primitive e.g. different protocol revision
Access denied 23 Negative service response initiated by a communication error, eg.
Parameter value out of range 30 Service PDU transferred, but not processed due to device error.
Parameter value above limit 31 Service PDU transferred, but not processed due to device error.
Parameter value below limit 32 Service PDU transferred, but not processed due to device error.
Interfering parameter 40 Service PDU transferred, but not processed due to device error.
Application failure 81 Service PDU transferred, but not processed due to device error.
Application not ready 82 Service PDU transferred, but not processed due to device error.
Comment
ceived SPDU
ceived SPDU
ter and device
on Write Request
IO-Link connection interrupted
See error details in Additional Code
See error details in Additional Code
See error details in Additional Code
See error details in Additional Code
See error details in Additional Code
See error details in Additional Code
EPP6228-002228 Version: 1.1
Appendix

6 Appendix

6.1 General operating conditions

Protection degrees (IP-Code)
The standard IEC 60529 (DIN EN 60529) defines the degrees of protection in different classes.
1. Number: dust protection and touch guard
0 Non-protected
1 Protected against access to hazardous parts with the back of a hand. Protected against solid
2 Protected against access to hazardous parts with a finger. Protected against solid foreign ob-
3 Protected against access to hazardous parts with a tool. Protected against solid foreign objects
4 Protected against access to hazardous parts with a wire. Protected against solid foreign objects
5 Protected against access to hazardous parts with a wire. Dust-protected. Intrusion of dust is not
6 Protected against access to hazardous parts with a wire. Dust-tight. No intrusion of dust.
Definition
foreign objects of Ø50mm
jects of Ø12.5mm.
Ø2.5mm.
Ø1mm.
totally prevented, but dust shall not penetrate in a quantity to interfere with satisfactory operation of the device or to impair safety.
2. Number: water* protection Definition
0 Non-protected
1 Protected against water drops
2 Protected against water drops when enclosure tilted up to 15°.
3 Protected against spraying water. Water sprayed at an angle up to 60° on either side of the ver-
4 Protected against splashing water. Water splashed against the disclosure from any direction
5 Protected against water jets
6 Protected against powerful water jets
7 Protected against the effects of temporary immersion in water. Intrusion of water in quantities
tical shall have no harmful effects.
shall have no harmful effects
causing harmful effects shall not be possible when the enclosure is temporarily immersed in wa­ter for 30min. in 1m depth.
*) These protection classes define only protection against water!
Chemical Resistance
The Resistance relates to the Housing of the IP 67 modules and the used metal parts. In the table below you will find some typical resistance.
Character Resistance
Steam at temperatures >100°C: not resistant
Sodium base liquor (ph-Value > 12)
Acetic acid not resistant
Argon (technical clean) resistant
at room temperature: resistant > 40°C: not resistant
Key
• resistant: Lifetime several months
• non inherently resistant: Lifetime several weeks
• not resistant: Lifetime several hours resp. early decomposition
EPP6228-0022 29Version: 1.1
Appendix

6.2 Accessories

Mounting
Ordering information Description
ZS5300-0001 Mounting rail (500mmx129mm)
Cables
A complete overview of pre-assembled cables for EtherCAT Box modules can be found here.
Ordering information Description
ZK2000-5xxx-xxxx ZK2000-71xx-xxxx
ZK2000-6xxx-xxxx
ZK700x-xxxx-xxxx
Labeling material, protective caps
Ordering information Description
ZS5000-0010 Protective cap for M8 sockets, IP67 (50 pieces) ZS5000-0020 Protective cap M12, IP67 (50 pieces) ZS5100-0000 Inscription labels, unprinted, 4 strips of 10 ZS5000-xxxx Printed inscription labels on enquiry
Sensor cable M12 5-wire Link to website
Sensor cable M12 4-wire Link to website
EtherCAT P cable M8 Link to website
Tools
Ordering information Description
ZB8801-0000 Torque wrench for plugs, 0.4…1.0Nm ZB8801-0001 Torque cable key for M8/ wrench size 9 for ZB8801-0000 ZB8801-0002 Torque cable key for M12/ wrench size 13 for ZB8801-0000 ZB8801-0003 Torque cable key for M12 field assembly/ wrench size 18 for ZB8801-0000
Further accessories
Further accessories can be found in the price list for fieldbus components from Beckhoff and online at https://www.beckhoff.com.
EPP6228-002230 Version: 1.1
Appendix

6.3 Version identification of EtherCAT devices

Designation
A Beckhoff EtherCAT device has a 14-digit designation, made up of
• family key
• type
• version
• revision
Example Family Type Version Revision
EL3314-0000-0016 EL terminal
(12 mm, non­pluggable connection level)
ES3602-0010-0017 ES terminal
(12 mm, pluggable connection level)
CU2008-0000-0000 CU device 2008 (8-port fast ethernet switch) 0000 (basic type) 0000
3314 (4-channel thermocouple terminal)
3602 (2-channel voltage measurement)
0000 (basic type) 0016
0010 (high­precision version)
0017
Notes
• The elements mentioned above result in the technical designation. EL3314-0000-0016 is used in the
example below.
• EL3314-0000 is the order identifier, in the case of “-0000” usually abbreviated to EL3314. “-0016” is the
EtherCAT revision.
• The order identifier is made up of
- family key (EL, EP, CU, ES, KL, CX, etc.)
- type (3314)
- version (-0000)
• The revision -0016 shows the technical progress, such as the extension of features with regard to the
EtherCAT communication, and is managed by Beckhoff. In principle, a device with a higher revision can replace a device with a lower revision, unless specified otherwise, e.g. in the documentation. Associated and synonymous with each revision there is usually a description (ESI, EtherCAT Slave Information) in the form of an XML file, which is available for download from the Beckhoff web site. From 2014/01 the revision is shown on the outside of the IP20 terminals, see Fig. “EL5021 EL terminal, standard IP20 IO device with batch number and revision ID (since 2014/01)”.
• The type, version and revision are read as decimal numbers, even if they are technically saved in
hexadecimal.
Identification number
Beckhoff EtherCAT devices from the different lines have different kinds of identification numbers:
Production lot/batch number/serial number/date code/D number
The serial number for Beckhoff IO devices is usually the 8-digit number printed on the device or on a sticker. The serial number indicates the configuration in delivery state and therefore refers to a whole production batch, without distinguishing the individual modules of a batch.
Structure of the serial number: KKYYFFHH
KK - week of production (CW, calendar week) YY - year of production FF - firmware version HH - hardware version
EPP6228-0022 31Version: 1.1
Appendix
Example with Ser. no.: 12063A02: 12 - production week 12 06 - production year 2006 3A - firmware version 3A 02 ­hardware version 02
Exceptions can occur in the IP67 area, where the following syntax can be used (see respective device documentation):
Syntax: D ww yy x y z u
D - prefix designation ww - calendar week yy - year x - firmware version of the bus PCB y - hardware version of the bus PCB z - firmware version of the I/O PCB u - hardware version of the I/O PCB
Example: D.22081501 calendar week 22 of the year 2008 firmware version of bus PCB: 1 hardware version of bus PCB: 5 firmware version of I/O PCB: 0 (no firmware necessary for this PCB) hardware version of I/O PCB: 1
Unique serial number/ID, ID number
In addition, in some series each individual module has its own unique serial number.
See also the further documentation in the area
• IP67: EtherCAT Box
• Safety: TwinSafe
• Terminals with factory calibration certificate and other measuring terminals
Examples of markings
Fig.15: EL5021 EL terminal, standard IP20 IO device with serial/ batch number and revision ID (since 2014/01)
EPP6228-002232 Version: 1.1
Fig.16: EK1100 EtherCAT coupler, standard IP20 IO device with serial/ batch number
Appendix
Fig.17: CU2016 switch with serial/ batch number
Fig.18: EL3202-0020 with serial/ batch number 26131006 and unique ID-number 204418
EPP6228-0022 33Version: 1.1
Appendix
Fig.19: EP1258-00001 IP67 EtherCAT Box with batch number/ date code 22090101 and unique serial number 158102
Fig.20: EP1908-0002 IP67 EtherCAT Safety Box with batch number/ date code 071201FF and unique serial number 00346070
Fig.21: EL2904 IP20 safety terminal with batch number/ date code 50110302 and unique serial number 00331701
Fig.22: ELM3604-0002 terminal with unique ID number (QR code) 100001051 and serial/ batch number 44160201
EPP6228-002234 Version: 1.1
Appendix

6.3.1 Beckhoff Identification Code (BIC)

The Beckhoff Identification Code (BIC) is increasingly being applied to Beckhoff products to uniquely identify the product. The BIC is represented as a Data Matrix Code (DMC, code scheme ECC200), the content is based on the ANSI standard MH10.8.2-2016.
Fig.23: BIC as data matrix code (DMC, code scheme ECC200)
The BIC will be introduced step by step across all product groups.
Depending on the product, it can be found in the following places:
• on the packaging unit
• directly on the product (if space suffices)
• on the packaging unit and the product
The BIC is machine-readable and contains information that can also be used by the customer for handling and product management.
Each piece of information can be uniquely identified using the so-called data identifier (ANSIMH10.8.2-2016). The data identifier is followed by a character string. Both together have a maximum length according to the table below. If the information is shorter, spaces are added to it. The data under positions 1 to 4 are always available.
The following information is contained:
EPP6228-0022 35Version: 1.1
Appendix
Item
Type of
no.
information
1 Beckhoff order
number
2 Beckhoff Traceability
Number (BTN)
3 Article description Beckhoff article
4 Quantity Quantity in packaging
5 Batch number Optional: Year and week
6 ID/serial number Optional: Present-day
7 Variant number Optional: Product variant
...
Explanation Data
Beckhoff order number 1P 8 1P072222
Unique serial number, see note below
description, e.g. EL1008
unit, e.g. 1, 10, etc.
of production
serial number system, e.g. with safety products
number on the basis of standard products
Number of digits
identifier
S 12 SBTNk4p562d7
1K 32 1KEL1809
Q 6 Q1
2P 14 2P401503180016
51S 12 51S678294104
30P 32 30PF971, 2*K183
incl. data identifier
Example
Further types of information and data identifiers are used by Beckhoff and serve internal processes.
Structure of the BIC
Example of composite information from item 1 to 4 and 6. The data identifiers are marked in red for better display:
BTN
An important component of the BIC is the Beckhoff Traceability Number (BTN, item no.2). The BTN is a unique serial number consisting of eight characters that will replace all other serial number systems at Beckhoff in the long term (e.g. batch designations on IO components, previous serial number range for safety products, etc.). The BTN will also be introduced step by step, so it may happen that the BTN is not yet coded in the BIC.
NOTE
This information has been carefully prepared. However, the procedure described is constantly being further developed. We reserve the right to revise and change procedures and documentation at any time and with­out prior notice. No claims for changes can be made from the information, illustrations and descriptions in this information.
EPP6228-002236 Version: 1.1
Appendix

6.4 Support and Service

Beckhoff and their partners around the world offer comprehensive support and service, making available fast and competent assistance with all questions related to Beckhoff products and system solutions.
Beckhoff's branch offices and representatives
Please contact your Beckhoff branch office or representative for local support and service on Beckhoff products!
The addresses of Beckhoff's branch offices and representatives round the world can be found on her internet pages:
http://www.beckhoff.com
You will also find further documentation for Beckhoff components there.
Beckhoff Headquarters
Beckhoff Automation GmbH & Co. KG
Huelshorstweg 20 33415 Verl Germany
Phone: +49 5246 963 0 Fax: +49 5246 963 198 e-mail: info@beckhoff.com
Beckhoff Support
Support offers you comprehensive technical assistance, helping you not only with the application of individual Beckhoff products, but also with other, wide-ranging services:
• support
• design, programming and commissioning of complex automation systems
• and extensive training program for Beckhoff system components
Hotline: +49 5246 963 157 Fax: +49 5246 963 9157 e-mail: support@beckhoff.com
Beckhoff Service
The Beckhoff Service Center supports you in all matters of after-sales service:
• on-site service
• repair service
• spare parts service
• hotline service
Hotline: +49 5246 963 460 Fax: +49 5246 963 479 e-mail: service@beckhoff.com
EPP6228-0022 37Version: 1.1
More Information:
www.beckhoff.com/epp6228/
Beckhoff Automation GmbH & Co. KG Hülshorstweg 20 33415 Verl Germany Phone: +49 5246 9630 info@beckhoff.com www.beckhoff.com
Loading...
Buy Points How it Works FAQ Contact Us Questions and Suggestions Privacy Policy Cookie Policy Terms of Use