Weidmuller UR20-4COM-IO-LINK Manual 

1 About this documentation 3 1.1 Symbols and notes 3 1.2 Complete documentation 3 1.3 Standard data structure 4 1.4 Software releases described 4 2 Safety 5 2.1 General safety notice 5 2.2 Intended use 6 2.3 Use in a potentially explosive atmosphere 6 2.4 Legal notice 7 3 IO-Link overview 9 4 Module description 11 4.1 Device description 12 4.2 Connections 13 4.3 LED indicators 13 4.4 Block diagram 14 4.5 Technical data 15 4.6 Editable parameters 17 5 Assembly and installation 21 5.1 Connecting the IO-Link device 21 5.2 Connecting standard field devices 22 6 Commissioning 23 6.1 Requirements 23 6.2 Device description files 23 6.3 Procedure for commissioning 24 6.4 Commissioning with the SIMATIC Manager (PROFINET) 25 6.5 Commissioning with the TIA portal(PROFINET) 27 6.6 Commissioning with TwinCAT (EtherCAT) 29 6.7 Commissioning with Studio 5000(Ethernet/IP) 30 6.8 Commissioning with Automation Studio (POWERLINK) 33 6.9 Reading and writing data objects on IO-Link devices 35 6.10 “IO_LINK_CALL” function block 38 6.11 I&M functions 40 7� Planning�IO-Link�device�configurations� 41 7.1 u-remote IO-Link configurator 41 7.2 Installing the u-remote IO-Link configurator 41 7.3 Operating the u-remote IO-Link configurator 41 7.4 Editing IO-Link device configurations 44 7.5 Editing IO-Link device configurations online 45 8 Process data 49 8.1 Process data mapping 49 8.2 Process input data 50 8.3 Process output data 50 8.4 Fieldbus-dependent process data widths 51 9 Diagnostics and troubleshooting 55 9.1 Diagnostic data 55 9.2 IO-Link master event codes 55 9.3 LED indicators and troubleshooting 56 10 Disassembly and disposal 57 10.1 Disassembling a u-remote-Modul 57 10.2 Disposing of a u-remote-Modul 57 Manufacturer Weidmüller Interface GmbH & Co. KG Klingenbergstraße 26 D-32758 Detmold T +49 5231 14-0 F +49 5231 14-292083 www.weidmueller.com Document No. 2547720000 Revision 03/September 2019

3 Manual Communication module UR20-4COM-IO-LINK 2547720000/03/09.2019 1.1 Symbols and notes The safety notices in this documentation are designed ac- cording to the severity of the danger. DANGER Imminent danger to life! Notes with the signal word “Danger” warn you of situations that will result in serious injury or death if you do not follow the instructions given in this manual. WARNING Possible danger to life! Notes with the signal word “Warning” warn you of situations that may result in serious injury or death if you do not follow the instructions given in this manual. CAUTION Risk of injury! Notes with the signal word “Caution” warn you of situations that may result in injury if you do not follow the instructions given in this manual. ATTENTION Material damage! Notes with the signal word “Attention” warn you of hazards that may result in material damage. Text next to this arrow are notes that are not relevant to safety, but provide important information about proper and effective work procedures. The situation-dependent safety notices may contain the fol- lowing warning symbols: Symbol Meaning Warning against dangerous electrical voltage Warning against explosive atmospheres Warning against electrostatically charged com- ponents Warning against automatic startups Observe the documentation ▶ All instructions can be identified by the black triangles next to the text. – Lists are marked with a tick. 1.2 Complete documentation The documentation is intended for trained electri- cians who are familiar with national and interna- tional laws, provisions and standards. This manual contains product-specific information and notes about the communication module UR20-4COM-IO-LINK. It supplements but does not replace the u-remote IP20 manual (document No. 1432790000). The u-remote Web Server Manual (document No. 2112220000) describes how to use the web server application. All documents are available to download on the Weidmüller Website. 1 About this documentation

4 2547720000/03/09.2019 Manual Communication module UR20-4COM-IO-LINK 1.3 Standard data structure All given details of data structure (e.g. process data, parameters) refer to the u-remote internal mapping, when the standard data format is set in the coupler parameters (see table below). The way these data are represented by other fieldbus participants (e.g. the PLC), depends addi- tionally on the fieldbus specification and the data format of the communicating device. Therefore it might happen, that bytes are changed within a word or words are changed within a double word. Standard data formats Fieldbus couler Standard data format UR20-FBC-PB-DP, UR20-FBC-PB-DP-V2 Motorola UR20-FBC-PN-IRT, UR20-FBC-PN-IRT-V2 UR20-FBC-MOD-TCP, UR20-FBC-MOD-TCP-V2 UR20-FBC-CAN Intel UR20-FBC-EC UR20-FBC-EIP UR20-FBC-DN UR20-FBC-PL 1.4 Software releases described The present manual describes the following firmware re- leases of the couplers: Firmware releases Order No. Fieldbus coupler Release 1334870000 UR20-FBC-PB-DP 01.07.00 2614380000 UR20-FBC-PB-DP-V2 01.08.00 1334880000 UR20-FBC-PN-IRT 01.07.00 2566380000 UR20-FBC-PN-IRT-V2 01.09.00 1334910000 UR20-FBC-EC, HW 02.xx.xx 01.11.00 1334910000 UR20-FBC-EC, HW 01.xx.xx 01.10.00 2476450000 UR20-FBC-MOD-TCP-V2 02.07.00 1334930000 UR20-FBC-MOD-TCP 02.07.00 1334920000 UR20-FBC-EIP, HW 02.xx.xx 02.08.00 1334920000 UR20-FBC-EIP, HW 01.xx.xx 01.08.00 1334900000 UR20-FBC-DN 01.07.00 1334890000 UR20-FBC-CAN 01.07.00 1334940000 UR20-FBC-PL 01.07.00 Device description files Fieldbus protocol Release PROFIBUS UR20-FBC-PB-DP: 2.88 UR20-FBC-PB-DP-V2: 2.88 PROFINET UR20-FBC-PN-IRT: 20190628 UR20-FBC-PN-IRT-V2: 20190628 EtherCAT 45 (coupler), 49 (modules) Ethernet/IP 1.5 DeviceNet 1.3 CANopen 1.18 POWERLINK 01.01 Web server language files Language Release Availability German 01.04.00 On delivery English 01.04.00 On delivery Chinese 01.04.00 On delivery French 01.04.00 Available online Italian 01.04.00 Available online Spanish 01.04.00 Available online Portuguese 01.04.00 Available online Korean 01.04.00 Available online Japanese 01.04.00 Available online Additional software Software Release u-remote IO-Link configurator 01.02.00

5 Manual Communication module UR20-4COM-IO-LINK 2547720000/03/09.2019 This chapter includes general safety instructions for handling the communication module UR20-4COM-IO-LINK. Specific warning notices for specific tasks and situations are given at the appropriate places in the documentation. Failure to ob- serve the safety and warning notices can result in damage to persons and material. This manual contains product-specific information and notes about the communication module UR20-4COM-IO-LINK. It supplements but does not replace the u-remote IP20 manual (document No. 1432790000). The manual is available to download from the Weidmüller website. 2.1 General safety notice Work on the u-remote products may only be performed by qualified electricians with the support of trained persons. As a result of their professional training and experience, an electrician is qualified to perform the necessary work and identify any potential risks. Before any work is carried out on the products (installa- tion, maintenance, retrofitting), the power supply must be switched off and secured against being switched on again. Work may be carried out with safety extra-low voltage (SELV/PELV). When working during continued operations, the emergency stop mechanisms must not be made ineffec- tive. The u-remote products do not comprehend any components or parts that can be maintained by the operator. If a malfunc- tion on a u-remote product cannot be fixed after following the recommended measures (see Chapter 9), the product in question must be sent back to Weidmüller. Weidmüller does not assume any liability if the product has been tampered with! Electrostatic discharge u-remote products can be damaged or destroyed by electro- static discharge. When handling the products, the neces- sary safety measures against electrostatic discharge (ESD) according to IEC 61340-5-1 and IEC 61340-5-2 must be observed. All devices are supplied in ESD-protected packaging. The packing and unpacking as well as the installation and di- sassembly of a device may only be carried out by qualified personnel and in accordance with the ESD information. Open equipment u-remote products are open equipment that may only be in- stalled and operated in lockable housings, cabinets or electri- cal operations rooms. Only trained and authorised personnel may access the equipment. For applications requiring functional safety, the surrounding housing must meet at least IP54. The standards and guide- lines applicable for the assembly of switch cabinets and the arrangement of data and supply lines must be complied with. Fuse protection The operator must set up the equipment so that it is pro- tected against overloading. The 24 V DC power supply units used must fulfill the SELV category, no matter whether they supply the system or feed-in modules. The output voltage of the feed-in power supply has to fulfill overvoltage category 1 according to IEC 61010. When connecting to outer current circuits the respective overload category has to be regarded for each single module of the u-remote station (see technical data). The main switch, the switches of the subsequent circuits, the cable cross-sections and the fuse protection have to be configured according to IEC 61010. The current demand must be caluclated separately for each single u-remote sta- tion as described in the u-remote IP20 manual. In the case of modules without fused sensor/actuator power supplies, all lines to the connected sensors/actuators must be fused corresponding to their conductor cross-section (as per DIN VDE 0298 Part 4). To meet UL-specifications in accordance with UL 248-14, a UL-certified automatic fuse (e.g. ABB Type S201-B16) or a 10 A fuse with a medium time-lag (e.g. ESKA Part No. 522.227) must be used. All connections of the u-remote components are protected against voltage pulses and overcurrent in accordance with IEC 61131-2, Zone B. The operator has to decide whether additional overvoltage protection according to IEC 62305 is required. Voltages that exceed +/-30 V may cause the de- struction of couplers and modules. Earthing Via an FE spring on its underside each coupler and each module is electrically connected to the DIN rail. This con- nection is only established certainly if the assembly is car- ried out carefully and in accordance with the instructions (u-remote IP20 manual). In order to ensure the earthing of the station the DIN rail must be connected to the protective earth via the earth terminals (PE). 2 Safety

6 2547720000/03/09.2019 Manual Communication module UR20-4COM-IO-LINK Shielding IO-Link Devices and conventional sensors/actuators are con- nected to the UR20-4COM-IO-LINK communication module via unshielded cables. 2.2 Intended use The UR20-4COM-IO-LINK communication module is an I/O module from the u-remote series. It is intended for use in a u-remote station. As an IO-Link master the module can inte- grate up to four IO-Link Devices in an automation system. The products of the u-remote series are intended for use in industrial automation. A u-remote station with bus coupler and connected modules is intended for the decentralised control of systems or sub-systems. Via the fieldbus coupler every module of a station is integrated into a fieldbus struc- ture and connected to the superordinate control unit. The u-remote products conform to protection class IP20 (in ac- cordance with IEC 60529). The observance of the documentation is part of the intended use. The products described in this manual may only be used for the intended applications and only in connection with certified third-party devices or components. The product- specific protective measures can become ineffective in the event of deviating use. 2.3 Use in a potentially explosive atmosphere Unless otherwise noted, the u-remote products can be used in potentially explosive atmospheres rated as Zone 2 (as per Directive 2014/34/EU). The u-remote products are suitable for use in Class I, Division 2, Groups A to D according to NFPA publication 70. If u-remote products are used in potentially explosive atmos- pheres, the following notes are also applicable: – Staff involved in assembly, installation and operation must be qualified to perform safe work on electrical systems protected against potentially explosive atmospheres. – The requirements according to IEC 60079-14 must be observed. – The substitution of any components may impair suitability for Class I, Divsion 2. – The equipment shall be installed in an enclosure that pro- vides a degree of protection not less than IP54 in accord- ance with IEC 60079-15, accessible only by the use of a tool. – The housing enclosing must meet the requirements of explosion protection type Ex n or Ex e. – The u-remote station may only be installed in horizontal orientation. – Sensors and actuators that are located in Zone 2 or in a safe zone can be connected to the u-remote station. – If the ambient temperature under rated conditions exeeds 55 °C, the cables used for feed-in (on the fieldbus coupler and on power-feed modules) must be specified for at least 90 °C. – If the temperature under rated conditions exceeds 70 °C at the cable or conduit entry point, or 80 °C at the branching point of the conductors, the temperature speci- fication of the selected cable shall be in compliance with the actual measured temperature values. – The equipment shall only be used in an area of not more than pollution degree 2, as defined in IEC 60664-1. – A stabilized 24 V DC power supply with double or rein- forced insulation shall be used. – A visual inspection of the u-remote station is to be per- formed once per year. – While explosive atmosphere is present: – No electrical connection shall be separated in ener- gized condition. – The USB interface shall not be used. – Dip-switches, binary-switches and potentiometers shall not be actuated.

7 Manual Communication module UR20-4COM-IO-LINK 2547720000/03/09.2019 2.4 Legal notice The communication module UR20-4COM-IO-LINK is CE- compliant in accordance with Directive 2014/30/EU (EMC Directive). It also meets the requirements of the ATEX Direc- tive 2014/34/EU. The results of the measurements according to CISPR 16-2- 3 should also be suitable to demonstrate the compliance of the u-remote devices to the limits for radiated emissions as defined by CFR 47 Part 15, Subpart B, §15.109, Class A (2010) and ICES-003, Issue 5, Class A (2012). Components of the following free software products are inte- grated into the u-remote products: Component Licence Link eCos modified GPL http://ecos.sourceware.org/license-overview. html mongoose WebServer MIT http://web.archive.org/ web/20111015092802/http://code.google. com/p/mongoose/source/browse/LICENSE jQuery MIT https://github.com/jquery/jquery/blob/master/ LICENSE.txt jQuery-cus- tomSelect MIT https://github.com/jquery/jquery/blob/master/ LICENSE.txt jQuery-i18n MIT https://github.com/jquery/jquery/blob/master/ LICENSE.txt jQuery- overscroll MIT https://github.com/jquery/jquery/blob/master/ LICENSE.txt jQuery-ui MIT https://github.com/jquery/jquery/blob/master/ LICENSE.txt JSZip MIT https://github.com/Stuk/jszip/blob/master/ LICENSE.markdown md5 (as part of CryptoJS) modified BSD https://code.google.com/archive/p/crypto-js/ wikis/License.wiki snap-svg Apache license 2.0 https://github.com/adobe-webplatform/Snap. svg/blob/master/LICENSE underscore MIT https://github.com/jashkenas/underscore/blob/ master/LICENSE mustache MIT https://github.com/janl/mustache.js/blob/ master/LICENSE Components of free software products are integrated into the u-remote IO-Link Configurator. The licence terms are ac- cessible from within the program.

2547720000/03/09.2019 ������� ������� �������� ������������������� IO-Link for automation technology IO-Link is a communication protocol for automation tech- nology. IO-Link enables serial, bi-directional point-to-point communication between devices on the sensor-actuator level and devices on the field level or control level. Besides cyclic process data, IO-Link allows parameters, diagnoses and identification data to be exchanged acyclically. IO-Link is standardised worldwide in IEC 61131-9 under the designa- tion “single-drop communication interface for small sensors and actuators” (SDCI). An IO-Link system consists of two components: – IO-Link master: represents the interface between IO- Link devices and the superordinate communication sys- tem. – IO-Link device: communication-capable field device, e.g. a sensor which is controlled by a IO-Link master. IO-Link master and IO-Link device communicate via the switching and communication cable C/Q. The IO-Link device is supplied with voltage by the IO-Link master via the L+ and L- cables. Depending on the port class, an IO-Link port has additional connections: – Port class A: The function of the additional connections is selected by the manufacturer. Often, this connection is occupied with an additional digital input or output. – Port class B: The IO-Link master provides a second sup- ply voltage via two further connections. An IO-Link device is connected with an IO-Link port of the IO-Link master with 3-cable or 5-cable technology. � � � � � ������� ������� ��� ��� �������������������� �������� ��� �� �� ��� �������������� �������������� IO-Link communication principle The IO-Link ports can be operated in IO-Link mode for bi- directional communication or in SIO mode as digital inputs or outputs. In IO-Link mode, the IO-Link master automati- cally sets the right transmission rate for IO-Link commu- nication after activation. The IO-Link master then checks the identity of the IO-Link device (device comparison). The Data Storage function ensures correct parameterization of the IO-Link device after replacement of IO-Link device or IO-Link master without additional programming. You can parameterise IO-Link devices using a configura- tion application or by means of acyclic services. To do so, you will need the device description files from the IO-Link device-manufacturer (IODDs). You can search for and download IODDs using the “IODDfinder” on the IO-Link Con- sortium website. You will find more information on IO-Link and IODDs at http://www.io-link.com. 3 IO-Link overview

2547720000/03/09.2019 Digital communication module UR20-4COM-IO-LINK (order no. 1315740000) The digital communication module UR20-4COM-IO-LINK is an IO-Link master according to IO-Link specification V1.1.2. One IO-Link device can be connected to each plug-in connec- tor. The IO-Link devices must comply with port class A. Port class B is possible if additional potential distribution modules are used. One digital input can be used at each plug-in con- nector. Process data is exchanged with the IO-Link device con- nected via each IO-Link port. In addition, acyclic data can be exchanged (diagnosis data, parameter data, status informa- tion). The parameter data of the IO-Link devices connected can be stored in the master module where they are managed from a parameterising server (Data Storage). This means that the IO-Link master or an IO-Link device (from IO-Link specifi- cation version 1.1) are very easy to replace. The four communication channels can also be used as digi- tal inputs or outputs with standard field devices. A status LED is assigned to each channel. The module elec- tronics supply the connected sensors with power from the input current path (IIN). The inputs are protected against voltage surges and overcur- rent. Voltages that exceed ± 30 V may cause the destruction of the module. You can use the “u-remote IO-Link configurator” software to configure the IO-Link system for the UR20-4COM-IO-LINK. 4 Module description

12 2547720000/03/09.2019 Manual Communication module UR20-4COM-IO-LINK 4.1 Device description � � � � � � � � �� �� � � �� �� �� �� Communication module UR20-4COM-IO-LINK 1 Release lever for DIN rail fixing 2 System bus 3 System current path 4 Input current path 5 Output current path 6 Seats for module markers 7 Type designation 8 Connector frame unlocking device 9 Module status LED (collective message) 10 Connector 11 Channel status LED 12 Latching hook for latching onto module sides 13 DIN rail foot 14 Type plate � � � � � � I/O-Module components 1 Base module 2 Electronic unit 3 Removal lever for electronic unit 4 Connector frame 5 Connector 6 Plug-in unit

13 Manual Communication module UR20-4COM-IO-LINK 2547720000/03/09.2019 4.2 Connections IO-LINK Device IO-LINK Device IO-LINK Device IO-LINK Device 1 2 3 4 2 1 3 4 1 2 3 4 2 4 3 1 2 4 3 1 4 IO LINK C/Q 1 L+ 1 DI 1 C/Q 2 L+ 2 DI 2 C/Q 3 L+ 3 DI 3 C/Q 4 L+ 4 L– 1 L– 2 L– 3 L– 4 DI 4 Connection diagram UR20-4COM-IO-LINK A plug-in connector corresponds to an IO-Link port of type A. Connector Connection Signal Function � � � � 1 C/Q IO-Link communication 2 L- GND IN 3 L+ 24 V DC IN 4 DI Digital input (type 1) A description of how IO-Link devices for both port classes and standard field devices can be connected to the module is available in chapter 5. 4.3 LED indicators 4 IO LINK Module status LED Green: Communication on system bus Red: Collective error diagnostic 1.1 Yellow: Status COM 1 1.2 Red: Error IO-Link port 1 1.4 Yellow: Status DI 1 2.1 Yellow: Status COM 2 2.2 Red: Error IO-Link port 2 2.4 Yellow: Status DI 2 3.1 Yellow: Status COM 3 3.2 Red: Error IO-Link port 3 3.4 Yellow: Status DI 3 4.1 Yellow: Status COM 4 4.2 Red: Error IO-Link port 4 4.4 Yellow: Status DI 4 LED indicators UR20-4COM-IO-LINK

14 2547720000/03/09.2019 Manual Communication module UR20-4COM-IO-LINK 4.4 Block diagram GND C/Q 2 L– 2 L+ 2 DI 2 C/Q 1 L– 1 L+ 1 DI 1 C/Q 3 L– 3 L+ 3 DI 3 C/Q 4 L– 4 L+ 4 DI 4 System bus USYS UIN UOUT µC µC 24VDC IN 4x GND IN 1 2 3 4 Block diagram UR20-4COM-IO-LINK The numbering of the channels in the u-remote system dif- fers from the numbering of the IO-Link port as per the IO-Link specification. The following table shows the assignment of plug-in connectors and channels to IO-Link ports for the UR20-4COM-IO-LINK communication module. Plug-in connector IO-Link port Channel 1 1 0 2 2 1 3 3 2 4 4 3

15 Manual Communication module UR20-4COM-IO-LINK 2547720000/03/09.2019 4.5 Technical data UR20-4COM-IO-Link System data Data (coupler dependent) see Chapter 8 Interface u-remote system bus System bus transfer rate 48 MBit/s Digital inputs Number 4 Sensor types Typ 1 and Typ 3 acc. IEC 61131-2 Low input voltage < 5 V High input voltage > 11 V IO-Link interfaces Number 4 Type IO-Link as per IEC 61131-9 Transfer rate 4,8 kBaud / 38,4 kBaud / 230,4 kBaud, depending on the connected IO-Link device Output current C/Q (in DO mode) 0,1 A Input type C/Q (in DI mode)1) Typ 1 and Typ 3 acc. IEC 61131-2 Output current L+ 0.5 A per channel, total max. 2 A Line break detection yes Short-circuit-proof yes Module diagnosis yes Individual channel diagnosis yes Supply Supply voltage 24 V DC +20 %/-15 % Current consumption from system current path ISYS 8 mA Current consumption from input current path IIN 25 mA + sensor supply General data Type of connection “PUSH IN” Single-wired, fine-wired Conductor cross-section 0.14 – 1.5 mm2 (AWG 16 – 26) Dimensions Height 120.0 mm / 4.72" (with release lever: 128.0 mm / 5.04") Width 11.5 mm / 0.45" Depth 76.0 mm / 2.99" Weight (operational status) 88 g Protection�class�(IEC 60529) IP 20 1) If C/Q is used as digital input, the connected device shall only be supplied via the L+ and L- connections of the respective channel. 2) Higher altitudes are possible when particular deratings are considered. Please contact your responsible Weidmüller company as needed.

16 2547720000/03/09.2019 Manual Communication module UR20-4COM-IO-LINK UR20-4COM-IO-Link Flammability�rating�UL 94 V-0 Temperature data Operation -20 °C ... +60 °C / - 4 ... +140 °F Storage, transport -40 °C ... +85 °C / - 40 ... +185 °F Humidity Operation, storage, transport 5 % to 95 %, non-condensing as per IEC 61131-2 Air pressure Operation2) ≥ 795 hPa (altitude ≤ 2000 m) as per IEC 61131-2 Storage, transport ≥ 700 hPa (altitude ≤ 3000 m) as per IEC 61131-2 Potential isolation Test voltage 500 V DC field/system (as per EN 60079-15:2010) Pollution severity level 2 (as per DIN EN 60664-1:2008) Overvoltage category II (as per DIN EN 50178) Vibration resistance 5 Hz ≤ f ≤ 8.4 Hz: 3.5-mm amplitude as per IEC 60068-2-6 8.4 Hz ≤ f ≤ 150 Hz: 1-g acceleration as per IEC 60068-2-6 Shock resistance 15 g over 11 ms, half sinewave, as per IEC 60068-2-27 Approvals and standards cULus UL 61010 Potentially explosive atmosphere Zone 2 ATEX Directive 2014/34/EU EMC IEC 61131-9 Explosion protection IEC 60079-0:2012, IEC 60079-15:2010, EN 60079-0:2012, EN 60079-15:2010 PLC IEC 61131-2, IEC 61131-9 1) If C/Q is used as digital input, the connected device shall only be supplied via the L+ and L- connections of the respective channel. 2) Higher altitudes are possible when particular deratings are considered. Please contact your responsible Weidmüller company as needed.

17 Manual Communication module UR20-4COM-IO-LINK 2547720000/03/09.2019 4.6 Editable parameters Overview of the editable parameter UR20-4COM-IO-LINK Channel Description Options1 Default 0 ... 3 Operating mode disabled (0) / DO (1) / DI (2) / IO-Link (3) disabled 0 ... 3 Port cycle Free running (0) / Fixed cycle (1) / Message sync (2) Free running 0 ... 3 Port cycle time [n*0.1 ms] 4 ... 1326 4 0 ... 3 IO-Link device check disabled (0) / Type compare (1) / Identical (2) disabled 0 ... 3 DS activation state disabled (0) / enabled (1) / Clear (2) disabled 0 ... 3 Channel diagnostics disabled (0) / enabled (1) disabled 0 ... 3 Process data length input 0 Byte (0) / 1 Byte (1) / 2 Byte (2) / ... / 32 Byte (32) / auto (255) auto 0 ... 3 Process data length output 0 Byte (0) / 1 Byte (1) / 2 Byte (2) / ... / 32 Byte (32) / auto (255) auto 1) Values in brackets for EtherCAT “Operating mode” parameter The “Operation mode” parameter defines the function of the respective IO-Link port (C/Q, L+ and L- connections). The parameter does not influence the function of the additional digital input (DI connection). Disabled (default) The supply voltage at L+ and communication via C/Q are disabled. DO The C/Q connection works as a digital output. The length of the process output data for this IO-Link port is 1 byte. DI The C/Q connection works as a digital input. The length of the process input data for this IO-Link port is 1 byte. IO-Link The IO-Link port uses the C/Q connection for IO-Link com- munication. The length of the process data is determined by the “Process data IN length” and “Process data OUT length” parameters. “Port cycle” parameter The “Port cycle” parameter defines how the cycle time of the IO-Link port is determined. Free running (default) The cycle time of the IO-Link port is automatically set to match the IO-Link device connected. Fixed cycle The cycle time of the IO-Link port is set to the value which is defined by the “Port cycle time (n*0.1 ms)” parameter. The real cycle time of the IO-Link port depends on the IO-Link device connected. If you set a cycle time which is shorter than the minimum cycle time of the IO-Link device, the smallest possible cycle time is automatically set. The web view is not updated. Message sync All IO-Link ports with this parameter setting start simultane- ously with message transmission. The IO-Link device with the longest cycle time at these IO-Link ports determines the cycle time.

18 2547720000/03/09.2019 Manual Communication module UR20-4COM-IO-LINK “Port�cycle�time�(n*0.1 ms)”�parameter The “Port cycle time (n*0.1 ms)” defines the cycle time of the IO-Link port. This parameter is only relevant if the “Port cycle” parameter has been set to “Fixed value”. According to the IO-Link specification, the cycle time is coded with a time base (2 bits) and a multiplier (6 bits). The coding is dependent on the cycle time. Coding the cycle time Cycle time Time base Multipl. Calculation 0,4 ms ... 6,3 ms 0,1 ms 4 ... 63 Time Base × Multipl. 6,4 ms … 31,6 ms 0,4 ms 0 ... 63 6,4 ms + Time Base × Multipl. 32,0 ms … 132,8 ms 1,6 ms 0 ... 63 32,0 ms + Time Base × Multipl. 4 … 1326 (default:�4) The cycle time of the IO-Link port set is (4 … 1326) × 0.1 ms. Cycle times which cannot be coded as above, are automatically converted by the IO-Link master into the next-possible, codable time. The web view is not updated. “IO-Link device check” parameter This function allows the identification characteristics of a connected IO-Link device to be checked. The transfer of the process data is only started once the characteristics match the values set in the IO-Link master. disabled (default) The function is disabled and there is no validation. Type compare The Vendor ID and the Device ID are compared. Identical The Vendor ID, the Device ID and the serial number are com- pared. “DS activation state” parameter The “DS activation state” activates the Data Storage func- tion. The Data Storage function controls the parameter setting server of the IO-Link master. The parameter setting server manages the IO-Link device parameters, such that the IO-Link master or a IO-Link device (from IO-Link specification version 1.1) is very easy to replace. disabled (default) The Data Storage function is disabled. Parameter data al- ready saved in IO-Link master is retained. enabled The Data Storage function is enabled. Parameter data is ex- changed between the IO-Link master and IO-Link device if an inconsistency is detected. The direction of replacement depends on the status of IO-Link master and IO-Link device. An upload of IO-Link device to the IO-Link master takes place if a connected IO-Link device requests an upload (upload flag set) or if there is no valid data in the IO-Link master. A IO-Link device requests an upload for each change in the IO-Link device parameter. If the parameter data saved in the IO-Link master does not match the data on the connected IO-Link device and there have been no upload requests made by the IO-Link device, data is downloaded from the IO-Link master to the IO-Link device. Data Storage function enabled IO-Link master status IO-Link device status Action No valid data Upload flag set Upload No valid data Upload flag not set Upload Valid data Upload flag set Upload Valid data Upload flag not set Download Clear The Data Storage function is disabled. Parameter data al- ready stored in the IO-Link master is deleted. If the Data Storage function is enabled, do not connect any IO-Link devices with unknown parameters to avoid saving incorrect parameters. Reset IO-Link devices to factory settings before you connect them.

19 Manual Communication module UR20-4COM-IO-LINK 2547720000/03/09.2019 “Channel diagnostics” parameter The “Channel diagnostics” parameter activates channel diag- nostics. Disabled (default) Channel diagnostics is disabled. Enabled Channel diagnostics is enabled. “Process data length input” parameter The “Process data length input” parameter defines how many bytes the process input data of the IO-Link master are occupied by the cyclic input data of the IO-Link device con- nected. 0 … 32�bytes The cyclic input data of the IO-Link device connected occu- pies 0 … 32 bytes of the IO-Link master process input data. auto (default) The length of the cyclic input data is automatically set to the IO-Link device connected. “Process data length output” parameter The “Process data length output” parameter defines how many bytes of the IO-Link master process output data are oc- cupied by the cyclic data of the IO-Link device connected. 0 … 32�bytes The cyclic output data of the IO-Link device connected occu- pies 0 … 32 bytes of the IO-Link master process output data. auto (default) The length of the cyclic output data is automatically set to match the IO-Link device connected.

21 Manual Communication module UR20-4COM-IO-LINK 2547720000/03/09.2019 WARNING Explosion risk! During installation work, sparks can form and surfaces may become excessively hot ▶ Before starting any work, make sure that there is not a potentially explosive atmos- phere! ▶ For applications in explosive risk zones, observe the installation and construction requirements of EN 60079-15 and coun- try-specific regulations. WARNING Dangerous contact voltage! ▶ Carry out assembly and wiring work only when the power supply disconnected. ▶ Make sure that the place of installation has been disconnected from the power supply! ATTENTION The product can be destroyed by elec- trostatic discharge! u-remote products can be destroyed by elec- trostatic discharge. ▶ Please make sure that persons and work equipment are adequately earthed! ▶ In addition, always refer to the complete doc- umentation in the u-remote IP20 manual. ▶ Carry out all work during the installation/removal and replacement of components as described in the u-remote manual. 5.1 Connecting the IO-Link device ATTENTION The module can be destroyed! The voltage between C/Q and L- must not be greater that the voltage between L+ and L-. ▶ Only connect the devices as shown. Use unshielded cables of maximum 20 m length to connect IO-Link devices. Connecting IO-Link device for class A port ��� �� �� �� � � � � � � � � � �� �� ��� �� ����������������� �������������� Connecting IO-Link device for class A port (DI connection optional) ▶ Connect the IO-Link device as shown in the figure. The use of the additional digital input at the DI connection is optional. You can use this digital input, e.g. if the IO-Link device provides an additional switching signal. 5 Assembly and installation

22 2547720000/03/09.2019 Manual Communication module UR20-4COM-IO-LINK Connecting IO-Link device for class B port To connect an IO-Link device with class B port to your u- remote station, you also need the following potential distribu- tion modules: – for input current path – UR20-16AUX-I (order no. 1334770000) – UR20-16AUX-GND-I (order no. 1334800000) – for output current path – UR20-16AUX-O (order no. 1334780000) – UR20-16AUX-GND-O (order no. 1334810000) ��� �� �� �� � � � � � � � � � �� �� ��� �� ��� ��� ����� � � � � ������� ����� � � � � ����������������� ������������ ���������������� �������������� Connecting IO-Link device for type B port ▶ Install the three modules in a u-remote station. ▶ Connect the IO-Link device as shown in the figure. 5.2 Connecting�standard�field�devices ATTENTION The module can be destroyed! The voltage between C/Q and L- must not be greater that the voltage between L+ and L-. ▶ Only connect the devices as shown. Connecting sensor to C/Q � � � � � � � � ��� �� �� ��� �� Connecting sensor to C/Q ▶ Connect the sensor as shown in the figure. Connecting sensor to DI � � � � �� ������� � � � � �� �� � � � � �� �� �� Connecting sensor to DI ▶ Connect the sensor as shown in the figure. Connect load to C/Q � � � � � � � � ��� �� �� ��� �� Connect load to C/Q ▶ Connect the load as shown in the figure.

23 Manual Communication module UR20-4COM-IO-LINK 2547720000/03/09.2019 WARNUNG Explosion risk! ▶ Before starting any work, make sure that there is not a potentially explosive atmos- phere! WARNUNG! Manipulation of the control unit! During commissioning, the system may be manipulated to such an extent that risk to life and material damage can result. ▶ Make sure that system components can- not start up unintentionally! ATTENTION The product can be destroyed! ▶ Perform an insulation test every time before putting the station into operation (see section 7.6 in the u-remote IP20 manual). ▶ Always observe the complete documentation in the u-remote IP20 manual (document no. 1432780000) and in the u-remote web server manual (document no. 2112220000). 6.1 Requirements Before you start the commissioning work, the following re- quirements must be fulfilled. – The control unit must be in operation. – The u-remote station must be completely assembled and wired. – The fieldbus coupler and UR20-4COM-IO-LINK module must use the current firmware versions. – The control unit and u-remote station must be connected to each other, and a PC/laptop must also be connected. – The power supply must be turned on. 6.2 Device�description�files ▶ Download the current device description files from the Weidmüller website. These include: – GSDML files for PROFINET couplers – GSD files for PROFIBUS couplers – ESI files for EtherCAT couplers – EDS files for Ethernet/IP couplers – EDS files for DeviceNet couplers – EDS files for CANopen couplers – XDD files for POWERLINK couplers If bitmap files for visualising the couplers are also supplied, store them in the same folder as the device description files. You require the current device description files in order to use all the functions of the UR20-4COM-IO-LINK communication module. The naming convention for GSDML files always follows this pattern: GSDML_V2.3-WI-UR20-yyyymmdd.xml. The date in the file name (dd.mm.yyyy) indicates the version of the GSDML file and helps to determine whether you are already using the latest version. The version number of a GSD file can be found from the file. If you open the file with a GSD editor, you can find the ver- sion number in the “Info_Text” entry. If you open the file with a text editor, you can find the version number in the entry comment. The version number of an ESI file can be found from the file. If you open the file with a text editor, you can find the version number in the “FileVersion” attribute of the “Vendor” tag. The version number of an EDS file can be found from the file. Open the file using a text editor. – Ethernet/IP: “Revision” entry in the “File” section – DeviceNet: “Revision” entry in the “File” section – CANopen: “FileVersion” entry in the “FileInfo” section The version number of an XDD file can be found from the file. If you open the file with a text editor, you can find the version number in the “FileVersion” attribute of the “Profile- Body” tag. 6 Commissioning

24 2547720000/03/09.2019 Manual Communication module UR20-4COM-IO-LINK 6.3 Procedure for commissioning Updating the software ▶ Update the firmware of the fieldbus coupler and that of the UR20-4COM-IO-LINK modules to the latest version. Configuring�the�IO-Link�master ▶ Install the current device description files. ▶ Configure the control unit and the network as usual. ▶ Add the required fieldbus coupler and the UR20-4COM- IO-LINK module to your configuration. ▶ Adjust the process data length of the UR20-4COM-IO- LINK module and the fieldbus coupler to your IO-Link device configuration. The procedure for adjusting the process data length depends on which fieldbus coupler and which engineering tool you are using. For commissioning examples, see sections 6.4 to 6.8. Parameterising the IO-Link port The IO-Link ports are parameterised via the parameters of the IO-Link master. A field device is integrated using the suit- able parameterisation of the associated IO-Link port. An over- view of all parameters can be found in section 4.6. ▶ For each IO-Link port, set the “Operating mode” parame- ter such that the setting corresponds with the connected device. ▶ Change the other parameters as required. Configuring�IO-Link�devices�online You can use the u-remote IO-Link configurator to configure the IO-Link system during ongoing operation. ▶ Start the u-remote IO-Link configurator. ▶ Establish a connection between the computer and the u-remote station. ▶ Activate the IO-Link ports to which IO-Link devices are connected. ▶ Assign the correct IODDs to these IO-Link ports. ▶ Parameterise the IO-Link devices. ▶ Write the edited parameters to the IO-Link devices. You can find further information on installation and opera- tion of the u-remote IO-Link configurator in Chapter 7. Loading�the�IO-Link�device�configuration�to�the�u-remote� station You can load an exported IO-Link device configuration to the u-remote station via the u-remote web server. This procedure is suitable when you want to use the same configuration a number of times. ▶ Always observe the complete documentation in the u-remote web server manual (document no. 2112220000). If you access a fieldbus coupler via the u-remote IO-Link Configurator and the u-remote web server simultaneously, this may result in access con- flicts. ▶ Start the u-remote web server. ▶ Open the component view of the IO-Link module by click- ing on the IO-Link module in the station overview. ▶ In the component view, click Load device configura- tion. Loading the IO-Link device configuration to the u-remote station ▶ Select the required configuration file (.json) and click Open. A dialogue box with details for the IO-Link device configura- tion is opened. ▶ Check whether the details for the IO-Link device configu- ration correspond with the actual configuration. ▶ Click Upload. The IO-Link device configuration is written to the module. You can find further information on installation and opera- tion of the u-remote IO-Link configurator in Chapter 7. You will receive an error message if the IO-Link device configuration does not match the connected IO-Link devices.

25 Manual Communication module UR20-4COM-IO-LINK 2547720000/03/09.2019 6.4 Commissioning with the SIMATIC Manager (PROFINET) Installing�the�device�description�files Projects must not be open in the hardware configuration tool while the files are being installed! ▶ Close any open projects before installing the device description files! ▶ In the hardware configuration tool, open Installing Extras / GSD files ▶ Select the directory in which you have stored the device description files. The available files are displayed. Selecting the GSD(-ML) file ▶ Select the files that you would like to install. ▶ Click Install. ▶ When the installation is complete, click Close. ▶ Update the device catalogue via Extras / Update cata- logue. The devices associated with the current device description file are now listed in the device catalogue. Integrating IO-Link master with SIMATIC Manager ▶ Start SIMATIC Manager. ▶ Create a new project or open an existing project. ▶ Configure the controller and the network as usual. ▶ Add the appropriate u-remote fieldbus coupler to the sub- net. ▶ In the hardware configuration tool, click the icon for the fieldbus coupler. The module list is displayed in the lower part of the window. ▶ In the module list, click the slot to which you want to add the IO-Link master. The device description files support various configura- tions for the UR20-4COM-IO-LINK module. The configu- rations differ only in the length of the process data for the IO-Link devices connected, e.g. 16 bytes input data and 16 bytes output data for IO-Link devices for the configuration UR20-4COM-IOL-16BYTE-INOUT. Select module with the appropriate process data length ▶ Determine the required process data length of the IO-Link master, by adding the length of the input data and output data of the IO-Link devices connected. ▶ In the device catalogue, select the UR20-4COM-IO-LINK module with a process data length greater than or equal to the required length. ▶ Double-click the module, or drag it into the module list. The module is displayed in the module list.

26 2547720000/03/09.2019 Manual Communication module UR20-4COM-IO-LINK Adding�IO-Link�master�in�SIMATIC�Manager�(Example:�PROFINET) Parameterising IO-Link port with SIMATIC Manager The IO-Link ports are parameterised using the IO-Link master parameters. An overview of all parameters is presented in section 4.6. ▶ Double-click the module in the module list. The UR20-4COM-IO-LINK Properties window opens. ▶ Select the Parameters tab The list of all parameters is displayed. Editing module parameters ▶ Click the parameter that you would like to change and select the desired setting. ▶ Use this method to edit all of the parameters that you want to change. ▶ Click OK to save the settings. All settings only take effect once they have been loaded into the component. Integrating IO-Link device with SIMATIC Manager An IO-Link device is integrated using the suitable parameteri- zation of the associated IO-Link port. ▶ Double-click the module in the module list. The UR20-4COM-IO-LINK Properties window opens. ▶ Select the Parameters tab. ▶ Set the “Operating mode” parameter of the IO-Link port to the value “IO-Link”. ▶ Set each of the parameters “Process data length input” and “Process data length output” to the value “auto”. ▶ Change the other parameters as required. ▶ Save the setting by clicking OK. All settings only take effect once they have been loaded into the component.

27 Manual Communication module UR20-4COM-IO-LINK 2547720000/03/09.2019 6.5 Commissioning with the TIA portal (PROFINET) Installing�the�device�description�files ▶ In the project view, open: Extras / Manage general station description files (GSD) ▶ Select the directory in which you have stored the device description files. The available files are displayed. Selecting the GSD(-ML) file ▶ Select the files that you would like to install. ▶ Click Install. ▶ When the installation is complete, click Close. The hardware catalogue is updated automatically. The devic- es from the current device description file are now listed in the hardware catalogue. Integrating IO-Link master with the TIA portal ▶ Start the TIA portal. ▶ Create a new project or open an existing project. ▶ Configure the controller and the network as usual. ▶ Add the appropriate u-remote fieldbus coupler to the sub- net. ▶ In the hardware configuration tool, click the icon for the fieldbus coupler. The device overview is displayed. ▶ In the device overview, click the plug-in station to which you want to add the IO-Link master. The device description files support various configura- tions for the UR20-4COM-IO-LINK module. The configu- rations differ only in the length of the process data for the IO-Link devices connected, e.g. 16 bytes input data and 16 bytes output data for IO-Link devices for the configuration UR20-4COM-IOL-16BYTE-INOUT. Select module with the appropriate process data length ▶ Determine the required process data length of the IO-Link master, by adding the length of the input data and output data of the IO-Link devices connected. ▶ In the device catalogue, select the UR20-4COM-IO-LINK module with a process data length greater than or equal to the required length.

28 2547720000/03/09.2019 Manual Communication module UR20-4COM-IO-LINK ▶ Double-click the module, or drag it into the device over- view. The module is displayed in the device overview. Adding�IO-Link�master�with�the�TIA�portal�(example:�PROFINET) Parameterising IO-Link port with the TIA portal The IO-Link ports are parameterised using the IO-Link master parameters. An overview of all parameters is presented in section 4.6. ▶ Select the module in the device overview. ▶ In the inspection window, select the General tab. ▶ Select Component parameters. The list of all parameters is displayed. Editing module parameters ▶ Click the parameter that you would like to change and select the desired setting. ▶ Use this method to edit all of the parameters that you would like to change. All settings only take effect once they have been loaded into the component. Integrating IO-Link device with the TIA portal A IO-Link device is integrated using the suitable parameteri- zation of the associated IO-Link port. ▶ Select the module in the device overview. ▶ In the inspection window, select the General tab. ▶ Select Component parameters. The list of all parameters is displayed. ▶ Set the “Operating mode” parameter of the IO-Link port to the value “IO-Link”. ▶ Set the “Process data length input” parameter to the value “auto (default)”. ▶ Set the “Process data length output” parameter to the value “auto (default)”. ▶ Change the other parameters as required. All settings only take effect once they have been loaded into the component.

29 Manual Communication module UR20-4COM-IO-LINK 2547720000/03/09.2019 6.6 Commissioning with TwinCAT (EtherCAT) Installing�the�device�description�files ▶ Before starting TwinCAT, copy the ESI files to the Twin- CAT installation folder, e.g. C:\TwinCAT\3.1\Config\Io\ EtherCAT. Existing folder structures in the ESI files must remain un- changed when copying. After starting TwinCAT 3, the devices from the device de- scription files are available in the hardware catalogue. Integrating�IO-Link�master�with�TwinCAT 3 ▶ Start TwinCAT 3. ▶ Create a new project or open an existing project. ▶ Establish an online connection to the EtherCAT master. ▶ Switch to Solution Explorer. ▶ Right-click I/O. ▶ Select Scan... and follow the configuration wizard. All the EtherCAT slaves available on the network are added. IO-Link master in Solution Explorer Parameterising IO-Link port with TwinCAT The IO-Link ports are parameterised via the parameters of the IO-Link master. An overview of all parameters can be found in section 4.6. ▶ In the Editor window of the coupler, switch to Startup. The current parameter setting is displayed. You can edit the parameter setting. ▶ Double-click the parameter you want to edit. The Edit dialogue box is opened. Editing module parameters with TwinCAT ▶ Change the value in the Data text field. ▶ Click OK. ▶ Use this method to edit all of the parameters that you would like to change. All settings only take effect once they have been loaded into the component.

30 2547720000/03/09.2019 Manual Communication module UR20-4COM-IO-LINK Integrating IO-Link device with TwinCAT An IO-Link device is integrated using the appropriate parame- terisation of the associated IO-Link port. ▶ Switch to Startup. The current parameter setting is displayed. You can edit the parameter setting. ▶ Double-click the parameter you want to edit. The Edit dialogue box is opened. Editing module parameters with TwinCAT ▶ Set the “Operating mode” parameter of the IO-Link port to the value “IO-Link” (0x03). ▶ Set the “Process data length input” parameter to the value “auto (default)” (0x21). ▶ Set the “Process data length output” parameter to the value “auto (default)” (0x21). ▶ Change the other parameters as required. All settings only take effect once they have been loaded into the component. 6.7 Commissioning with Studio 5000 (Ethernet/IP) Installing�the�device�description�files ▶ Start Studio 5000. ▶ Download and unzip the archive file from the Weidmüller website. ▶ In the Tools menu within the Studio 5000 software, select the EDS Hardware Installation Tool option. ▶ Follow the installation wizard. Integrating IO-Link master with Studio 5000 ▶ Start Studio 5000. ▶ Create a new project or open an existing project. ▶ Configure the control unit and the network as usual. ▶ Establish a connection to the controller (Go Online). If your project does not match the project on the controller, load your project onto the controller (Download) or transfer the project from the controller to Studio 5000 (Upload). The controller must be in programming mode in both cases. All projects downloaded from Studio 5000 to the controller irrevocably overwrite any projects saved on the controller. ▶ Add the u-remote station as usual. The fieldbus coupler and module are added with the stand- ard process data width. Usually, this process data width does not correspond with the existing IO-Link device configura- tion. You can adjust the process data length of the module to your IO-Link device configuration using a sequence of acyclic write operations. The following descriptions are examples of the procedure with RSNetworx for EtherNet/IP. Alternatively, you can implement the write operations with the MSG func- tion component as generic CIP messages. ▶ Switch to RUN mode. ▶ Start RSNetworx for EtherNet/IP. ▶ Scan the network. ▶ Right-click the fieldbus coupler. ▶ In the context menu, click Class Instance Editor. ▶ Read the warning message and confirm by clicking on Yes. The Class Instance Editor is opened.

31 Manual Communication module UR20-4COM-IO-LINK 2547720000/03/09.2019 Change the length of the input data for the module: ▶ Select the service code “Set Single Attribute” (10) ▶ Set the object address parameter as hexadecimal num- bers. – Class: 67 (module parameters) – Instance: slot of the UR20-4COM-IO-LINK module – Attribute: 65 (length of the input data) ▶ In the drop-down list Transmit data size, select Byte. ▶ Determine the required length of the input data of the UR20-4COM-IO-LINK module by adding the length of the input data of the connected IO-Link devices as well as 2 status bytes for the module. ▶ In the text field Data sent to the device, enter the determined value as a hexadecimal number. ▶ Click Execute to trigger the transaction. Changing the length of the input data for the module Change the length of the output data for the module: ▶ Select the service code “Set Single Attribute” (10) ▶ Set the object address parameter as hexadecimal num- bers. – Class: 67 (module parameters) – Instance: slot of the UR20-4COM-IO-LINK module – Attribute: 66 (length of output data) ▶ In the drop-down list Transmit data size, select Byte. ▶ Determine the required length of the output data of the UR20-4COM-IO-LINK module by adding the length of the output data of the connected IO-Link devices as well as 2 control bytes for the module. ▶ In the text field Data sent to the device, enter the determined value as a hexadecimal number. ▶ Click Execute to trigger the transaction. Changing the length of the output data for the module Save the module parameters in the coupler: ▶ Select the service code “Set Single Attribute” (10) ▶ Set the object address parameter as hexadecimal num- bers. – Class: 64 (gateway) – Instance: 1 – Attribute: 6E (save/restore module parameters) ▶ In the drop-down list Transmit data size, select Double (4 byte). ▶ In the text field Data sent to the device, enter “45564153” (“SAVE”, ASCII-coded, Intel format). ▶ Click Execute to trigger the transaction. Saving the module parameters in the coupler

32 2547720000/03/09.2019 Manual Communication module UR20-4COM-IO-LINK Restart the coupler: ▶ Select the service code “Reset” (5). ▶ Deactivate Send the attribute ID. ▶ Set the object address parameter as hexadecimal num- bers. – Class: 1 – Instance: 1 ▶ In the drop-down list Transmit data size, select Byte. ▶ In the text field Data sent to the device, enter “0”. ▶ Click Execute to trigger the transaction. Restarting the coupler ▶ Switch to Studio 5000. ▶ Switch to offline mode. ▶ Open the properties of the fieldbus coupler. ▶ Click the General Change tab. ▶ Set the process data length of the connection in accord- ance with the process data length of the fieldbus coupler. ▶ Click OK. ▶ Download the changes to the controller. Setting the process data length of the coupler Parameterising the IO-Link port with Ethernet/IP First set the process data length of the IO-Link master to the required value. Setting the process data length requires that the coupler is restarted. In doing so, the parameter settings that were not saved in the coupler via the “Save module pa- rameters” function are reset to the factory settings. The IO-Link ports are parameterised via the parameters of the IO-Link master. An overview of all parameters can be found in section 4.6. Use the u-remote web server to param- eterise IO-Link ports. ▶ Start the u-remote web server. ▶ Open the component view of the IO-Link module by click- ing on the IO-Link module in the station overview. ▶ Under parameters, click the channel whose parameters you want to change. The parameters are displayed. For parameters that can be edited, you can enter the chang- es in the respective entry field or choose alternative settings from a drop-down menu. ▶ Enter the required changes. Each change is labelled with a green symbol until it has been applied. All changes are only saved when you click Apply changes. All changes are reset when you click Restore. ▶ When you have entered all changes, click Apply changes. The changes are then transferred to the coupler and the green labels are removed. Alternatively, you can parameterise IO-Link ports using acy- clic write accesses.

33 Manual Communication module UR20-4COM-IO-LINK 2547720000/03/09.2019 Integrating IO-Link device with Ethernet/IP First set the process data length of the IO-Link master to the required value. Setting the process data length requires that the coupler is restarted. In doing so, the parameter settings are reset to the factory settings. An IO-Link device is integrated using the appropriate param- eterisation of the associated IO-Link port. Use the u-remote web server to parameterise IO-Link ports. ▶ Start the u-remote web server. ▶ In the station overview, click the IO-Link module to open the component view of the IO-Link module. ▶ Click Parameter. The parameters are displayed. ▶ Set the “Operating mode” parameter of the IO-Link port to the value “IO-Link”. ▶ Set the “Process data length input” parameter of the IO-Link port to the value “auto (default)”. ▶ Set the “Process data length output” parameter of the IO-Link port to the value “auto (default)”. ▶ Change the other parameters as required. Each change is labelled with a green symbol until it has been applied. All changes are only saved when you click Apply changes. All changes are reset when you click Restore. ▶ Click Apply changes. The changes are then transferred to the coupler and the green labels are removed. Alternatively, you can parameterise IO-Link ports using acy- clic write accesses 6.8 Commissioning with Automation Studio (POWERLINK) Installing�the�device�description�file ▶ Start Automation Studio. ▶ On the menu bar, click Tools/Import Fieldbus Device.... ▶ Select the directory where you have stored the device description files. Selecting XDD files ▶ Select the files that you would like to install. ▶ Click Open. The hardware catalogue is updated automatically. The devic- es from the current device description file are now listed in the hardware catalogue. Integrating IO-Link master with Automation Studio ▶ Start Automation Studio. ▶ Create a new project or open an existing project. ▶ Configure the control unit and the network as usual. ▶ Add the appropriate u-remote fieldbus coupler. ▶ Add the UR20-4COM-IO-LINK module from the hardware catalogue to the u-remote station. ▶ Connect the fieldbus coupler to the controller. The device description files support various configurations for the UR20-4COM-IO-LINK module. The configurations differ in terms of the process data length for the connected IO-Link devices. The process data length you select should only be as long as is required, in order to relieve the fieldbus system.

34 2547720000/03/09.2019 Manual Communication module UR20-4COM-IO-LINK Restarting the coupler ▶ In the Physical View, right-click the module. ▶ Click Configuration in the context menu. The list of all parameters is displayed. ▶ Determine the required process data length of the IO-Link master, by adding the length of the input data and output data of the connected IO-Link devices. ▶ Set the “Process data length input” parameter of the IO-Link master to the required value. ▶ Set the “Process data length input” parameter of the IO-Link master to the required value. All settings only take effect once they have been loaded into the component. Parameterising IO-Link port with Automation Studio The IO-Link ports are parameterised via the parameters of the IO-Link master. An overview of all parameters can be found in section 4.6. ▶ In the Physical View, right-click the module. ▶ In the context menu, click Configuration. The list of all parameters is displayed. Editing module parameters ▶ Click the parameter that you would like to change and amend the setting as required. ▶ Use this method to edit all of the parameters that you would like to change. All settings only take effect once they have been loaded into the component. Integrating IO-Link device with Automation Studio An IO-Link device is integrated using the appropriate parame- terisation of the associated IO-Link port. ▶ In the Physical View, right-click the module. ▶ In the context menu, click Configuration. The list of all parameters is displayed. ▶ Set the “Operating mode” parameter of the IO-Link port to the value “IO-Link”. ▶ Set the “Process data length input” parameter of the IO-Link port to the value “auto (default)”. ▶ Set the “Process data length output” parameter of the IO-Link port to the value “auto (default)”. ▶ Change the other parameters as required. All settings only take effect once they have been loaded into the component.

35 Manual Communication module UR20-4COM-IO-LINK 2547720000/03/09.2019 6.9 Reading and writing data objects on IO-Link devices Protocol for acyclic accesses If you want to read and write IO-Link data objects only during commissioning, we recommend us- ing the IO-Link Configurator (see Chapter 7). In order to access data objects for a field device (FD), e.g.those of a IO-Link device, you must create a client appli- cation (client app) for the fieldbus master (FB_M). This client application communicates with a server on the u-remote station (FBC/IO_M). The server communicates with the field device application (FD app) on the field device. An acyclic access to an IO-Link device always begins with a write access by the client application to the server (acy- clic-write.req). The data written determine which request is sent by the server to the IO-Link device application (write.req oder read.req). The client application then performs a sequence of read ac- cesses (acyclic-read.req). Provided that the IO-Link device ap- plication has not yet processed the request, the server feeds back that the IO-Link device application is busy (acyclic-read. res with status “Busy”). If the server has received a response from the IO-Link device application (write.conf or read.conf), the server then forwards the response to the client applica- tion (acyclic-read.res with status “Done” or “Error”). For integrating the IO-Link with PROFIBUS and PROFINET, also refer to the integration guidelines of the PROFIBUS user organisation. – IO-Link Integration Part 1: Technical Specifica- tion for PROFIBUS and PROFINET – IO-Link Integration – Edition 2: Guideline for PROFINET Client app Server FB_M FBC/IO-M FD FD app data data write_data.res / with data acyclic-read.req acyclic-read.res / without data write.conf / without data / “resource busy“ acyclic-read.req acyclic-read.res / without data / Resource busy / “resource busy“ acyclic-read.req acyclic-read.res / without data / Resource busy acyclic-write.req acyclic-write.res / without data / with data write.req / with data write_data.req Writing a data object on an IO-Link device Client app Server FB_M FBC/IO-M FD FD app data data read_data.res / with data acyclic-read.req acyclic-read.res / without data read.conf / with data / “resource busy“ acyclic-read.req acyclic-read.res / without data / Resource busy / “resource busy“ acyclic-read.req acyclic-read.res / without data / Resource busy acyclic-write.req acyclic-write.res / without data / with data read.req / without data read_data.req Reading a data object on an IO-Link device

36 2547720000/03/09.2019 Manual Communication module UR20-4COM-IO-LINK Addresses for acyclic accesses Acyclic�write�access:�Addressing�the�requests�(.req) Protocol Address PROFIBUS 227 or 255 PROFINET 227 (0x00E3) CANopen 0x2200:0 MODBUS-TCP 0x2C00 - 2C7F EtherCAT 0x4020:1 Ethernet/IP Class 0x64, Instance 1, Attribute 0x78 DeviceNet Class 0x64, Instance 1, Attribute 0x78 POWERLINK 0x2200:0 Acyclic�read�access:�Addressing�the�responses�(.res) Protocol Address PROFIBUS 227 or 255 PROFINET 227 (0x00E3) CANopen 0x2201:0 MODBUS-TCP 0x2D00 - 2D7F EtherCAT 0x4020:2 Ethernet/IP Class 0x64, Instance 1, Attribute 0x78 DeviceNet Class 0x64, Instance 1, Attribute 0x78 POWERLINK 0x2201:0 IO-Link Call IO-Link data objects and IO-Link port functions are accessed via IO-Link Call. With PROFIBUS and PROFINET, you can use the function block “IO_LINK_CALL” or “IO_LINK_DE- VICE” (see section 6.10) IO-Link�Call:�Request Data object Length [bytes] Description Example Length1) 1 Total length in bytes 0x0A Slot1) 1 Slot IO-Link master 0x01 Ext. Function Number2) 1 0x08 (fixed) 0x08 Port 1 Number of the IO-Link port (0x01 ...0x04) 0x02 FI index 2 65098 (0xFE4A) 0xFE4A Control 1 Write (0x02), Read (0x03) 0x02 IOL index 2 IO-Link device index (0x0000 ... 0xFFFF) 0x0050 IOL subindex 1 IO-Link device data or port function 0x00 IOL data object 0 ... 232 Data for write access 0x42 1) Not for PROFIBUS and PROFINET 2) Not for PROFIBUS and PROFINET IO-Link�Call:�Response Data object Length [bytes] Description Example Length1) 1 Total length in bytes 0x0A Slot1) 1 Slot IO-Link master 0x01 Ext. Function Number2) 1 0x08 (fixed) 0x08 Port 1 Number of the IO-Link port (0x01 ...0x04) 0x02 FI index 2 65098 (0xFE4A) 0xFE4A Status 1 PROFIBUS/PROFINET: Done (0x00), IDLE (0x01), Error (0x80) Other fieldbus systems: Error (0x00), DONE (0x01), Busy (0x02) 0x01 Control response1) 1 Write (0x02), Read (0x03) 0x02 IOL index 2 IO-Link device index (0x0000 ... 0xFFFF) 0x0050 IOL subindex 1 IO-Link device data or port function 0x00 IOL data object 0 ... 232 Read access: Data Write access: – Error incident: error code – 1) Not for PROFIBUS and PROFINET 2) Not for PROFIBUS and PROFINET

37 Manual Communication module UR20-4COM-IO-LINK 2547720000/03/09.2019 Reading out device information You can read out device information of connected IO-Link devices. Read�out�device�information:�Request Data object Length [bytes] Description Example Length1) 1 Total length in bytes (0x05) 0x05 Slot1) 1 Slot IO-Link master 0x01 Ext. Function Number2) 1 0x08 (fixed) 0x08 Port 1 0x00 0x00 FI index 2 Port 1: 65016 (0xFDF8) Port 2: 65017 (0xFDF9) Port 3: 65018 (0xFDFA) Port 4: 65019 (0xFDFB) 0xFDFA 1) Not for PROFIBUS and PROFINET 2) Not for PROFIBUS and PROFINET Read�out�device�information:�Response Data object Length [bytes] Description Example Length1) 1 Total length in bytes (0x05) 0x0D Slot1) 1 Slot IO-Link master 0x01 Ext. Function Number2) 1 0x08 (fixed) 0x08 Port 1 0x00 0x00 FI index 2 Port 1: 65016 (0xFDF8) Port 2: 65017 (0xFDF9) Port 3: 65018 (0xFDFA) Port 4: 65019 (0xFDFB) 0xFDFA Status 1 PROFIBUS/PROFINET: Done (0x00), IDLE (0x01), Error (0x80) Other fieldbus systems: Error (0x00), DONE (0x01), Busy (0x02) 0x01 Vendor ID 2 Identification number of the IO-Link device manufacturer 0 x 0134 Device ID 3 Manufacturer-related identification number of the IO-Link device 0x000050 Function ID 2 Reserved (0x0000) 0 x 0000 1) Not for PROFIBUS and PROFINET 2) Not for PROFIBUS and PROFINET Reading out process data mapping You can read out the process data mapping of an IO-Link master (details in bytes). Read�out�process�data�mapping:�Request Data object Length [bytes] Description Example Length1) 1 Total length in bytes (0x05) 0x05 Slot1) 1 Slot IO-Link master 0x01 Ext. Function Number2) 1 0x08 (fixed) 0x08 Port 1 0x00 0x00 FI index 2 65100 (0xF34C) 0xF34C 1) Not for PROFIBUS and PROFINET 2) Not for PROFIBUS and PROFINET Read�out�process�data�mapping:�Response Data object Length [bytes] Description Example Length1) 1 Total length in bytes (0x16) 0 x 16 Slot1) 1 Slot IO-Link master 0x01 Ext. Function Number2) 1 0x08 (fixed) 0x08 Port 1 0x00 0x00 FI index 65100 (0xF34C) 0xF34C Status 1 PROFIBUS/PROFINET: Done (0x00), IDLE (0x01), Error (0x80) Other fieldbus systems: Error (0x00), DONE (0x01), Busy (0x02) 0x01 Port 1: Len IN 1 Port 1: Length of process input data 0x02 Port 1: Pos IN 1 Port 1: Position of process input data 0x02 Port 1: Len OUT 1 Port 1: Length of process output data 0x00 Port 1: Pos OUT 1 Port 1: Position process output data 0x02 Port 2: Len IN 1 Port 2: Length of process input data 0x04 Port 2: Pos IN 1 Port 2: Position of process input data 0x04 Port 2: Len OUT 1 Port 2: Length of process output data 0x02 Port 2: Pos OUT 1 Port 2: Position process output data 0x02 Port 3: Len IN 1 Port 3: Length of process input data 0x02 Port 3: Pos IN 1 Port 3: Position of process input data 0x08 Port 3: Len OUT 1 Port 3: Length of process output data 0x05 Port 3: Pos OUT 1 Port 3: Position process output data 0x04 Port 4: Len IN 1 Port 4: Length of process input data 0 x 03 Port 4: Pos IN 1 Port 4: Position of process input data 0x0A Port 4: Len OUT 1 Port 4: Length of process output data 0 x 03 Port 4: Pos OUT 1 Port 4: Position process output data 0 x 09 1) Not for PROFIBUS and PROFINET 2) Not for PROFIBUS and PROFINET

38 2547720000/03/09.2019 Manual Communication module UR20-4COM-IO-LINK Reading out the event queue You can read out events from the event queue. Read�out�event�queue:�Request Data object Length [bytes] Description Example Length1) 1 Total length in bytes (0x05) 0x05 Slot1) 1 Slot coupler (0x00) 0x00 Ext. Function Number2) 1 0x08 (fixed) 0x08 Port 1 0x00 0x00 FI index 2 65101 (0xF34D) 0xF34D 1) Not for PROFIBUS and PROFINET 2) Not for PROFIBUS and PROFINET Read�out�event�queue:�Response Data object Length [bytes] Description Example Length1) 1 Total length in bytes (0x0F) 0x0F Slot1) 1 Slot coupler (0x00) 0x00 Ext. Function Number2) 1 0x08 (fixed) 0x08 Port 1 0x00 0x00 FI index 2 65101 (0xF34D) 0xF34D Status 1 PROFIBUS/PROFINET: Done (0x00), IDLE (0x01), Error (0x80) Other fieldbus systems: Error (0x00), DONE (0x01), Busy (0x02) 0x01 Event at slot 1 Coupler (0x00) I/O module (0x01 ... 0x40) 0x01 Event at port 1 Number of the IO-Link port (0x01 ...0x04) 0x02 Event status 1 OK (0x00), error with event communica- tion (0x01), event queue empty (0x02) 0x00 Instance 1 Source instance: Physical layer (0x01), data link layer (0x02), application layer (0x03), application (0x04) 0x04 Mode 1 Event single shot (0x01), Event disap- pears (0x02), Event appears (0x03) 0x01 Type 1 Notification (0x01), Warning (0x02), Error (0x03) 0x02 Source 1 Source device: IO-Link device (0x00), IO-Link master (0x01) 0x00 Event code 2 Event code in accordance with IO-Link specification 0x5012 1) Not for PROFIBUS and PROFINET 2) Not for PROFIBUS and PROFINET 6.10 “IO_LINK_CALL” function block The “IO_LINK_ CALL” function block allows acyclic communi- cation with an IO-Link device: device parameters are written and parameters, measured values and diagnostic data are read. ������������ ��� �� ��� ����� ���� �������� ��������� ������������ ��� ��������������� ���������� ���� ����� ������ ���������� ��� ���� ����� ��� ���� ��� ��� ��� ��� ��� �������������� ���� ���� ���� ����� ���� ����� “IO_LINK_ CALL” function block IO_LINK_CALL:�input�parameters Parameter Data type Description REQ BOOL Rising edge starts data transmission ID DWORD HW_ID Address of the IO-Link master. S7-300/400: log. start address S7-1200/1500: Hardware ID CAP INT CAP-ID PROFIBUS: 227 oder 255 PROFINET: 227 RD_WR BOOL 0: read access 1: write access PORT INT Number of the IO-Link port (1 ... 4) FI_INDEX INT 65098 IOL_INDEX INT Parameter index IOL_SUBINDEX INT Parameter subindex LEN INT Length of data to be written in bytes Read access: not required Write access: 1 ... 232 RECORD_IOL_DATA ARRAY OF BYTES Read access: Target range for data Write access: Source range for data

39 Manual Communication module UR20-4COM-IO-LINK 2547720000/03/09.2019 IO_LINK_CALL:�output�parameters Parameter Data type Description DONE_VALID BOOL Validity of data 0: Data invalid 1: Data valid BUSY BOOL Read access / write access is executed ERROR BOOL 0: no error 1: error and cancellation STATUS DWORD Communication error message IOL_STATUS DWORD IO-Link error message RD_LEN DWORD Length of the data read Processing of the function block lasts several PLC cycles. The access, use of IO-Link port functions and the remaining backup and recovery of device data must be controlled by the user program. SIEMENS offers the STEP7 IO-Link library for SIMATIC Man- ager and the TIA Portal. In the more recent versions of the IO-Link library, “IO_LINK_CALL” has been replaced by the “IO_LINK_DEVICE” block. Further information is available in the SIEMENS document “Acyclic reading and writing with the IO-Link library”. You can download the SIEMENS IO-Link library from the SIEMENS support website. Reading and writing with “IO_LINK_DEVICE” in STEP7 You can read and write IO-Link device parameters using the “IO_LINK_DEVICE” function block. ▶ Add the “IO_LINK_DEVICE” function block to the OB1 of your user program. ▶ Create a new data block of type ARRAY [0 ... 231] of BYTE. This data block is the target range for data read and the source range for data to be written. ▶ Generate a new variable table for the input parameters and output parameters of the function block. Variable table for “IO_LINK_DEVICE” (TIA portal) ▶ Assign the variables to the inputs and outputs of the function block. You can enter the parameters ID and CAP directly on the function block. “IO_LINK_DEVICE” function block (TIA portal) ▶ Create a watch and force table with the input parameters and output parameters of the function block. ▶ Force the variables for the input parameters to the required values. In the case of S7-300/400 CPUs, use the logical start address of the module inputs as ID. In the case of S7-1200/1500 CPUs, use the hard- ware address of the module as ID.

40 2547720000/03/09.2019 Manual Communication module UR20-4COM-IO-LINK For PORT, use the number of the IO-Link port, not the number of the channel. ▶ Generate a rising edge at REQ to start the data transmis- sion. Processing of the function block takes several PLC cycles. During processing, the BUSY output is on 1. After successful processing, the BUSY output switches to 0. The DONE_VALID output switches to 1. During read access, the data read is displayed in the data block. 6.11 I&M functions Reading and writing can be realised with the functional blocks RDREC (SFB52) and WRREC (SFB53) in STEP 7. I&M�0:�Basic Protokoll CAP ID FI index PROFIBUS 227 or 255 65000 PROFINET 45040 (0xAFF0) – Data object Length [bytes] Access Default / Description MANUFACTURER_ ID 2 Read 0x0134 (Weidmüller) ORDER_ID 20 Read Order number of module SERIAL_NUMBER 16 Read Defined in production process HARDWARE_REVISION 2 Read Hardware revision of device SOFTWARE_REVISION 4 Read Software revision of device REVISION_COUNTER 2 Read Incremented for every static stored parameter change on IO-Link-Master (e.g. Device Name or IP-Address) PROFILE_ID 2 Read 0x4E00 (IO-Link-Master) PROFILE_SPECIF- IC_TYPE 2 Read 0x0000 IM_VERSION 2 Read 0x0101 (I&M Version 1.1) IM_SUPPORTED 2 Read 0x0001 (Profile specific) I&M�99:�IOL-M�directory Protocol CAP ID FI index PROFIBUS 227 or 255 65099 PROFINET 45155 (0xB063) – Data object Length [bytes] Access Default / Description Version 1 Read 0x09 (IO-Link version 1.1) Profile_Version 1 Read 0x01 (IO-Link profile version 1.0) Feature_Support 4 Read 0x00000000 (supported features) Num_of_Ports 1 Read 0x04 (number of IO-Link ports) REF_Port_Config 1 Read 0xDC (reference Port configuration) REF_IO_Mapping 1 Read 0xDE (reference Get IO mapping) REF_iPar_directory 1 Read 0xDF (reference iPar directory) REF_IOL_M 1 Read 0xDD (reference IOL-M parameter) Number_of_cap 1 Read 0x01 (number of Client Access Points) Index_cap1 1 Read 0xE3 (IOL_CALL: Client Access Point 1) Send Upload Request Protocol CAP ID FI index PROFIBUS 227 or 255 65101 PROFINET 223 (0xDF) – Data object Length [bytes] Access Default / Description Status 1 Read False (0x00), True (0x01)

41 Manual Communication module UR20-4COM-IO-LINK 2547720000/03/09.2019 7.1 u-remote�IO-Link�configurator You can use the u-remote IO-Link configurator to configure the IO-Link system. You can carry out the following functions for test purposes, during commissioning or service work: – Create and export IO-Link device configurations. – Parameterise IO-Link devices during ongoing operation. – Read out identification data, process data and diagnoses of IO-Link devices. You can download the software from the Weidmüller web- site. 7.2 Installing�the�u-remote�IO-Link�configurator Installing the installation version The installation version links project files (“.ucc”) with the u-remote IO-Link configurator. You can open project files by double-clicking on the file. ▶ Download the u-remote IO-Link configurator from the Weidmüller website. ▶ Navigate to the download folder. ▶ Double-click IOLink-Device-Configurator-Set- up_1.2.0.exe. ▶ Follow the installation wizard. Once successfully installed, you can start the IO-Link Config- urator. The starting page is displayed. Installing the portable version You can use the portable version without install- ing it. You can only open project files from the u-remote IO-Link configurator. ▶ Download the u-remote IO-Link configurator from the Weidmüller website. ▶ Navigate to the download folder. ▶ Double-click IOLink-Device-Configurator-Porta- ble_1.2.0.exe. The starting page is displayed. The licence conditions are displayed when the program is started for the first time. ▶ Read and confirm the licence conditions. 7.3 Operating�the�u-remote�IO-Link�configurator Displaying the starting page The starting page is displayed each time you start the u-re- mote IO-Link Configurator. On the starting page you can con- nect to the fieldbus coupler, create a new project or open an existing project. Calling up the starting page ▶ In the menu bar, click the house icon. IO-Link port overview 1 2 3 6 7 8 9 10 4 5 11 12 13 14 IO-Link port overview (online mode) 1 Displaying the starting page 2 Selecting IO-Link master in the device tree 3 Opening the IODDfinder in the standard browser 4 Displaying diagnoses 5 Displaying IO-Link device parameters 6 Deleting IODD from IO-Link port 7 Adding IODD to IO-Link port 8 Changing the language 9 Separating the connection to the fieldbus coupler 10 Displaying the process data 11 Detecting the connected IO-Link device 12 Deactivating the IO-Link port 13 Activating an IO-Link port 14 Displaying the context menu 7 Planning�IO-Link�device�configurations

42 2547720000/03/09.2019 Manual Communication module UR20-4COM-IO-LINK 1 2 3 4 5 6 7 8 9 IO-Link port overview (offline mode) 1 Displaying the starting page 2 Opening the IODDfinder in the standard browser 3 Adding IODD to IO-Link port 4 Parameterising the IO-Link device 5 Deleting IODD from IO-Link port 6 Changing the language 7 Connecting to the fieldbus coupler 8 Reading out the process data length of the configuration 9 Displaying the context menu IO-Link device detailed view 1 2 3 4 5 6 7 12 8 9 11 10 IO-Link device detailed view 1 Displaying the starting page 2 Switching to section 3 Displaying details (mouse-over) 4 Editing the parameters 5 Changing the language 6 Connecting to the fieldbus coupler/separate the connection to the fieldbus coupler 7 Reading all the parameters in the section (only in online mode) 8 Writing all the changed parameters in the section (only in online mode) 9 Reading individual parameters (only in online mode) 10 Reading current parameter value (only in online mode) 11 Writing individual parameters (only in online mode) 12 Displaying the context menu Displaying the context menu What functions are displayed in the context menu depends on the current program context. The functions relate to the current displayed view in the program. Displaying the context menu ▶ Click ☰ to display the context menu.

43 Manual Communication module UR20-4COM-IO-LINK 2547720000/03/09.2019 Creating a new project A project incorporates the configuration of an IO-Link master. ▶ Navigate to the IO-Link port overview. ▶ Open the context menu. ▶ Click Create new. ▶ If you wish to discard the existing project, click OK. A new project is created. Saving a project A project incorporates the configuration of an IO-Link master. ▶ Open the context menu. ▶ Click Save as. ▶ Select a storage location and a file name and click Save. The project is saved with the file ending “ucc”. After you have saved a project for the first time, you can save the changes by clicking on Save. Opening a project ▶ Navigate to the IO-Link port overview. ▶ Open the context menu. ▶ Click Open. ▶ Select the required project (.ucc) and click Open. ▶ If you wish to discard the existing project, click OK. The project is opened. Changing the language You can change the language of the user interface. ▶ In the menu bar, click Language. ▶ Select the required language. The language is changed immediately. Some of the texts from the IODDs of the IO-Link device manufacturer, such as parameter names, may not have been translated. Opening�the�IODDfinder�in�the�standard�browser Your computer must be connected to the Internet. To add an IO-Link device to a configuration, you will need the relevant IODD from the manufacturer. You can search for and download IODDs using the IODDfinder. ▶ Navigate to the IO-Link port overview. ▶ Click the link to the IODDfinder. Link to the IODDfinder The IODDfinder is opened in your standard browser. ▶ Search for the required IODDs and load the files onto your computer. Exporting�the�IO-Link�device�configuration You can export a configuration file from a configuration pro- ject, in order to then load it to the u-remote station. ▶ Navigate to the IO-Link port overview. ▶ Open the context menu. ▶ Click Export configuration. ▶ Select a storage location and a file name and click Save. The configuration is exported as a file with the file ending “.json”. Configurations that contain a parameter error cannot be exported. For some IO-Link devices, you need to enter val- ues for all subindexes in order to export the con- figuration. If you do not enter a required subindex, an error message is displayed. An exported configuration only contains the IO- Link device parameters that you have activated. Therefore, only the activated parameters are over- written when you load the configuration to the u-remote station.

44 2547720000/03/09.2019 Manual Communication module UR20-4COM-IO-LINK 7.4 Editing�IO-Link�device�configurations Assigning the IO-Link device to an IO-Link port Adding an IODD ▶ Navigate to the IO-Link port overview. ▶ For the empty IO-Link port, click Select IODD, in order to add the IODD. ▶ Select the IODD of the IO-Link device (.zip, .xml). ▶ Click Open. Some IODDs describe several device types. In this case, a dialogue window is displayed containing the available device types. ▶ Select the required device type from the list. ▶ Click OK. Changing the device type Some IODDs describe several device types. You can change the device type. Changing the device type ▶ Navigate to the IO-Link port overview. ▶ For the IO-Link port for which you want to change the device type, click Change type (double arrow icon). A dialogue window is displayed containing the available de- vice types. ▶ Select the required device type from the list. ▶ Click OK. Removing the IO-Link device assignment Deleting the IO-Link device ▶ Navigate to the IO-Link port overview. ▶ For the IO-Link port for which you want to remove the assignment, click Remove (bin icon). The assigment of the IO-Link device to this IO-Link port is removed. Editing the IO-Link device parameters Parameterising the IO-Link device ▶ Navigate to the IO-Link port overview. ▶ For the IO-Link device whose data you want to edit, click Edit (cog icon). The detailed view of the IO-Link device is opened. The parameters of an IO-Link device are defined by its manufacturer. ▶ Observe the manufacturer's documentation. Determining the process data length You can determine the process data length that is required for the IO-Link device configuration. Determining the process data length ▶ Navigate to the IO-Link port overview. ▶ Read the process data length of the current configuration. – PD IN: Length of the input data in bytes – PD OUT: Length of the output data in bytes

45 Manual Communication module UR20-4COM-IO-LINK 2547720000/03/09.2019 Finding and rectifying parameter errors Faulty parameterised IO-Link devices are indicated by a red frame around the IO-Link port concerned. Faulty parameterised IO-Link device ▶ Open the detailed view of the IO-Link device. Jumping to the faulty parameter entry ▶ Click Scroll to error in order to jump to the next faulty parameter entry. The faulty entry is indicated by a red frame. A note regarding error diagnosis is displayed. Faulty parameter entry ▶ Correct the faulty entry. ▶ Repeat the procedure until all errors have been rectified. 7.5 Editing�IO-Link�device�configurations�online WARNING! Manipulation of the control unit! During commissioning, the system may be manipulated to such an extent that this can result in risks to life and material damage. ▶ Make sure that system components can- not start up unintentionally! Connecting�to�the�fieldbus�coupler The u-remote station must be completely assembled and supplied with voltage. The computer must be connected to the u-remote station via USB or Ethernet. If you access a fieldbus coupler via the u-remote IO-Link configurator and the u-remote web server simultaneously, this may result in ac- cess conflicts. ▶ Click Connect on the starting page. Alternatively, you can click Connect in the menu bar. ▶ Enter the IP address of the fieldbus coupler. ▶ Click OK. ▶ You may be requested to enter your user name and pass- word. You need the same user name and the same password that you use when logging in for the u-remote web server of this fieldbus coupler. The following login data applies on delivery: user name: admin password: Detmold ▶ Enter the user name and password. The online mode of the IO-Link Configurator is started. The fieldbus coupler with connected UR20-4COM-IO-LINK mod- ules is displayed in the device tree. ▶ Click in the device tree on the IO-Link master whose configuration you want to edit. The IO-Link port overview of the IO-Link master is displayed.

46 2547720000/03/09.2019 Manual Communication module UR20-4COM-IO-LINK Activating an IO-Link port You must be connected to the fieldbus coupler. Activating an IO-Link port ▶ In the device tree, switch to the required IO-Link master. ▶ For the IO-Link port that you want to activate, click Acti- vate (play icon). The “Operating mode” parameter of the IO-Link port con- cerned is set to the value “IO-Link”. The supply voltage of the IO-Link port is switched on. The connected IO-Link device sends and receives process data. Deactivating an IO-Link port You must be connected to the fieldbus coupler. Deactivating an IO-Link port ▶ In the device tree, switch to the required IO-Link master. ▶ For the IO-Link port that you want to deactivate, click Deactivate (stop icon). The “Operating mode” parameter of the IO-Link port con- cerned is set to the value “Deactivated”. The supply voltage of the IO-Link port is switched off. Identifying a connected IO-Link device The IO-Link port to which the IO-Link device is connected must be activated. Identifying an IO-Link device The configurator can determine the identification data of a connected IO-Link device. You can use the identification data to find the corresponding IODD or to check whether you have assigned the correct IO-Link device to the IO-Link port. ▶ In the device tree, switch to the required IO-Link master. ▶ For the IO-Link port to which the IO-Link device is con- nected, click Identify (magnifying class icon). The Configurator calls up the identification data of the IO-Link device and illustrates it in the IO-Link port overview. If you have already assigned an IO-Link device to this IO-Link port, the Configurator compares the identification data of the IODD with the identification data of the connect- ed IO-Link device. Matches are highlighted in green. Devia- tions are highlighted in red. Downloading IODDs for a connected IO-Link device The connected IO-Link device must be identified by the IO- Link Configurator. Your computer must be connected to the Internet. Downloading IODDs ▶ In the device tree, switch to the required IO-Link master. ▶ For the empty IO-Link port, click Download IODD to which you want to add the IO-Link device. The IODDfinder is opened in your standard browser. ▶ Search for the required IODDs and load the files onto your computer. Reading out IO-Link device parameters The IO-Link device must be assigned to the IO-Link port. The connected IO-Link device must be identified by the IO-Link Configurator. The IODD must match the connected IO-Link device. Depending on the number of parameters to be read and the capacity utilisation of the coupler, it may take a while until all data is read. ▶ In the device tree, switch to the required IO-Link master. ▶ For the IO-Link device whose data you want to edit, click Edit (cog icon). The detailed view of the IO-Link device is opened. Updating the parameters If you want to update an individual parameter: ▶ Click the update icon next to the entry.

47 Manual Communication module UR20-4COM-IO-LINK 2547720000/03/09.2019 If you want to update all parameters in a section: ▶ Click the update icon next to the section heading. If you want to update all parameters of an IO-Link device: ▶ Open the context menu. ▶ Click Read all parameters. Writing IO-Link device parameters An IO-Link device must be assigned to the IO-Link port. The connected IO-Link device must be identified by the IO-Link Configurator. The IODD must match the connected IO-Link device. Depending on the number of parameters to be written and the capacity utilisation of the coupler, it may take a while un- til all data is written. ▶ In the device tree, switch to the required IO-Link master. ▶ For the IO-Link device whose data you want to edit, click Edit (cog icon). The detailed view of the IO-Link device is opened. Writing parameters If you want to write an individual parameter: ▶ Edit the parameter. ▶ Click the apply icon next to the entry. If you want to update all edited parameters in a section: ▶ Edit the parameters in this section. ▶ Click the apply icon next to the section heading. If you want to write all edited parameters of an IO-Link device: ▶ Edit the parameters of the IO-Link device. ▶ Open the context menu in the detailed view of this IO-Link device. ▶ Click Apply configuration. If you want to write all edited parameters of all IO-Link device to one IO-Link master: ▶ Edit the parameters of the IO-Link devices. ▶ Navigate to the IO-Link port overview of the IO-Link master. ▶ Open the context menu in the IO-Link port overview of the IO-Link master. ▶ Click Apply configuration. Displaying process data You must be connected to the fieldbus coupler. ▶ In the device tree, switch to the required IO-Link master. ▶ In the IO-Link port overview, click Show process data. A dialogue box opens. In the Mapping Information section, the process data mapping for the individual IO-Link ports is displayed in pro- cess data tables. In the IN section, the entire process input data telegram including current values is mapped in bytes. In the OUT section, the entire process output data telegram including current values is mapped in bytes. The values are illustrated in hexadecimal format. ▶ Click Ⅱ to pause the process data update. ▶ Click ▶ to continue the process data update. ▶ Click Close to close the dialogue box. Displaying diagnoses You must be connected to the fieldbus coupler. ▶ In the device tree, switch to the required IO-Link master. ▶ In the IO-Link port overview, click Diagnoses. A dialogue box opens. The available diagnoses are displayed in a table. ▶ Click the bin icon to delete a diagnosis. ▶ Click the bin icon in the header to delete all diagnoses.

49 Manual Communication module UR20-4COM-IO-LINK 2547720000/03/09.2019 8.1 Process data mapping ������������������������������� ��������������������������� ������ ���������������������������������� ������������������������������� ��������������������������� ������ ���������������������������������� ������������ ������� ������������ ������ ������������������������������� ��������������������������� ������ ���������������������������������� ������������������������������� ��������������������������� ������ ���������������������������������� ��� ��� ��� ��� ��� ��� ��� ��� ��� ��� ���� ���� ���� ��� ��� ��� ��� ��� ��� ��� ��� ��� ��� ���� ���� ���� ���� ���� ���� ���� ���� ���� ���� ���� ���� ���� ������������� ������ �������� ������������� ��������������� ��������� Example:�Process�data�mapping�(Configuration:�UR20-4COM-IOL-16BYTE-INOUT) The process data length of the UR20-4COM-IO-LINK module is adjustable and can be adjusted to the respective IO-Link device configuration. The procedure for adjusting the pro- cess data length depends on which fieldbus coupler and which engineering tool you are using (see Chapter 6). The first two bytes of the input data and output data respec- tively contain the process data of the module. This is fol- lowed by the process data of the IO-Link device connected. Mapping of the process data for the individual IO-Link de- vices to the process data of the module is defined with the „Process data length input“ and „Process data length output“ parameters of the respective IO-Link port. You can read out the mapping of the process data (see section 6.9). 8 Process data

50 2547720000/03/09.2019 Manual Communication module UR20-4COM-IO-LINK 8.2 Process input data Process data inputs UR20-4COM-IO-LINK Byte Bit Description IB0 IX0.0 DI 1 IX0.1 DI 2 IX0.2 DI 3 IX0.3 DI 4 IX0.4 C/Q 1 IX0.5 C/Q 2 IX0.6 C/Q 3 IX0.7 C/Q 4 IB1 IX1.0 Process data IN valid IO-Link-Port 1 IX1.1 Process data IN valid IO-Link-Port 2 IX1.2 Process data IN valid IO-Link-Port 3 IX1.3 Process data IN valid IO-Link-Port 4 IX1.4 Error IO-Link-Port 1 IX1.5 Error IO-Link-Port 2 IX1.6 Error IO-Link-Port 3 IX1.7 Error IO-Link-Port 4 IB2 ... Process data of the IO-Link device1) 1) The process data length of the IO-Link devices is adjustable. The mapping of the IO-Link devices depends on the length of their process data and the parameter settings. – DI X: Status DI on channel X. – C/Q X: Status C/Q on channel X. – Process data IN valid channel X: Process input data of the IO-Link devices at IO-Link port X valid. – Error channel X: Error on channel X. – Process input data of the IO-Link devices: see sec- tion 8.1. 8.3 Process output data Process data outputs UR20-4COM-IO-LINK Byte Bit Description OB0 OX0.0 DO 1 OX0.1 DO 2 OX0.2 DO 3 OX0.3 DO 4 OX0.4 reserved OX0.5 reserved OX0.6 reserved OX0.7 reserved OB1 OX1.0 Process data OUT valid IO-Link-Port 1 OX1.1 Process data OUT valid IO-Link-Port 2 OX1.2 Process data OUT valid IO-Link-Port 3 OX1.3 Process data OUT valid IO-Link-Port 4 OX1.4 reserved OX1.5 reserved OX1.6 reserved OX1.7 reserved OB2 ... Process data of the IO-Link device1) 1) The process data length of the IO-Link devices is adjustable. The mapping of the IO-Link devices depends on the length of their process data and the parameter settings. – DO X: Control C/Q on channel X in DI operation mode. – Process data OUT valid channel X: Process output data of the IO-Link devices on channel X valid. – Process output data of the IO-Link devices: see sec- tion  8.1

51 Manual Communication module UR20-4COM-IO-LINK 2547720000/03/09.2019 8.4 Fieldbus-dependent process data widths The following tables show which process data lengths are available for the individual couplers, and the relevant field- bus-dependent data widths. UR20-FBC-PB-DP Process data for IO-Link devices Fieldbus dependent data widths1) Input Output Input Output Byte Byte Byte Byte 4 4 6 6 8 8 10 10 16 16 18 18 32 32 34 34 16 8 18 10 32 16 34 18 32 8 34 10 1) incl. 2 Byte module process data UR20-FBC-PN-IRT Process data for IO-Link devices Fieldbus dependent data widths1) Input Output Input Output Byte Byte Byte Byte 4 4 7 7 8 8 11 11 16 16 19 19 32 32 35 35 64 64 67 67 128 128 131 131 16 8 19 11 32 16 35 19 32 8 35 11 64 8 67 11 64 16 67 19 64 32 67 35 128 8 131 11 128 16 131 19 128 32 131 35 128 64 131 67 1) incl. 2 Byte module process data

52 2547720000/03/09.2019 Manual Communication module UR20-4COM-IO-LINK UR20-FBC-EC With EtherCAT, configurable data widths are not supported. Process data for IO-Link devices Fieldbus dependent data widths1) Input Output Input Output Byte Byte Byte Byte 16 16 19 18 1) incl. 2 Byte module process data UR20-FBC-MOD-TCP, UR20-FBC-MOD-TCP-V2 You can select the length of the process input data and the length of the process output data independently of each other. Process data for IO-Link devices Fieldbus dependent data widths1) Input Output Input Output Byte Byte Byte Byte 0 ... 62 0 ... 62 2 ... 64 2 ... 64 1) incl. 2 Byte module process data UR20-FBC-PL Process data for IO-Link devices Fieldbus dependent data widths1) Input Output Input Output Byte Byte Byte Byte 8 8 10 10 8 16 10 18 8 32 10 34 8 62 10 64 16 8 18 10 16 16 18 18 16 32 18 34 16 62 18 64 32 8 34 10 32 16 34 18 32 32 34 34 32 62 34 64 62 8 64 10 62 16 64 18 62 32 64 34 62 62 64 64 1) incl. 2 Byte module process data

53 Manual Communication module UR20-4COM-IO-LINK 2547720000/03/09.2019 UR20-FBC-EIP You can select the length of the process input data and the length of the process output data independently of each other. Process data for IO-Link devices Fieldbus dependent data widths1) Input Output Input Output Byte Byte Byte Byte 0 ... 128 0 ... 128 2 ... 130 2 ... 130 1) incl. 2 Byte module process data UR20-FBC-DN You can select the length of the process input data and the length of the process output data independently of each other. Process data for IO-Link devices Fieldbus dependent data widths1) Input Output Input Output Byte Byte Byte Byte 0 ... 128 0 ... 128 2 ... 130 2 ... 130 1) incl. 2 Byte module process data UR20-FBC-CAN You can select the length of the process input data and the length of the process output data independently of each other. Process data for IO-Link devices Fieldbus dependent data widths1) Input Output Input Output Byte Byte Byte Byte 0 ... 62 0 ... 62 2 ... 64 2 ... 64 1) incl. 2 Byte module process data

55 Manual Communication module UR20-4COM-IO-LINK 2547720000/03/09.2019 9.1 Diagnostic data Channel diagnoses can be activated with the “Channel diag- nosis” parameter. Diagnostic data UR20-4COM-IO-LINK Name Byte Bit Description Default Error indicator 0 0 Module error 0 1 Internal Error 0 2 External error 0 3 Channel error 0 4 Error 0 5 Power supply fault 0 6 Reserved 0 7 Parameter error 0 Module type 1 0 Module Type 0x05 1 2 3 4 Reserved 1 5 Reserved 0 6 Reserved 0 7 Reserved 0 Error byte 2 2 0 ... 7 Reserved 0 Error byte 3 3 0 ... 2 Reserved 0 3 Diagnostic Alarm Lost 0 4 Communication fault 0 5 Reserved 0 6 Reserved 0 7 IO-Link Event in Queue 0 Channel type 4 0 Channel type 1 1 1 2 0 3 1 4 1 5 1 6 1 7 Reserved 0 Diagnostic bits per channel 5 Number of diagnostic bit per channel 16 Number of channels 6 Number of similar channels per module 4 Channel error 7 0 Error at channel 0 0 1 Error at channel 1 0 2 Error at channel 2 0 3 Error at channel 3 0 4 ... 7 Reserved 0 8 ... 10 8 ... 31 Reserved 0 Diagnostic data UR20-4COM-IO-LINK Name Byte Bit Description Default Error channel 0 Error channel 1 Error channel 2 Error channel 3 11 13 15 17 0 Short Circuit 0 1 Undervoltage 0 2 Overvoltage 0 3 Overload 0 4 Overtemperature 0 5 Line Break 0 6 Upper Limit Value 7 Lower Limit Value 0 Error channel 0 Error channel 1 Error channel 2 Error channel 3 12 14 16 18 0 Error 0 1 Parameter fault 0 2 Powersupply fault 0 3 Fuse blown 0 4 Communication fault 0 5 Error 1 0 6 Unknown Error 7 Unknown Error 2 0 Error channel 4 ... Error channel 15 19 ... 42 0 ... 7 Reserved 0 Time stamp 43-46 time stamp [µs] (32bit) 9.2 IO-Link master event codes Event Code Description 0xC101 Overcurrent at transmitter 0xC102 Overtemperature at transmitter 0xC103 Undervoltage at VDD 0xC104 Undervoltage at VDDH 0xC105 Undervoltage at L+ 0xC106 Overcurrent at L+ shunt 0xC201 Error at Data Storage EEPROM access 0xFF21 A new connection has been established between the Master and the Device 0xFF22 The Device hasn‘t answered for three consequent Master request 0xFF23 DS header settings doesn‘t match with the read IDs 0xFF24 The DS buffer overflows 0xFF25 A DS parameter can‘t be accessed 0xFF91 Request DS upload 9 Diagnostics and troubleshooting

56 2547720000/03/09.2019 Manual Communication module UR20-4COM-IO-LINK 9.3 LED indicators and troubleshooting LED Status Recommended action Status LED Red: – Error in the supply voltage at input current path – Communication error on the system bus – Configuration error IO-Link – There is a new diagnostic message – Check the supply voltage – Check that the module has been snapped into place properly – Check the configuration Channel LED 1.1 ... 4.1 Yellow: – Status COM 1 ... COM 4 – 1.2 ...4.2 Red: – Fehler IO-Link port 1 ... IO-Link port 4 – Check the wiring – Check the configuration 1.4 ... 4.4 Yellow: – Status DI 1 ... DI 4 –

57 Manual Communication module UR20-4COM-IO-LINK 2547720000/03/09.2019 10.1 Disassembling a u-remote-Modul WARNING Explosion risk! ▶ Prior to starting work, make sure that there is not a potentially explosive atmos- phere! WARNING Dangerous contact voltage! ▶ Carry out all disassembly work on the u-remote station only when the power supply is disconnected. ▶ Make sure that the place of installation (switch cabinet etc.) has been discon- nected from the power supply! Before you can disassemble a specific module, you must dis- assemble every module right of that module as well. ▶ Remove all cables and lines. ▶ Remove the end bracket marker (if present). ▶ Unfasten the mounting screw on the right-hand end bracket. ▶ Slide the end bracket with the end plate to the right and remove both from the DIN rail. You can now disassemble the modules and the fieldbus cou- pler either individually or in groups of three to four modules. ▶ Press all the release levers of a module group towards the mounting plate so that they click into place. ▶ Slide the module group to the right and remove it from the DIN rail. ▶ Repeat the above procedure for all remaining modules/ module groups. ▶ Please observe the instructions for proper disposal.. 10.2 Disposing of a u-remote-Modul ATTENTION Products in the u-remote series are subject to WEEE (EU Directive 2012/19/EU), which regulates the collection and recycling of elec- trical and electronic equipment. ▶ Make sure that disassembled products are properly disposed of! When all u-remote products reach the end of their life cycle, you can return them to Weidmüller, and we will arrange for their proper disposal. This also applies to countries outside the European Union. ▶ Please pack the products properly and send them to your responsible distributor. You can find the address of your respective country repre- sentative in the annex and at the Weidmüller website. 10 Disassembly and disposal

As experienced experts we support our customers and partners around the world with products, solutions and services in the industrial environment of power, signal and data. We are at home in their industries and markets and know the technological challenges of tomorrow. We are therefore continuously developing innovative, sustainable and useful solutions for their individual needs. Together we set standards in Industrial Connectivity. Weidmüller Interface GmbH & Co. KG Klingenbergstraße 26 D-32758 Detmold, Germany T +49 5231 14-0 F +49 5231 14-292083 www.weidmueller.com Personal support can be found on our website: www.weidmueller.com/contact Order number.: 2547720000/03/09.2019