IFM AL1323 Manual
IFM
Ikke kategoriseret
AL1323
Læs gratis den danske manual til IFM AL1323 (170 sider) i kategorien Ikke kategoriseret. Denne vejledning er vurderet som hjælpsom af 10 personer og har en gennemsnitlig bedømmelse på 3.9 stjerner ud af 5.5 anmeldelser. Har du et spørgsmål om IFM AL1323, eller vil du spørge andre brugere om produktet?
Side 1/170
>
>
80284133 / 03 10 / 2021
Operating instructions
IO-Link master with EtherNet/IP interface
DataLine
8 ports
IP 65 / IP 66 / IP 67 / IP 69K
AL1323
Firmware: 3.1 or higher
English
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
2
Contents
1 Preliminary note 5
1.1 Legal and copyright information ........................................................................................... 5
1.2 Purpose of the document ..................................................................................................... 5
1.3 Explanation of Symbols ....................................................................................................... 5
1.4 Change history ..................................................................................................................... 6
2 Safety instructions 7
2.1 General ................................................................................................................................ 7
2.2 Required background knowledge ........................................................................................ 7
2.3 Safety symbols on the device .............................................................................................. 7
2.4 IT security ............................................................................................................................. 8
3 Functions and features 9
4 Function 10
4.1 Communication, parameter setting, evaluation ................................................................. 11
4.1.1 - IO Link........................................................................................................................................ 11
4.1.2 EtherNet/IP ................................................................................................................................. 11
4.1.3 Internet of Things (IoT) ............................................................................................................... 11
4.1.4 Security mode ............................................................................................................................ 12
4.1.5 Parameter setting ....................................................................................................................... 12
4.1.6 Visual indication .........................................................................................................................12
4.2 Digital inputs ....................................................................................................................... 12
4.3 -Link supply IO .................................................................................................................... 12
5 Mounting 13
5.1 Mount the device ................................................................................................................ 13
6 Electrical connection 14
6.1 Notes .................................................................................................................................. 14
6.2 Connecting the EtherNet/IP ports ...................................................................................... 15
6.3 Connecting the IoT port ..................................................................................................... 15
6.4 -Link ports IO ....................................................................................................................... 16
6.4.1 Connecting IO-Link devices for Class A operati on ..................................................................... 16
6.5 Connecting the device ....................................................................................................... 17
7 Operating and display elements 18
7.1 Overview ............................................................................................................................ 18
7.2 LED indicators .................................................................................................................... 19
7.2.1 Status LEDs ............................................................................................................................... 19
7.2.2 Ethernet ports ............................................................................................................................. 19
7.2.3 IoT port ....................................................................................................................................... 20
7.2.4 Voltage supply ............................................................................................................................ 20
7.2.5 -Link Ports (Class A) IO ............................................................................................................... 20
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
3
8 Set- up 21
9 Configuration 22
9.1 LR DEVICE ........................................................................................................................ 23
9.1.1 Remarks ..................................................................................................................................... 24
9.1.2 IoT: Congure IP settings ........................................................................................................... 24
9.1.3 IoT: Congure security mode ..................................................................................................... 25
9.1.4 IoT: Conguring access rights .................................................................................................... 26
9.1.5 IoT: Congure the interface to LR AGENT or LR SMARTOBSERVER ...................................... 27
9.1.6 Fieldbus: Congure IP settings ................................................................................................... 28
9.1.7 Fieldbus: set the conguration mode .......................................................................................... 29
9.1.8 - ports: Activate data transfer to LR AGENT or LR SMARTOBSERVER IO Link ......................... 30
9.1.9 -Link ports: Congure operating mode IO ....................................................................................31
9.1.10 -Link ports: Set the device validation and data storage IO .......................................................... 32
9.1.11 -Link ports: Setting fail-safe values IO ......................................................................................... 33
9.1.12 Info: Show device information .................................................................................................... 33
9.1.13 Firmware: Reset device to factory settings ................................................................................. 34
9.1.14 Firmware: Reboot the device ...................................................................................................... 34
9.1.15 Congure IO-Link devices .......................................................................................................... 35
9.2 ifm IoT Core ....................................................................................................................... 36
9.2.1 Programmers' notes ................................................................................................................... 37
9.2.2 First steps ................................................................................................................................... 40
9.2.3 General functions ....................................................................................................................... 41
9.2.4 IoT: Conguring access rights .................................................................................................... 45
9.2.5 IoT: Conguring IP settings ........................................................................................................ 45
9.2.6 IoT: Conguring the LR AGENT or LR SMARTOBSERVER interface ....................................... 46
9.2.7 IoT: Conguring security mode ................................................................................................... 46
9.2.8 Fieldbus: Conguring IP settings ................................................................................................ 49
9.2.9 Fieldbus: Selecting the conguration mode ................................................................................ 49
9.2.10 Fieldbus: Setting fail-safe values ................................................................................................ 50
9.2.11 -Link ports: Setting the operating mode of pin 4 (US) IO ............................................................. 50
9.2.12 -Link ports: Conguring device validation and data storage IO ................................................... 50
9.2.13 -Link ports: Conguring data transfer to LR AGENT or LR SMARTOBSERVER IO .................... 52
9.2.14 -Link ports: Reading / writing process data IO ............................................................................. 52
9.2.15 -Link ports: Indicating port events IO ........................................................................................... 55
9.2.16 -Link devices: Accessing parameters IO ..................................................................................... 55
9.2.17 -Link devices: Reading an writing device information IO ............................................................. 57
9.2.18 -Link devices: Indicating IO-Link events IO ................................................................................. 57
9.2.19 Gateway: Resetting, rebooting and localising the device ........................................................... 57
9.2.20 Gateway: Reading device information ........................................................................................ 58
9.2.21 Gateway: Reading status and diagnostic information ................................................................. 58
9.2.22 Gateway: Updating the rmware ................................................................................................ 59
9.2.23 Gateway: Setting the application tag .......................................................................................... 60
9.2.24 Subscribing to notications ......................................................................................................... 61
9.2.25 Using Web Socket ...................................................................................................................... 64
9.2.26 MQTT support ............................................................................................................................ 66
9.2.27 Using the IoT-Core Visualizer ..................................................................................................... 70
9.3 EtherNet/IP ......................................................................................................................... 77
9.3.1 Registration of the EDS le ........................................................................................................ 77
9.3.2 Integrate the IO-Link Master into the EtherNet/IP project ........................................................... 77
9.3.3 Set connection types and RPI .................................................................................................... 78
9.3.4 Congure AL1323 ......................................................................................................................79
9.3.5 Congure IO-Link ports .............................................................................................................. 80
9.3.6 Congure IO-Link devices .......................................................................................................... 81
9.3.7 Read process data ..................................................................................................................... 82
9.3.8 Write process data .....................................................................................................................82
9.3.9 Read diagnostic and status information .....................................................................................83
9.3.10 EtherNet/IP: Programmers' notes ............................................................................................... 84
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
4
10 86 Operation
10.1 Using web-based management ......................................................................................... 86
11 87 Maintenance, repair and disposal
11.1 Cleaning process ............................................................................................................... 87
11.2 Updating the rmware ........................................................................................................ 87
11.3 Replacing IO-Link device ................................................................................................... 87
12 88 Factory settings
13 89 Accessories
14 90 Appendix
14.1 Technical data .................................................................................................................... 91
14.1.1 Application .................................................................................................................................. 91
14.1.2 Electrical data ............................................................................................................................. 91
14.1.3 Inputs / outputs ........................................................................................................................... 91
14.1.4 Inputs .........................................................................................................................................92
14.1.5 Outputs ....................................................................................................................................... 92
14.1.6 Interfaces .................................................................................................................................... 92
14.1.7 Operating conditions ..................................................................................................................93
14.1.8 Approvals / tests ......................................................................................................................... 93
14.1.9 Mechanical data ......................................................................................................................... 93
14.1.10 Electrical connection ..................................................................................................................94
14.2 EtherNet/IP ......................................................................................................................... 95
14.2.1 Supported connection types ....................................................................................................... 95
14.2.2 Parameter data ........................................................................................................................... 96
14.2.3 Cyclic data .................................................................................................................................. 99
14.2.4 Acyclic data .............................................................................................................................. 110
14.3 ifm IoT Core .....................................................................................................................145
14.3.1 Overview: IoT prole ................................................................................................................146
14.3.2 Overview: IoT types .................................................................................................................. 153
14.3.3 Overview: IoT services ............................................................................................................. 154
15 168 Index
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
5
1 Preliminary note
Content
Legal and copyright information ............................................................................................................... 5
Purpose of the document ......................................................................................................................... 5
Explanation of Symbols ............................................................................................................................ 5
Change history ......................................................................................................................................... 6
33203
>
1.1 Legal and copyright information
33117
© All rights reserved by ifm electronic gmbh. No part of this manual may be reproduced and used
without the consent of ifm electronic gmbh.
All product names, pictures, companies or other brands used on our pages are the property of the
respective rights owners:
• -i is the property of the AS-International Association, ( AS →www.as-interface.net)
• CAN is the property of the CiA (CAN in Automation e.V.), Germany ( ) →www.can-cia.org
• CODESYS™ is the property of the CODESYS GmbH, Germany ( ) →www.codesys.com
• DeviceNet™ is the property of the ODVA™ (Open DeviceNet Vendor Association), USA
( ) →www.odva.org
• EtherNet/IP® is the property of the → ODVA™
• EtherCAT® is a registered trade mark and patented technology, licensed by Beckho Automation
GmbH, Germany
• -LinkIO ® is the property of the → PROFIBUS Nutzerorganisation e.V., Germany
( ) →www.io-link.com
• ISOBUS is the property of the AEF Agricultural Industry Electronics Foundation e.V., –
Deutschland ( →www.aef-online.org)
• Microsoft® is the property of the Microsoft Corporation, USA ( ) →www.microsoft.com
• Modbus® is the property of the Schneider Electric SE, France ( ) →www.schneider-electric.com
• PROFIBUS®
is the property of the PROFIBUS Nutzerorganisation e.V., Germany
( ) →www.probus.com
• PROFINET® is the property of the → PROFIBUS Nutzerorganisation e.V., Germany
• Windows® is the property of the Microsoft Corporation, USA →
>
1.2 Purpose of the document
34227
This document is only for device types "IO- nk master - EtherNet/IP gateway (DataLine) 8 port IP 65 / Li
IP 66 / IP 67 / IP 69K" (art. no.: AL1323).
It is part of the device and contains information about the correct handling of the product.
► Read this document before using the device.
► Keep this document during the service life of the device.
>
1.3 Explanation of Symbols
34171
WARNING
Warning of serious personal injury.
Death or serious irreversible injuries may result.
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
6
CAUTION
Warning of personaly injury.
Slight reversible injuries may result.
NOTICE
Warning of damage to property
Important note
Non-compliance can result in malfunction or interference
Information
Supplementary note
► ...
Request for action
> ...
Reaction, result
→ ...
"see"
abc
Cross-reference
123
0x123
0b010
Decimal number
Hexadecimal number
Binary number
[...]
Designation of pushbuttons, buttons or indications
>
1.4 Change history
61118
Version
Topic
Date
00
New creation of the document
04 / 2019
01
Correction: Technical data - current rating per output
09 / 2019
02
▪ Added: New IoT core functions
▪ Added: IoT Core Visualizer
▪ Correction: Description of the IoT Core Service getsubscriptioninfo
10 / 2020
03
Deleted: ifm IoT Core DNS support –
10 / 2021
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
7
2 Safety instructions
Content
General ..................................................................................................................................................... 7
Required background knowledge ............................................................................................................. 7
Safety symbols on the device ................................................................................................................... 7
IT security ................................................................................................................................................. 8
28333
>
2.1 General
58525
• The device described is a subcomponent for integration into a system. The manufacturer is
responsible for the safety of the system. The system manufacturer undertakes to perform a risk
assessment and to create documentation in accordance with legal and normative requirements to
be provided to the operator and user of the system. This documentation must contain all
necessary information and safety instructions for the operator, the user and, if applicable, for any
service personnel authorised by the manufacturer of the system.
• Read this document before setting up the product and keep it during the entire service life.
• The product must be suitable for the corresponding applications and environmental conditions
without any restrictions.
• Only use the product for its intended purpose ( →Functions and features ( →p. 9)).
• If the operating instructions or the technical data are not adhered to, personal injury and/or
damage to property may occur.
• The manufacturer assumes no liability or warranty for any consequences caused by tampering
with the product or incorrect use by the operator.
• Installation, electrical connection, set-up, programming, conguration, operation and maintenance
of the product must be carried out by personnel qualied and authorised for the respective activity.
• Protect units and cables against damage.
>
2.2 Required background knowledge
34185
This document is intended for specialists. Specialists are people who, based on their relevant training
and experience, are capable of identifying risks and avoiding potential hazards that may be caused
during operation or maintenance of the product.
The document contains information about the correct handling of the product.
>
2.3 Safety symbols on the device
34199
General warning
Observe instructions in chapter "Electrical connection" ( →Electrical connection ( →p. 14))!
>
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
8
2.4 IT security
54678
NOTICE!
If the device is operated in an unprotected network environment.
> Unauthorised read or write access to data is possible.
> Unauthorised manipulation of the device function is possible.
► Check and restrict access options to the device:
▪ Restrict access to authorised persons.
▪ Do not connect the device to open networks or the internet.
If access from the internet is inevitable:
► choose a safe method to connect with the device (e. g. VPN).
► Use encrypted data transmission (e. g. https / TLS).
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
10
4 Function
Content
Communication, parameter setting, evaluation ...................................................................................... 11
Digital inputs ........................................................................................................................................... 12
IO-Link supply ......................................................................................................................................... 12
33836
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
11
4.1 Communication, parameter setting, evaluation
Content
IO-Link .................................................................................................................................................... 11
EtherNet/IP ............................................................................................................................................. 11
Internet of Things (IoT) ........................................................................................................................... 11
Security mode ......................................................................................................................................... 12
Parameter setting ................................................................................................................................... 12
Visual indication ...................................................................................................................................... 12
33860
>
4.1.1 -Link IO
34084
The device oers the following IO-Link functions:
• -Link master (IO-Link revision 1.0 and 1.1) IO
• 8 IO-Link ports for connection of IO-Link devices
• Provision of process data of the connected IO-Link devices for LR SMARTOBSERVER monitoring
software ( ) →www.ifm.com
>
4.1.2 EtherNet/IP
52585
The device oers the following EtherNet/IP functions:
• EtherNet/IP Device
• 2 port switch for access to the EtherNet/IP interface
• Gateway for transmission of the process and parameter data between the connected IO-Link
devices and the higher-level EtherNet/IP controller
• Min. cycle time: 1 ms (RPI)
• Connection classes: 1, 3
• Connection Application types: Exclusive Owner, Input Only, Listen Only Connections
• UCMM supported
• Predened standard objects:
▪ Identity Object (0x01)
▪ Message Router Object (0x02)
▪ Assembly Object (0x04)
▪ Connection Manager (0x06)
▪ DLR Object (0x47)
▪ QoS Object (0x48)
▪ TCP/IP Interface Object (0xF5)
▪ Ethernet Link Object (0xF6)
• Supported protocols: DHCP, BOOTP, ACD, DLR
• Device description: EDS le
>
4.1.3 Internet of Things (IoT)
54679
The device oers the following IoT functions:
• Gateway for the transmission of process, parameter and monitoring data between IO-Linkmaster /
IO-Link devices and the IT network level
• REST-API to access process and parameter data
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
12
• Supported protocols: TCP/IP JSON, MQTT
>
4.1.4 Security mode
54697
The IoT interface oers the following optional sercurity functions:
• Secure data transfer via encrypted connection (Secure Layer Transport - TLS)
• Access protection via authentication
>
4.1.5 Parameter setting
34210
The device provides the following conguration options:
• Parameter setting of the IO-Link master of the AL1323 with LR DEVICE parameter setting
software, EtherNet/IP projection software or ifm IoT-Core services.
• Parameter setting of the connected IO-Link devices (sensors, actuators) with LR DEVICE
parameter setting software, EtherNet/IP projection software or ifm IoT-Core services
• Storage of parameter sets of the connected IO-Link devices for automatic recovery (data storage)
>
4.1.6 Visual indication
34192
The device has the following visual indicators:
• Status and error indication of the gateway, of the EtherNet/IP connection and of the system
• Status display of the voltage supply
• Status and activity display of the Ethernet connection
• Status, error and short circuit/overload indication of the IO-Link ports
>
4.2 Digital inputs
33817
The device has 8 additional digital inputs (type 2 according to EN 61131-2).
The digital inputs are on pin 2 of the ports X01...X04.
All inputs refer to the potential of the device supply (pin 3).
>
4.3 -Link supply IO
34077
The device has 8 supplies for IO-Link devices.
The IO-Link ports X01...X08 are ports class A.
Every supply provides short circuit monitoring.
The device ensures re protection for the connected IO-Link devices by providing a power-restricted
circuit at the IO-Link ports (according to IEC61010-1 and Class 2 according to UL1310).
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
13
5 Mounting
Content
Mount the device .................................................................................................................................... 13
34058
>
5.1 Mount the device
34059
► Disconnect the system from power before installation.
► For installation choose a at mounting surface.
► Please observe the maximum tightening torque.
► the unit to the mounting surface using 2 M5 mounting screws and washers. Fix
▪ Tightening torque: 1.8 Nm
► Ground the unit via the two mounting screws of the upper mounting lugs.
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
14
6 Electrical connection
Content
Notes ...................................................................................................................................................... 14
Connecting the EtherNet/IP ports ........................................................................................................... 15
Connecting the IoT port .......................................................................................................................... 15
IO-Link ports ........................................................................................................................................... 16
Connecting the device ............................................................................................................................ 17
33805
>
6.1 Notes
51957
A qualied electrician must connect the unit.
► The national and international for regulations setting up electrical equipment must be
complied with.
The unit is only suitable for operation using SELV/PELV voltages.
► Please note the information concerning IO-Link wiring!
This unit contains components that may be damaged or destroyed by electrostatic discharge
(ESD).
► Please observe the required precautions against electrostatic discharge!
The M12 connection parts in the device comply with the ingress resistance requirements of
the standard EN 61076-2-101. To adhere to the protection rating, only cables certied to this
standard must be used. The system creators undertake to ensure ingress resistance for
cables which they cut to length themselves.
► Carry out the tting according to the indications of the cable manufacturer. A maximum of
0.8 Nm is permitted.
► During installation, place the M12 connector vertically so that the coupling nut will not
damage the thread.
► Depending on the mounting conditions, cables must be provided with a strain relief to
avoid unacceptable loads on the mounting points and M12 connections.
► Make sure that the M12 connection parts are correctly seated and mounted correctly. The
specied protection rating can not be guaranteed if this is not observed.
For UL applications:
► To connect the IO-Link master and the IO-Link devices, only use UL-certied cables of the
CYJV or PVVA category with a minimum temperature of 80 °C (75 °C in case of maximum
ambient temperature of 40 °C).
Wiring: ( ) →Technical data →p. 91
By means of basic insulation according to EN61010-1, the circuits are separated from each other and
from device surfaces that could be touched (secondary circuit with 28 V DC maximum, supplied from
mains circuit up to 300 V overvoltage category II).
By means of basic insulation according to EN61010-1, the communication interfaces are separated
from each other and from device surfaces that could be touched (secondary circuit with 28 V DC
maximum, supplied from mains circuit up to 300 V overvoltage category II). They are designed for
network environment 0 according to IEC TR62102.
>
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
15
6.2 Connecting the EtherNet/IP ports
33671
► Connect the device via the M12 socket X21 and/or X22 to the
EtherNet/IP network
(e.g. EtherNet/IP PLC, additional EtherNet/IP device)
► To connect the devices, use M12 connectors with protection rating
IP 65 / IP 66 / IP 67 / IP 69K or higher ( ( →Accessories →p. 89)).
► Cover the unused sockets with M12 protective caps (art no.
E12542).
>
6.3 Connecting the IoT port
34044
► Connect the device via the M12 socket X23 to the IT network (e.g.
laptop/PC with LR DEVICE parameter setting software, laptop/PC
with LR SMARTOBSERVER monitoring software, laptop/PC with
software capable of processing http requests).
► To connect the devices, use M12 connectors with protection rating
IP 65 / IP 66 / IP 67 / IP 69K or higher ( ( →Accessories →p. 89)).
► Cover the unused sockets with M12 protective caps (art no.
E12542)
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
16
6.4 -Link ports IO
51958
The IO-Link ports of the AL1323 meet the requirements of the IO-Link specications 1.0 to 1.1.2.
► Please note the information concerning IO-Link wiring!
► Cover unused sockets with M12 protective caps (art. no.: E12542 ).
>
6.4.1 Connecting IO-Link devices for Class A operation
51959
Wiring information:
• The connected IO-Link devices must be supplied exclusively via the IO-Link master.
• The additional digital inputs IO-Link ports X01...X08 (pin 2) have a type 2 behaviour according to
the standard EN61131-2. The connected electronics must be electrically suited for this.
► Connect the connectors of the IO-Link devices with the M12
sockets of the IO-Link ports X01...X08.
▪ Maximum cable length per IO-Link port: 20 m
► To connect the devices, use M12 connectors with protection
rating IP 65 / IP 66 / IP 67 / IP 69K or higher ( →Accessories
( )). →p. 89
>
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
17
6.5 Connecting the device
33882
► Disconnect power.
► Connect the IO-Link Master via M12 socket X31 to 24 V DC
(20...28 V SELV/PELV; according to EN61010-1, secondary circuit
with maximum 30 V DC supplied by mains circuit up to 300 V of
overvoltage category II).
▪ Maximum cable length: 25 m
► To connect the device, use M12 connectors with protection rating IP
65 / IP 66 / IP 67 / IP 69K or higher ( ( →Accessories →p. 89)).
When using cable length greater than 25 m keep in mind the voltage drop as well as the
required minimum voltage supply of 20 V!
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
18
7 Operating and display elements
Content
Overview ................................................................................................................................................. 18
LED indicators ........................................................................................................................................ 19
34063
>
7.1 Overview
34356
1
RDY, NET and MOD status LEDs
→ → (Status LEDs ) p. 19
2
LNK and ACT status LEDs of the EtherNet/IP
interfaces 1 (X21) and 2 (X22)
→ → (Ethernet ports ) p. 19
3
LNK, ACT status-LEDs and IoT LED of the IoT
interface (X23)
→ → (IoT port ) p. 20
4
IOL and DI status-LEDs of the IO-Link port (X01...X08)
→ → (IO-Link Ports (Class A) p. 20)
5
PWR status LED of the voltage supply (X31)
→ → (Voltage supply p. 20)
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
19
>
7.2 LED indicators
34047
The device only has the following LED indicators:
>
7.2.1 Status LEDs
34408
The RDY LED indicates the status of the gateway.
The NET LED (Network Status) indicates the status of the network.
The MOD LED (Module Status) indicates the status of the EtherNet/IP module.
Status LED
Description
RDY
green
on
Status: OK
ashes 5 Hz
Status: Error
ashes (200 ms on,
800 ms o)
Status: Firmware update is running
off
Status: Gateway not running or gateway booting
NET
green / red
off
Not powered or powered, but IP address not yet configured
ashes
Device self-testing
green
ashes
No connection: no CIP connection established and a Exclusive Owner
connection has not timed out
on
Connection: at least one CIP connection established and an Exclusive
Owner connection has not timed out
red
ashes
Connection timeout: an Exclusive Owner connection has timed out
on
Duplicate IP address: IP address aready in use
MOD
green / red
off
No voltage or voltage too low
ashes
Device self-testing
green
ashes
Standby: device not yet congured (no IP address)
on
Operational
red
ashes
Major recoverable fault (e.g. incorrect conguration)
on
Major unrecoverable fault (e.g. module failed)
>
7.2.2 Ethernet ports
34348
Each Ethernet port has 2 LEDs (LNK and ACT). The LEDs indicate the status of the Ethernet
connection.
Status LED
Description
LNK
green
on
Ethernet connection established
off
No Ethernet connection
ACT
yellow
ashes
Data is transmitted via the Ethernet interface.
off
No data transmission
>
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
20
7.2.3 IoT port
34043
The IoT port has the 3 LNK, ACT and IoT LEDs. The LEDs indicate the status of the Ethernet
connection and the device identication.
Status LED
Description
LNK
green
on
Ethernet connection established
off
No Ethernet connection
ACT
yellow
ashes
Data is transmitted via the Ethernet interface.
off
No data transmission
IoT
green
flashes
Device identication active
>
7.2.4 Voltage supply
34191
The interface for voltage supply (X31) has the LED that is marked as US. The LED indicates the status
of the voltage supply.
Status LED
Description
US
green
on
The supply voltage Us is applied.
off
No supply voltage is applied or the applied supply voltage is too low.
>
7.2.5 -Link Ports (Class A) IO
34074
Each IO-Link Port Class A has 2 LEDs labelled IOL and DI. The LEDs indicate the status of the
IO-Link port.
Status LED
Description
IOL
yellow
O
Port congured as DI/DO: pin 4 (C/Q) = OFF
on
Port congured as DI/DO: pin 4 (C/Q) =ON
green
ashing 1 Hz
Port congured asIO-Link: no IO-Link device found
Flashing with 2 Hz
Port congured asIO-Link: Status PREOPERATE
on
Port congured asIO-Link: Status OPERATE
red
Flashing with 2 Hz
Port conguration error or short circuit / overload on US
on
Transmission Error
DI
yellow
O
Digital input: pin 2 = OFF
on
Digital input: pin 2 = ON
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
21
8 Set- up
52357
When the supply voltage is switched on, the AL1323 starts with the factory settings. The display
elements signal the current operating mode ( →Operating and display elements ( )). →p. 18
To enable parameter setting of the AL1323, the IoT interface and / or the eldbus interface must be
congured according to the network environment.
► Congure IoT interface (LR DEVICE: →IoT: Congure IP settings IoT: ( ) or →p. 24 →
Conguring IP settings ( →p. 45)).
► Congure eldbus interface (LR DEVICE: →Fieldbus: Congure IP settings ( →p. 28) or IoT:
→ Feldbus-Schnittstelle kongurieren).
> IoT / eldbus interface has valid IP settings.
> User can set the parameters of the AL1323.
Further steps:
• Optional: Update rmware of AL1323 ( →Updating the rmware ( )). →p. 87
• Set the parameters of the AL1323 ( ( )). →Conguration →p. 22
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
22
9 Conguration
Content
LR DEVICE ............................................................................................................................................. 23
ifm IoT Core ............................................................................................................................................ 36
EtherNet/IP ............................................................................................................................................. 77
33858
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
23
9.1 LR DEVICE
Content
Remarks ................................................................................................................................................. 24
IoT: Congure IP settings ....................................................................................................................... 24
IoT: Congure security mode ................................................................................................................. 25
IoT: Conguring access rights ................................................................................................................ 26
IoT: Congure the interface to LR AGENT or LR SMARTOBSERVER ................................................. 27
Fieldbus: Congure IP settings .............................................................................................................. 28
Fieldbus: set the conguration mode ..................................................................................................... 29
IO-Link ports: Activate data transfer to LR AGENT or LR SMARTOBSERVER .................................. 30
IO-Link ports: Congure operating mode ............................................................................................... 31
IO-Link ports: Set the device validation and data storage ...................................................................... 32
IO- nk ports: Setting fail-safe values Li ................................................................................................... 33
Info: Show device information ................................................................................................................ 33
Firmware: Reset device to factory settings ............................................................................................ 34
Firmware: Reboot the device.................................................................................................................. 34
Congure IO-Link devices ...................................................................................................................... 35
33692
On delivery, the AL1323 is congured with the factory settings ( ( )). →Factory settings →p. 88
Required software: LR DEVICE (1.5.0.x or higher) (art.-no.: QA0011/QA0012)
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
24
9.1.1 Remarks
Content
Oine parameter setting ........................................................................................................................ 24
VPN connection ...................................................................................................................................... 24
34180
>
Offline parameter setting
34060
The AL1323 supports the ofine parameter setting. In this context, the user creates and stores a
conguration for the IO-Link master and the connected IO-Link devices without being connected to the
AL1323 (OFFLINE mode). The configuration created in this way can be stored as a le (*.lrp) and
loaded to the AL1323 and activated at a later date.
Further information about oine parameter setting: Operating instructions LR DEVICE →
>
VPN connection
34382
An active VPN connection blocks the access of the parameter setting software LR DEVICE to
the EtherNet/IP interface of the AL1323.
► Deactivate the VPN connection in order to be able to access the AL1323 with the LR
DEVICE.
>
9.1.2 IoT: Configure IP settings
34049
For access to the IO-Link master via the IT infrastructure the user has to set the IP settings of the IoT
port.
To congure the IP settings with DHCP, a DHCP server has to be active in the IT network. If
no DHCP server can be reached in the IT network, an IP address is automatically assigned to
the IoT port with the Zerocong protocol (address range: ( →Factory settings →p. 88)).
To congure the IP settings of the IoT interface:
► Select [IoT] menu.
> The menu page shows the current settings.
► Set the following parameters as required:
Name
Description
Possible values
[DHCP]
Activate/deactivate the DHCP client of the
device
[Static IP]
IP settings were set by the user
[DHCP]
IP settings are set by a DHCP
server in the network.
[IP address]*
IP address of the IoT port
Factory setting: 169.254.X.X
[Subnet mask]*
Subnet mask of the Ethernet network
Factory setting: 255.255.0.0
[Default gateway IP address]*
IP address of the network gateway
Factory setting: 0.0.0.0
[MAC address]
MAC address of the IoT port
The value is rmly set.
* ... can only be edited if parameter [DHCP] = [Static IP]
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
25
► Save changed values on the device.
>
9.1.3 IoT: Configure security mode
54680
The IoT interface of the IO-Link oers a security mode. It enables secure data transmission via
transport encryption and restriction of the access to IO-Link masters and IO-Link devices via user
authentication.
To congure the security mode:
► Select [IoT] menu.
> The menu page shows the current settings.
► Set the following parameters as required:
Name
Description
Possible values
[Security mode HTTPS]
Set the security mode
[Disabled]
Security mode disabled
[Enabled]
Security mode enabled
[Security password]
Password
Note: The set password is not displayed.
► Save changed values on the device.
The security mode only protects the access to the device via the IoT interface.
The user name "administrator" cannot be changed.
The security mode can be enabled without setting the password. During the attempt to write to
the device, LR DEVICE requires to enter and conrm the password.
After entering the password, the user has unrestricted access to IO-Link masters and
connected IO-Link devices. The password will only be requested again if the current LR
DEVICE session is over (e. g. after restarting the LR DEVICE).
To change the set password:
► Sign in with a valid password.
► Enter the new password in the eld [Security password].
► Write changes to the device.
> The new password is set.
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
26
>
9.1.4 IoT: Configuring access rights
34046
The access rights define which instance may read and / or write the parameter data, process data and
event/diagnostic messages.
In order to configure the access rights to the IO-Link master:
► Select [IoT] menu.
> The menu page shows the current settings.
► Set the following parameters as required:
Name
Description
Possible values
[Access Rights]
The access rights to the
parameter data, process data
and the event/diagnostic
messages of the IO-Link master
as well as the connected IO-Link
devices
[EtherNet/IP + IoT]*
▪ EtherNet/IP and IoT Core have read
and write access rights to parameters
and process data
▪ EtherNet/IP and IoT Core have read
access rights to events/alarms
[EtherNet/IP + IoT
(read-only)]
▪ EtherNet/IP has read and write access
rights to parameters and process data
▪ EtherNet/IP has read access rights to
events/alarms
▪ IoT Core only has read access rights to
parameters, process data and
events/alarms
[IoT only]
▪ IoT Core has read and write access
rights to parameters and process data
▪ IoT has read access rights to
events/alarms
▪ EtherNet/IP has no access rights
* ... Factory setting
► Save changed values on the device.
If in LR DEVICE and EtherNet/IP projection software the parameter [Access Rights] is =
[EtherNet/IP + IoT], the parameter values set in the EtherNet/IP projection software will always
apply.
If the parameter [Access Rights] in LR DEVICE is = [IoT only], set the parameter [Access
Rights] = [Keep settings] in the EtherNet/IP projection software.
If the parameter [Access Rigts] in LR DEVICE is = [<Fieldbus> + IoT (read-only)], write access
to the device configuration via LR DEVICE and IoT core services is blocked. To enable write
access again, set the parameter to [<Fieldbus> + IoT] via fieldbus configuration software.
Changes of the parameter [Access Rights] will only be effective after restarting the IO-Link
master ( → Firmware: Reboot the device ( )). → p. 34
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
27
>
9.1.5 IoT: Configure the interface to LR AGENT or LR SMARTOBSERVER
34048
To enable transfer of process data from the IO-Link master to LR AGENT or LR SMARTOBSERVER,
the interface has to be configured accordingly.
► Select [IoT] menu.
> The menu page shows the current settings.
► Set the following parameters as required:
Name
Description
Possible values
[IP address LR Agent or
SMARTOBSERVER]
IP address of LR AGENT or
LR SMARTOBSERVER
Factory setting: 255.255.255.255
[Port LR Agent or
SMARTOBSERVER]
Port number that is used to send process data
to LR AGENT or LR SMARTOBSERVER
0
...
65535
Factory setting:: 35100
[Interval LR Agent or
SMARTOBSERVER]
Cycle time for the transfer of the process data to
LR AGENT or LR SMARTOBSERVER (value in
milliseconds)
[Off]
no transfer
500
...
2147483647
500 ms
...
2147483647 ms
[Application Tag]
Source identifier of the IO-Link master in the
structure of LR AGENT or
LR SMARTOBSERVER (String32)
Factory setting: AL1323
After changing the parameter [Port LR Agent or SMARTOBSERVER] or [Application Tag], it
may take 120 seconds before the device establishes a new TCP connection.
To prevent the delay:
► Reboot the device after changing the the parameter.
► Save changed values on the device.
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
28
>
9.1.6 Fieldbus: Configure IP settings
54692
For communication with the EtherNet/IP network, the EtherNet/IP interface must be configured.
► Select [Fieldbus] menu.
> The menu page shows the current settings.
► Set the following parameters as required:
Name
Description
Possible values
[DHCP]
Enable / disable the DHCP client of the device
[Static IP]
IP parameters are set by the
user
[DHCP]
IP parameters are set by a
DHCP server in the network.
[BOOTP]
IP parameters are set via the
Bootstrap Protocol (BOOTP)
[IP address]*
IP address of the EtherNet/IP port
Factory setting: 192.168.1.250
[Subnet mask]*
Subnet mask of the IP network
Factory setting: 255.255.255.0
[Default gateway IP address]*
IP address of the gateway
Factory setting: 0.0.0.0
[Host name]
Name of the device in the EtherNet/IP network
e.g. al1xxx
[MAC address]
MAC address of the device
The value is firmly set.
[Fieldbus firmware]
e.g. 3.4.04 (EtherNet/IP Adapter)
* ... Parameter can only be edited if parameter [DHCP] = [Static IP]
► Save changed values on the device.
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
29
>
9.1.7 Fieldbus: set the configuration mode
54693
The AL1323 supports the EtherNet/IP configuration modes "top-down" and "independent".
Additionally, the user can configure the length of the transmitted process data and select the required
connection types.
► Select [Fieldbus] menu.
> The menu page shows the current settings.
► Set the following parameters as required:
Name
Description
Possible values
[Configuration]*
EtherNet/IP configuration mode
Independent mode off
Configuration via fieldbus PLC
Independent mode on
Configuration via AL1323
[Process data length]*
Length of process data per IO-Link
port
2 bytes input 2 bytes
output
2 bytes input data, 2 bytes output
data
4 bytes input 4 bytes
output
4 bytes input data, 4 bytes output
data
8 bytes input 8 bytes
output
8 bytes input data, 8 bytes output
data
16 bytes input 16 bytes
output
16 bytes input data, 16 bytes output
data
32 bytes input 32 bytes
output
32 bytes input data, 32 bytes output
data
[Swap]*
Sequence of bytes in the data
word
off
as Array of Bytes
on
as Integer16 value; during an
update of the process data, the
bytes are exchanged
[Explicitpdmode]**
Enable / disable explicit PD mode
and select the process data to be
transmitted (connection types)
Explicit process data
mode off
Explicit PD mode disabled
Explicit process data
mode with IO-Link I/O +
Acyclic + Diag
Explicit PD mode enabled: IO-Link
inputs /outputs, acyclic data and
diagnostic data are transmitted
Explicit process data
mode with IO-Link I/O +
Acyclic
Explicit PD mode enabled: IO-Link
inputs/outputs and acyclic data are
transmitted
Explicit process data
mode with IO-Link I/O
Explicit PD mode enabled: IO-Link
inputs/outputs are transmitted
* ... Parameter can only be changed if the EtherNet/IP controller is disconnected
** ... Parameter only valid if [Configuration] = [Independent mode on]
► Save changed values on the device.
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
30
>
9.1.8 -Link ports: Activate data transfer to LR AGENT or IO
LR SMARTOBSERVER
33690
The user can decide separately for each IO-Link port whether the process data of the connected
IO-Link devices should be transferred to LR ENT or LR SMARTOBSERVER. AG
To transfer process data the interface to the LR AGENT or LR SMARTOBSERVER has to be
correctly configured ( → IoT: Configure the interface to LR AGENT or LR
SMARTOBSERVER ( → p. 27)).
To activate / deactivate data transfer:
► Select [Port x] menu (x = 1...8).
> The menu page shows the current settings.
► Set the following parameters as required:
Name
Description
Possible values
[Transmission to LR
Agent
or SMARTOBSERVER]
Transfer of process data of the connected
IO-Link device to LR AGENT oder
LR SMARTOBSERVER
[Disabled]
Transfer process data
[Enabled]
Don't transfer process data
► Save changed values on the device.
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
31
>
9.1.9 -Link ports: Configure operating mode IO
33694
The IO-Link ports X01...X08 of the device support the following operating modes:
• Disabled: no data transfer at pin 4 (C/Q) of the IO- nk port Li
• Digital input (DI): binary input signal at pin 4 (C/Q) of the IO-Link port
• Digital output (DO): binary output signal at pin 4 (C/Q) of the IO-Link port
• -Link: IO-Link data transfer via pin 4 (C/Q) of the IO-Link port IO
The user can set the operating mode separately for each -Link port. IO
To set the operating mode of an IO-Link port:
► Select [Port x] menu (x = 1...8).
> The menu page shows the current settings.
► Set the following parameters as required:
Name
Description
Possible values
[Mode Pin4 US]
Operating mode of pin 4 of the IO-Link port
[Disabled]
Port deactivated
[DI]
Operation as digital input
[DO]
Operation as digital output
[IO-Link]
Operation as IO-Link interface
[Cycle time actual]**
Current cycle time of the data transfer between
IO IO-Link master and -Link device on the port
(value in microseconds)
Parameter can only be read
[Cycle time preset]*
Cycle time of the data transfer between the IO-Link
master and the IO-Link device at the port (value in
microseconds)
0
The device matically sets auto
the fastest possible cycle time.
1
...
132800
1 microsecond
...
132800 microseconds
[Bitrate]**
Current transmission rate of the data transfer
between the IO-Link master and the IO-Link device
on the port
Parameter can only be read
* ... Parameter only available if [Mode] = [IO-Link]
** ... Parameter only visible if the IO-Link device is connected to the IO-Link port.
► Save changed values on the device.
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
32
>
9.1.10 -Link ports: Set the device validation and data storage IO
33697
The user can choose how the IO-Link ports are to behave with regard to the device validation and the
storage / recovery of parameter data of the connected IO-Link device.
The following options are available:
Option
Validation of the IO-Link
device
Storage of the parameter values
Recovery of the parameter
values
[No check and clear]
no
no
no
[Type compatible
V1.0 device]
yes, test the compatibility with
IO-Link standard V1.0
no
no
[Type compatible
V1.1 device]
yes, test the compatibility with
IO-Link standard V1.1
no
no
[Type compatible
V1.1 device with
Backup + Restore]
yes, test the compatibility with
IO-Link standard V1.1 and
identity of design (vendor ID
and device ID)
yes, automatic storage of the
parameter values; changes of the
current parameter values will be
stored
yes, recovery of the parameter
values when connecting an
identical IO-Link device with
factory settings
[Type compatible
V1.1 device with
Restore]
yes, test the compatibility with
IO-Link standard V1.1 and
identity of design (vendor ID
and device ID)
no, there is no automatic storage
changes of the current parameter
values will not be stored
yes, recovery of the parameter
values when connecting an
identical IO-Link device with
factory settings
The options only apply if the IO-Link port is in the operating mode "IO-Link".
For options [Type compatible V1.1 device with Backup + Restore] and [Type compatible V1.1
device with Restore]: If the vendor ID and device ID are changed in the online mode, the data
memory will be deleted and a new backup of the parameter values of the connected -Link IO
device will be created in the IO-Link master.
To configure the device validation and the data storage:
► select [Port x] menu (x = 1...8).
> The menu page shows the current settings.
► Set the following parameters as required:
Name
Description
Possible values
[Validation / Data
Storage]
Supported IO-Link standard and behaviour of the
IO-Link master when connecting a new IO-Link
device at port x (x = 1...8)
[No check and clear]
[Type compatible V1.0
device]
[Type compatible V1.1
device]
[Type compatible V1.1 device
with Backup + Restore]
[Type compatible V1.1 device
with Restore]
[Vendor ID]
ID of the manufacturer that is to be validated
0...65535
Factory setting: 0#
ifm electronic: 310
[Device ID]
ID of the IO that i-Link device s to be validated
0...16777215
Factory setting: 0
► Save changed values on the device.
>
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
33
9.1.11 -Link ports: Setting fail-safe values IO
34329
For the configuration mode "Independent" the user can set fail-safe values for the outputs of IO-Link
ports. The fail-safe values will be activated in case of an interuption of the EtherNet/IP conection.
To set the fail-safe values:
► Select [Port x] menu (x = 1...8).
> The menu page shows the current settings.
► Set the following parameters as required:
Name
Description
Possible values
[Fail-safe digital out]*
Fail-safe value of the output for operating mode
"Digital Output (DO)"
[Reset]
OFF
[Old]
old value
[Set]
ON
[Fail-safe IO-Link]*
Fail-safe value of ting mode the output for opera
"IO-Link"
[Off]
no Fail-safe
[Reset]
Fail-safe: OFF
[Old
Fail-safe: old value
[Pattern]
Fail-safe: byte pattern
* ... Parameter only changeable, if the connection to the EtherNet/IP controller is closed
► Save changed values on the device.
>
9.1.12 Info: Show device information
34065
To read the general information of the ifm IO-Link master:
► Select [Info] menu.
> The menu page shows the current settings.
Name
Description
Possible values
[Product code]
Article number of the IO-Link master
AL1323
[Device family]
Device family of the IO-Link master
IO-Link master
[Vendor]
Vendor
ifm electronic gmbh
[SW-Revision]
Firmware of the IO-Link master
[HW revision]
Hardware version of the IO-Link master
[Bootloader revision]
Bootloader version of the IO-Link master
[Serial number]
Serial number
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
34
>
9.1.13 Firmware: Reset device to factory settings
33838
When the -Link master is reset, all parameters are set to the factory settings: IO
To reset the device to factory settings:
► Select [Firmware] menu.
> The menu page shows the current settings.
► Click on [Factory Reset] to reset the device.
> LR DEVICE sets the device to the factory settings.
>
9.1.14 Firmware: Reboot the device
33832
When rebooting the device, all settings are kept.
To restart the AL1323:
► Select [Firmware] menu.
> The menu page shows the current settings.
► Click on [Reboot] to reboot the device.
> LR DEVICE reboots the ifm IO-Link master.
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
35
>
9.1.15 Configure IO-Link devices
33856
To configure the IO-Link devices connected to the device with the LR DEVICEparameter setting
software:
Requirements:
> IO-Link master is correctly installed and connected to the LR DEVICE parameter setting software.
> The IO-Link device is connected correctly with the AL1323.
> Operating mode of the IO-Link port is "IO-Link" ( → IO-Link ports: Configure operating mode
( )). → p. 31
> IoT has write access rights to the IO-Link master ( → IoT: Configuring access rights ( → p. 26)).
1 Select IO-Link master
► Start LR DEVICE.
► Update IODD file library
OR:
Import IODD file of the IO-Link device manually.
► Scan network for devices.
> LR DEVICE detects IO-Link master.
2 Add IO-Link device
► Under [ONLINE]: Click on the required -Link master. IO
> LR DEVICE automatically detects the IO-Link devices connected to the IO-Link master (e.g. ifm sensor KG5065).
3 Configure IO-Link device
► Mouse click on the port to which the IO-Link device is connected.
> LR DEVICE reads and shows the current parameter values of the IO-Link device.
► Configure IO-Link device.
Information about the available parameters of the IO-Link device: IO Device Description →
(IODD) des IO-Link Devices
► Save the changed configuration on the IO-Link device.
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
36
9.2 ifm IoT Core
Content
Programmers' notes ............................................................................................................................... 37
First steps ..............................................................................................................................................40
General functions ................................................................................................................................... 41
IoT: Configuring access rights ................................................................................................................ 45
IoT: Configuring IP settings .................................................................................................................... 45
IoT: Configuring the LR AGENT or LR SMARTOBSERVER interface .................................................. 46
IoT: Configuring security mode ..............................................................................................................46
Fieldbus: Configuring IP settings ............................................................................................................ 49
Fieldbus: Selecting the configuration mode ........................................................................................... 49
Fieldbus: Setting fail-safe values ............................................................................................................ 50
IO-Link ports: Setting the operating mode of pin 4 (US) ........................................................................ 50
IO-Link ports: Configuring device validation and data storage ............................................................... 50
IO-Link ports: Configuring data transfer to LR AGENT or LR SMARTOBSERVER .............................. 52
IO-Link ports: Reading / writing process data ........................................................................................ 52
IO-Link ports: Indicating port events ....................................................................................................... 55
IO-Link devices: Accessing parameters ................................................................................................. 55
IO-Link devices: Reading an writing device information ........................................................................ 57
IO-Link devices: Indicating IO-Link events ............................................................................................. 57
Gateway: Resetting, rebooting and localising the device ....................................................................... 57
Gateway: Reading device information .................................................................................................... 58
Gateway: Reading status and diagnostic information ............................................................................ 58
Gateway: Updating the firmware ............................................................................................................ 59
Gateway: Setting the application tag .................................................................................................... 60
Subscribing to notifications ..................................................................................................................... 61
Using Web Socket .................................................................................................................................. 64
MQTT support ........................................................................................................................................ 66
Using the IoT-Core Visualizer ................................................................................................................ 70
52244
General notes on the ifm IoT Core: ( ) → Programmers' notes → p. 37
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
37
9.2.1 Programmers' notes
Content
IoT Core: General information ................................................................................................................ 37
Access the ifm IoT Core ......................................................................................................................... 38
IoT Core: Diagnostic codes .................................................................................................................... 40
34229
>
IoT Core: General information
52256
The DataLine device family has an IoT Core. The IoT Core allows the user to address the AL1323
from IT networks via a REST API and to integrate it into Internet- -Things applications. of
A device description is stored on the AL1323. This device description is a structured,
machine-readable data object in JSON format. All current values of parameters, process data,
diagnostic data and device information are mapped in this data object. These data values can be read
and changed by means of services.
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
38
>
Access the ifm IoT Core
52257
The user can access the ifm IoT Core via HTTP requests. The following request methods are
available.
>
GET request
33804
Using the GET method the user has read access to a data point.
The syntax of the request to the IoT Core is:
http://ip/datapoint/service
Parameter
Description
ip
IP address of the IoT interface
data_point
Data point which is to be accessed
service
Service
The syntax of the return of the IoT Core is:
{
"cid":id,
"data":{"value":resp_data},
"code":diag_code
}
Parameter
Description
id
Correlation ID for the assignment of request and return
resp_data
Value of the data point; depending on the data type of the data point
diag_code
Diagnostic code ( ( →IoT Core: Diagnostic codes →p. 40))
>
Example: GET request
54033
Request (via browser):
http://192.168.0.250/devicetag/applicationtag/getdata
Response:
{
"cid":-1,
"data":{"value":"AL1323"},
"code":200
}
>
POST request
54700
Using a POST request the user has read and write access to a data point.
The syntax of the request to the IoT Core is:
{
"code":"code_id",
"cid":id,
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
39
"adr":"data_point/service",
"data":{req_data},
"auth":{"user":"usr_id","passwd":"password"}
}
Field
Parameter
Description
code
code_id
Service class
▪ request
Request
▪ transaction
Transaction
▪ event
Event
cid
id
Correlation ID for the assignment of request and response; ID freely assignable by the user
adr
data_point
Data point of the element tree which is to be accessed
service
Service to be performed ( ( → Overview: IoT services → p. 154))
data*
req_data
Data to be transferred to the IoT Core (e.g. new values); syntax depending on the service
auth**
usr_id
user name (base64 coded); default value: administrator
password
password (base64 coded)
* = optional; only required for services, that submit data to the IoT core (e. g. setdata)
** = optional; only required, if security mode is activated
The syntax of the return of the IoT Core is:
{
"cid":id,
"data":{resp_data},
"code":diag_code
}
Field
Parameter
Description
cid
id
Correlation ID for the assignment of request and response (see request)
data*
resp_data
Value of the data point; syntax depending on the service
code
diag_code
Diagnostic code ( ( → IoT Core: Diagnostic codes → p. 40))
* = optional; only required for services, that receive data from the IoT core (e.g. getdata)
>
Example: POST request
54035
Request:
{
"code":"request",
"cid":4711,
"adr":"devicetag/applicationtag/getdata"
}
Response:
{
"cid":4711,
"data":{"value":"AL1323"},
"code":200
}
>
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
40
IoT Core: Diagnostic codes
54688
Code
Text
Description
200
OK
Request successfully processed
230
OK but needs reboot
Request successfully processed; IO-Link master must be restarted
231
OK but block request not finished
Request successfully processed; blockwise request, but not yet
finished
232
Data has been accepted, but internally modified
New values have been accepted, but were adjusted by the IO-Link
master (Master cycle time)
233
IP settings (of IoT-Port) have been updated.
Application needs to reload device. Wait at least
1 second before reloading device.
IP settings have been successfully changed, IO-Link master will be
reloaded; wait for at least 1 second
400
Bad request
Invalid request
401
Unauthorized
Non authorised request
403
Forbidden
Forbidden request
500
Internal Server Error
Internal fault
503
Service Unavailable
The service is not available (e. -Link port in wrong operating g. IO
mode; no IO-Link device at IO-Link port)
530
The requested data is invalid
Invalid process data
531
IO-Link error
Error in IO-Link Master / device
532
PLC connected Error
Error while setting data, because IO-Link master is still connected
to fieldbus PLC
>
9.2.2 First steps
52245
To read the device description of the AL1323:
► Send the following POST request to the AL1323:
{"code":"request","cid":-1,"adr":"gettree"}
> AL1323 returns the device description as structured JSON object.
► Identify all substructures and the data points contained therein in the tree structure of the JSON
object.
► Identify the applicable services for the access to substructures and the data points contained
therein.
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
41
>
9.2.3 General functions
61148
The AL1323 has the type device ( ( )). →Overview: IoT types →p. 153
The following services can be used on the root element of the type : device
Service
Description
../gettree
Provide the complete tree or subtree of the device description (JSON)
../getidentity
Reading device information
../getdatamulti
Reading several parameter values sequentially
../getelementinfo
Reading detailed information of an element
../getsubscriberlist
Print a list of all active notification subscriptions
../querytree
Search device description for specific elements
Depending on the read and write access rights, the following services can be applied to elements of
type : data
Service
Description
../getdata
Reading the value of the element
../setdata
Write the value of the element
>
Example: Reading properties of an element
59782
Task: Determine the data type and value range of the accessrights parameter.
Solution: Read the properties of the element of the getelementinfo service. iotsetup/accessrights
The fields type (data type) and valuation (range of values) contain the required information.
• Request:
{
"code":"request",
"cid":4711,
"adr":"getelementinfo",
"data":{"adr":"iotsetup/accessrights"}
}
• Response:
{
"cid":4711,
"data":{
"identifier":"accessrights",
"type":"data",
"uid":null,
"profiles":["parameter"],
"format":{
"type":"enum",
"namespace":"json",
"encoding":"integer",
"valuation":{
"valuelist":{
"0":"Fieldbus + IoT",
"1":"Fieldbus + IoT (read-only)",
"3":"IoT only"}}}},
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
42
"code":200
}
The accessrights parameter has the data type ENUM with the valid values "Fieldbus + IoT", "Fieldbus
+ IoT (read only)" and "IoT only".
>
Example: output subtree
61149
Task: Output all direct sub-elements of the node . firmware
Solution: Use the service gettree to output the required subtree (root node: rmware, sub-levels to be
shown: 1)
• Request:
{
"code":"request",
"cid":4711,
"adr":"gettree",
"data":{
"adr":"firmware",
"level":1}
}
• Response:
{
"cid":4711,
"data":{
"identifier":"firmware",
"type":"structure",
"profiles":[
"software","software/uploadablesoftware"],
"subs":[
{
"identifier":"version","type":"data","profiles":["parameter"],
"format":{"type":"string","namespace":"json","encoding":"UTF-8"}},
{
"identifier":"type","type":"data",
"format":{"type":"string","namespace":"json","encoding":"UTF-8"}},
{
"identifier":"install","type":"service"},
{
"identifier":"factoryreset","type":"service"},
{
"identifier":"signal","type":"service"},
{
"identifier":"container","type":"data",
"format":{"type":"binary","namespace":"json","encoding":"base64"}},
{
"identifier":"reboot","type":"service"}]
},
"code":200
}
>
Example: Read several parameter values of the IO-Link master simultaneously
33840
Task: The following current values are to be read by the IO- nk master: temperature, serial number Li
Solution: Read the current parameter values using the getdatamulti service (data point temperature:
/processdatamaster/temperature; data point serial number: /deviceinfo/serialnumber)
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
43
• Request:
{
"code":"request",
"cid":4711,
"adr":"/getdatamulti",
"data":{"datatosend":["/processdatamaster/temperature","/deviceinfo/serialnumber"]
}
}
• Response:
{
"cid":4711,
"data":{"processdatamaster/temperature":{"code":200,"data":44},
"deviceinfo/serialnumber":{"code":200,"data":"000174210147"}},
"code":200
}
>
Example: Browsing device description
61150
Task: List all elements with the designation "status" and the prole "runcontrol".
Solution: Use the service querytree to browse the device description with the parameters "status"
(name) and "runcorntrol" (prole)
• Request:
{
"cid":4711,
"adr":"querytree",
"code": request","
"data":{
"profile":"runcontrol",
"name":"status"}
}
• Response:
{
"cid":4711,
"data":{
"adrList":[
"device/connections/mqttConnection/status",
"device/connections/mqttConnection/mqttCmdChannel/status"]},
"code":200
}
>
Setting the storage duration
61153
The IoT Core oers the possibility to set the storage duration of data and notications. The Services
Service: setdata ( ) and ( →p. 164 Service: subscribe →p. ) therefore have the parameter 166
"duration".
>
Example: Subscribing to notications
61154
Task: The current values of the following parameters are to be sent regularly to a network server with
IP address 192.168.0.4:
• Product name of the IO-Link Devices an IO-Link port X02
• Cyclic input data of the IO-Link Devices an IO-Link port X02
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
44
• Operating temperature of the IO-Link master.
The subscription is only to be active until the next restart of the IO-Link master.
Solution: Subscribe to the required data using the subscribe service.
• Request:
{
"code":"request",
"cid":4711,
"adr":"/timer[1]/counter/datachanged/subscribe",
"data":{
"callback":"http://192.168.0.4:80/temp",
"datatosend":[
"/iolinkmaster/port[2]/iolinkdevice/productname",
"/iolinkmaster/port[2]/iolinkdevice/pdin",
"/processdatamaster/temperature"],
"duration":"uptime"}
}
• Response:
{
"cid":4711,
"code":200
}
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
45
>
9.2.4 IoT: Configuring access rights
59785
Substructure: iotsetup
Available data points:
Name
Description
Access
../accessrights
Access rights to the IO-Link master
rw
rw ... read and write
If in IoT and EtherNet/IP projection software the parameter [Access Rights] is = [EtherNet/IP +
IoT], the parameter values set in the EtherNet/IP projection software will always apply.
If in IoT the parameter [Access Rights] is = [IoT only], set the parameter [Access Rights] =
[Keep settings] in the EtherNet/IP projection software.
If in LR DEVICE the parameter [Access Rigts] is = [EtherCAT + IoT (read-only)], write access
to the device conguration via LR DEVICE and IoT core services is blocked. To enable write
access again, set the parameter to [EtherCAT + IoT] via eldbus conguration software.
Changes of the parameter [Access Rights] will only be eective after restarting the IO-Link
master ( →Firmware: Reboot the device ( )). →p. 34
>
9.2.5 IoT: Configuring IP settings
61155
Substructure: iotsetup
Available data points:
Name
Description
Access
../network/dhcp
Conguration of the IP settings of the IoT port
rw
../network/ipaddress
IP address of the IoT port
rw
../network/subnetmask
Subnet mask of the network segment
rw
../network/ipdefaultgateway
IP address of the network gateway
rw
rw ... read and write
Applicable services:
Name
Description
../network/setblock
Write all values of the substructure blockwise
Change the IP parameters in the substructure network only blockwise with the setblock
service!
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
46
>
9.2.6 IoT: Configuring the LR AGENT or LR SMARTOBSERVER interface
59786
Substructure: iotsetup
Avalable data points:
Name
Description
Access
../smobip
IP address of the LR SMARTOBSERVER
rw
../smobport
Port number of the LR SMARTOBSERVER
rw
../smobinterval
Cycle time for data transmission to LR SMARTOBERVER (value in
milliseconds)
rw
rw ... read and write
>
9.2.7 IoT: Configuring security mode
54683
The access to the IoT interface of the IO-Link master can be protected with a security mode:
Substructure: iotsetup
Available data points:
Name
Description
Access
../security/securitymode
active security mode
rw
../security/password
Password for authentication (Base64 coded)
w
rw ... read and write
w ... write only
Valid character set for the Base64 coding / decoding of the password: UTF-8
Online tool for coding / decoding: →www.base64encode.org)
>
Note: Security mode
54684
The security mode enables restricting access to the IO-Link master and the connected IO-Link devices
from the IT network. In the activated security mode, the following restrictions apply:
• Access only with authentication (password-protected user account)
• Access only via secure https connection (Transport Layer Security - TLS)
The security mode only protects the access to the device via the IoT interface.
The standard value for users is: administrator
The set password cannot be read with getdata.
The current status of the security function can be read with the getidentity service ( →Servicet:
getidentity ( )). →p. 157
For the authentication, the user must additionally provide the POST requests with a valid user name
and password in the eld "auth". The user name and the password will be shown as Base64-coded
character strings ( →Example: Request with authentication ( →p. 47)).
The following requests can be done if the security mode is enabled, also without authentication:
• /getidentity
• /deviceinfo/vendor/getdata
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
47
• /deviceinfo/productcode/getda ta
>
Example: Activate security mode
54701
Task: Activate the security mode of the IO-Link interface of the IO-Link master. Set the password
"password" (Base64 coded: cGFzc3dvcmQ=)
Solution: The activation sonsists of 2 steps:
1 Activate security mode
Use service setdata with datapoint iotsetup/security/securitymode to activate the security mode.
• Request:
{
"code":"request",
"cid":-1,
"adr":"/iotsetup/security/securitymode/setdata",
"data":{"newvalue":"1"}
}
• Response:
{
"cid":-1,
"code":200
}
2 Set required password
Use service setdata with data point iotsetup/security/password to set the required password.
• Request:
{
"code":"request",
"cid":-1,
"adr":"/iotsetup/security/password/setdata",
"data":{"newvalue":"cGFzc3dvcmQ="}
}
• Response:
{
"cid":-1,
"code":200
}
>
Example: Request with authentication
54685
Task: The temperature of the IO-Link master is to be read. The security function is enabled (current
password: password).
Solution: Read the data point processdatamaster/temperature with the getdata service. The request
must be sent using https. The user name and the password are transferred as a Base64-coded
character string ("administrator" = "YWRtaW5pc3RyYXRvcg==", "password" = "cGFzc3dvcmQ=")
• Request:
{
"code":"request",
"cid":-1,
"adr":"processdatamaster/temperature/getdata",
"auth":{"user":"YWRtaW5pc3RyYXRvcg==","passwd":"cGFzc3dvcmQ="}
}
• Response:
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
48
{
"cid":-1,
"data":{"value":37},
"code":200
}
>
Example: reset password
54686
Task: The existing password is to be reset.
Solution: To reset a password, disable the security mode. To disable it, enter the user name and the
password (the elds "user" and "passwd").
• Request:
{
"code":"request",
"cid":-1,
"adr":"iotsetup/security/securitymode/setdata",
"data":{"newvalue":0},
"auth":{"user":"YWRtaW5pc3RyYXRvcg==","passwd":"SW9UNGlmbQ=="}
}
• Response:
{
"cid":-1,
"code":200
}
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
49
>
9.2.8 Fieldbus: Configuring IP settings
59783
Substructure: fieldbussetup
Available data points:
Name
Description
Access
../hostname
Name of the IO-Link master in the eldbus project
rw
../eldbusrmware
Firmware version of the IO-Link master
r
../network/macaddress
MAC address of the eldbus port
r
../network/ipaddress
IP address of the eldbus port
rw*
../network/subnetmask
Subnet mask of the network segment
rw*
../network/ipdefaultgateway
IP address of the network gateway
rw*
../network/dhcp
Conguration of the IP settings of the eldbus interface
rw
../connectionstatus
Status of the connection to the EtherNet/IP network
r
r ... read only
rw ... read and write
* ... only changeable, if the EtherNet/IP controller is not in RUNNING state
Applicable services:
Name
Description
../network/setblock
Write all values of the substructure at once
Change the IP parameters in the substructure only blockwise by using the service network
setblock!
>
9.2.9 Fieldbus: Selecting the configuration mode
52486
Substructure: fieldbussetup/configuration
Available data points:
Name
Description
Access
../in dependentmode
Set the conguration mode (Top-down, Independent)
r/w*
../explicitpdmode
Connection types
r/w*
../processdataconguration
Length of the process input data and process output data
rw*
../conguration/swap
Byte order of process data
r/w*
rw ... read and write
* ... only changeable, if the EtherNet/IP controller is not in RUNNING stated
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
50
>
9.2.10 Fieldbus: Setting fail-safe values
61120
Substructure: fieldbussetup/configuration/port[n] ( )n = 1...8
Available data points:
Name
Description
Access
../failsafedigitalout
Fail-safe value for the digital output - pin 4 (DO)
rw*
../failsafeiolink
Fail-safe value for IO-Link output data - pin 4 (IO-Link)
rw*
rw ... read and write
* ... can only be changed if EtherNet/IP PLC is not in RUNNING state
>
9.2.11 -Link ports: Setting the operating mode of pin 4 (US) IO
59793
Substructure: iolinkmaster/port[n] (n = 1...8).
Available data points:
Name
Description
Access
../mode
Operating mode of the IO-Link port
rw*
../mastercycletime_preset
Cycle time of the data transfer at the IO-Link port (value in ms)
rw*
../mastercycletime_actual
Current cycle time of the data transfer at the IO-Link port (value in ms)
r
../comspe ed
Data transfer rate of the IO-Link port
r
r ... read only
rw ... read and write
* ... only changeable, if the <Feldsbus> plc is not in RUNNING state
>
9.2.12 -Link ports: Configuring device validation and data storage IO
59792
Substructure: iolinkmaster/port[n] (n = 1...8).
Available data points:
Name
Description
Access
../validation_datastorage_mode
Response of the IO-Link port when a new IO-Link device is connected
rw*
../validation_vendorid
IO-Link ID of the manufacturer that is to be validated
rw*
../validation_deviceid
IO-Link ID of the device that is to be validated
rw*
../datastorage
Structure for port data storage
rw
../datastorage/maxsize
Maximum size of the data storage content (in bytes)
r
../datastorage/chunksize
Size of a data segment (in bytes)
r
../datastorage/size
Size of the data storage content (in bytes)
r
r ... read only
rw ... read and write
* ... can only be changed if the EtherNet/IP PLC is not in RUNNING state
Applicable services:
Service
Description
../validation_useconnecteddevice
Validate the IO-Link device connected to the IO-Link port*
../datastorage/getblobdata
Reading the content of the data storage area
../datastorage/stream_set
Transfer an individual data segment*
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
51
../datastorage/start_stream_set
Start sequential transmission of several data segments*
* ... can only be changed if the EtherNet/IP PLC is not in the RUNNING state
>
Example: Clone the Data Storage of an IO-Link port
52344
Task: Save the Data Storage of IO-Link port X02 of IO-Link master 1 and restore the data at IO-Link
master 2.
Solution: The cloning process consists of 2 steps. In the rst step, the Data Storage of the IO-Link
port of -Link master 1 is saved. In the second step, the saved data is restored at the Data Storage of IO
port IO-Link port of -Link master 2. IO
Save Data Storage:
1 Preparations
► Read size of segments of Data Storage (h = number of bytes):
{"code":"request", "cid" -1,"adr":"/iolinkmaster/port[2]/datastorage/chunksize/getdata"} :
Example: h = 256
► Read total size of Data Storage area (g = number of bytes):
{"code": "request", "cid": -1, "adr": "/iolinkmaster/port[2]/datastorage/size/getdata"}
Example: g = 550
► Calcuate the number of reading steps n: n = first integer value to which the following applies: g < n*h
Example: n= 3, because 550 < 3*256
2 Read Data Storage of IO-Link port
► Read Data Storage segment by segment ("pos" is the byte offset, at which the reading process with length "length"
starts).
{"code": "request", "cid": -1, "adr": "/iolinkmaster/port[2]/datastorage/getblobdata", "data": {"pos": 0, "length": h}}
{"code": "request", "cid": -1, "adr": "/iolinkmaster/port[2]/datastorage/getblobdata", "data": {"pos": h, "length": h}}
{"code": "request", "cid": -1, "adr": "/iolinkmaster/port[2]/datastorage/getblobdata", "data": {"pos": 2*h, "length": h}}
...
{"code": "request", "cid": -1, "adr": "/iolinkmaster/port[2]/datastorage/getblobdata", "data": {"pos": n*h, "length": h}}
Example:
1st read request: pos = 0, length = 256
2nd read resquest: pos = 256, length =256
3rd read request: pos = 512, length = 256
> Each segment value will be returned as BASE64 coded string.
► Join segments.
Restore Data Storage:
1 Preparations
► Determine the size of the saved Data Storage value (n = number of bytes).
Example: n = 550
► Read size of segments (s = number of bytes):
{"code":"request", "cid": -1,"adr":"/iolinkmaster/port[1]/datastorage/chunksize/getdata"}
Example: s = 256
2 Transfer Data Storage strings
► Start transfer of Data Storage string ("size" = size of Data Storage string):
{"code":"request", "cid": -1, "adr":"/iolinkmaster/port[1]/datastorage/start_stream_set", "data": {"size": n}}
Example: size = 550
► Transfer Data Storage string segment by segment ("value" = string value of length s):
{"code": "request", "cid": -1, "adr": "/iolinkmaster/port[1]/datastorage/stream_set", "data": {"value":
"aWZtfgIAAABBTDF4NXhfY25faXRfdDIuMi43Nw..."}
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
52
>
9.2.13 -Link ports: Configuring data transfer to LR AGENT or LR IO
SMARTOBSERVER
59795
Substructure: iolinkmaster/port[n] (n = 1...8).
Available data points:
Name
Description
Access
../senddatatosmob
Process data to LR AGENT or LR SMARTOBSERVER
rw
rw ... read and write
>
9.2.14 -Link ports: Reading / writing process data IO
61156
Substructure: iolinkmaster/port[n] (n = 1...8)
Available data points:
Name
Description
Access
../pin2in
Value -Link port of the digital input on pin 2 of the IO
r
../iolinkdevice/pdin
Value of the -Link input on pin 4 of the IO-Link port IO
r
../iolinkdevice/pdout
Value of the IO-Link output on pin 4 of the IO-Link port
rw*
r ... read only
rw ... read and write
*... can only be changed if the eldbus PLC is not in RUNNING state
>
Example: Read IO-Link process data (operating mode "IO-Link")
33842
Task: Read the current measured value of the ifm temperature sensor TN2531 at IO-Link port X02
Solution: Read the data point for the process input data with the service. getdata
• Request:
{
"code":"request",
"cid":4711,
"adr":"/iolinkmaster/port[2]/iolinkdevice/pdin/getdata"
}
• Response:
{
"cid":4711,
"data":{"value": "03C9"},
"code":200
}
The return value is given in hexadecimal format. Besides the temperature value the return value
comprises additional information ( IO Device Description (IODD) of the sensor). The temperature →
value is shown in bits 2 to 15.
0x03C9 = 0b 1111001001
Temperature value: 0b11110010 = 242
Therefore: The current temperature value is 24.2 °C.
>
Example: Writing IO-Link value (operating mode "IO-Link")
59804
Task: Switch on the buzzer of DV2500 at IO-Link Port X2. The DV2500 operates in On/O mode.
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
53
Solution: The IODD of the DV2500 shows the structure of the IO-Link process value ( e.g. LED →
activity). The buzzer will be switched using bit 40 of the process value (OFF = 0, ON = 1).
To switch the buzzer:
1. Read the current process value ( →Example: Read IO-Link process data (operating mode
"IO-Link") ( →p. 52)).
2. t bit 40 of the read value to 1. Se
3. Write the process value to the IO-Link device.
Example:
Read process value:
0x0000 0000 004D = 0b0000 0000 0000 0000 0000 0000 0 0000 1101 0000 000 0000 0100
New process value:
0b0000 000 0000 0000 0000 0000 0000 0000 0100 1101 = 0x0100 0000 004D 1 0000 0000
• Request:
{
"code":"request",
"cid":10,
"adr":"iolinkmaster/port[2]/iolinkdevice/pdout/setdata",
"data":{"newvalue":"01000000004D"}
}
• Response:
{
"cid":10,
"code":200
}
>
Example: Writing digital output (operating mode "DO")
59803
Task: Set the output value of the IO-Link devices at IO-Link Port X1 to "ON". The operating mode of
the IO-Link port is "Digital Output (DO)".
Solution: Write the value 1 to data point pdout. The value has to be written as hexadecimal value with
a length of 1 byte (OFF = "00", ON = "01").
• Request:
{
"code":"request",
"cid":10,
"adr":"iolinkmaster/port[1]/iolinkdevice/pdout/setdata",
"data":{"newvalue":"01"}
}
• Response:
{
"cid":10,
"code":200
}
>
Example: Reading digital input (operating mode "DI")
59802
Task: Read the current input value of the IO-Link device at IO-Link port X5. The operating mode of the
IO-Link port is "Digital Intput (DI)".
Solution: Read the value of data point pdin. The value will be returned as hexadecimal value with a
length of 1 byte (OFF = "00", ON = "01"').
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
54
• Request:
{
"code":"request",
"cid":10,
"adr":"iolinkmaster/port[5]/iolinkdevice/pdin/getdata"
}
• Response:
{
"cid":10,
"data":{"value":"00"},
"code":200
}
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
55
>
9.2.15 -Link ports: Indicating port events IO
59796
Substructure: iolinkmaster/port[n] (n = 1...8).
Available data points:
Name
Description
Access
../portevent
Indication of the following events at IO-Link port n:
▪ plugging -Link device IO
▪ pulling IO-Link device
▪ changing operating mode of IO-Link port
r
r ... read only
Subscribing events: → Subscribing to notifications ( ) → p. 61
>
9.2.16 -Link devices: Accessing parameters IO
59800
The ifm IoT Core supports the configuration of the connected IO-Link devices. A parameter is
accessed via -Link index and subindex ( IO Device Description (IODD) of the device). IO →
Substructure: iolinkmaster/port[n]/iolinkdevice (n = 1...8)
Applicable services:
Service
Description
../iolreadacyclic
Read a parameter of an IO-Link device (acyclic)
../iolwriteacyclic
Write a parameter of an IO-Link device (acyclic)
>
Example: Read the parameter value of an IO-Link device
33847
Task: Read the serial number of the ifm temperature sensor TN2531 at IO-Link port X02
Solution: Read the serial number with the service from the IO-Link device (index: iolreadacyclic
21, subindex: 0)
• Request:
{
"code":"request",
"cid":4711,
"adr":"/iolinkmaster/port[2]/iolinkdevice/iolreadacyclic",
"data":{"index":21,"subindex":0}
}
• Return:
{
"cid":4711,
"data":{"value":"4730323134323830373130"},
"code":200
}
The returned value is given in hexadecimal format. The conversion of the HEX value in a STRING
value is: G0214280710
>
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
56
Example: Change the parameter value of an IO-Link device
33844
Task: Set the output configuration OUT1 of the ifm temperature sensor TN2531 at IO-Link port X02 to
the value "Hnc / hysteresis function, normally closed".
Solution: Change the parameter [ou1] of the sensor to the value 4 using the iolwriteacyclicdata
service. The parameter can be accessed via IO-Link index 580, subindex 0 ( -Link description of → IO
the sensor).
• Request:
{
"code":"request",
"cid":4711,
"adr":"/iolinkmaster/port[2]/iolinkdevice/iolwriteacyclic",
"data":{"index":580,"subindex":0,"value":"34"}
}
The value has to be given in hexadecimal format. The conversion of the STRING value in a HEX value
is: 34.
• Response:
{
"cid":4711,
"code":200
}
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
57
>
9.2.17 -Link devices: Reading an writing device information IO
59797
Substructure: iolinkmaster/port[n]/iolinkdevice (n = 1...8)
Available data point s:
Name
Description
Access
../status
Status of the connected IO-Link device
r
../vendorid
IO-Link ID of the vendor
r
../deviceid
IO-Link ID of the IO-Link device
r
../productname
Product name of the IO-Link device
r
../serial
Serial number of the IO-Link device
r
../applicationspecifictag
Device-specific identification (application tag)
rw
r ... read only
rw ... read and write
>
9.2.18 -Link devices: Indicating IO-Link events IO
59798
Substructure: iolinkmaster/port[n]/iolinkdevice (n = 1...8).
Available data points:
Name
Description
Access
../iolinkevent
Indication of IO-Link events
r
r ... read only
Subscribing events: → Subscribing to notifications ( ) → p. 61
>
9.2.19 Gateway: Resetting, rebooting and localising the device
59790
Substructure: firmware
Applicable services:
Name
Description
../factoryreset
Reset IO-Link master to factory settings
../reboot
Reboot IO-Link master
../signal
Trigger the flashing of the status LED
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
58
>
9.2.20 Gateway: Reading device information
52254
Substructure: deviceinfo
Available data points:
Name
Description
Access
../productcode
Article number
r
../vendor
Manufacturer
r
../devicefamily
Device family
r
../hwrevision
Hardware revision
r
../serialnumber
Serial number
r
../revision
Firmware version
r
../bootloaderrevision
Bootloader version
r
../extensionrevisions
Firmware and bootloader version
r
../fieldbustype
Fieldbus
r
r ... read only
Additional information about the AL1323 can be read with the service (getidentity → Servicet:
getidentity ( )). → p. 157
>
9.2.21 Gateway: Reading status and diagnostic information
61157
Substructure: processdatamaster
Available data points:
Name
Description
Access
../temperature
Temperature of the IO-Link master (value in °C)
r
../voltage
Present voltage value of the supply voltage US (value in mV)
r
../current
Present current value of the sensor supply US (value in mA)
r
../supervisionstatus
Status of the device supply US
r
r ... read only
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
59
>
9.2.22 Gateway: Updating the firmware
59789
Substructure: firmware
Available data points:
Name
Description
Access
../version
Software version
r
../type
Software type
r
../container
Structure for updating the firmware
w
../container/maxsize
Maximum size of the container structure (in bytes)
r
../container/chunksize
Size of a data segment (in bytes)
r
../container/size
Size of the container content (in bytes)
r
r = only read
w = write only
Applicable services:
Name
Description
../install
Install firmware transferred to the IO-Link master
../container/stream_set
Transfer an individual data segment
../container/start_stream_set
Start sequential transmission of several data segments
>
Example: Update firmware
52252
Task:
Update the firmware of the device; size of the firmware file: 356676 bytes
Solution:
The firmware is transferred to the device in fragments (chunks). The size of the fragments depends on
the size of the flash memory of the IO-Link master. To transfer the firmware, the firmware file must be
converted into a character string using BASE64.
1 Preparations
► Determine the size of the fragments (g = number of bytes):
{"code":"request", "cid": -1, "adr":"/firmware/container/chunksize/getdata"}
► Convert the firmware file into a BASE64 string.
2 Start the transfer of the firmware
► Start the transfer of the firmware via the service start_stream_set (parameter "size": size of the firmware file):
{"code":"request", "cid": -1, "adr":"/firmware/container/start_stream_set", "data":{"size":356676}}
3 Load the firmware into the flash memory of the IO-Link master
► Send the BASE64 string of the firmware file to the IO-Link master fragment by fragment (value = string value with
length g).
{"code": "request", "cid": -1, "adr": "/firmware/container/stream_set", "cid": -1, "data": {"value":
"aWZtfgIAAABBTDF4NXhfY25faXRfdDIuMi43Nw..."}
► Repeat step 3 until all fragments of the firmware file have been sent to the IO-Link master.
> -Link master stores the segments received in the container area. IO
4 Install firmware
► Start the installation of the transmitted firmware.
{"code": "request", "cid": -1, "adr": "/firmware/install", "data": {}}
>
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
60
9.2.23 Gateway: Setting the application tag
59791
Substructure: devicetag
Available data points:
Name
Description
Access
../applicationtag
Name of the -Link master (application tag) IO
rw
rw ... read and write
For the storage of the applicationtag 32 bytes are available on the IO-Link master. If the
memory area is exceeded during writing with setdata, the IoT core aborts the write process
and returns the diagnostics code 400.
When writing the application tag, note the different memory requirements of the individual
UTF-8 characters:
• characters 0-127: 1 byte per character
• characters >127: more than 1 byte per character
>
Example: Change name of the IO-Link master
a33823
Task: Set the name of the IO-Link master to AL1323 for the representation in the
LR SMARTOBSERVER.
Solution: Change the parameter [Application Tag] with the setdata service to the value [AL1323].
The data point of the parameter [Application Tag] in the device description object is
/devicetag/applicationtag.
• Request:
{
"code":"request",
"cid":4711,
"adr":"/devicetag/applicationtag/setdata",
"data":{"newvalue":"AL1323"}
}
• Response:
{"cid":4711,"code":200}
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
61
>
9.2.24 Subscribing to notifications
61159
If a data point has the sub-element datachanged, the user can subscribe to notifications on value and
condition changes. Notifications can be triggered by the expiration of a timer or an event. The IoT Core
supports the output of notifications in CSV or JSON format.
Available data points:
Name
Description
Access
timer[x]/counter
Timer for triggering a notification
rw
timer[x]/interval
Cycle time of the update of the subscribed values
rw
iolinkmaster/port[n]/portevent
Display of the following events on IO-Link port n:
▪ -Link device connected IO
▪ -Link device disconnected IO
▪ Operating mode of the IO-Link port changed
rw
iolinkmaster/port[n]/iolinkdevice/iolinkevent
Display of IO-Link events
rw
r ... read only
rw ... read and write
x = [1,2]
n = 1...8
Applicable services:
Name
Description
../datachanged/subscribe
Subsrscibe to notification
../datachanged/unsubsribe
Unsubscribe notification
../datachanged/getsubscriptioninfo
Show information about notifications
Additionally, the user can use ( ) show all active subscriptions. Service: getsubscriberlist → p. 158
>
Example: Subscribing to notifications
61160
Task: The current values of the following parameters are to be sent regularly to a network server with
IP address 192.168.0.4:
• cyclic input data of the IO-Link Devices an IO-Link port X02
• Operating temperature of the IO-Link master.
Solution: Subscribe to the required data using the subscribe service.
The following options are additionally available:
• via WebSockets (ws://): Example: Subscribing notifications via WebSocket ( → p. ) 64
• via MQTT (mqtt://): Example: Configuring the MQTT command channel ( → p. ) 67
• Request:
{
"code":"request",
"cid":4711,
"adr":"/timer[1]/counter/datachanged/subscribe",
"data":
{
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
62
"callback":"http://192.168.0.4:80/temp",
"datatosend":[
"/iolinkmaster/port[2]/iolinkdevice/pdin",
"/processdatamaster/temperature"]
}
}
In addition, the time interval of the timer[1] must be set to a value between 500 ms and
2147483647 ms.
• Request:
{
"code":"request",
"cid":4712,
"adr":"/timer[1]/interval/setdata",
"data":{"newvalue":500}
}
• Response:
{
"cid":4712,
"code":200
}
• Notication (JSON)
{
"code":"event",
"cid":4711,
"adr":"",
"data":{
"eventno":"6317",
"srcurl":"/timer[1]/counter/datachanged",
"payload":{
"/timer[1]/counter":{"code":200,"data":1},
"/processdatamaster/temperature":{"code":200,"data":39},
"/iolinkmaster/port[2]/iolinkdevice/pdin":{"code":200,"data":"03B0"}}}
}
>
Example: Changing a subscription
61161
Task: The existing subscription (Example: Subscribing to notications ( )) is to be changed. →p. 61
Instead of the temperature of the IO-Link master, the operating voltage applied is to be transmitted.
Solution: Overwrite the existing subscription. For this purpose, the parameter values for "cid" and
"callback" in the request must be the same as those of the existing subscription.
• Request:
{
"code":"request",
"cid":4711,
"adr":"/timer[1]/counter/datachanged/subscribe",
"data":{
"callback":"http://192.168.0.4:80/temp",
"datatosend":[
"/iolinkmaster/port[2]/iolinkdevice/pdin",
"/processdatamaster/voltage"]}
}
>
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
63
Example: Subscribing to notications in CSV format
61162
Task: Every 2 seconds, the current values of the following parameters are to be sent to a network
server with the IP address 192.168.0.4
• cyclic IO-Link input data of the IO-Link device at port X02
• Operating temperature of the IO-Link master.
The data should be transmitted in CSV format (comma separator).
Solution:
► Use the subscribe service to subscribe to the required data and set the output format to "csv0".
Data in CSV format can only be sent via TCP protocol.
• Request:
{
"cid": 1,
"adr":"/timer[1]/counter/datachanged/subscribe",
"code":"request",
"callback":"tcp://192.168.50.59:1883/topic",
"codec":"csv0",
"data":{
"datatosend":[
"/iolinkmaster/port[2]/iolinkdevice/pdin",
"/processdatamaster/temperature"]}
}
► Set the interval of the timer to 2 seconds:
• Request:
{
"code":"request",
"cid":4712,
"adr":"/timer[1]/interval/setdata",
"data":{"newvalue":2000}
}
The cyclically sent notication has the following structure:
/timer[1]/counter/datachanged,6317,200,1,200,39,200,03B0
>
Example: Unsubscribing from notications
61163
Task: The existing subscription (Example: Subscribing to notications ( )) is to be deleted. →p. 61
Solution: Use the unsubscribe service to delete the subscription. For this purpose, the value of the
parameter "callback" in the request must be equal to the value of the existing subscription.
{
"code":"request",
"cid":4711,
"adr":"/timer[1]/counter/datachanged/unsubscribe",
"data":{
"callback":"http://192.168.0.4:80/temp"
}
>
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
64
Example: Checking subscriptions
61164
Task: Information about the existing subscription (Example: Subscribing to notications
( )Show →p. 61 Example: Subscribing to notications ( )). →p. 61
Solution: Use the service getsubscriptioninfo and the parameter values cid, "adr" and "callback" of the
existing subscription to retrieve the information.
• Request:
{
"code":"request",
"cid":4711,
"adr":"/timer[1]/counter/datachanged/getsubscriptioninfo",
"data":{
"callback":"http://192.168.0.4:80/temp"}
}
• Response:
{
"cid." 4711,
"data":{
"callback":"http://192.168.0.4:80/temp",
"datatosend":[
"/iolinkmaster/port[2]/iolinkdevice/productname",
"/iolinkmaster/port[2]/iolinkdevice/pdin",
"/processdatamaster/temperature"]},
"code":200
}
>
9.2.25 Using Web Socket
61165
The IoT Core supports communication via WebSocket protocol. With Web Sockets, the user can
establish a full-duplex communication channel via a TCP connection.
WebSockets can be used for the following services:
• subscribe / unsubscribe
Maximum number of WebSocket connections: 8
Fail-safe WebSocket connections (wss://) are not supported.
To transmit notications via a WebSockets connection:
► Establish the WebSocket connection (e.g. "ws://192.168.0.55:80/websocket")
• Option 1: without parameter "callback”
► make subscribe/unsubscribe request without parameter "callback".
> IoT-Core sends notications about existing WebSocket connections.
• Option 2. with parameter "callback”
► make subscribe/unsubscribe requests with parameter "callback" ( "ws:///myTopic").
> IoT-Core sends notications about existing WebSocket connections to the topic . myTopic
>
Example: Subscribing notications via WebSock et
61166
Task: The current values of the following parameters are to be sent regularly to the data sink myTopic
via an existing WebSocket connection:
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
65
• Product name of the IO-Link Devices an IO-Link port X02
• cyclic input data of the IO-Link Devices an IO-Link port X02
• Operating temperature of the IO-Link master.
Solution: Subscribe to the required data using the subscribe service.
• Request:
{
"code":"request",
"cid":4711,
"adr":"/timer[1]/counter/datachanged/subscribe",
"data":{
"callback":"ws:///myTopic",
"datatosend":[
"/iolinkmaster/port[2]/iolinkdevice/productname",
"/iolinkmaster/port[2]/iolinkdevice/pdin",
"/processdatamaster/temperature"]}
}
If the notications are to be transmitted via the existing WebSocket connection, but without a special
data sink, the callback parameter is not required.
• Request:
{
"code":"request",
"cid":4711,
"adr":"/timer[1]/counter/datachanged/subscribe",
"data":{
"datatosend":[
"/iolinkmaster/port[2]/iolinkdevice/productname",
"/iolinkmaster/port[2]/iolinkdevice/pdin",
"/processdatamaster/temperature"]}
}
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
66
>
9.2.26 MQTT support
61168
The IoT Core supports the MQTT protocol. The protocol allows an MQTT client to communicate with
the IoT Core via an MQTT broker to request and receive data. The IoT Core can publish data via the
MQTT connection.
>
Conguring the MQTT command channel
61169
To enable MQTT communication, the user needs to activate and congure an MQTT command
channel.
Substructure: connections/mqttConnection
Name
Description
Access
../type
Type of the connection (MQTT)
r
../status
Global MQTT status
r
../status/preset
Presetting of the MQTT status; Basic settings:
running
r
../MQTTSetup
Substructure for general MQTT settings
w
../MQTTSetup/QoS
Quality of Service of the MQTT communication
▪ 0: QoS Level 0 - PUBLISH (without
conrmation)
▪ 1: QoS Level 1 - PUBLISH > PUBREC
(one-time conrmation)
▪ 2: QoS Level - PUBLISH > PUBREC > 2
PUBREL > PUBCOMP (double conrmation)
rw
../MQTTSetup/version
MQTT version
r
../mqttCmdChannel
Substructure of the MQTT command channel
w
../mqttCmdChannel/type
Type of the MQTT command channel
r
../mqttCmdChannel/status
Status of the MQTT command channel
r
../mqttCmdChannel/status/preset
Presetting of the MQTT status; Basic setting:
stopped
r
../mqttCmdChannel/mqttCmdChannelSetup
Structure for settings of the command channel
w
../mqttCmdChannel/mqttCmdChannelSetup/brokerIP
IP address of the MQTT broker
rw
../mqttCmdChannel/mqttCmdChannelSetup/brokerPort
Port number of the MQTT broker
rw
../mqttCmdChannel/mqttCmdChannelSetup/cmdTopic
Designation of the MQTT topic
rw
../mqttCmdChannel/mqttCmdChannelSetup/defaultReplyTopic
Standard response topic
rw
Applicable services:
Name
Description
../status/start
Enable MQTT
../status/stop
Deactivate MQTT
../status/reset
Reset MQTT
../mqttCmdChannel/status/start
Activate MQTT command channel
../mqttCmdChannel/status/stop
Deactivate MQTT command channel
../mqttCmdChannel/status/reset
Reset MQTT command channel
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
67
Notes on the states of an MQTT connection: Note: Connection states ( ) →p. 67
To create an MQTT connection, perform the following steps in sequence:
Ensure that the MQTT broker can be reached and that the selected port of the MQTT broker is
enabled for data transmission.
Max. number of simultaneous MQTT connections: 10
Wildcards "+" and "#" in topics are not supported.
► Activate MQTT command channel.
► Set the IP address of the MQTT .
► Set the port number of the MQTT broker.
► Set topic.
► Set standard response topic.
> The command channel is created with the selected properties.
> The user can publish on the topic with the IoT Core.
> MQTT clients can subscribe to the topic.
>
Note: Connection states
61170
The following status diagram shows the inuence of the services "start", "stop" and "reset" on the
status of an MQTT connection:
After the initialisation in the "init" state has been completed, the connection automatically changes to
the "running" state.
The connection automatically switches to the "error" state if at least one of the following events occurs:
• no MQTT broker availab le
>
Example: Conguring the MQTT command channel
61171
Task: Conguring and activating the MQTT command channel (IP address MQTT broker:
192.168.82.100, port: 1883, topic: abc).
Solution:
► Check whether MQTT broker can be reached and the port has been released.
► Activate command channel
• Request:
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
68
{
"code":"request",
"cid":4711,
"adr":"/connections/mqttConnection/MQTTSetup/mqttCmdChannel/status/start"
}
► Set the IP address of the MQTT broker/server.
• Request:
{
"code":"request",
"cid":4712,
"adr":"/connections/mqttConnection/mqttCmdChannel/mqttCmdChannelSetup/brokerIP/set
data"
"data":{"192.168.82.100"}
}
► Set the port number of the MQTT broker/server.
• Request:
{
"code":"request",
"cid":4713,
"adr":"/connections/mqttConnection/mqttCmdChannel/mqttCmdChannelSetup/brokerPort/s
etdata"
"data":{"1883"}
}
► Set topic.
• Request:
{
"code":"request",
"cid":4714,
"adr":"/connections/mqttConnection/mqttCmdChannel/mqttCmdChannelSetup/cmdTopic/set
data"
"data":{"abc"}
}
► Set standard response topic.
• Request:
{
"code":"request",
"cid":4715,
"adr":"/connections/mqttConnection/mqttCmdChannel/mqttCmdChannelSetup/defaultReply
Topic/setdata"
"data":{"xyz"}
}
► Set the QoS.
• Request:
{
"code":"request",
"cid":4716,
"adr":"/connections/mqttConnection/MQTTSetup/QoS/setdata",
"data":{"QoS2"}
}
>
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
69
Example: Publish the temperature to an MQTT broker
54687
Task: Publish the temperature of the IO-Link master to an MQTT broker (IP address MQTT broker:
192.168.82.100, port: 1883, topic: abc
Solution:
• Request:
{
"code":"request",
"cid":-1,
"adr":"/timer[1]/counter/datachanged/subscribe",
"data":{
"callback":"mqtt://192.168.82.100:1883/abc",
"datatosend":["processdatamaster/temperature"}
}
• Response:
{
"c 1,id":-
"code":200
}
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
70
9.2.27 Using the IoT-Core Visualizer
Content
Managing notications ............................................................................................................................ 71
Searching for elements in the device tree .............................................................................................. 73
Conguring IO-Link the master .............................................................................................................. 74
Reading and writing process da ta .......................................................................................................... 75
Updating the rmware ............................................................................................................................ 76
61173
The ifm-IoT Core Visualizer of the IO-Link master provides a graphical user interface for accessing
functions of the ifm-IoT Core.
To start the IoT Core Visualizer:
► Start web browser.
► Call the following address: http://ipaddress/web/subscribe
> Browser shows IoT Core Visualizer:
The navigation menu gives the user access to the following functions:
• [Notication]: Creating and managing notications (subscribe / unsubscribe)
• [Elements]: Searching for elements in device description
• [Parameter]: Conguring IO-Link master
• [Processdata]: Reading and writing process data
• [Update]: Updating the rmware of the IO-Link master
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
71
>
Managing notications
61174
The menu page allows you to perform the following functions
• Creating notications
• Showing active notications
• Deleting notications (single, all)
Requirements:
• Iot-Core Visualizer has been started.
► Click on [Notication].
> The menu page for managing notications appears.
> The menu page shows all registered notifications in a table
>
Creating a new notification
61175
A wizard is used to register new notications.
Requirements:
• The [Notication] menu page is open.
► Click on [+] on the right side of the table.
> The wizard for the creation of notifications appears.
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
72
► Use the wizard to enter the required notication parameters step by step.
> Created notication subscription is displayed in the table.
For cyclical notications via timer[1] or timer[2], the user also needs to set the interval time of
the timer in question.
>
Deleting a notication
61176
Requirements:
• The [Notication] menu page is open.
• At least one notication is active.
► Click on [x] in the column [Unsubscribe].
> The selected notication will be deleted (unsubscribe).
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
73
>
Searching for elements in the device tree
61177
The [Elements] menu page allows you to search the device description for elements with specic
properties (status, prole, name) and to output the results.
Requirements:
• Iot-Core Visualizer has been started.
► Click on [Elements].
> The input mask appears.
► Enter the search criteria of the required item in the [identier], [prole] and [type] boxes.
► Click on [Search for ...].
> IoT-Core Visualizer searches device description for elements with selected search criteria.
> The result list shows all elements found.
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
74
>
Conguring IO-Link the master
61178
The [Parameter] menu page allows you to congure the IO-Link master.
Available options:
• Reading and writing individual parameters
• Backup and restore the current conguration of the machine.
Requirements:
• Iot-Core Visualizer has been started.
► Click on [Parameter].
> The menu page shows the available parameters of the -Link master. IO
> Current parameter values are displayed.
> Editable parameters can be changed.
To change a parameter:
► Navigate to the desired parameter in the device description.
► Changing the parameter value
► Click on the pencil icon to save the change on the IO-Link master.
> The changed parameter value is active.
► Optional: Repeat the procedure to change further parameter values.
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
75
>
Reading and writing process data
61179
The menu page allows the process data of the IO-Link master and the connected IO-Link devices to
be read and written.
Requirements:
• Iot-Core Visualizer has been started.
► Click on [Processdata].
> Menu page shows the substructures of the device description that contain process data and
events.
> The current process values are displayed.
> Editable process data can be changed.
To change the value of a process date:
► Navigate to the required process date in the device description.
► Change the process value.
► Click on the pencil icon to save the change on the IO-Link master.
> The changed process value is active.
► Optional: Repeat the procedure to change further process values.
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
76
>
Updating the rmware
61180
The [Update] menu page allows you to update the rmware of the IO-Link master:
Requirements:
• Iot-Core Visualizer has been started.
► Click on [Update].
> Menu page displays information about the current rmware version.
► Click on [Load software le] and select a new rmware le (*.bin).
► Click on [Update] to start the update process.
> The rmware of the IO-Link master will be updated.
> The area shows the progress bar.
> If the update process has been successful, the IO-Link master will restart automatically.
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
77
9.3 EtherNet/IP
Content
Registration of the EDS file .................................................................................................................... 77
Integrate the IO-Link Master into the EtherNet/IP project ...................................................................... 77
Set connection types and RPI ................................................................................................................ 78
Congure AL1323 ................................................................................................................................... 79
Congure IO-Link ports .......................................................................................................................... 80
Congure IO-Link devices ...................................................................................................................... 81
Read process data ................................................................................................................................. 82
Write process data .................................................................................................................................. 82
Read diagnostic and status information ................................................................................................. 83
EtherNet/IP: Programmers' notes ........................................................................................................... 84
34391
On the eldbus side, the device can be congured with any EtherNet/IP compatible projection
software.
The information in the following sections refers to the EtherNet/IP projection software RSLogix 5000.
>
9.3.1 Registration of the EDS file
34324
ifm provides an EDS le to integrate the AL1323 in a EtherNet/IP projection software. The user can
download the EDS le from the ifm website ( ). In the EDS le, all parameters, process →www.ifm.com
data, and their valid value ranges are dened.
To add the AL1323 to the device catalogue of RSLogix5000:
► Download the EDS file of the AL1323 from the ifm website.
► Start RSLogix5000.
► Select [Tools] > [EDS Hardware Installation Tool].
> EDS Wizard appears.
► Register the downloaded EDS file of the AL1323 with the EDS Wizard.
> EDS Wizard installs the EDS file and adds the AL1323 to the device catalogue.
>
9.3.2 Integrate the IO-Link Master into the EtherNet/IP project
34392
The AL1323 is integrated as module of an I/O scanner in the EtherNet/IP project.
Requirements:
> The EDS file of the AL1323 is installed ( →Registration of the EDS le ( →p. 77)).
1 Create/open EtherNet/IP project
► Start RSLogix 5000.
► Create new EtherNet/IP project.
OR
Open an existing EtherNet/IP project.
2 Configure EtherNet/IP PLC and IO scanner
► Select and configure EtherNet/IP controller and IO scanner.
> EtherNet/IP project includes a EtherNet/IP controller and an IO scanner.
3 Integrate AL1323 in project
► In the Controller Organizer: Right mouse click on the IO scanner.
> Context menu appears.
► In the context menu: Select [New Module...].
> The window [Select Module Type] appears.
► Select AL1323 and click on [Create].
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
78
> The [New Module] window appears.
► Enter name and IP address of the AL1323.
► Click on [OK] to adopt the entered values.
> RSLogix 5000 adds AL1323 as sub-element of the IO scanner to the project.
4 Save the project
► Save EtherNet/IP project
>
9.3.3 Set connection types and RPI
34407
The IO-Link master supports dierent connection types ( →Supported connection types ( )). →p. 95
The user can choose which object instances of the input assembly and the output assembly are used.
This makes it possible to adapt the size of the transmitted and received data. Additionaly the Request
Package Interval (RPI) can be selected.
To set the connection type:
Requirements:
> AL1323 is correctly integrated into the EtherNet/IP project ( →Integrate the IO-Link Master into the
EtherNet/IP project Example: Reading properties of an element ( →p. 77, " " → p. 41)).
1 Open the module properties
► In the Controller Organizer: Double-click on the IO-Link master node
> Dialogue window appears.
2 Set connection type
► Click on [Change.. .].
> The [Module Definition] dialogue window appears.
► Select the required connection type from the list [Connections].
► Click on [OK] to apply the changes.
3 Change RPI
► Click on [Connection] tab.
> The connection settings appear.
► Select required time value from [RPI] list.
► Click on [OK] to apply the changes.
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
79
>
9.3.4 Configure AL1323
34357
The AL1323 is congured via the controller tags.
Requirements:
> AL1323 is correctly integrated in the EtherNet/IP project ( →Integrate the IO-Link Master into the
EtherNet/IP project Example: Reading properties of an element ( →p. 77, " " → p. 41)).
1 Open controller tags
► In the Controller Organizer: Double click on [Controller Name_of_Project] > [Controller Tags]
> [Controller Tags] window appears.
► In the tree view: Click on [AL1323:C].
> Controller tags for the configuration of the device appear.
2 Configure AL1323
► Set the following controller tags as required:
Name
Description
Possible values
[AL1323:C.Communication_Prole]
The access rights to the
parameter data, process data
and events/diagnostic
messages of the IO-Link
master and the connected
IO-Link devices
0x00
EtherNet/IP + LineRecorder
▪ EtherNet/IP and LR DEVICE have read
and write access rights to parameters and
process data
▪ EtherNet/IP and LR DEVICE have read
access rights to events/alarms
0x01
EtherNet/IP + LineRecorder (ro)
▪ EtherNet/IP has read and write access
rights to parameters and process data
▪ EtherNet/IP has read access rights to
events/alarms
▪ LR DEVICE only has read access rights to
parameters, process data and
events/alarms
0x02
EtherNet/IP only
▪ EtherNet/IP has read and write access
rights to parameters and process data
▪ EtherNet/IP has read access rights to
events/alarms
▪ LR DEVICE has no access rights
(parameters, process data, events/alarms,
web interface, rmware update)
0x03
Continue in Use Case
previous setting is valid
[AL1323:C.Port_Process_Data_Size]
Length of the process input
data and process output data
0x00
2 bytes input, 2 bytes output
0x01
4 bytes input, 4 bytes output
0x02
8 bytes input, 8 bytes output
0x03
16 bytes input, 16 bytes output
0x04
32 bytes input, 32 bytes output
► Save EtherNet/IP project
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
80
>
9.3.5 Configure IO-Link ports
34365
The IO-Link ports are congured via the controller tags. The user can congure each IO-Link port
separately.
To congure the IO-Link ports:
Requirements:
> AL1323 is correctly integrated in the EtherNet/IP project ( →Integrate the IO-Link Master into the
EtherNet/IP project Example: Reading properties of an element ( →p. 77, " " → p. 41)).
1 Open controller tags
► In the Controller Organizer: Double click on [Controller Name_of_Project] > [Controller Tags]
> [Controller Tags] window appears.
► In the tree view: Click on [AL1323:C].
> Controller tags for the configuration of the device appear.
2 Configure IO-Link ports
► Configure the following tags for each IO-Link port at will:
Name
Description
Possible values
[AL1323:C.Port_Mode_Port_x]
Operating mode of the
IO-Link port
0x00
Interface deactivated
0x01
Operation as digital input (DI)
0x02
Operation as digital output (DO)
0x03
Operation as IO-Link interface
[AL1323:C.Port_Cycle_Time_Port_x]
Cycle time of the data
transmission between the
IO-Link master and the
IO-Link device
0x00
The device automatically sets the fastest
possible cycle time
0x01
2 milliseconds
0x02
4 milliseconds
0x03
8 milliseconds
0x04
16 milliseconds
0x05
32 milliseconds
0x06
64 milliseconds
0x07
128 milliseconds
[AL1323:C.Swap_Port_x]
Visualisation of the process
data
(EtherNet/IP uses Little
Endian Format (Intel), IO-Link
uses Big Endian Format
(Motorola))
0x00
Byte swapping for IO-Linkdata
deactivated
0x01
Byte swapping for IO-Linkdata activated
[AL1323:C.Validation_Data_Storage_Port_x]
Supported IO-Link standard
and behaviour of the IO-Link
master when connecting new
IO-Link devices to the IO-Link
port
0x00
No validation
0x01
Type compatible V1.0 device
0x02
Type compatible V1.1 device
0x03
Type compatible V1.1 device with
Backup + Restore
0x04
Type compatible V1.1 device with
Restore
[AL1323:C.Vendor_ID_Port_x]
Vendor ID of the
manufacturer of the device on
the IO-Link port
0x0000...0xFFFF
ifm electronic: 0x136
[AL1323:C.Device_ID_Port_x]
Device ID of the device on the
IO-Link port
0x000000...0xFFFFFF
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
81
Name
Description
Possible values
[AL1323:C.Fail_Safe_Mode_Port_x]
Fail-safe mode for output data
when the EtherNet/IP
connection is interrupted
0x00
No Failsafe
0x01
Failsafe Reset Value
0x02
Failsafe Old Value
0x03
Failsafe with Pattern
[AL1323:C.Fail_Safe_Value_DO_Port_x]
Fail-safe value for the
operating mode "digital output
(DO)"
0x00
Failsafe Reset Value
0x01
Failsafe Old Value
0x02
Failsafe Set Value
x = 1...8
► Save EtherNet/IP project.
>
9.3.6 Configure IO-Link devices
34359
The AL1323 supports the conguration of the connected IO-Link devices from the EtherNet/IP
projection software. For this, ifm oers the EtherNet/IP object "IO-Link Request" ( →IO-Link requests
(object class: 0x80) ( )). The object enables direct read and write access to IO-Link objects →p. 132
of the IO-Link device (Indexed Service Data Unit (ISDU)). The extent of the congurable parameters
depends on the -Link device. IO
The following services are available:
Name
Description
Reference
Read request
Send a request to read an IO-Link object
→ → (Read_ISDU ) p. 133
Write request
Send a request to write an IO-Link object
→ → (Write_ISDU ) p. 136
Information for the execution of acyclic commands: ( ) →Use acyclic services →p. 84
Available parameters of the IO-Link devices: Operating instructions of the IO-Link device →
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
100
>
Input assembly (Instance 100): I/O data + acyclic data + diagnosis data
34344
Byte
Content
0...1
Port X01...X08: Digital input - pin 2 / 4 (DI) ( ( →Mapping: digital input data (DI) →p. 103))
2...3
Status information ( ( →Mapping: Status information →p. 103))
4...45
Acyclic command area: Response channel ( ( →Response channel →p. 112))
46...47
Port X01: PQI ( ( →Mapping: PQI →p. 104))
48...63
Port X01: Diagnostic, vendor ID, device ID, events ( →Mapping: IO-Link device information + events
( →p. 105))
64...65
Port X02: PQI ( ( →Mapping: PQI →p. 104))
66...81
Port X02: Diagnostic, vendor ID, device ID, results ( →Mapping: IO-Link device information + events
( →p. 105))
82...83
Port X03: PQI ( ( →Mapping: PQI →p. 104))
84...99
Port X03: Diagnostic, vendor ID, device ID, events ( →Mapping: IO-Link device information + events
( →p. 105))
100...101
Port X04: PQI ( ( →Mapping: PQI →p. 104))
102...117
Port X04: Diagnostic, vendor ID, device ID, events ( →Mapping: IO-Link device information + events
( →p. 105))
118...119
Port X05: PQI ( ( →Mapping: PQI →p. 104))
120...135
Port X05: Diagnostic, vendor ID, device ID, events ( →Mapping: IO-Link device information + events
( →p. 105))
136...137
Port X06: PQI ( ( →Mapping: PQI →p. 104))
138...153
Port X06: Diagnostic, vendor ID, device ID, events ( →Mapping: IO-Link device information + events
( →p. 105))
154...155
Port X07: PQI ( ( →Mapping: PQI →p. 104))
156...171
Port X07: Diagnostic, vendor ID, device ID, events ( →Mapping: IO-Link device information + events
( →p. 105))
172...173
Port X08: PQI ( ( )) →Mapping: PQI →p. 104
174...189
Port X08: Diagnostic, vendor ID, device ID, events ( →Mapping: IO-Link device information + events
( →p. 105))
190
Port X01: Input data IO-Link (n bytes)
190+n
Port X02: Input data IO-Link (n bytes)
190+2n
Port X03: Input data IO-Link (n bytes)
190+3n
Port X04: Input data IO-Link (n bytes)
190+4n
Port X05: Input data IO-Link (n bytes)
190+5n
Port X06: Input data IO-Link (n bytes)
190+6n
Port X07: Input data IO-Link (n bytes)
190+7n
Port X08: Input data IO-Link (n bytes)
Legend:
n = [2,4,8,16,32]; is determined by the parameter [Prozess_Data_Length] ( →Conguration Assembly (Instance 199)
( ) →p. 96
>
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
101
Input Assembly (Instance 101): I/O data + acyclic data
34369
Byte
Content
0...1
Port X01...X08: Digital Input pin 2 / 4 (DI) ( ( →Mapping: digital input data (DI) →p. 103))
2...3
Status information ( ( →Mapping: Status information →p. 103))
4...45
Acyclic commando area: Response channel ( ( →Response channel →p. 112))
46...47
Port X01: PQI ( ( →Mapping: PQI →p. 104))
48...49
Port X02: PQI ( ( →Mapping: PQI →p. 104))
50...51
Port X03: PQI ( ( →Mapping: PQI →p. 104))
52...53
Port X04: PQI ( ( →Mapping: PQI →p. 104))
54...55
Port X05: PQI ( ( →Mapping: PQI →p. 104))
56...57
Port X06: PQI ( ( →Mapping: PQI →p. 104))
58...59
Port X07: PQI ( ( →Mapping: PQI →p. 104))
60...61
Port X08: PQI ( ( →Mapping: PQI →p. 104))
62
Port X01: Input data IO-Link (n bytes)
62+n
Port X02: Input data IO-Link (n bytes)
62+2n
Port X03: Input data IO-Link (n bytes)
62+3n
Port X04: Input data IO-Link (n bytes)
62+4n
Port X05: Input data IO-Link (n bytes)
62+5n
Port X06: Input data IO-Link (n bytes)
62+6n
Port X07: Input data IO-Link (n bytes)
62+7n
Port X08: Input data IO-Link (n bytes)
Legend:
n = [2,4,8,16,32]; is determined by the parameter [Prozess Data Length] ( →Conguration Assembly (Instance 199)
( →p. 96))
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
102
>
Input Assembly (Instance 102): I/O data
34372
Byte
Content
0...1
Digital inputs of the IO-Link ports in DI operating mode ( ( →Mapping: digital input data (DI) →p. 103))
2...3
Status information ( ( →Mapping: Status information →p. 103))
4...5
Port X01: PQI ( ( →Mapping: PQI →p. 104))
6...7
Port X02: PQI ( ( →Mapping: PQI →p. 104))
8...9
Port X03: PQI ( ( →Mapping: PQI →p. 104))
10...11
Port X04: PQI ( ( →Mapping: PQI →p. 104))
12...13
Port X05: PQI ( ( →Mapping: PQI →p. 104))
14...15
Port X06: PQI ( ( →Mapping: PQI →p. 104))
16...17
Port X07: PQI ( ( →Mapping: PQI →p. 104))
18...19
Port X08: PQI ( ( →Mapping: PQI →p. 104))
20
Port X01: Cyclic input data (n bytes)
20+n
Port X02: Cyclic input data (n bytes)
20+2n
Port X03: Cyclic input data (n bytes)
20+3n
Port X04: Cyclic input data (n bytes)
20+4n
Port X05: Cyclic input data (n bytes)
20+5n
Port X06: Cyclic input data (n bytes)
20+6n
Port X07: Cyclic inp ut data (n bytes)
20+7n
Port X08: cyclic input data (n bytes)
Legend:
n = [2,4,8,16,32]; is determined by the parameter [Prozess Data Length] ( →Conguration Assembly (Instance 199)
( →p. 96))
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
103
>
Mapping: digital input data (DI)
34380
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
X08: pin 4
X07: pin 4
X06: pin4
X05: pin 4
X04: pi n 4
X03: pin 4
X02: pin 4
X01: pin 4
X08: pin 2
X05: pin 2
X06: pin 2
X05: pin 2
X04: pin 2
X03: pin 2
X02: pin 2
X01: pin 2
Legend:
▪ [pin 4]
Signal level on pin 4 of the IO-Link port
1 bit
0x0
LOW
0x1
HIGH
▪ [pin 2]
Signal level on pin 2 of the IO-Link port
1 bit
0x0
LOW
0x1
HIGH
>
Mapping: Status information
34396
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
X08:
Short / OL
X07:
Short / OL
X06:
Short / OL
X05:
Short /OL
X04:
Short / OL
X03:
Short / OL
X02:
Short / OL
X01:
Short / OL
reserved
reserved
reserved
reserved
reserved
reserved
Sensor PWR
AUX PWR
Legend:
▪ [Short / OL]
Occurrence of a short circuit or of an overvoltage on
the IO-Link port
1 bit
0x0
no error
0x1
short circuit or overvoltage
detect ed
▪ [Sensor PWR]
Status of the supply voltage US
1 bit
0x0
no error
0x1
error
▪ [AUX PWR]
Status of the supply voltage UA
1 bit
0x0
UA present and no error
0x1
no error
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
104
>
Mapping: PQI
34393
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
Diagnosis
present
Wrong PD
Output Length
Wrong PD
Input Length
Wrong
Cycle Time
Wrong
VID / DID
Invalid Data
Bit
Dev Not Conn
IOL Mode
reserved
Legend:
▪ [IOL Mode]
Operating mode of the IO-Link port
1 bit
0x0
not IO-Link
0x1
IO-Link
▪ [Dev Not Conn]
Connection between IO-Link Device and IO-Link port
1 bit
0x0
connected
0x1
not connected
▪ [Invalid Data]
Status of the process input data on the -Link port IO
1 bit
0x0
valid Data
0x1
invalid Data
▪ [Wrong VID/DID]
Evaluation, whether actual and projected Vendor ID
and Device ID match
1 bit
0x0
OK
0x1
wrong VID and/or DID
▪ [Wrong Cycle
Time]
Evaluation, whether actual and projected cycle time
match
1 bit
0x0
OK
0x1
wrong cycle time
▪ [Wrong PD Input
Length]
Evaluation, whether actual and projected input process
data length match
1 bit
0x0
OK
0x1
projected length too small
▪ [Wrong PD
Output Length]
Evaluation, whether actal and projected output process
data length match
1 bit
0x0
OK
0x1
projected length too small
▪ [Diagnosis
present]
Signals a new diagnosis event (Coming Event, Single
Shot Event)
▪ Coming Events are removed when if the related
Disappearing Event appears
▪ Single Shot Events are removed automatically
1 Bit
0x0
no event
0x1
New event present
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
105
>
Mapping: IO- Link device information + events
34413
Byte
(oset)
Contents
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
n
VID (LSB)
n+1
VID (MSB)
n+2
DID (LSB)
n+3
DID
n+4
DID (MSB)
n+5
reserved
n+6
Event 1: Mode
Event 1: Type
Event 1: Src
Event 1: Instance
n+7
Event 1: Code (LSB)
n+8
Event 1: Code (MSB)
n+9
Event 2: Mode
Event 2: Type
Event 2: Src
Event 2: Instance
n+10
Event 2: Code (LSB)
n+11
Event 2: Code (MSB)
n+12
Event 3: Mode
Event 3: Type
Event 3: Src
Event 3: Instance
n+13
Event 3: Code (LSB)
n+14
Event 3: Code (MSB)
n+15
reserved
Legend:
▪ [VID]
Vendor ID of the connected -Link device IO
VID = 0x1234
▪ DID (MSB) = 0x12
▪ DID (LSB) = 0x34
2 bytes
0x0000...0xFFFF
▪ [DID]
Device ID of the connected IO- nk device Li
DID = 0x123456
▪ DID (MSB) = 0x12
▪ DID = 0x34
▪ DID (LSB) = 0x56
3 bytes
0x000000...0xFFFFFF
▪ [Event m:
Mode]
Mode: Mode of the event
2 bits
0x0
reserved
0x1
One-time event
0x2
Event has disappeared
0x3
Event has appeared
▪ [Event m:
Type]
Type: category of the event
2 bits
0x0
reserved
0x1
Notication
0x2
Warning
0x3
Error
▪ [Event m: Src]
Source: Source of the event
1 bit
0x0
IO-Link Device
0x1
IO-Link master
▪ [Event m:
Instance]
Instance: Trigger of the event
3 bits
0x0
Unknown
0x1 ... 0x3
reserved
0x4
Application
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
106
0x5 ... 0x7
reserved
▪ [Event m:
Code]
Code: Event code
Code = 0x1234
▪ Code (MSB) = 0x12
▪ Code (LSB) = 0x34
2 bytes
depends on the device ( IODD description →
of the IO-Link device)
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
107
>
Output assembly (Instance 150): I/O data + acyclic data
34370
Byte
Conte nt
0
Port X01...X08: Digital output - pin 4 (DO) ( ( →Mapping: Digital output data (DO) →p. 109))
1
reserved
2
reserved
3
reserved
4...45
Acyclic command area: Request channel ( ( →Request channel →p. 111))
46
Port X01: Output data IO-Link (n bytes)
46+n
Port X02: Output data IO-Link (n bytes)
46+2n
Port X03: Output data IO-Link (n bytes)
46+3n
Port X04: Output data IO-Link (n bytes)
46+4n
Port X05: Output data IO-Link (n bytes)
46+5n
Port X06: Output data IO-Link (n bytes)
46+6n
Port X07: Output data IO-Link (n bytes)
46+7n
Port X08: Output data IO-Link (n bytes)
Legend:
n = [2,4,8,16,32]; is determined by the parameter [Prozess_Data_Length] ( →Conguration Assembly (Instance 199)
( ) →p. 96
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
108
>
Output Assembly (Instance 151): I/O data
34341
Byte
Content
0
Port X01...X08: Digital output - pin 4 (DO) ( ( →Mapping: Digital output data (DO) →p. 109))
1
reserved
2
Port X01: Output data IO-Link (n bytes)
2+n
Port X02: Output data IO-Link (n bytes)
2+2n
Port X03: Output data IO-Link (n bytes)
2+3n
Port X04: Output data IO-Link (n bytes)
2+4n
Port X05: Output data IO-Link (n bytes)
2+5n
Port X06: Output data IO-Link (n bytes)
2+6n
Port X07: Output data IO-Link (n bytes)
2+7n
Port X08: Output data IO-Link (n bytes)
Legend:
n = [2,4,8,16,32]; is determined by the parameter [Process_Data_Length] ( →Conguration Assembly (Instance 199)
( ) →p. 96
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
109
>
Mapping: Digital output data (DO)
34411
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
X08: pin 4
X07: pin 4
X06: pin4
X05: pin 4
X04: pin 4
X03: pin 4
X02: pin 4
X01: pin 4
Legend:
▪ [pin 4]
Signal level on pin 4 of the IO-Link port
1 bit
0x0
LOW
0x1
HIGH
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
110
14.2.4 Acyclic data
Content
Acyclic command channel ....................................................................................................................110
Acyclic commands ................................................................................................................................115
Field bus objects ...................................................................................................................................122
33868
>
Acyclic command channel
34325
In the cyclic process data, command channels for the transmission of acyclic data is available.
Object
Contents
Bytes
Access
Output assembly
Request channel (eld bus PLC >>> IO-Link master)
→ → (Request channel ) p. 111
4...45
r/w
Input assembly
Response channel (IO-Link master >>> eldbus PLC)
→ → (Response channel ) p. 112
4...45
r
Legend:
r
r/w
= only read access rights
= read and write access rights
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
111
>
Request channel
34398
Byte
Content
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
4
Port No. (LS B)
5
Port No. (MSB)
6
Index (LSB)
7
Index (MSB)
8
Sub-index (LSB)
9
Sub-index (MSB)
10
Trigger
Command id
11
Length of the user data (number of bytes)
12
Data (byte 0)
13
Data (byte 1)
..
...
43
Data (byte 31)
44
reserved
45
reserved
Legend:
▪ [Port No.]
Number of the IO-Link port
Port No. = 0x1234
▪ Port No. (MSB) = 0x12
▪ Port No. (LSB) = 0x34
1 Word
0x0001
Port X01
0x0002
Port X02
...
0x0008
Port X08
▪ [Index]
Index of the IO-Link object
Index = 0x1234
▪ Index (MSB) = 0x12
▪ Index (LSB) = 0x34
1 Word
0x0000...0xFFFF
▪ [Subindex]
Subindex of the IO-Link object
Subindex = 0x1234
▪ Subindex (MSB) = 0x12
▪ Subindex (LSB) = 0x34
1 Word
0x0000...0xFFFF
▪ [Trigger]
Control of the command execution
1 Bit
0x0
do not process
command
0x1
execute command
▪ [Command ID]
Command number
7 Bit
0x01
read
0x02
write
▪ [Length of user data
(number of bytes)]
Number of bytes that contain relevant user data
1 Byte
0x00
0 bytes
...
0x20
32 bytes
▪ [Data (byte n)]
User data
1 Byte
per byte: 0x00...0xFF
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
112
>
Response channel
34401
Byte
Content
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
4
Port No. (LSB)
5
Port No. (MSB)
6
Index (LSB)
7
Index (MSB)
8
Sub-index (LSB)
9
Sub-index (MSB)
10
Handshake
Command ID
11
Result
12
Length of response data (number of bytes)
13
Data (byte 0) or Error Code
14
Data (byte 1) or Additional Code
...
...
44
Data (byte 31)
45
reserved
Legend:
▪ [Port No.]
Number of the IO-Link port
Port No. = 0x1234
▪ Port No. (MSB) = 0x12
▪ Port No. (LSB) = 0x34
1 word
0x0001
Port X01
0x0002
Port X02
...
0x0008
Port X08
▪ [Index]
Index of the IO-Link object
Index = 0x1234
▪ Index (MSB) = 0x12
▪ Index (LSB) = 0x34
1 word
0x0000...0xFFFF
▪ [Subindex]
Subindex of the -Link object IO
Subindex = 0x1234
▪ Subindex (MSB) = 0x12
▪ Subindex (LSB) = 0x34
1 word
0x0000...0xFFFF
▪ [Handshake]
Validity of the IO-Link response data
1 bit
0x0
Data invalid
0x1
Data valid
▪ [Command ID]
Command number
7 bits
0x01
Read
0x02
Write
▪ [Result]
Status of the command processing
8 bits
0x00
OK
0x0F
OK, data read >32 bytes
0xFF
Error occurred
▪ [Length of response
data (number of
bytes)]
Number of bytes that contain relevant user
data
1 byte
0x00
0 bytes
...
0x20
32 bytes
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
113
▪ [Data (byte 0) or
Error Code]
User data (byte 0) or error codes
1 byte
User data: 0x00...0xFF
Error Code: ( ) →Error codes →p. 114
▪ [Data (byte 1) or
Additional Code]
User data (byte1) or additional error codes
1 byte
User data: 0x00...0xFF
Additional Code: →Additional Codes
( ) →p. 114
▪ [Data (byte n)]
User data (byte n)
1 byte
0x00...0xFF
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
114
>
Error codes
34342
Error code
Description
0x71
Service not available (unknown command has been sent to the -Link port) IO
0x72
Port blocked (another cyclic process accesses the IO-Link port)
0x73
Forbidden (access rights don't allow command processing)
0x74
Invalid data (wrong parameter has been sent in the command)
0x76
Wrong port (wrong port number)
0x77
Wrong port function (wrong port function or wrong parameter has been sent to the device)
0x78
Invalid length (set length is > 0x20)
0x80
Error in the device application; observe additional code ( ( →Additional Codes →p. 114))
>
Additional Codes
54584
Code
Name
Description
0x00
APP_DEV
Device application error - no details
0x11
IDX_NOTAVAIL
Index not available
0x12
SUBIDX_NOTAVAIL
Subindex not available
0x20
SERV_NOTAVAIL
Service temporarily not available
0x21
SERV_NOTAVAIL_LOCCTRL
Service temporarily not available - local control
0x22
SERV_NOTAVAIL_DEVCTRL
Service temporarily not available - device control
0x23
IDX_NOT_WRITEABLE
Access denied
0x30
PAR_VALOUTOFRNG
Parameter value out of range
0x31
PAR_VALGTLIM
Parameter value above limit
0x32
PAR_VALLTLIM
Parameter value below limit
0x33
VAL_LENOVRR UN
Parameter length overrun
0x34
VAL_LENUNDRUN
Parameter length underrun
0x35
FUNC_NOTAVAIL
Function not available
0x36
FUNC_UNAVAILTEMP
Function temporarily not available
0x40
PAR_SETINVALID
Invalid parameter set
0x41
PAR_SETINCONSIST
Inconsistent parameter set
0x82
APP_DEVNOTRDY
Application not ready
Additional Codes are only available, if Error Code = 0x80 ( →Error codes ( →p. 114))
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
115
Acyclic commands
Content
Command 0x10 Set mode –.................................................................................................................116
Command 0x20 Set validation ID / data storage –...............................................................................118
Command 0x30 Set fail-safe data pattern –.........................................................................................120
34331
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
116
Command 0x10 Set mode –
34322
The command changes the operating mode of an IO-Link port of the AL1323.
Corresponding parameter: [Port Mode] ( → Mapping: Port configuration ( → p. 97))
>
Command request
34314
Byte
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
4
Port No. (LSB)
5
Port No. (MSB)
6
reserved
7
reserved
8
reserved
9
reserved
10
Trigger
0x10
11
Target Mode
12...45
reserved
Legend:
▪ [Port No.]
Number of the IO-Link port
Port No. = 0x1234
▪ Port No. (MSB) = 0x12
▪ Port No. (LSB) = 0x34
1 word
0x0001
Port X01
0x0002
Port X02
...
0x0008
Port X08
▪ [Trigger]
Control of the command execution
1 bit
0x0
do not process command
0x1
execute command
▪ [Target Mode]
Operating type of the IO-Link port
1 byte
0x00
deactivated
0x01
operation as digital input (DI)
0x02
operation as digital output (DO)
0x03
operation as IO-Link intervals
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
117
>
Command response
34316
Byte
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
4
Port No. (LSB)
5
Port No. (MSB)
6
reserved
7
reserved
8
reserved
9
reserved
10
Handshake
0x10
11
Result
12
Target Mode
13...45
reserved
Legend:
▪ [Port No.]
Number of the IO-Link port
Port No. = 0x1234
▪ Port No. (MSB) = 0x12
▪ Port No. (LSB) = 0x34
1 word
0x0001
Port X01
0x0002
Port X02
...
0x0008
Port X08
▪ [Handshake]
Status of the execution of the command
1 bit
0x0
command is executed
0x1
execution of the command was
successful
▪ [Result]
Error indication
1 byte
0x00
no error
0x01
error occured
▪ [Target Mode]
Operating type of the IO-Link port
1 byte
0x00
deactivated
0x01
operation as digital input (DI)
0x02
operation as digital output (DO)
0x03
operation as IO-Link intervals
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
118
Command 0x20 Set validation ID / data storage –
34321
The command sets the behaviour of the IO-Link master when connecting a new IO-Link device to an
IO-Linkport of the device.
Corresponding parameter: [Validation ( ID] (→ Mapping: Port configuration → p. 97))
>
Command request
34315
Byte
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
4
Port No. (LSB)
5
Port No. (MSB)
6
reserved
7
reserved
8
reserved
9
reserved
10
Trigger
0x20
11
Validation ID
12...42
reserved
Legend:
▪ [Port No.]
Number of the IO-Link port
Port No. = 0x1234
▪ Port No. (MSB) = 0x12
▪ Port No. (LSB) = 0x34
1 word
0x0001
Port X01
0x0002
Port X02
...
0x0008
Port X08
▪ [Trigger]
Control command execution
1 Bit
0x0
do not process command
0x1
execute command
▪ [Validation ID]
Behaviour of the IO-Link master when
connecting an IO-Link device to the IO-Link port
1 byte
0x00
No check
0x01
Type compatible V1.0 Device
0x02
Type compatible V1.1 Device
0x03
Type compatible V1.1 Device
with Backup + Restore
0x04
Type compatible V1.1 Device
with Restore
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
119
>
Command response
34362
Byte
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
4
Port No. (LSB)
5
Port No. (MSB)
6
reserved
7
reserved
8
reserved
9
reserved
10
Handshake
0x20
11
Result
12
Validation ID
13..45
reserved
Legend:
▪ [Port No.]
Number of the IO-Link port
Port No. = 0x1234
▪ Port No. (MSB) = 0x12
▪ Port No. (LSB) = 0x34
1 word
0x0001
Port X01
0x0002
Port X02
...
0x0008
Port X08
▪ [Handshake]
Status of the execution of the command
1 bit
0x0
command is executed
0x1
execution of the command was
successful
▪ [Result]
Error indication
1 byte
0x00
no error
0x01
errors occurred
▪ [Validation ID]
Behaviour of the IO-Link master when
connecting an IO-Link device to the IO-Link port
1 byte
0x00
No check
0x01
Type compatible V1.0 Device
0x02
Type compatible V1.1 Device
0x03
Type compatible V1.1 Device
with Backup + Restore
0x04
Type compatible V1.1 Device
with Restore
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
120
Command 0x30 Set fail-safe data pattern –
34379
The command sets the behaviour of the outputs when the EtherNet/IP connection and the
corresponding fail-safe values are interrupted.
Corresponding parameter: [Fail-safe Mode] ( → Mapping: Port configuration ( ) → p. 97
The number of the required fail-safe values results from the size of the output data
( → Configuration Assembly (Instance 199) ( → p. 96)).
>
Command request
34317
Byte
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
4
Port No. (LSB)
5
Port No. (MSB)
6
reserved
7
reserved
8
reserved
9
reserved
10
Trigger
0x30
11
Fail-safe mode
12
Byte Length N
13
Fail-safe data (byte 0)
...
...
44
Fail-safe data (byte 31)
45
reserved
Legend:
▪ [Port No.]
Number of the IO-Link port
Port No. = 0x1234
▪ Port No. (MSB) = 0x12
▪ Port No. (LSB) = 0x34
1 word
0x0001
Port X01
0x0002
Port X02
...
0x0008
Port X08
▪ [Trigger]
Control command execution
1 bit
0x0
do not process command
0x1
execute command
▪ [Fail-safe Mode]
Behaviour of the outputs when the
EtherNet/IP connection is interrupted and
setting of the corresponding fail-safe values
1 byte
0x00
No Fail-safe
0x01
Fail-safe Reset Value
0x02
Fail-safe Old Value
0x03
Fail-safe with Pattern
▪ [Byte Length N]
Number of the bytes that contain fail-safe
values
1 byte
0x00
0 Bytes
...
0x20
32 Bytes
▪ [Fail-safe Data (Byte n)]
Fail-Safe value n (n = 0...31)
1 bytet
per byte: 0x00...0xFF
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
121
>
Command response
34361
Byte
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
4
Port No. (LSB)
5
Port No. (MSB)
6
reserved
7
reserved
8
reserved
9
reserved
10
Handshake
0x30
11
Result
12
Fail-safe mode
13...45
reserved
Legend:
▪ [Port No.]
Number of the IO-Link port
Port No. = 0x1234
▪ Port No. (MSB) = 0x12
▪ Port No. (LSB) = 0x34
1 word
0x0001
Port X01
0x0002
Port X02
...
0x0008
Port X08
▪ [Handshake]
Status of the execution of the command
1 bit
0x0
command is executed
0x1
execution of the command was
successful
▪ [Result]
Error indication
1 byte
0x00
no error
0x01
error occured
▪ [Fail-safe Mode]
Behaviour of the outputs when the
EtherNet/IP connection is interrupted
1 byte
0x00
No Fail-safe
0x01
Fail-safe Reset Value
0x02
Fail-safe Old Value
0x03
Fail-safe with Pattern
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
122
Field bus objects
Content
CIP class services ................................................................................................................................123
CIP object classes ................................................................................................................................123
Identity Object (object class: 0x01) ......................................................................................................124
Message Router Object (object class: 0x02) ........................................................................................126
Assembly Object (object class: 0x04) ..................................................................................................127
Connection Manager Object (object class: 0x06) ................................................................................129
Device Level Ring Object (object class: 0x47) .....................................................................................130
Quality of Service (object class: 0x48) ................................................................................................. 131
IO-Link requests (object class: 0x80) ...................................................................................................132
TCP/IP object (object class: 0xF5) .......................................................................................................141
Ethernet Link Object (object class: 0xF6) .............................................................................................143
34352
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
123
>
CIP class services
34335
The device supports the following class and instance services:
Class code
Service
Description
dec
hex
01
01
Get Attribute All
Read all attribute values of the class or instance
02
02
Set Attribute All
Change all attribute values of the class or instance
05
05
Reset
Reset
09
09
Delete
Delete
14
0E
Get Attribute Single
Read single attribute value of the class or instance
16
10
Set Attribute Single
Change single attribute value of the class or instance
75
4B
Read ISDU
Read ISDU
76
4C
Write ISDU
Write ISDU
77
4D
Write Failsafe Pattern
Write failsafe pattern
78
4E
Forward Close
Close connection
84
54
Forward Open
Open new connection
>
CIP object classes
34334
The device supports the following CIP object classes:
Class code
Object type
Reference
dec
hex
01
01
Identity Object
→ → (Identity Object (object class: 0x01) ) p. 124
02
02
Message Router Object
→ → (Message Router Object (object class: 0x02) ) p. 126
04
04
Assembly Object
→ → (Assembly Object (object class: 0x04) ) p. 127
06
06
Connection Manager Object
→ Connection Manager Object (object class: 0x06)
( ) → p. 129
71
47
Device Level Ring Object
→ → (Device Level Ring Object (object class: 0x47) ) p. 130
72
48
Quality of Service
→ → (Quality of Service (object class: 0x48) ) p. 131
128
80
IO-Link Requests
→ → (IO-Link requests (object class: 0x80) ) p. 132
245
F5
TCP/IP Object
→ → (TCP/IP object (object class: 0xF5) ) p. 141
246
F6
Ethernet Link Object
→ → (Ethernet Link Object (object class: 0xF6) ) p. 143
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
124
Identity Object (object class: 0x01)
34340
The Identity Object contains the general information about the device.
>
Class attributes
34310
Attr. ID
Access
Name
Data type
Description
Value
1
Get
Revision
UINT
Revisio n of the object
1
2
Get
Max instance
UINT
Max. number of instances of the object
1
6
Get
Maximum ID Number
Class Attributes
UINT
ID of the last class attribute
7
7
Get
Maximum ID Number
Instance Attributes
UINT
ID of the last instance attribute
9
>
Instance attributes
34339
Attr. ID
Access
Name
Data type
Description
Preset
1
Get
Vendor ID
UINT
Manufacturer ID
322
2
Get
Device type
UINT
Type of unit
12
3
Get
Product code
UINT
Identification of a particular product of a vendor
1323
4
Get
Revision
STRUCT
Revision of the article that is represented by the
Identity Object
1.1
▪ Major
revision
USINT
Main revision (1...127)
1
▪ Minor
revision
USINT
Side revision (3 digits, if necessary with zeros in the
beginning)
1
5
Get
Status
WORD
Status of the device
6
Get
Serial number
UDINT
Serial number of the device
7
Get
Product Name
SHORT
STRING
Readable device designation (max. 32 ASCII
characters)
IO-Link master DL
EIP 8P IP69K
8
Get
State
USINT
Current status of the device (according to status
transition diagram)
0
Nonexistent
1
Device Self Testing
2
Standby
3
Operational
4
Major Recoverable Fault
5
Major Unrecoverable Fault
6...254
Reserved
255
Default for Get_Attributes_All service
9
Get
Configuration
Consistency
Value
UINT
The content shows the configuration of the device
0
>
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
125
Supported services
34377
Service code
Name
Class
Attribute
Description
dec
hex
01
01
Get_Attribute_All
yes
yes
Read all attributes
05
05
Reset
yes
yes
Reset
14
0E
Get_Attribute_Single
yes
yes
Read single attribute
16
10
Set_Attribute_Single
yes
yes
Change single attribute
If an Identity Object receives a reset request, it carries out the following actions:
• It checks if it supports the requested reset type.
• It responds to the request.
• It tries to execute the requested reset type.
Supported reset types:
▪ 0
Reboot the device (obligatory for all EtherNet/IP devices).
▪ 1
Restore factory settings and reboot the device.
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
126
Message Router Object (object class: 0x02)
34390
The Message Router Object provides an access with which an EtherNet/IP client can address a
service to any object class or instance in the physical device.
>
Class attributes
34320
Attr. ID
Access
Name
Data type
Description
Value
1
Get
Revision
UINT
Revision of the object
1
2
Get
Max instance
UINT
Max. number of instances of the object
1
3
Get
Number of Instances
UINT
Number of instances
1
6
Get
Maximum ID Number
Class Attributes
UINT
ID of the last class attribute
7
7
Get
Maximum ID Number
Instance Attributes
UINT
ID of the last instance attribute
0
>
Instance attributes
34402
The object has no instance attributes.
>
Supported services
34374
Service code
Name
Class
Attribute
Description
dec
hex
14
0E
Get_Attribute_Single
yes
no
Read single attribute value
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
127
Assembly Object (object class: 0x04)
34332
The Assembly Object combines attributes of several objects to allow data to be sent to or received
from each object via one connection.
>
Class attributes
34309
Attr. ID
Access
Name
Data type
Description
Value
1
G et
Revision
UINT
Revision of the object
2
2
Get
Max instance
UINT
Max. number of instances of the object
0x00C7
3
Get
Number of Instances
UINT
Number of instances
3
6
Get
Maximum ID Number
Class Attributes
UINT
ID of the last class attribute
7
7
Get
Maximum ID Number
Instance Attributes
UINT
ID of the last instance attribute
4
>
Instances
34403
Attr. ID
Access
Name
Data type
Description
100
Get
Input assembly
STRUCT
Cyclic input data ( →Input assembly (Instance 100): I/O data + acyclic
data + diagnosis data ( →p. 100))
101
Get
Input assembly
STRUCT
Cyclic input data ( →Input Assembly (Instance 101): I/O data + acyclic
data ( →p. 101))
102
Get
Input assembly
STRUCT
Cyclic input data ( →Input Assembly (Instance 102): I/O data
( →p. 102))
150
Get, Set
Output assembly
STRUCT
Cyclic output data ( →Output assembly (Instance 150): I/O data +
acyclic data ( →p. 107))
151
Get, Set
Output assembly
STRUCT
Cyclic output data ( →Output Assembly (Instance 151): I/O data
( →p. 108))
199
Set
Conguration
assembly
STRUCT
Conguration data ( →Conguration Assembly (Instance 199)
( )) →p. 96
>
Instance attributes
61121
Attr. ID
Access
Name
Data type
Description
Preset:
1
Number of
member
UINT
Manufacturer ID
-
2
Get
Member
UINT
Memeber List
-
3
Get, Set
Data
UINT
Image of the process data
-
4
Get
Size
UINT
Size of the process data (in bytes)
-
300
Member data list
UINT
Data of the Assembly members
-
301
Parameter
UINT
Assembly parameters
-
302
Status
UINT
Status of the assembly
-
>
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
128
Supported services
34376
Service code
Name
Class
Attribute
Description
dec
hex
14
0E
Get_Attribute_Single
yes
yes
Read attribute value
16
10
Set_Attribute_Single
no
yes
Change attribute value
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
129
Connection Manager Objec (object class: 0x06) t
34367
The Connection Manager Object structures and manages the internal resources that are used for the
connection.
>
Class attributes
34319
Attr ID
Access
Name
Data type
Description
Value
1
Get
Revision
UINT
Revision of the object
1
2
Get
Max instance
UINT
Max. number of instances of the object
1
3
Get
Number of Instances
UINT
Number of instances
3
6
Get
Maximum ID Number
Class Attributes
UINT
ID of the last class attribute
7
7
Get
Maximum ID Number
Instance Attributes
UINT
ID of the last instance attribute
0
>
Instance attributes
34402
The object has no instance attributes.
>
Supported services
34375
Service code
Name
Class
Attribute
Description
dec
hex
14
0E
Get_Attribute_Single
yes
yes
Read single attribute
16
10
Set_Attribute_Single
no
yes
Change single attribute
78
4E
Forward_Close
yes
no
Close connection
84
54
Forward_Open
yes
no
Open new connection
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
130
Device Level Ring Object (object class: 0x47)
34345
The Device Level Ring (DLR) Object represents the interface for conguration and status information.
>
Class attributes
34313
Attr ID
Access
Name
Data type
Description
Value
1
Get
Revision
UINT
Revision of the object
3
2
Get
Max instance
UINT
Max. number of instances of the object
1
6
Get
Maximum ID Number
Class Attributes
UINT
ID of the last class attribute
7
7
Get
Maximum ID Number
Instance Attributes
UINT
ID of the last instance attribute
12
>
Instance attributes
34327
Attr. ID
Access
Name
Data type
Description
Preset
1
Get
Network
Topology
USINT
current network topology
0
2
Get
Network status
USINT
current network status
0
10
Get
Active Supervisor
STRUCT of
Identication of the supervisor
0
▪ UDINT
IP address of the supervisor
▪ ARRAY
of 6
USINT
s
MAC address of the supervisor
12
Get
Capability Flags
DWORD
DLR functions of the device
0x82
Bit 0
Announced-based ring node
0
Bit 1
Beacon-based ring node
1
Bit 2...4
reserved
--
Bit 5
Supervisor capable
0
Bit 6
Redundant Gateway capable
0
Bit 7
Flush_Table frame capable
1
Bit 8..31
reserved
--
l
>
Supported services
34409
Service code
Name
Class
Attribute
Description
dec
hex
1
01
Get_Attribute_All
no
yes
Read all attribute values
14
0E
Get_Attribute_Single
yes
yes
Read single attribute value
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
131
Quality of Service (object class: 0x48)
34371
Quality of Service (QoS) enables prioritising of Ethernet frames. The priorities of the Ethernet frames
can be inuenced with the attributes "Dierentiate Service Code Points" (DSCP) or "802.1Q Tag".
>
Class attributes
34307
Attr ID
Access
Name
Data type
Description
Value
1
Get
Revision
UINT
Revision of the object
3
2
Get
Max instance
UINT
Max. number of instances of the object
1
6
Get
Maximum ID Number
Class Attributes
UINT
ID of the last class attribute
7
7
Get
Maximum ID Number
Instance Attributes
UINT
ID of the last instance attribute
8
>
Instance attributes
34328
Attr ID
Access
Name
Data type
Description
Value
1
Get
802.1Q tagRevision
USINT
Current network topology
0
2
Get, Set
DSCP PTP Event
USINT
DSCP value for PTP event frames
59
3
Get, Set
DSCP PTP general
USINT
DSCP value for PTP general frames
47
4
Get, Set
DSCP PTP Urgent
USINT
DSCP value for implicit messages with "urgent"
priority
55
5
Get, Set
DSCP Scheduled
USINT
DSCP value for implicit messages with "scheduled"
priority
47
6
Get, Set
DSCP High
USINT
DSCP value for implicit messages with "high" priority
43
7
Get, Set
DSCP Low
USINT
DSCP value for implicit messages with "low" priority
31
8
Get, Set
DSCP explicit
USINT
DSCP value for explicit messages with "scheduled"
priority
27
>
Supported services
34406
Service code
Name
Class
Attribute
Description
dec
hex
01
01
Get_Attribute_All
yes
yes
Read all attribute values
14
0E
Get_Attribute_Single
no
yes
Read single attribute value
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
132
IO-Link requests (object class: 0x80)
34412
The manufacturer-specic object "IO-Link Requests" enables read and write access to the IO-Link
objects of an IO-Link device connected to a AL1323 via ISDU (Index Service Data Unit). The object
projects the mechanisms of the CIP addressing on the IO-Link protocol.
>
Class attributes
34308
Attr ID
Access
Name
Data type
Description
Value
1
Get
Revision
UINT
Revision of the object
4
2
Get
Max instance
UINT
Max. number of instances of the object
2
6
Get
Maximum ID Number
Class Attributes
UINT
Number of instances of the object
8
>
Instance attributes
34399
The required IO-Link port of the device is addressed via the instance attribute.
>
Supported services
34378
Service code
Name
Class
Attribute
Description
dec
hex
75
4B
→ → (Read_ISDU ) p. 133
no
yes
Read ISDU
76
4C
→ → (Write_ISDU ) p. 136
no
yes
Read ISDU
77
4D
→ Write Failsafe Pattern
( ) →p. 138
no
yes
Write failsafe values of IO-Link port
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
133
>
Read_ISDU
34323
With Read_ISDU, parameters of a connected IO-Link device can be read.
>
Request
34337
CIP Attribute determines the IO-Link port to which the IO-Link device is connected. The area CIP User
Specic Service Data contains the IO-Link index and the IO-Link sub-index of the IO-Link object
whose value is to be read:
CIP format
Data type
MSG Cong
IO-Link mapping
CIP Class ID
UINT
0x80
IO-Link acyclic access
CIP Instance ID
UINT
0x01
IO-Link master
CIP Attributes
USINT
0x01...0x08
Port number
CIP Service code ID
USINT
0x4B
Request "Read_ISDU"
CIP User specic service data
UINT
0x0000...0xFFFF
IO-Link ISDU object index
USINT
0x00...0xFF
IO-Link ISDU object sub-index
>
Response
34326
• Positive response
If the service has been executed successfully (CIP Error Code = 0), the read data are returned bit by
bit (CIP User Specic Service Data). The answer has the following format:
CIP format
Data type
MSG Cong
IO-Link mapping
CIP Class ID
UINT
0x80
IO-Link acyclic access
CIP Instance ID
UINT
0x01
IO-Link master
CIP Attributes
USINT
0x01...0x08
Port number
CIP Service Code ID
USINT
0x4C
Response "Read_ISDU"
CIP Error Code
USINT
0x00
--
CIP Extended Error Code
USINT
0x00
--
CIP User Specic Service Data
USINT
0x00...0xFF
Data (byte 0)
USINT
0x00...0xFF
Data (byte 1)
...
...
USINT
0x00...0xFF
Data (byte n)
The read data is in the IO-Link format. If necessary, the user needs to adapt the byte
arrangement of the read data to the CIP format.
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
134
• Negative response
If an error occurs while executing the service (CIP Error Code <> 0), an extended error code is
transmitted. If the CIP Error Code = 0x1E, then the CIP Ext Error Code = 0x00 and the CIP User ended
Specic Service Data area contains the IO-Link Error Code as well as IO-Link Additional Code. The
answer has the following format:
CIP format
Data type
MSG Cong
IO-Link mapping
CIP Class ID
UINT
0x80
IO-Link acyclic access
CIP Instance ID
UINT
0x01
IO-Link master
CIP Attributes
USINT
0x01...0x08
Port number
CIP Service Code ID
USINT
0x4B
Response "Read_ISDU"
CIP Error Code
USINT
<> 0x00
Error code: see table below
CIP Extended Error Code
USINT
0x00
Extended error code
CIP User Specic Service Data
USINT
<> 0x00
IO-Link Error Code: ( ) →Error codes →p. 114
(only if CIP Error Code = 0x1E)
USINT
<> 0x00
IO-Link Additional Code: →Additional Codes
( ) →p. 114
(only if CIP Error Code = 0x1E)
CIP Error Code:
Code
Description
0x02
Resource not available: The IO-Link port is busy processing another acyclic service.
0x05
Invalid class ID or instance ID
0x08
Wrong service ID: only service code 0x4B or 0x4C is permitted
0x09
Wrong attribute ID: wrong port number
0x20
Invalid parameter value (e.g. invalid length)
0x1E
Embedded service, error: Error occurred during an IO-Link service. Byte 0 and byte 1 of the User Specic Service
Data contain the IO-Link error code and an additional code that are returned by the IO-Link master.
>
Example: reading the parameter value of anIO-Link device
34350
Task: reading the value of the parameter X of an IO-Link device
• -Link device at the port: 0x02 IO
• Parameter X in the object directory of an IO-Link device: Index: 90, sub-index 3
From this, the following results for the conguration of the EtherNet/IP command Message (MSG):
CIP format
Data type
MSG Cong
Description
CIP Class ID
UINT
0x80
IO-Link acyclic access
CIP Instance ID
UINT
0x01
IO-Link master
CIP Attributes
USINT
0x02
Port number
CIP Service Code ID
USINT
0x4B
Request "ISDU_Read"
CIP User Specic Service Data
UINT
0x005A
IO-Link ISDU object index
USINT
0x03
IO-Link ISDU object sub-index
After successful execution of the request, the response area has the following content:
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
135
CIP format
Data type
MSG Cong
Description
CIP Class ID
UINT
0x80
Object class "IO-Link requests"
CIP Instance ID
UINT
0x01
IO-Link master
CIP Attributes
USINT
0x02
Port number
CIP Service Code ID
USINT
0x4B
Response "ISDU_Read"
CIP Error Code
USINT
0x00
Request processed successfully
CIP Extended Error Code
USINT
0x00
--
CIP User Specic Service Data
USINT
e.g. 0x12
Parameter value that has been read (byte 0)
USINT
e.g. 0x34
Parameter value that has been read (byte 1)
If an error occurs while the request is executed, the response area has the following content:
CIP format
Data type
MSG Cong
Description
CIP Class ID
UINT
0x80
Object class "IO-Link requests"
CIP Instance ID
UINT
0x01
IO-Link master
CIP Attributes
USINT
0x02
Port number
CIP Service code ID
USINT
0x4B
Response "ISDU_Read"
CIP Error code
USINT
0x1E
Error code: Embedded service error
CIP Extended error code
USINT
0x00
--
CIP User specic service data
USINT
e.g. 0x80
IO-Link Error Code: Error in device application
USINT
e.g. 0x20
IO-Link Additional Code: Service temporarily
unavailable
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
136
>
Write_ISDU
34385
With Write_ISDU, the parameters of a connected IO-Link device can be changed.
>
Reque st
34387
CIP Attribute determines the IO-Link port to which the IO-Link device is connected. The area CIP User
Specic Service Data contains the IO-Link index, the IO-Link sub-index of the IO- nk object whose Li
value is to be changed. It is followed, bit by bit, by the value that is to be assigned to the parameter.
CIP format
Data type
MSG Cong
IO-Link mapping
CIP Class ID
UINT
0x80
IO-Link acyclic access
CIP Instance ID
UINT
0x1
IO-Link master
CIP Attribute
USINT
0x01...0x08
Port number
CIP Service Code ID
USINT
0x4C
Request "Write_ISDU"
CIP User Specic Service Data
UINT
0x0000...0xFFFF
IO-Link ISDU object index
USINT
0x00...0xFF
IO-Link ISDU object sub-index
USINT
0x00...0xFF
IO-Link ISDU data (byte 0)
USINT
0x00...0xFF
IO te 1)-Link ISDU data (by
>
Response
34384
• Positive response
If the service has been executed successfully (CIP Error Code = 0), the area CIP User Specic
Service Data stays empty The answer has the following format:
CIP format
Data type
MSG Cong
IO-Link mapping
CIP Class ID
UINT
0x80
IO-Link acyclic access
CIP Instance ID
UINT
0x01
IO-Link master
CIP Attribute
USINT
0x01...0x08
Port number
CIP Service Code ID
USINT
0x4C
Response "Write_ISDU"
CIP Error Code
USINT
0x00
--
CIP Extended Error Code
USINT
0x00
--
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
137
• Negative response
If an error occurs while executing the service (CIP Error Code <> 0), an extended error code is
transmitted. If the CIP Error Code = 0x1E, then the CIP Extended Error Code = 0x00 and the CIP User
Specic Service Data area contains the IO-Link Error Code as well as IO-Link Additional Code. The
answer has the following format:
CIP format
Data type
MSG Cong
IO-Link mapping
CIP Class ID
UINT
0x80
IO-Link acyclic access
CIP Instance ID
UINT
0x01
IO-Link master
CIP Attributes
USINT
0x01...0x08
Port number
CIP Service Code ID
USINT
0x4C
Response "Write_ISDU"
CIP Error Code
USINT
<> 0x00
Error code. see table below
CIP Extended Error Code
USINT
0x00
Extended error code
CIP User Specic Service Data
USINT
<> 0x00
IO-Link Error Code: ( ) →Error codes →p. 114
(only if CIP Error Code = 0x1E)
USINT
<> 0x00
IO-Link Additional Code: →Additional Codes
( ) →p. 114
(only if CIP Error Code = 0x1E)
CIP Error Code:
Code
description
0x02
Resource not available: The IO-Link port is busy processing another acyclic service.
0x05
Invalid class ID or instance ID
0x08
Wrong service ID: only service code 0x4B or 0x4C is permitted
0x09
Wrong attribute ID: wrong port number
0x20
Invalid parameter value (e.g. invalid length)
0x1E
Embedded service, error: Error occurred during an IO-Link service. Byte 0 and byte 1 of the User Specic Service
Data contain the IO-Link error code and an additional code that are returned by the IO-Link master (see below).
>
Example: changing the parameter value of an IO-Link device
34355
Task: changing the parameter X of an IO-Link device
• -Link device at the port: 0x03 IO
• Parameter X in the object directory of an IO-Link device: Index: 91, sub-index 5
• new parameter value: 0xABCD
From this, the following results for the conguration of the EtherNet/IP command Message (MSG):
CIP format
Data type
MSG Cong
Description
CIP Class ID
UINT
0x80
IO-Link acyclic access
CIP Instance ID
UINT
0x01
IO-Link master
CIP Attributes
USINT
0x03
Port number
CIP Service code ID
USINT
0x4C
Service "Write_ISDU"
CIP User specic service data
UINT
0x005B
IO-Link ISDU object index
USINT
0x05
IO-Link ISDU object sub-index
USINT
0xAB
New parameter value (MSB)
USINT
0xCD
New parameter value (LSB)
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
138
After successful execution of the request, the response area has the following content:
CIP format
Data type
MSG Cong
Description
CIP Class ID
UINT
0x80
Object class "IO-Link Requests"
CIP Instance ID
UINT
0x01
IO-Link master
CIP Attributes
USINT
0x03
Port number
CIP Service code ID
USINT
0x4B
Service "Write_ISDU"
CIP Error code
USINT
0x00
Request processed successfully
CIP Extended error code
USINT
0x00
--
If an ror occurs while the request is executed, the response area has the following content: er
CIP format
Data type
MSG Cong
Description
CIP Class ID
UINT
0x80
Object class "IO-Link Requests"
CIP Instance ID
UINT
0x01
IO-Link master
CIP Attributes
USINT
0x03
Port number
CIP Service code ID
USINT
0x4B
Service "Write_ISDU"
CIP Error code
USINT
0x1E
Error code: Embedded Service Error
CIP Extended error code
USINT
0x00
--
CIP User specic service data
USINT
0x80
IO-Link Error Code: Error in device application
USINT
0x23
IO-Link Additional Code: Access denied
>
Write Failsafe Pattern
54597
By using Write Failsafe Pattern the fail-safe value of a IO-Link port can be written.
>
Request
54694
CIP Attribute determines the IO-Link port. The area CIP User Specific Service Data includes the
fail-safe mode and the fail-safe value (Failsafe Pattern).
CIP Format
Data type
MSG Cong
Description
CIP Class ID
UINT
0x80
IO-Link acyclic access
CIP Instance ID
UINT
0x01
IO-Link master
CIP Attribute
USINT
0x01...0x08
Port number
CIP Service Code ID
USINT
0x4D
Request "Write Failsafe Pattern"
CIP User Specic Service Data
USINT
0x00 = No Fail-safe
0x01 = Fail-safe Reset Value
0x02 = Fail-safe Old Value
0x03 = Fail-safe with Pattern
Failsafe Mode
USINT
0x00...0xFF
Failsafe Pattern (MSB)
USINT
0x00...0xFF
Failsafe Pattern (LSB)
>
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
139
Response
54695
• Positive response
If the service was executed successfully (CIP Error Code = 0), the area "User Specic Data" will
remain empty. The response has the following format:
CIP Format
Data type
MSG Cong
Description
CIP Class ID
UINT
0x80
IO-Link acyclic access
CIP Instance ID
UINT
0x01
IO-Link master
CIP Attribute
USINT
0x01...0x08
Port number
CIP Service Code ID
USINT
0x4D
Response "Write Failsafe Pattern"
CIP Error Code
USINT
0x00
--
CIP Extended Error Code
USINT
0x00
--
• Negative response
If an error occurs while executing the service (CIP Error Code <> 0), an extended error code is
transmitted (CIP Extended Error Code). The answer has the following format:
CIP-Format
Data type
MSG Cong
Description
CIP Class ID
UINT
0x80
IO-Link acyclic access
CIP Instance ID
UINT
0x01
IO-Link master
CIP Attribute
USINT
0x01...0x08
Port number
CIP Service Code ID
USINT
0x4D
Response "Write Failsafe Pattern"
CIP Error Code
USINT
<> 0x00
Error code: see below
CIP Extended Error Code
USINT
<> 0x00
Extended error code
CIP Error Code:
Code
Description
0x02
Resource not available: The IO-Link port is busy processing another acyclic service.
0x05
Invalid class ID or instance ID
0x08
Wrong service ID: only service 0x4B, 0x4C or 0x4D is permitted
0x09
Wrong attribute ID: wrong port number
0x20
Invalid parameter value (e.g. invalid length)
0x1E
Embedded service, error: Error occurred during an IO-Link service. Byte 0 and byte 1 of the User Specic Service
Data contain the IO-Link error code and an additional code that are returned by the IO-Link master (see below).
0x0F
Insucient access rights
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
140
>
Example: Write fail-safe value
54696
Task: Write fail-safe mode for IO-Link port X02 to "Fail-safe with pattern" and fail-safe value to 0x1234
• -Link device in the port: 0x02 IO
• Fail-safe mode: 0x03
• Fail-safe value: 0x1234
From this, the following results for the conguration of the EtherNet/IP command message (MSG):
CIP Format
Data type
MSG Cong
Description
CIP Class ID
UINT
0x80
IO-Link acyclic access
CIP Instance ID
UINT
0x01
IO-Link master
CIP Attribute
USINT
0x02
Port number
CIP Service Code ID
USINT
0x4D
Request "Write Failsafe Pattern"
CIP User Specic Service Data
USINT
0x03
"Fail-safe with Pattern" mode
USINT
0x12
Failsafe Pattern (MSB)
USINT
0x34
Failsafe Pattern (LSB)
After successful execution of the request, the response area has the following content:
CIP-Format
Data type
MSG Cong
Description
CIP Class ID
UINT
0x80
IO-Link acyclic access
CIP Instance ID
UINT
0x01
IO-Link master
CIP Attribute
USINT
0x02
Port number
CIP Service Code ID
USINT
0x4D
Response "Write Failsafe Pattern"
CIP Error Code
USINT
0x00
Request processed successfully
CIP Exended Error Code
USINT
0x00
--
If an error occurs while the request is executed, the response area will have the following content:
CIP-Format
Data type
MSG Cong
Description
CIP Class ID
UINT
0x80
IO-Link acyclic access
CIP Instance ID
UINT
0x01
IO-Link master
CIP Attribute
USINT
0x02
Port number
CIP Service Code ID
USINT
0x4D
Response "Write Failsafe Pattern"
CIP Error Code
USINT
e. g. 0x0F
Error code: Insucient access rights
CIP Exended Error Code
USINT
0x00
no additional information
IO-Link master with EtherNet/IPinterface DataLine 8 ports IP 65 / IP 66 / IP 67 / IP 69K
141
TCP/IP object (object class: 0xF5)
34388
TCP/IP Interface Object enables the conguration of the physical network interface of the device.
>
Class attributes
34311
Attr ID
Access
Name
Data type
Description
Value
1
Get
Revision
UINT
Revision of the object
4
2
Get
Max instance
UINT
Max. number of instances of the object
1
>
Instance attributes
34330
Attr.
ID
Access
Name
Data type
Description
Preset
1
Get
Status
DWORD
Status of the TCP/IP interface
Bit
0...3
Conguration status of the interface
Bit 4
Mcast pending (always 0)
Bit 5
Interface conguration pending
Bit 6
ACD Status
Bit 7
ACD Fault
Bit
8...31
reserved
2
Get
Conguration Capability
DWORD
Functions of the interface (ags)
0x95
(BOOTP,DHCP
Client,TCP/IP
congurable,
ACD capable)
Bit 0
BOOTP Client
Bit 1
reserved
Bit 2
DHCP Client
Bit 3
reserved
Bit 4
TCP/IP congurable via EtherNet/IP
Bit 5
reserved
Bit 6
reserved
Bit 7
ACD Capable
Bit
8...31
reserved
3
Get,
Set
Conguration Control
DWORD
Interface control (control ags):
0
Bit
0...3
Start-up conguration
0
Static IP conguration
1
Conguration via BOOTP
2
Conguration via DHCP
Bit 4
reserved
Bit
5...31
reserved
4
Get
Physical Link Object path
STRUCT:
Logical path to the physical communication
interface: the Ethernet Link object
▪ Path Size
▪ UINT
Length (in Little Endian Format as WORD)
02 00
Produkt Specifikationer
| Mærke: | IFM |
| Kategori: | Ikke kategoriseret |
| Model: | AL1323 |
Har du brug for hjælp?
Hvis du har brug for hjælp til IFM AL1323 stil et spørgsmål nedenfor, og andre brugere vil svare dig
Ikke kategoriseret IFM Manualer
10 August 2025
10 August 2025
10 August 2025
10 August 2025
10 August 2025
9 August 2025
9 August 2025
9 August 2025
9 August 2025
9 August 2025
Ikke kategoriseret Manualer
- Lutec
- Workzone
- BeamZ
- Ygnis
- 9.solutions
- MB Music
- Elbro
- WesAudio
- JL Cooper
- Linn
- Dux
- Sonorous
- Octavio
- Kindercraft
- KEF
Nyeste Ikke kategoriseret Manualer
15 August 2025
15 August 2025
15 August 2025
15 August 2025
15 August 2025
15 August 2025
15 August 2025
15 August 2025
14 August 2025
14 August 2025