Directory contents of /download/ - Documentation EP6224 and … · 2019-10-28 · Foreword EP6224...

Documentation

EP6224 and EP6228

IO-Link Master with protection class IP67

1.52019-10-28

Version:Date:

Table of Contents

EP6224 and EP6228 3Version: 1.5

Table of Contents1 Foreword .................................................................................................................................................... 5

1.1 Notes on the documentation.............................................................................................................. 51.2 Safety instructions ............................................................................................................................. 61.3 Documentation issue status .............................................................................................................. 7

2 Product overview....................................................................................................................................... 92.1 Product group: EtherCAT Box Modules ............................................................................................ 92.2 Module overview................................................................................................................................ 92.3 EP6224............................................................................................................................................ 10

2.3.1 Introduction ...................................................................................................................... 102.3.2 Technical data ................................................................................................................. 122.3.3 Scope of supply ............................................................................................................... 132.3.4 Process image ................................................................................................................. 14

2.4 EP6228............................................................................................................................................ 152.4.1 Introduction ...................................................................................................................... 152.4.2 Technical data ................................................................................................................. 172.4.3 Scope of supply ............................................................................................................... 182.4.4 Process image ................................................................................................................. 19

3 IO-Link master principles ....................................................................................................................... 20

4 Mounting and Access.............................................................................................................................. 224.1 Mounting.......................................................................................................................................... 22

4.1.1 Dimensions ...................................................................................................................... 224.1.2 Mounting .......................................................................................................................... 254.1.3 Tightening torques for plug connectors ........................................................................... 25

4.2 Connection ...................................................................................................................................... 264.2.1 Supply voltage ................................................................................................................. 274.2.2 EtherCAT ......................................................................................................................... 314.2.3 IO-Link ............................................................................................................................. 33

4.3 UL Requirements............................................................................................................................. 35

5 Commissioning and configuration ........................................................................................................ 365.1 Configuration in TwinCAT................................................................................................................ 365.2 IO-Link configuration ....................................................................................................................... 37

5.2.1 Opening the configuration tool......................................................................................... 375.2.2 Assigning devices to ports ............................................................................................... 385.2.3 Supplementing the device catalog................................................................................... 385.2.4 Parameterizing a port ...................................................................................................... 395.2.5 Parameterizing a device .................................................................................................. 395.2.6 Configuring a port as a digital input/output ...................................................................... 395.2.7 Activating the configuration.............................................................................................. 39

5.3 Object description and parameterization ......................................................................................... 405.3.1 Objects for commissioning............................................................................................... 405.3.2 Objects for regular operation ........................................................................................... 425.3.3 Standard objects (0x1000-0x1FFF) ................................................................................. 425.3.4 Profile specific objects (0x6000-0xFFFF) ........................................................................ 46

Table of Contents

EP6224 and EP62284 Version: 1.5

6 Diagnosis.................................................................................................................................................. 496.1 IO-Link Events ................................................................................................................................. 496.2 ADS Error Codes............................................................................................................................. 50

7 Appendix .................................................................................................................................................. 527.1 General operating conditions........................................................................................................... 527.2 EtherCAT Box- / EtherCAT P Box - Accessories ............................................................................ 537.3 General note on the introduction of the Beckhoff Identification Code (BIC) .................................... 547.4 Support and Service ........................................................................................................................ 56

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 whoare familiar with the applicable national standards.It is essential that the documentation and the following notes and explanations are followed when installingand commissioning these components.It is the duty of the technical personnel to use the documentation published at the respective time of eachinstallation and commissioning.

The responsible staff must ensure that the application or use of the products described satisfy all therequirements 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 underdevelopment.

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 thedata, 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 AutomationGmbH. Other designations used in this publication may be trademarks whose use by third parties for theirown purposes could violate the rights of the owners.

Patent Pending

The EtherCAT Technology is covered, including but not limited to the following patent applications andpatents: EP1590927, EP1789857, EP1456722, EP2137893, DE102015105702 with correspondingapplications 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 toothers 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 apatent, utility model or design.

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 theapplication. Modifications to hardware or software configurations other than those described in thedocumentation 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 arefamiliar 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!

DANGERSerious risk of injury!Failure to follow this safety instruction directly endangers the life and health of persons.

WARNINGRisk of injury!Failure to follow this safety instruction endangers the life and health of persons.

CAUTIONPersonal injuries!Failure to follow this safety instruction can lead to injuries to persons.

NOTEDamage to environment/equipment or data lossFailure to follow this instruction can lead to environmental damage, equipment damage or data loss.

Tip or pointerThis symbol indicates information that contributes to better understanding.

Foreword


1.3 Documentation issue statusVersion Modifications1.5 • IO-Link master principles updated

• IO-Link configuration updated1.4 • Update Technical data

• EP6228-3132 added1.3.0 • Update Technical data

• Safety instructions new layout1.2.5 • EP6228-x0x2 – Technical Data updated

• Safety instructions adapted to IEC 82079-1.1.2.4 • EP6228-3032 added

• EP6224-x022 – Technical Data updated• EP6228-x0x2 – Technical Data updated• EP6228-x0x2 – Introduction updated• EP622x Module overview updated• Conductor losses 7/8" added• Configuration with TwinCAT - explanation of tab and IO-Link Master updated

1.2.3 • Object description and parameterization updated• IO-Link principles updated

1.2.2 • Object description and parameterization updated1.2.1 • Nut torques for connectors updated1.2.0 • EP6228-0022 added

• Object description and parameterization updated• EP6224-x022 Process image updated• Images for IO-Link and sensor cable updated

1.1.0 • Power Connection updated1.0.0 • First release0.6 • Corrections0.5 • First preliminary version

Foreword


Firmware and hardware versions

This documentation refers to the firmware and hardware version that was applicable at the time thedocumentation was written.

The module features are continuously improved and developed further. Modules having earlier productionstatuses cannot have the same properties as modules with the latest status. However, existing propertiesare 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 onthe 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 productionFF - firmware versionHH - hardware version

Example with D No. 29 10 02 01:

29 - week of production 2910 - year of production 201002 - firmware version 0201 - hardware version 01

Beckhoff Identification Code (BIC)

The Beckhoff Identification Code contains additional information about the delivery state of the module:General note on the introduction of the Beckhoff Identification Code (BIC) [} 54].

Product overview


2 Product overview

2.1 Product group: EtherCAT Box ModulesEtherCAT Box modules are I/O modules for industrial controllers.

They comply with protection class IP67 and are intended for use outside the control cabinet in wet, dirty ordusty industrial environments.

EtherCAT Box modules communicate with the controller via the EtherCAT fieldbus. They each have twoconnections for EtherCAT communication and for the power supply:

• Feed• Downstream connection

This enables the cabling of EtherCAT Box modules in a line structure:

Power

EtherCAT ...

...

Fig. 1: EtherCAT Box modules: Example of cabling in a line structure

2.2 Module overviewModule IO-Link ports Output current

Sensor/logic supplyL+

Actuator supply (class B ports)P24

per port Sum per port SumEP6224-2022 [} 10] 4 x Class A 1.4 A 4.0 A - -

EP6224-3022 [} 10] 4 x Class B 1.4 A 4.0 A 2.0 A 2.0 A

EP6228-0022 [} 15] 8 x Class A 1.4 A 4.0 A - -

EP6228-3032 [} 15] 8 x Class B 1.4 A 16.0 A 4.0 A 1) 16.0 A

EP6228-3132 [} 15] 4 x Class A4 x Class B

1.4 A 16.0 A 4.0 A 1) 16.0 A

1) This output current is additionally the maximum sum current for a port pair. The port pairs are specified in the Technical Data [} 17].

Product overview


2.3 EP6224

2.3.1 Introduction

Fig. 2: EP6224-2022

Fig. 3: EP6224-3022

IO-Link master

The EP6224 IO-Link module enables connection of up to four IO-Link devices, e.g. actuators, sensors orcombinations of both. A point-to-point connection is used between the terminal and the device. The terminalis parameterised via the EtherCAT master. IO-Link is designed as an intelligent link between the fieldbuslevel and the sensor, wherein parameterisation information can be exchanged bidirectionally via the IO-Linkconnection. The parameterisation of the IO-Link devices with service data can be done from TwinCAT viaADS or very conveniently via the integrated IO-Link configuration tool.

Product overview


In the standard setting, the EP6224 functions as a 4-channel input terminal, 24 V DC, which communicateswith connected IO-Link devices, parameterises them and, if necessary, changes their operating mode.

Quick Links

Installation [} 22]

Commissioning [} 36]

Product overview


2.3.2 Technical dataAll values are typical values at 25 °C, unless otherwise stated.

Technical data EP6224-2022 EP6224-3022Fieldbus Fieldbus EtherCAT Connection 2 x M8 socket, green Electrical isolation 500 V (fieldbus / IO)Supply voltages Connection Feed: 1 x M8 plug, 4-pin

Downstream connection: 1 x M8 socket, 4-pin Control voltage US

Nominal voltage 24 VDC (-15 % / +20 %) Sum current max. 4 A 1)

Consumers • Module electronics: 130 mA

• IO-Link devices: Sensor/logic supply L+ Peripheral voltage UP

Nominal voltage 24 VDC (-15 % / +20 %) Sum current max. 4 A 1)

Consumers - IO-Link devices Class B:Actuator supply P24

IO-Link Number of ports 4 x Class A 4 x Class B Connection 4 x M12 socket Cable length max. 20 m Specification IO-Link V1.1 Transmission rate COM1: 4,8 kbit/s

COM2: 38,4 kbit/sCOM3: 230,4 kbit/s

Sensor/logic supply L+ 24 VDC from the control voltage US

max. 1.4 A per portmax. 4.0 A in total

Actuator supply P24 (Ports class B)

- 24 VDC from peripheral voltage UP


Environmental conditions Ambient temperature during operation

-25 .. +60 °C 0 .. +55 °C according to cURus

Ambient temperature during storage

-40 .. +85 °C

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 60529Mechanics Weight approx. 250 g Mounting position variableApprovals and conformity Approvals CE, cURus

1) Sum current of consumers and power transmission. This value corresponds to the current carrying capacity of the connections for the supply voltages.

Product overview


Additional checks

The boxes have been subjected to the following checks:

Verification ExplanationVibration 10 frequency sweeps in 3 axes

5 Hz < f < 60 Hz displacement 0.35 mm, constant amplitude60.1 Hz < f < 500 Hz acceleration 5 g, constant amplitude

Shocks 1000 shocks in each direction, in 3 axes35 g, 11 ms

2.3.3 Scope of supplyMake sure that the following components are included in the scope of delivery:

• 1x EtherCAT Box EP6224• 1x protective cap for supply voltage input, M8, transparent (pre-assembled)• 1x protective cap for supply voltage output, M8, black (pre-assembled)• 2x protective cap for EtherCAT socket, M8, green (pre-assembled)• 10x labels, blank (1 strip of 10)

Pre-assembled protective caps do not ensure IP67 protectionProtective caps are pre-assembled at the factory to protect connectors during transport. They maynot be tight enough to ensure IP67 protection.Ensure that the protective caps are correctly seated to ensure IP67 protection.

Product overview


2.3.4 Process image

2.3.4.1 Assignment of IO-Link ports to process dataProcess image in TwinCAT IO-Link

portStatus variable Process data of

the IO-Link de-vice

1 Module 2

DeviceState Inputs State Ch1

Module 3 1)

2 Module 2


Module 4 1)

3 Module 2


Module 5 1)

4 Module 2


Module 6 1)

1) The modules "Module 3" to "Module 6" only exist in the process data if the corresponding IO-Link portshave been configured [} 37].

Product overview


2.4 EP6228

2.4.1 Introduction

Fig. 4: EP6228-0022

Fig. 5: EP6228-3032

Product overview


Fig. 6: EP6228-3132

IO-Link master

The EP6228 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 thedevice. The terminal is parameterised via the EtherCAT master. IO-Link is designed as an intelligent linkbetween the fieldbus level and the sensor, wherein parameterisation information can be exchangedbidirectionally via the IO-Link connection. The parameterisation of the IO-Link devices with service data canbe done from TwinCAT via ADS or very conveniently via the integrated IO-Link configuration tool.

In the standard setting, the EP6228 functions as a 8-channel input terminal, 24 V DC, which communicateswith connected IO-Link devices, parameterises them and, if necessary, changes their operating mode.

Quick Links

Dimensions [} 22]

Commissioning [} 36]

Product overview


2.4.2 Technical dataAll values are typical values at 25 °C, unless otherwise stated.

Technical data EP6228-0022 EP6228-3032 EP6228-3132Fieldbus Fieldbus EtherCAT Connection 2 x M8 socket, green Electrical isolation 500 V (fieldbus / IO)Supply voltages Connection Power supply:

1 x M8 plug, 4-pin

Downstream connection:1 x M8 socket, 4-pin

Power supply:1 x 7/8" plug, 5-pin

Downstream connection:1 x 7/8" socket, 5-pin

Control voltage US

Nominal voltage 24 VDC (-15 % / +20 %) Consumers • Module electronics: 130 mA

• IO-Link devices: Sensor/logic supply L+ Sum current max. 4 A 1) max. 16 A 1)

Peripheral voltage UP

Nominal voltage 24 VDC (-15 % / +20 %) Consumers - IO-Link devices class B:

Actuator supply P24 Sum current max. 4 A 1) max. 16 A 1)

IO-Link Number of ports 8 x Class A 8 x Class B 4 x Class A (ports 1, 2, 5, 6)

4 x Class B (ports 3, 4, 7, 8) Connection 8 x M12 socket Cable length max. 20 m Specification IO-Link V1.1 Transmission rate COM1: 4,8 kbit/s

COM2: 38,4 kbit/sCOM3: 230,4 kbit/s

Sensor/logic supply L+ 24 VDC from the controlvoltage US


24 VDC from the control voltage US


Actuator supply P24 (Ports class B)

- 24 VDC from peripheral voltage UP

max. 4.0 A per port pair 2)

max. 16.0 A in totalEnvironmental conditions Ambient temperature during operation

-25 .. +60 °C 0 .. +55 °C according to cURus

Ambient temperature during storage

-40 .. +85 °C

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 60529Mechanics Weight approx. 250 g approx. 450 g Mounting position variableApprovals and conformity Approvals CE, cURus CE, cURus in preparation

1) Sum current of consumers and power transmission. This value corresponds to the current carrying capacity of the connections for the supply voltages.2) Port pairs with common limitation of the actuator supply:

• EP6228-3032: Port pair 1+5, 2+6, 3+7, 4+8• EP6228-3132: Port pair 3+7, 4+8

Product overview


Additional checks

The boxes have been subjected to the following checks:

Verification ExplanationVibration 10 frequency sweeps in 3 axes

5 Hz < f < 60 Hz displacement 0.35 mm, constant amplitude60.1 Hz < f < 500 Hz acceleration 5 g, constant amplitude

Shocks 1000 shocks in each direction, in 3 axes35 g, 11 ms

2.4.3 Scope of supply

EP6228-0022

Make sure that the following components are included in the scope of delivery:

• 1x EP6228-0022 EtherCAT Box• 1x protective cap for supply voltage input, M8, transparent (pre-assembled)• 1x protective cap for supply voltage output, M8, black (pre-assembled)• 2x protective cap for EtherCAT socket, M8, green (pre-assembled)• 10x labels, blank (1 strip of 10)

EP6228-3x32

Make sure that the following components are included in the scope of delivery:

• 1x EP6228-3x32 EtherCAT Box• 1x Protective cap for supply voltage output, 7/8”, black (pre-fitted)• 2x protective cap for EtherCAT socket, M8, green (pre-assembled)• 10x labels, blank (1 strip of 10)

Pre-assembled protective caps do not ensure IP67 protectionProtective caps are pre-assembled at the factory to protect connectors during transport. They maynot be tight enough to ensure IP67 protection.Ensure that the protective caps are correctly seated to ensure IP67 protection.

Product overview


2.4.4 Process image

2.4.4.1 Assignment of IO-Link ports to process dataProcess image in TwinCAT IO-Link

portStatus variable Process data of

the IO-Link de-vice

1 Module 2


Module 3 1)

2 Module 2


Module 4 1)

3 Module 2


Module 5 1)

4 Module 2


Module 6 1)

5 Module 2


Module 7 1)

6 Module 2


Module 8 1)

7 Module 2


Module 9 1)

8 Module 2


Module 10 1)

1) The modules "Module 3" to "Module 10" only exist in the process data if the corresponding IO-Link portshave been configured [} 37].

IO-Link master principles


3 IO-Link master principles

3.1 TopologyThe IO-Link master serves as a gateway between an automation system (EtherCAT) and the IO-Linkdevices. It has several IO-Link ports, to each of which an IO-Link device can be connected.

IO-Link Master

...IO

-Lin

k Po

rt

IO-L

ink

Port

IO-L

ink

Port

...

...

IO-L

ink

Dev

ice

IO-L

ink

Dev

ice

IO-L

ink

Dev

ice

Fig. 7: IO-Link topology

3.2 PortsTwo classes of IO-Link ports are defined in the IO-Link specification:

Class A ports

Class A ports are intended for the connection of IO-Link devices of the type sensor.

Contacts of a class A port:

• Supply voltage for the IO-Link device: L+, L-• Data cable for serial communication or switching signals: C/Q• Data cable for switching signals (optional): DI/DQ

Class B ports

Class B ports are intended for the connection of IO-Link devices of the type actuator.

Contacts of a class B port:

• Two electrically isolated supply voltages for the IO-Link device:◦ Sensor/logic supply: L+, L-◦ Actuator supply: P24, N24

• Data cable for serial communication or switching signals: C/Q

IO-Link master principles


3.3 „Data storage“ functionThe IO-Link Master supports the „Data storage“ function. It can save a non-volatile copy of the parameters ofconnected devices.

If a device fails, its parameters remain in the memory of the IO-Link Master.

If a defective device is replaced by a new, identical device, the master can automatically parameterize thenew device with the stored parameters.

Mounting and Access


4 Mounting and Access

4.1 Mounting

4.1.1 Dimensions

EP6224-xxxx

117

6013.5

26.5

126

Ø 4.5

Fig. 8: Dimensions

All dimensions are given in millimeters.

Housing features

Housing material PA6 (polyamide)Sealing compound polyurethaneMounting two fastening holes Ø 4.5 mm for M4Metal parts brass, nickel-platedContacts CuZn, gold-platedPower feed through max. 4 AMounting position variableProtection class IP65, IP66, IP67 (conforms to EN 60529) when screwed togetherDimensions (H x W x D) approx. 126 x 60 x 26.5 mm (without connectors)

Mounting and Access


EP6228-0022

117

6013.5

26.5

126

Ø 4.5

Fig. 9: Dimensions


Housing features

Housing material PA6 (polyamide)Sealing compound polyurethaneMounting two fastening holes Ø 4.5 mm for M4Metal parts brass, nickel-platedContacts CuZn, gold-platedPower feed through max. 4 AMounting position variableProtection class IP65, IP66, IP67 (conforms to EN 60529) when screwed togetherDimensions (H x W x D) approx. 126 x 60 x 26.5 mm (without connectors)

Mounting and Access


EP6228-xx32

150

60

141

Ø 4.5

Fig. 10: Dimensions


Housing features

Housing material PA6 (polyamide)Sealing compound polyurethaneMounting two fastening holes Ø 4.5 mm for M4Metal parts brass, nickel-platedContacts CuZn, gold-platedPower feed through max. 16 A at 40°C (according to IEC 60512-3)Mounting position variableProtection class IP65, IP66, IP67 (conforms to EN 60529) when screwed togetherDimensions (H x W x D) approx. 150 x 60 x 26.5 mm (without connectors)

Mounting and Access


4.1.2 MountingNOTE

Dirt during assemblyDirty plug connectors can lead to malfunctions. Protection class IP67 can only be guaranteed if all cablesand 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.1.3 Tightening torques for plug connectorsScrew connectors tight with a torque wrench. (e.g. ZB8801 from Beckhoff)

Connector diameter Tightening torqueM8 0.4 NmM12 0.6 Nm7/8” 1.5 Nm

Mounting and Access


4.2 Connection

Guidelines

Follow these guidelines to ensure IP67 protection:

• Mount connectors with the specified torque [} 25]. Use a torque wrench, e.g. Beckhoff ZB8801.• Seal unused connectors with protective caps.• Ensure the correct seating of pre-assembled protective caps.

Protective caps are pre-assembled at the factory to protect connectors during transport. They may notbe tight enough to ensure IP67 protection.

Mounting and Access


4.2.1 Supply voltageThe EtherCAT Box is supplied with two supply voltages. The supply voltages are electrically isolated in theEtherCAT Box.

• Control voltage US

• Peripheral voltage UP

4.2.1.1 EP6224-2022, EP6224-3022, EP6228-0022

4.2.1.1.1 M8 connector

NOTEDefect possible through incorrect insertionM8 connector for supply voltages have the same design as M8 connectors for EtherCAT. Observe the colorcoding of the connectors in order to avoid incorrect insertion: black: Supply voltage green: EtherCAT

Two connectors at the low-end of the modules are used for feeding and routing the supply voltages:

• Power supply: IN plug, left• Downstream connection: OUT socket, right

Fig. 11: Connector for the supply voltages

Connection

PlugFeed-in

SocketForwarding

3 1

24

3 1

24

Fig. 12: M8 connector

Contact Function Description Core color 1)

1 US Control voltage Brown2 UP Peripheral voltage White3 GNDS GND to US Blue4 GNDP GND to UP Black

1) The core colors apply to cables of the type: Beckhoff ZK2020-xxxx-xxxx

Mounting and Access


4.2.1.1.2 Status LEDs

Fig. 13: Status LEDs for the supply voltages

LED Display MeaningUS (control voltage) off Supply voltage US is not present

green illuminated Supply voltage US is presentUP (peripheral voltage) off Supply voltage UP is not present

green illuminated Supply voltage UP is present

4.2.1.1.3 Conductor losses

Take into account the voltage drop on the supply line when planning a system. Avoid the voltage drop beingso 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.

Voltage drop on the supply line

Vert. Faktor: 0,45 cm / V

5 10 15 20

2

4

6

8

10

2500

12

30


Volta

ge d

rop

(V)

Cable length (m)

35

0,25 mm²

0,34 mm²

0,5 mm²0,75 mm²

I = 2 A


5 10 15 20

2

4

6

8

10

2500

12

30


Volta

ge d

rop

(V)

Cable length (m)

35

0,25 mm²

0,34 mm²

0,5 mm²

0,75 mm²

I = 4 A

Mounting and Access


4.2.1.2 EP6228-3032, EP6228-3132

4.2.1.2.1 7/8" plug connectors

Two connectors at the low-end of the modules are used for feeding and routing the supply voltages:

• Power supply: IN plug, left• Downstream connection: OUT socket, right

Fig. 14: Connector for the supply voltages

Connection

1

2

3

4

5 5

4

3

2

1

PlugFeed-in

SocketForwarding

Fig. 15: 7/8" plug connectors


1 GNDP GND to UP Black2 GNDS GND to US Blue3 FE Functional earth Grey4 US Control voltage Brown5 UP Peripheral voltage White

1) The core colors apply to cables of the type: Beckhoff ZK203x-xxxx.

Mounting and Access


4.2.1.2.2 Status LEDs

Fig. 16: Status LEDs for the supply voltages

LED Display MeaningUS (control voltage) off Supply voltage US is not present

green illuminated Supply voltage US is presentUP (peripheral voltage) off Supply voltage UP is not present

green illuminated Supply voltage UP is present

4.2.1.2.3 Conductor losses

Take into account the voltage drop on the supply line when planning a system. Avoid the voltage drop beingso 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.

Voltage drop on the supply line

5 10 15 20

0,4

0,8

1,2

1,6

2500

2,0

30


Volta

ge d

rop

(V)

Cable length (m)

1,5 mm²

2,5 mm²

I = 2 A

5 10 15 20

0,4

0,8

1,2

1,6

2500

2,0

30


Volta

ge d

rop

(V)

Cable length (m)

1,5 mm²

2,5 mm²

I = 4 A

Mounting and Access


4.2.2 EtherCAT

4.2.2.1 Connectors

EtherCAT Box Modules have two green M8 sockets for the incoming and downstream EtherCATconnections.

Fig. 17: EtherCAT connector

Connection

3 1

24

Fig. 18: M8 socket

EtherCAT M8 connector

Core colors

Signal Contact ZB9010, ZB9020, ZB9030, ZB9032,ZK1090-6292,ZK1090-3xxx-xxxx

ZB9031 and old versions ofZB9030, ZB9032, ZK1090-3xxx-xxxx

TIA-568B

Tx + 1 yellow1) orange/white white/orangeTx - 4 orange1) orange orangeRx + 2 white1) blue/white white/greenRx - 3 blue1) blue greenShield Housing Shield Shield Shield

1) Core colors according to EN 61918

Adaptation of core colors for cables ZB9030, ZB9032 and ZK1090-3xxxx-xxxxFor standardization, the core colors of the ZB9030, ZB9032 and ZK1090-3xxx-xxxx cables havebeen changed to the EN61918 core colors: yellow, orange, white, blue. So there are different colorcodes in circulation. The electrical properties of the cables have been retained when the core colorswere changed.

Mounting and Access


4.2.2.2 Status LEDs

Fig. 19: EtherCAT Status LEDs

L/A (Link/Act)

A green LED labelled "L/A" is located next to each EtherCAT socket. The LED indicates the communicationstate of the respective socket:

LED Meaningoff no connection to the connected EtherCAT devicelit LINK: connection to the connected EtherCAT deviceflashes 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 theEtherCAT network:

LED Meaningoff Slave is in "Init" stateflashes uniformly Slave is in "Pre-Operational“ stateflashes sporadically Slave is in "Safe-Operational" statelit Slave is in "Operational" state

Description of the EtherCAT slave states

4.2.2.3 Cables

For connecting EtherCAT devices only shielded Ethernet cables that meet the requirements of at leastcategory 5 (CAT5) according to EN 50173 or ISO/IEC 11801 should be used.

EtherCAT uses four wires for signal transmission.Thanks to automatic line detection ("Auto MDI-X"), both symmetrical (1:1) or cross-over cables can be usedbetween Beckhoff EtherCAT.

Detailed recommendations for the cabling of EtherCAT devices

https://infosys.beckhoff.com/content/1033/ethercatsystem/1036980875.html?id=8582353789396071752

https://infosys.beckhoff.com/content/1033/ethernetcabling/index.html?id=1661412216745722148

Mounting and Access


4.2.3 IO-Link

4.2.3.1 Connector

The IO-Link ports are implemented as M12 sockets.

12

34

5

Fig. 20: M12 socket

EP6224-2022EP6228-0022


1 L+ Supply voltage (US1) brown2 - - white3 L- GND blue4 C/Q IO-Link data cable black5 - - grey

EP6224-3022EP6228-3032


1 L+ Sensor/logic supply (US1) brown2 P24 Actuator supply (UP1) white3 L- GND to L+ blue4 C/Q IO-Link data cable black5 N24 GND to P24 grey

EP6228-3132

Contact X01, X02, X05, X06:Class A ports

X03, X04, X07, X08:Class B ports

Core color 1)

Function Description Function Description1 L+ Supply voltage (US1) L+ Sensor/logic supply (US1) brown2 DI Digital input P24 Actuator supply (UP1) white3 L- GND L- GND to L+ blue4 C/Q IO-Link data cable C/Q IO-Link data cable black5 - - N24 GND to P24 grey

1) The core colors apply to M12 sensor cables from Beckhoff:

• ZK2000-5xxx• ZK2000-6xxx• ZK2000-7xxx.

Mounting and Access


4.2.3.2 Status LEDs

1 2

Fig. 21: Status LEDs of an IO-Link port

1 - IO-Link

LED signal Meaningoff Possibilities:

• Port not configured• Logic level low 1)

red illuminatedflashes 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 activegreen illuminated Logic level high 1)

1) Port configured as digital input or output

2 - Digital input DI (EP6228-3132 only)

The LED lights up when a high level is present on the digital input DI.

Mounting and Access


4.3 UL RequirementsThe installation of the EtherCAT Box Modules certified by UL has to meet the following requirements.

Supply voltage

CAUTIONCAUTION!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) powersource!

CAUTIONCAUTION!To meet the UL requirements, the EtherCAT Box Modules must not be connected to unlimited powersources!

Networks

CAUTIONCAUTION!To meet the UL requirements, EtherCAT Box Modules must not be connected to telecommunication net-works!

Ambient temperature range

CAUTIONCAUTION!To meet the UL requirements, EtherCAT Box Modules has to be operated only at an ambient temperaturerange of 0 to 55°C!

Marking for UL

All EtherCAT Box Modules certified by UL (Underwriters Laboratories) are marked with the following label.

Fig. 22: UL label

Commissioning and configuration


5 Commissioning and configuration

5.1 Configuration in TwinCATAn EtherCAT Box must be configured in TwinCAT so that its functions can be used in a PLC program.

The following link will take you to a quick start guide describing the configuration of an EtherCAT Box inTwinCAT:

https://infosys.beckhoff.com/content/1033/epioconfiguration/index.html?id=6991403443235907429

https://infosys.beckhoff.com/content/1033/epioconfiguration/index.html?id=6991403443235907429



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 assignedto 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[} 39].



5.2.2 Assigning devices to portsThere are four ways of assigning devices to ports:

Selecting a device from the device catalog1. Search for the desired device in the "Catalog" field.

Not available? Supplementing the device catalog [} 38]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 [} 38] > "Import from the file system"

2. Select a device from the device catalog [} 38]ð 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 manually1. 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 catalogFollowing 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 Internet1. 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 system1. Click on the "Import device description" button2. Open a device description file (IODD) in the dialog box that opensð The device description is added to the device catalog.



5.2.4 Parameterizing a portü Requirement: A device is assigned to the port. Assigning devices to ports [} 38].1. In the "Ports" field, right-click on the port2. 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 [} 38].1. In the "Ports" field, right-click on the device2. 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 devicedescription file. Die Standardwerte werden aus der Gerätebeschreibung im Device-Katalogübernommen.

• „Store“Store the current parameter values in the Parameter Server. „Data Storage“ [} 21].

5.2.6 Configuring a port as a digital input/outputIO-Link ports can also be configured as digital inputs or digital outputs. This allows digital sensors andactuators 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" field2. Right-click on "dig in" or "dig out" and click on "Add to Port n“

5.2.7 Activating the configurationChanges 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



5.3 Object description and parameterizationEtherCAT XML Device DescriptionThe display matches that of the CoE objects from the EtherCAT XML Device Description. We rec-ommend downloading the latest XML file from the download area of the Beckhoff website and in-stalling it according to installation instructions.

Parameterization via the CoE list (CAN over EtherCAT)The EtherCAT device is parameterized via the CoE - Online tab (double-click on the respective ob-ject) or via the Process Data tab (allocation of PDOs). Please note the following general CoE noteswhen using/manipulating the CoE parameters:- Keep a startup list if components have to be replaced- Differentiation between online/offline dictionary, existence of current XML description- use “CoE reload” for resetting changes

Introduction

The CoE overview contains objects for different intended applications:

• Objects required for parameterization during commissioning.• Objects intended for regular operation, e.g. through ADS access.• Objects for indicating internal settings (may be fixed).• Profile specific objects, for exposition the status of the inputs and outputs.

The following section first describes the objects require for normal operation, followed by a completeoverview of other objects.

5.3.1 Objects for commissioning

Index 1011 Restore default parameters

Index (hex) Name Meaning Data type Flags Default1011:0 Restore default param-

etersRestore default parameters UINT8 RO 0x01 (1dec)

1011:01 SubIndex 001 If this object is set to "0x64616F6C" in the set value di-alog, all backup objects are reset to their delivery state.

UINT32 RW 0x00000000(0dec)

http://www.beckhoff.de/german/download/elconfg.htm?id=1983920606140



Index 80n0 IO Settings Ch.1 - 4 (for 0 ≤ n ≤ 3)

Index (hex) Name Meaning Data type Flags Default80n0:0 IO Settings Ch.1- 4 IO Settings Channel x UINT8 RW 0x28 (40dez)80n0:04 Device ID The device ID is used for validating the IO link device. UINT32 RW 0x00000000

(0dez)80n0:05 VendorID The vendor ID is used for validating the manufacturer

of the IO link device.UINT32 RW 0x00000000

(0dez)80n0:20 IO-Link Revision ID of the specification version based on which the IO

link device communicates.

Bit 0-3: MinorRevBit 4-7: MajorRev

UINT8 RW 0x00 (0dez)

80n0:21 Frame capability The Frame capability indicates certain functionalities ofthe IO link device (e.g. SPDU supported).

Bit 0: SPDUBit 1: Type1Bit 7: PHY1


80n0:22 Min cycle time The cycle time refers to the communication betweenthe IO link master and the IO link device. This value is transferred in the IO link format for MinCycle Time.

Bit 6 und 7: Time BaseBit 0 to 5: Multiplier

0x00: The IO-Link master automatically uses the small-est possible update time of the IO-Link device.


80n0:23 Offset time reserved UINT8 RW 0x00 (0dez)80n0:24 Process data in length These parameters are transferred in the IO link format

for "Process data in length".

Bit 7: BYTE (indicates whether the value in LENGTH interpreted asbit length [bit not set] or as byte length + 1 [bit set]

Bit 6: SIO (indicates whether the device supports the standard IOmode [bit set])

Bit 0 to 4: LENGTH(length of the process data)




Index (hex) Name Meaning Data type Flags Default80n0:25 Process data out

lengthThese parameters are transferred in the IO link formatfor "Process data out length".



Bit 0 to 4: LENGTH(length of the process data)


80n0:26 Compatible ID reserved UINT16 RW 0x0000 (0dez)80n0:27 Reserved reserved UINT16 RW 0x0000 (0dez)80n0:28 Master Control 0: IO link port inactive

1: IO link port as digital input port2: IO link port as digital output port3: IO link port in communication via the IO link protocol4:IO link port in communication via the IO link protocol.

IO link state is ComStop (none cyclic communication,data are exchanged on demand).


5.3.2 Objects for regular operationIn normal functional range the EL6224 has no such objects.

Complete overview

5.3.3 Standard objects (0x1000-0x1FFF)The standard objects of all EtherCAT slaves have the same meaning.

Index 1000 Device type

Index (hex) Name Meaning Data type Flags Default1000:0 Device type Device Type of the EtherCAT slave: The Lo-Word con-

tains the supported CoE Profile (5001). The Hi-Wordcontains the Module Profile corresponding to the Mod-ular Device Profile.

UINT32 RO 0x184C1389(407638921dez)

Index 1008 Device name

Index (hex) Name Meaning Data type Flags Default1008:0 Device name Device name of the EtherCAT slave STRING RO EP6224

Index 1009 Hardware version

Index (hex) Name Meaning Data type Flags Default1009:0 Hardware version Hardware version of the EtherCAT slaves STRING RO 01

Index 100A Software version

Index (hex) Name Meaning Data type Flags Default100A:0 Software version Firmware version of the EtherCAT slaves STRING RO 01



Index 1018 Identity

Index (hex) Name Meaning Data type Flags Default1018:0 Identity contains informations to identify the EtherCAT slave UINT8 RO 0x04 (4dez)1018:01 Vendor ID Vendor ID of the EtherCAT slave UINT32 RO 0x00000002

(2dez)1018:02 Product code Product code of the EtherCAT slave UINT32 RO 0x18503052

(407908434dez)1018:03 Revision Revision number of the EtherCAT-Slave, the Lo-Word

(Bit 0-15) indicates the special functions terminal num-ber; the Hi-Word (Bit 16-31) refers to the device de-scription.

UINT32 RO 0x00100000(1048576dez)

1018:04 Serial number Serial number of the EtherCAT-Slave, the Lo-Byte (Bit0-7) of the Lo-Word contains the year of manufactur-ing, the Hi-Byte (Bit 8-15) of the Lo-Word contains theweek of manufacturing, the Hi-Word (Bit 16-31) is 0 .

UINT32 RO 0x00000000(0dez)

Index 10F0 Backup parameter handling

Index (hex) Name Meaning Data type Flags Default10F0:0 Backup parameter

handlingcontains informations for the standardized Upload andDownload of the Backup Entries

UINT8 RO 0x01 (1dez)

10F0:01 Checksum Checksum over all backup entries UINT32 RO 0x00000000(0dez)

Index 1600 IO RxPDOPDO-Map Ch.1

Index (hex) Name Meaning Data type Flags Default1600:0 IO RxPDOPDO-Map

Ch.1PDO Mapping RxPDO 1 UINT8 RW 0x01 (1dez)

1600:01 SubIndex 001 1. PDO Mapping entry (8 bits align) UINT32 RW 0x0000:00, 8













Index 1A00 IO TxPDOPDO-Map Ch.1

Index (hex) Name Meaning Data type Flags Default1A00:0 IO TxPDOPDO-Map

Ch.1PDO Mapping TxPDO 1 UINT8 RW 0x01 (1dez)

1A00:01 SubIndex 001 1. PDO Mapping entry (8 bits align) UINT32 RW 0x0000:00, 8















Index 1A04 TxPDOeState TxPDO-Map Device

Index (hex) Name Meaning Data type Flags Default1A04:0 TxPDOeState TxPDO-

Map DevicePDO Mapping TxPDO 5 UINT8 RW 0x04 (4dez)

1A04:01 SubIndex 001 1. PDO Mapping entry (object 0xF100 (Diagnosis Sta-tus data), entry 0x01 (State Ch1))

UINT32 RW 0xF100:01, 8


UINT32 RW 0xF100:02, 8


UINT32 RW 0xF100:03, 8


UINT32 RW 0xF100:04, 8

Index 1C00Sync manager type

Index (hex) Name Meaning Data type Flags Default1C00:0 Sync manager type Usage of the Sync Manager channels UINT8 RO 0x04 (4dez)1C00:01 SubIndex 001 Sync-Manager Type Channel 1: Mailbox Write UINT8 RO 0x01 (1dez)1C00:02 SubIndex 002 Sync-Manager Type Channel 2: Mailbox Read UINT8 RO 0x02 (2dez)1C00:03 SubIndex 003 Sync-Manager Type Channel 3: Process Data Write

(Outputs)UINT8 RO 0x03 (3dez)

1C00:04 SubIndex 004 Sync-Manager Type Channel 4: Process Data Read(Inputs)


Index 1C12 RxPDO assign

Index (hex) Name Meaning Data type Flags Default1C12:0 RxPDO assign PDO Assign Outputs UINT8 RW 0x04 (4dez)1C12:01 SubIndex 001 1. assigned RxPDO (contains the index of the corre-

sponding RxPDO Mapping object)UINT16 RW 0x1600

(5632dez)1C12:02 SubIndex 002 2. assigned RxPDO (contains the index of the corre-






(5635dez)



Index 1C13 TxPDO assign

Index (hex) Name Meaning Data type Flags Default1C13:0 TxPDO assign PDO Assign Inputs UINT8 RW 0x05 (5dez)1C13:01 SubIndex 001 1. assigned TxPDO (contains the index of the corre-

sponding TxPDO Mapping object)UINT16 RW 0x1A00

(6656dez)1C13:02 SubIndex 002 2. assigned TxPDO (contains the index of the corre-







sponding TxPDO Mapping object))UINT16 RW 0x1A04

(6660dez)

Index 1C32 SM output parameter

Index (hex) Name Meaning Data type Flags Default1C32:0 SM output parameter Synchronization parameter of the outputs UINT8 RO 0x20 (32dez)1C32:01 Sync mode actual synchronization mode:

0: Free Run

1: Synchron with SM 2 Event

2: DC-Mode - Synchron with SYNC0 Event

3: DC-Mode - Synchron with SYNC1 Event


1C32:02 Cycle time Cycle time (in ns):

Free Run: cycle time of the local timer

Synchron with SM 2 Event: Cycle time of the master

DC-Mode: SYNC0/SYNC1 Cycle time

UINT32 RW 0x000186A0(100000dez)

1C32:03 Shift time Time between SYNC0 Event and Outputs Valid (in ns,only in DC-Mode)

UINT32 RO 0x00000000(0dez)

1C32:04 Sync modes supported Supported synchronization modes:

Bit 0 = 1: Free Run is supported

Bit 1 = 1: Synchron with SM 2 Event is supported

Bit 2-3 = 01: DC-Mode is supported

Bit 4-5 = 10: Output Shift with SYNC1 Event (only DC-Mode)

Bit 14 = 1: dynamic times (could be measured Messenby writing 1C32:08)

UINT16 RO 0xC007(49159dez)

1C32:05 Minimum cycle time Minimum cycle time supported (in ns) UINT32 RO 0x000186A0(100000dez)

1C32:06 Calc and copy time Minimal time between SYNC0 and SYNC1 Event (inns, only in DC-Mode)

UINT32 RO 0x00000000(0dez)

1C32:08 Command 0: Measurement of the times will be stopped

1: Measurement of the times will be started

The Entries 1C32:03, 1C32:05, 1C32:06, 1C32:09,1C33:03, 1C33:06, 1C33:09 will be updated with themaximum measured values.


1C32:09 Delay time Time between SYNC1 Event and Outputs Valid (in ns,only in DC-Mode)

UINT32 RO 0x00000000(0dez)

1C32:0B SM event missedcounter

Number of the missed SM-Events in state OPERA-TIONAL (only in DC Mode)


1C32:0C Cycle exceededcounter

Number of the exceeded cycles in state OPERA-TIONAL


1C32:0D Shift too short counter Number of the too short distances between SYNC0and SYNC1 Event (only in DC Mode)


1C32:20 Sync error TRUE: In the last cycle the synchronization was notcorrect (only in DC Mode)

BOOLEAN RO 0x00 (0dez)



Index 1C33 SM input parameter

Index (hex) Name Meaning Data type Flags Default1C33:0 SM input parameter Synchronization parameter of the inputs UINT8 RO 0x20 (32dez)1C33:01 Sync mode actual synchronization mode:

0: Free Run

1: Synchron with SM 3 Event (no Outputs available)

2: DC - Synchron with SYNC0 Event

3: DC - Synchron with SYNC1 Event

34: Synchron with SM 2 Event (Outputs available)


1C33:02 Cycle time same as 1C32:02 UINT32 RW 0x000186A0(100000dez)

1C33:03 Shift time time between SYNC0-Event and Input Latch (in ns,only in DC-Mode)

UINT32 RO 0x00000000(0dez)

1C33:04 Sync modes supported Supported synchronization modes:

Bit 0: Free Run is supported

Bit 1: Synchron with SM 2 Event is supported (Outputsavailable)

Bit 1: Synchron with SM 3 Event is supported (no Out-puts available)

Bit 2-3 = 01: DC-Mode is supported

Bit 4-5 = 01: Input Shift with local event (Outputs avail-able)

Bit 4-5 = 10: Input Shift with SYNC1 Event (no Outputsavailable)

Bit 14 = 1: dynamic times (could be measured Messenby writing 1C32:08 or 1C33:08)

UINT16 RO 0xC007(49159dez)

1C33:05 Minimum cycle time same as 1C32:05 UINT32 RO 0x000186A0(100000dez)

1C33:06 Calc and copy time time between Input Latch and the availability of the in-puts for the master (in ns, only in DC-Mode)

UINT32 RO 0x00000000(0dez)

1C33:08 Command same as 1C32:08 UINT16 RW 0x0000 (0dez)1C33:09 Delay time time between SYNC1-Event and Input Latch (in ns,

only in DC-Mode)UINT32 RO 0x00000000

(0dez)1C33:0B SM event missed

countersame as 1C32:11 UINT16 RO 0x0000 (0dez)

1C33:0C Cycle exceededcounter

same as 1C32:12 UINT16 RO 0x0000 (0dez)

1C33:0D Shift too short counter same as 1C32:13 UINT16 RO 0x0000 (0dez)1C33:20 Sync error same as 1C32:32 BOOLEAN RO 0x00 (0dez)

5.3.4 Profile specific objects (0x6000-0xFFFF)The profile specific objects have the same meaning for all EtherCAT Slaves which support the profile 5001.

Index 60n0 IO Inputs Ch.1 - 4 (for 0 ≤ n ≤ 3)

Index (hex) Name Meaning Data type Flags Default60n0:0 IO Inputs Ch.1 - 4 Max. Subindex UINT8 RO 0x00 (0dez)60n0:01 Subindex 001 IO-Link input process data... ... ...60n0:10 Subindex 016 IO-Link input process data

Index 70n0 IO Outputs Ch.1 - 4 (for 0 ≤ n ≤ 3)

Index (hex) Name Meaning Data type Flags Default70n0:0 IO Outputs Ch.1 - 4 Max. Subindex UINT8 RO 0x00 (0dez)70n0:01 Subindex 001 IO-Link output process data... ... ...70n0:10 Subindex 016 IO-Link output process data



Index 90n0 IO Info data Ch.1 - 4 (for 0 ≤ n ≤ 3)

Index (hex) Name Meaning Data type Flags Default90n0:0 IO Info data Ch.1 - 4 Max. Subindex UINT8 RO 0x27 (39dez)90n0:04 Device ID The device ID is used for validating the IO link device. UINT32 RO 0x00000000

(0dez)90n0:05 VendorID The vendor ID is used for validating the manufacturer

of the IO link device.UINT32 RO 0x00000000

(0dez)90n0:07 IO-Link revision ID of the specification version based on which the IO

link device communicates.

Bit 0-3: MinorRevBit 4-7: MajorRev


90n0:20 FrameCapability The Frame Capability indicates certain functionalitiesof the IO link device (e.g. SPDU supported).

Bit 0: SPDUBit 1: Type1Bit 7: PHY1

UINT8 RO 0x00 (0

90n0:21 Min cycle time The cycle time refers to the communication betweenthe IO link master and the IO link device. This value is transferred in the IO link format for MinCycle Time.

Bit 6 und 7: Time BaseBit 0 to 5: Multiplier


90n0:22 Offset time reserved UINT8 RO 0x00 (0dez)90n0:23 Process data in length These parameters are transferred in the IO link format

for "Process data in length".



Bit 0 bis 4: LENGTH(length of the process data)


90n0:24 Process data outlength

These parameters are transferred in the IO link formatfor "Process data out length".



Bit 0 bis 4: LENGTH(length of the process data)


90n0:26 Reserved reserved UINT16 RO 0x0000 (0dez)90n0:27 Reserved2 reserved UINT16 RO 0x0000 (0dez)



Index A0n0 IO Diag data Ch.1 - 4 (for 0 ≤ n ≤ 3)

Index (hex) Name Meaning Data type Flags DefaultA0n0:0 IO Diag data Ch.1 - 4 Max. Subindex UINT8 RO 0x02 (2dez)A0n0:01 IO-Link State The value of the IO link state corresponds to a

state from the IO link master state machine

0: INACTIVE 1: DIGINPUT 2: DIGOUTPUT 3: ESTABLISHCOMM 4: INITMASTER 5: INITDEVICE

7: PREOPERATE8: OPERATE 9: STOP


A0n0:02 Lost Frames This parameter counts the number of lost IO linktelegrams. This value is deleted whenever IOlink starts up, otherwise it is incremented contin-uously.


Index F000 Modular device profile

Index (hex) Name Meaning Data type Flags DefaultF000:0 Modular device profile General information about the Modular Device

ProfileUINT8 RO 0x02 (2dez)

F000:01 Module index distance Index distance between the objects of two chan-nels


F000:02 Maximum number of mod-ules

Number of channels UINT16 RO 0x0004 (4dez)

Index F008 Code word

Index (hex) Name Meaning Data type Flags DefaultF008:0 Code word reserved UINT32 RW 0x00000000

(0dez)

Index F010 Module list

Index (hex) Name Meaning Data type Flags DefaultF010:0 Module list Max. Subindex UINT8 RW 0x04 (4dez)F010:01 SubIndex 001 - UINT32 RW 0x0000184C

(6220dez)F010:02 SubIndex 002 - UINT32 RW 0x0000184C



(6220dez)

Index F100 Diagnosis Status data

Index (hex) Name Meaning Data type Flags DefaultF100:0 Diagnosis Status data Max. Subindex UINT8 RO 0x04 (4dez)F100:01 State Ch1 Statusbyte Ch. 1 UINT8 RO 0x00 (0dez)F100:02 State Ch2 Statusbyte Ch. 2 UINT8 RO 0x00 (0dez)F100:03 State Ch3 Statusbyte Ch. 3 UINT8 RO 0x00 (0dez)F100:04 State Ch4 Statusbyte Ch. 4 UINT8 RO 0x00 (0dez)

Index F900 Info data

Index (hex) Name Meaning Data type Flags DefaultF900:0 Info data Max. Subindex UINT8 RO 0x09 (9dez)F900:01 IO-Link Version - UINT8 RO 0x10 (16dez)

Diagnosis


6 Diagnosis

6.1 IO-Link EventsSome of the IO-Link sensors forward events that occur to the master. These events may be items ofinformation, 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 eventscan be read via the CoE directory or the DiagHistory tab.

Fig. 23: DiagHistory tab

The events are arranged according to type (information, warning, error), flag, occurrence of the event (timestamp) and message (port number & event code).The meaning of the individual messages can be taken from the vendor documentation. The IO-Link devicecan be directly allocated on the basis of the port number. The events occurring can be managed using thevarious buttons.

• Update History: if the "Auto Update" field is not selected, then the current events can be displayed viathe "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.

Diagnosis


6.2 ADS Error CodesError 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 codesare 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 (HiByte, hex)

Comment

PDU buffer overflow remote S_PDU_BUFFER ERROR SiNGLESHOT

DL 52 Device buffer is too small forstoring the complete PDU

PDU checksum error(master)

local M_PDU_CHECK ERROR SiNGLESHOT

DL 56 Calculated PDU checksum inmaster does not match actualreceived SPDU

PDU checksum error(device)

remote S_PDU_CHECK ERROR SiNGLESHOT

DL 56 Calculated PDU checksum indevice does not match actualreceived SPDU

PDU flow control error remote S_PDU_FLOW ERROR SiNGLESHOT

DL 56 Violation of flow control ruleduring transfer of SPDU be-tween master and device

Illegal PDU serviceprimitive (master)

local M_PDU_ILLEGAL ERROR SiNGLESHOT

AL 57 Unknown service primitive orwrong response e.g. Read Re-sponse on Write Request

Illegal PDU serviceprimitive (device)

local /remote

S_PDU_ILLEGAL ERROR SiNGLESHOT

AL 58 Unknown service primitive e.g.different protocol revision

Communication error remote COM_ERR SiNGLESHOT

unknown 10 Negative service response initi-ated by a communication error,e.g.. IO-Link connection inter-rupted

Device application er-ror

remote S_APP_DEV** ERROR SiNGLESHOT

APP 80 Service PDU transferred, butnot processed due to device er-ror. See error details in Addi-tional Code**

Diagnosis


Additional Code (IO-Link Spec)

Type Value (LoByte, hex)

Comment

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-ceived SPDU

Subindex not available 12 Calculated PDU checksum in device does not match actual re-ceived SPDU

Service temporarily not available 20 Violation of flow control rule during transfer of SPDU between mas-ter and device

Service temporarily not available, local control 21 Unknown service primitive or wrong response e.g. Read Responseon Write Request

Service temporarily not available, device control 22 Unknown service primitive e.g. different protocol revisionAccess denied 23 Negative service response initiated by a communication error, eg.

IO-Link connection interruptedParameter value out of range 30 Service PDU transferred, but not processed due to device error.

See error details in Additional CodeParameter value above limit 31 Service PDU transferred, but not processed due to device error.

See error details in Additional CodeParameter value below limit 32 Service PDU transferred, but not processed due to device error.

See error details in Additional CodeInterfering parameter 40 Service PDU transferred, but not processed due to device error.

See error details in Additional CodeApplication failure 81 Service PDU transferred, but not processed due to device error.

See error details in Additional CodeApplication not ready 82 Service PDU transferred, but not processed due to device error.

See error details in Additional Code

Appendix


7 Appendix

7.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 andtouch guard

Definition

0 Non-protected1 Protected against access to hazardous parts with the back of a hand. Protected against solid

foreign objects of Ø 50 mm2 Protected against access to hazardous parts with a finger. Protected against solid foreign ob-

jects of Ø 12.5 mm.3 Protected against access to hazardous parts with a tool. Protected against solid foreign objects

Ø 2.5 mm.4 Protected against access to hazardous parts with a wire. Protected against solid foreign objects

Ø 1 mm.5 Protected against access to hazardous parts with a wire. Dust-protected. Intrusion of dust is not

totally prevented, but dust shall not penetrate in a quantity to interfere with satisfactory operationof the device or to impair safety.

6 Protected against access to hazardous parts with a wire. Dust-tight. No intrusion of dust.

2. Number: water* protection Definition0 Non-protected1 Protected against water drops2 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-

tical shall have no harmful effects.4 Protected against splashing water. Water splashed against the disclosure from any direction

shall have no harmful effects5 Protected against water jets6 Protected against powerful water jets7 Protected against the effects of temporary immersion in water. Intrusion of water in quantities

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 youwill find some typical resistance.

Character ResistanceSteam at temperatures >100°C: not resistantSodium base liquor(ph-Value > 12)

at room temperature: resistant> 40°C: not resistant

Acetic acid not resistantArgon (technical clean) resistant

Key• resistant: Lifetime several months• non inherently resistant: Lifetime several weeks• not resistant: Lifetime several hours resp. early decomposition

Appendix


7.2 EtherCAT Box- / EtherCAT P Box - Accessories

Fixing

Ordering information DescriptionZS5300-0001 Mounting rail (500 mm x 129 mm)

Marking material, plugs

Ordering information DescriptionZS5000-0000 Fieldbus Box set M8 (contact labels, plugs)ZS5000-0002 Fieldbus Box set M12 (contact labels, plugs)ZS5000-0010 plugs M8, IP67 (50 pieces)ZS5000-0020 plugs M12, IP67 (50 pieces)ZS5100-0000 marking labels, not printed, 4 stripes at 10 piecesZS5100-xxxx printed marking labels, on request

Tools

Ordering information DescriptionZB8800 torque wrench for M8 cables with knurl, incl. ratchetZB8800-0001 M12 ratchet for torque wrench ZB8800ZB8800-0002 M8 ratchet (field assembly) for torque wrench ZB8800ZB8801-0000 torque wrench for hexagonal plugs, adjustableZB8801-0001 torque cable key, M8/wrench size 9, for torque wrench ZB8801-0000ZB8801-0002 torque cable key, M12/wrench size 13, for torque wrench ZB8801-0000ZB8801-0003 torque cable key, M12 field assembly/wrench size 13, for torque wrench

ZB8801-0000

Further accessoriesFurther accessories may be found at the price list for Beckhoff fieldbus components and at the inter-net under https://www.beckhoff.com

https://www.beckhoff.de/english/fieldbus_box/ethercat_box_accessories_overview.htm?id=25525466903389

Appendix


7.3 General note on the introduction of the BeckhoffIdentification Code (BIC)

General

In future you will increasingly find machine-readable information on Beckhoff products in the form of a DataMatrix Code (DMC, ECC200). This helps us to improve the quality assurance process, beyond which youcan use it for better identification of our products.

The introduction of the Data Matrix Code (called BIC [Beckhoff Identification Code] at Beckhoff) is takingplace gradually across all product groups.

The information in the BICs is oriented to the ANSI standard MH10.8.2-2016

Representation and contents of the BIC

The BIC can be found in the following places, depending on the product:

• on the packaging unit• directly on the product (if space suffices)• on the packaging unit and the product

The BIC is readable and contains information that you can use for your internal handling and administrationof the products. When scanning the BICs you will find the following information:

Coded information on the BIC

Itemno.

Type of information Explanation

1 Beckhoff order number Beckhoff order number2 Beckhoff Traceability

Number (BTN)Unique serial number, see note below

3 Article description Beckhoff article description, e.g. EL10084 Quantity Quantity in packaging unit, e.g. 1, 10, etc.5 Batch number Optional: Year and week of production6 ID/serial number Optional: Present-day serial number system, e.g. with safety

products7 Variant number Optional: Product variant number on the basis of standard products8 Date code Internal9 Job/batch number Internal10 Serial number Internal...

Each item of information is clearly identifiable on the basis of the data identifier (ANSI MH10.8.2-2016). Thedata identifier is followed by a character string. Both together have a maximum length according to thefollowing table. If the items of information are shorter, they are replaced by spaces. The data under positions1-4 always exist (temporary restriction, see BTN below).

Appendix


Overview of the defined data identifiers with examples

Itemno.

Type of information Data identifier Number of char-acters

Sample

1 Beckhoff order number 1P 8 1P0722222 Beckhoff Traceability Number (BTN) S 12 SBTNk4p562d73 Article description 1K 32 1KEL18094 Quantity Q 6 Q15 Batch number 2P 14 2P4015031800166 ID/serial number 51S 12 51S6782941047 Version 30P 32 30PF971 , 2*K1838 Date code 9D 8 9DG01189 Job/batch number 1T 14 1TFA1234567810 Serial number 52S 23 52S2304853-1-004...

Structure of the BIC

Example of an item of information made up of positions 1 – 4 and 6. The data identifiers are each marked inred for clearer illustration:

1P072222SBTNk4p562d71KEL1809 Q1 51S6782941041P S 1K Q 51S

Order number BTN Article description IDQuantity

BTN

An important component of the BIC is the Beckhoff Traceability Number (BTN, item no. 2). The BTN is aunique 8-character serial number that in future will replace all other serial number systems at Beckhoff (e.g.batch designations on IO components, hitherto serial number circle for safety products, etc.). The BTN islikewise being introduced gradually, so it may be the case that the BTN is not yet coded in the BIC.

Appendix


7.4 Support and ServiceBeckhoff and their partners around the world offer comprehensive support and service, making available fastand 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 Beckhoffproducts!

The addresses of Beckhoff's branch offices and representatives round the world can be found on her internetpages:http://www.beckhoff.com

You will also find further documentation for Beckhoff components there.

Beckhoff Headquarters

Beckhoff Automation GmbH & Co. KG

Huelshorstweg 2033415 VerlGermany

Phone: +49 5246 963 0Fax: +49 5246 963 198e-mail: [email protected]

Beckhoff Support

Support offers you comprehensive technical assistance, helping you not only with the application ofindividual 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 157Fax: +49 5246 963 9157e-mail: [email protected]

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 460Fax: +49 5246 963 479e-mail: [email protected]

http://www.beckhoff.de/english/support/default.htm

http://www.beckhoff.com

http://www.beckhoff.com/english/download/default.htm

Table of Figures


Table of FiguresFig. 1 EtherCAT Box modules: Example of cabling in a line structure .................................................. 9Fig. 2 EP6224-2022............................................................................................................................... 10Fig. 3 EP6224-3022............................................................................................................................... 10Fig. 4 EP6228-0022............................................................................................................................... 15Fig. 5 EP6228-3032............................................................................................................................... 15Fig. 6 EP6228-3132............................................................................................................................... 16Fig. 7 IO-Link topology........................................................................................................................... 20Fig. 8 Dimensions .................................................................................................................................. 22Fig. 9 Dimensions .................................................................................................................................. 23Fig. 10 Dimensions .................................................................................................................................. 24Fig. 11 Connector for the supply voltages ............................................................................................... 27Fig. 12 M8 connector ............................................................................................................................... 27Fig. 13 Status LEDs for the supply voltages............................................................................................ 28Fig. 14 Connector for the supply voltages ............................................................................................... 29Fig. 15 7/8" plug connectors .................................................................................................................... 29Fig. 16 Status LEDs for the supply voltages............................................................................................ 30Fig. 17 EtherCAT connector .................................................................................................................... 31Fig. 18 M8 socket .................................................................................................................................... 31Fig. 19 EtherCAT Status LEDs ................................................................................................................ 32Fig. 20 M12 socket .................................................................................................................................. 33Fig. 21 Status LEDs of an IO-Link port .................................................................................................... 34Fig. 22 UL label........................................................................................................................................ 35Fig. 23 DiagHistory tab ............................................................................................................................ 49

Directory contents of /download/ - Documentation EP6224 and … · 2019-10-28 · Foreword EP6224...

Documents

Transcript of Directory contents of /download/ - Documentation EP6224 and … · 2019-10-28 · Foreword EP6224...