English Manual: For 7/8" 4-Pin and 5-Pin Devices of The IMPACT67 Compact Series

ENGLISH MANUAL
for 7/8“ 4-pin and 5-pin devices of the IMPACT67

compact series
© Murrelektronik GmbH
Document status:
Manual number 55142

Language EN
Version 1.2
Date 2019-11
Murrelektronik GmbH
Falkenstraße 3
71570 Oppenweiler
GERMANY
Phone +49 7191 47-0
Fax +49 7191 47-491000
info@murrelektronik.com
NOTE
Translation of the original instructions
This document applies to devices of the IMPACT67 series
Material short text Art.-No.

IMPACT67 E DIO16 5P 55138
IMPACT67 E DIO14 DIO2/IOL2 5P 55139
User manual 55142_hdb_en_12 3 / 112

Table of Contents
1 Introduction 7
1.1 Service and support 7
1.2 About this manual 8
1.3 Symbols 9
1.4 Trademarks 10
2 For your safety 11

2.1 General safety instructions 11
2.2 Intended purpose 12
2.3 Environmentally friendly disposal 13
3 Description 14
3.1 Ethernet/IP 14
3.1.1 Communication 14
3.1.2 RPI 15
3.1.3 QuickConnect™ 16
3.1.4 Device Level Ring (DLR) 16
3.2 IO-Link 17
3.3 Module 18
3.3.1 Product Designation Code 18
3.3.2 Module structure 19
3.3.3 Display elements 21
3.3.4 Connections 23
3.3.5 DIP switch settings 24
4 Technical Data 25
5 Mounting 28
5.1 Requirements 28
5.2 Dimensions 28
5.3 Mounting distance 29
5.4 Installing the module 30
5.4.1 Functional ground 32
5.4.2 Addressing lid 32
6 Installation 33
6.1 Electrical Installation of the Module 33
6.1.1 Sensors and actuators 34
6.1.2 Connecting Ethernet bus 36
6.1.3 Connecting the power supply 36
6.2 Ensuring Tightness (IP67) 37
7 Start-up 38
7.1 Loading the EDS files 39
7.2 Adding a module to the network 41
ENGLISH MANUAL 4 / 112

for 7/8“ 4-pin and 5-pin devices of the IMPACT67 compact series
7.3 Commissioning without EDS 46
7.3.1 Connections, parameters and properties 46
7.3.1.1 Connection matrix 46
7.3.1.2 Assemblies 53
7.4 Configuration/settings 57
7.4.1 Module configuration 57
7.4.2 Setting parameters 60
7.4.3 RPI configuration 61
7.4.4 QuickConnect™-configuration 63
7.4.5 DLR configuration 64
7.4.6 IO-Link configuration 65
7.4.7 Configuration values 66
7.5 Web server 70
7.5.1 The Murrelektronik web server 70
7.5.2 Device menu 71
7.5.2.1 STATUS menu 71
7.5.2.2 PARAMETERS menu 73
7.5.2.3 DIAGNOSTICS menu 74
7.5.2.4 MAINTENANCE menu 74
8 Operation 76
8.1 Diagnostics 76
8.1.1 LED indication for inputs and outputs 76
8.1.2 LED indication for state 77
8.1.3 LED display MS and NS 78
8.1.4 LED indication for LNK/ACT 79
8.1.5 LED indicator power US and UA 80
8.1.6 Extended LED indications 81
8.1.7 Diagnostics structure in the control system 84
8.1.8 Diagnostics in the web server 84
8.1.9 Diagnostic values 85
8.2 Acyclic IO-Link device access 89
8.2.1 Reading an IO-Link device index 89
8.2.2 Writing an IO-Link device index 90
8.2.3 Read/Write ISDU Service 91
8.2.4 IO-Link master error codes 91
9 Maintenance and cleaning 92
10 Appendix 93
10.1 Supported EtherNet / IP objects 93
10.2 Standards 93
10.2.1 Identity Object (Class Code: 0x01) 93
10.2.2 Message Router Object (Class Code: 0x02) 94
10.2.3 Assembly Object (Class Code: 0x04) 94
10.2.4 Connection Manager Object (Class Code: 0x06) 94
10.2.5 Discrete Input Point Object (Class Code: 0x08) 95

10.2.6 Discrete Output Point Object (Class Code: 0x09) 96
10.2.7 Device Level Ring (DLR) Object (Class Code: 0x47) 97
10.2.8 Quality of Service Object (Class Code: 0x48) 98
10.2.9 TCP/IP Interface Object (Class Code: 0xF5) 100
10.2.10 Ethernet Link Object (Class Code: 0xF6) 101
10.2.11 Vendor Specific Objects 103
10.2.11.1 IO-Link parameter object (class code: 0x80) 103
10.3 Explanation of the process data 106
10.3.1 Digital Input 106
10.3.2 DI Qualifier 106
10.3.3 DO Qualifier 107
10.3.4 System Status 107
10.3.5 IO-Link Port X Status 107
10.3.6 Diagnostic Buffer 107
10.3.7 Digital Output 108
10.4 Accessories 108
10.4.1 System components 108
10.4.2 Tools 108
10.5 Glossary 109
11 Legal notes 111

Introduction
1 Introduction
1.1 Service and support
Service and support

Sales Our sales staff in-house and in the field, and our technicians will support you
at all times.
CONNECTIVITY- Our system advisors are your competent contact persons if you want to devel-
System advisors op CONNECTIVITY solutions. They cooperate with you to find the best solu-
tions for your electrical installations.
Our CONNECTIVITY system advisors find ways that help you to permanently
improve the competitiveness of your machines and plants.
Customer Service Cen- Our staff of the Customer Service Center will help you with all questions con-
ter (CSC) cerning installation and start-up. They support you, for example, if you have
problems with combining hardware and software products from different man-
ufacturers.
A number of support tools and measurement facilities are available for field
bus systems and EMC interference.
Call us on +49 7191 47-2050 or send us an
e-mail to: support@murrelektronik.com
Service addresses Murrelektronik GmbH has a policy of customer proximity, both at the national
and international level. Please visit our website to find your contact person:
www.murrelektronik.com

Introduction
1.2 About this manual

Scope This document describes the use of the modules
Article name Article number

Information This document contains information on
 fitting and electrical installation

 startup and parameterization
 circuit examples
 fault diagnosis and troubleshooting
 conformity and approval
 Read this chapter carefully before you start working with the documenta-
tion or the device.
 Read the documentation carefully before starting up the device.
 Store the manual in a place that is accessible to all users at all times for
the entire service life of the device.
You will need general knowledge about automation engineering in order to un-
derstand this manual. In addition, planning and using automation systems re-
quires technical knowledge which is not contained in this manual.
Purpose of this This document instructs the technical staff of the machine manufacturer or
document machine operator on the safe use of the devices described in the
"Scope of Application".
It does not include instructions on the safe use of the machine in which the
devices are integrated. For information about this, refer to the operating man-
ual of the machine.
Other applicable docu- Document Art.-No. Location

ments Operating instructions 55138 Included in the scope of delivery or down-
55139 loadable from
55140 http://shop.murrelektronik.com
55142
55143
55144
EtherNet/IP specification http://www.odva.org
IO-Link http://www.io-link.com

Introduction
1.3 Symbols
This document includes information and notes that have to be observed for
your own safety and to avoid injuries and material damage. They are marked
as follows:
DANGER!
Immediate danger
 Failure to observe this warning involves an imminent risk of death or seri-
ous injuries.
WARNING!
Possible danger
 Failure to observe this warning can lead to death or serious injuries.
CAUTION!
Low-risk danger
 Failure to observe this warning can lead to mild to moderate injuries.
NOTICE
Possible material damage
 Failure to observe the warning may cause damage to the device and/or
the system.
NOTE
Other technical information and notes of Murrelektronik GmbH.
RECOMMENDATION
Notes with this symbol are recommendations of Murrelektronik GmbH.
PRODUCTS AND ACCESSORIES

This symbol indicates accessories or product recommendations.
Instruction for use  An arrow marks instructions.

 Read and observe the instructions.
1 | If they are numbered, it is absolutely necessary to follow them in the cor-
rect order.
2 | Read and observe the instructions.

Introduction
1.4 Trademarks
Trademarks of the following companies and institutions are used in this docu-
mentation:
EtherNet/IP © ODVA, Inc.
IO-Link c/o PROFIBUS Nutzerorganisation e.V. (PNO)

For your safety
2 For your safety

 Read this chapter carefully.
 Only after that you may work with the fieldbus module.
2.1 General safety instructions
DANGER!
High electrical voltage in the machine/system.
Death or severe injuries resulting from electric shock.
 When working on the machine/modules, comply with the five safety rules
of electrical engineering.
Protection of persons  In accordance with DIN VDE 0105-100 – Operation of electrical installa-
and material property. tions; Part 100: General specifications
The five safety rules Protect against high electrical voltage
1 | Disconnect
2 | Secure against switching on again
3 | Make sure that there is no voltage on all poles.
4 | Ground and short-circuit
5 | Cover or
block off neighboring parts that are live or energized
Qualified personnel Only qualified personnel instructed in safety is allowed to install the module
and to put it into operation.
They are qualified if they meet the following requirements:
 They have undergone suitable electrical engineering training,
 They were trained by the machine operator to operate the machine and
instructed on the related safety regulations,
 They have access to the Operating Instructions and the manual
 They are familiar with the safety standards which are common practice in
automation engineering
 They are familiar with the basic and technical standards related to the spe-
cific application
Use of the device  Comply with all safety and accident prevention regulations when conduct-
ing project engineering, installation, commissioning, operation, and testing
of the device.
 Check material resistance if aggressive media are used.
NOTE
Work on the hardware and software of the device may only be performed by
qualified personnel of Murrelektronik GmbH, with the exception of firmware
updates.

For your safety
NOTE
Use only a power supply unit that allows max. 60 V DC or 25 V AC in case of
error. The power supply must comply with SELV or PELV.
CAUTION!
Hot surface!
Minor injuries caused by contact with the surface.
 Wear thermally suitable gloves.
Protective measures by  Pay absolute attention to the instructions in this manual.

the  Pay attention to the test regulations contained in the operating instructions
machine operator of all connected components.
2.2 Intended purpose

Intended use IMPACT67 is a decentralized fieldbus module. It can be used in harsh indus-
trial environments up to degree of protection IP67.
Operation of the device in accordance with its designated use and the degree
of protection IP67 are only guaranteed if open male and female connectors
are closed using screw plugs.
Designated use also includes EMC-compliant electrical installation. The de-
vice is designated for use in industrial environment. Radio interference may
occur if used in a domestic or mixed environment.
 If the fieldbus module is used in domestic and mixed environments, the
applicable standards must be observed.
Foreseeable misuse  Do not alter the design, engineering, or electrical features of the module.
 Do not use the module outside the application fields described in this
manual, the Technical Data or in the operating instructions.
 Do not use the module as safety-related device. It does not meet the rel-
evant standards. Safety functions of the system are not ensured!
 Do not use the Off state of the module outputs for safety-related require-
ments of the system/machine!
 Do not use the module outdoors or for continuous operation in liquids.
 Do not clean the module with a high-pressure cleaner.
 Do not use the module as a climbing aid.
Warranty and liability Warranty and liability claims shall be lost if
claims  the product is not used according to its designated use,
 damage is caused because the manual and the operating instructions
have not been observed,
 the personnel was/is not qualified.

For your safety
2.3 Environmentally friendly disposal

Comply with  Always dispose of scrap devices in compliance with the valid
country-specific country-specific regulations for waste disposal
waste disposal regula- (e.g., the European Waste Code 16 02 14).
tions.
Only qualified persons  Proceed with caution when dismantling the device since you could injure
may sort scrap materi- yourself.
als.  Sort the separated components into the correct recycling line.
Disposal
The product can be returned to Murrelektronik GmbH free of charge for dis-
posal. The same is true for the original packaging and any batteries or power
packs. Any units that have been contaminated with hazardous substances will
not be accepted for repair or disposal.
Returns
 Label the product and the packaging with
"For disposal".
 Package the product.
 Send the package to:
Murrelektronik GmbH
Falkenstraße 3
71570 Oppenweiler | GERMANY
We will make sure that the items are disposed of in accordance with German
legislation. The most recent owner is responsible for transport to the return
point until items arrive at their destination.

Description
3 Description
3.1 Ethernet/IP
3.1.1 Communication
EtherNet/IP is based on a generator/receiver communication model for which

the multicast Ethernet communication enables fast "Report by exception" re-
sponses.
The connection to the control scanner is established in an Ethernet/IP network
only via Fast Ethernet switches (100MBit/s).
The maximum permissible cable length to the end point without any auxiliary
devices is 100 m.
A 2-port switch is integrated into the device (target). The switches send multi-
cast messages to all switch ports and behave in this case like a hub. When
EtherNet/IP Unmanaged Switches are used, this means that the more multi-
cast users (Ethernet/IP users) are added to the system, the higher the multi-
cast traffic for the users. Thus, a higher amount of bandwidth is used in the
system which results in longer response times. Each user must supply more
CPU power to view and reject messages that are not addressed to the user.
If the number of messages to be processed is too high, the user may be sub-
ject to an overload; missing responses may be at the incorrect RPI speed and,
ultimately, this may lead to an interruption in communication. This overload sit-
uation may influence both the PC/PLC scanner and the I/O user.
It is therefore recommended to split the entire network into several segments
by means of several switches. By choosing suitable RPI times and switches,
high-speed networks can be decoupled from non-time-critical systems.
The EtherNet/IP Unmanaged Switches should only be used in small isolated

systems, i.e., systems that are not connected to the company network or pro-
gram-wide networks.
For high-speed control systems of average size or any size, the use of Man-
aged Switches is recommended. To manage the multicast traffic, the switch
must support the IGMP Snooping function (Internet Group Management Pro-
tocol). For the connection of a control system to a large plant or company net-
work, a virtual LAN switch function of the use of routers is usually required.
Unicast connections.
The device has the possibility to establish data connections via so-called Uni-
cast connections. These connections allow a clear assignment of start and tar-
get addresses and this should result, in combination with the switches, in a
reduced data volume in the network. Please select the best type of connection
depending on your application.

Description
3.1.2 RPI
Requested Packet Inter- When setting up an EtherNet/IP system, the RPI value must be carefully set
val (RPI) in the scanner.
According to the manufacturer's version, this value is in the range between 1
ms and several hundred ms.
The RPI value determines the speed at which the scanner sends Ethernet/IP
messages (packets).
It also determines the maximum speed at which the bus node sends
messages.
The value that is set in the scanner is transmitted to the device as soon as the
connection is established so that the system uses the same time base.
The RPI value can be used not only to set the speed but also to set the speed
at which the scanner expects timely reception.
If the selected RPI time is too short, a higher network load is automatically
generated.
Due to the higher network load, the system must spend more time to process
the queries accordingly.
This is also applicable to the messages which are not addressed directly to the
device since they must be accepted and rejected anyway.
This results in an overload situation in which the device is no longer able to
execute the internal processes and adhere to the required RPI time.
If the reception of the telegram exceeds the set RPI time by a factor of 4, the
control interrupts the I/O communication and switches into an error state.
Please observe:
a | Configurations which require RPI times shorter than 10 ms must be tested
in advance for correct operation.
b | The minimum supported RPI time is 1 ms!
For further information, refer to chap. 7.4.3 "RPI configuration"

Description
3.1.3 QuickConnect™
QuickConnect™ QuickConnect™ describes the functional ability to quickly connect a device to

a network and to put it into operation.
This also applies to the mechanical and logical removal of the device.
The objective of QuickConnect™ is to establish a connection between device
and control system and to receive input process data within 500 ms (Class A)
or less.
To achieve this objective, devices which support this function must be special-
ly configured.
This includes the fixed setting of Ethernet port bandwidths and the deactiva-
tion of the MDIX function.
For further information, refer to chap. 7.4.4 "QuickConnect™-configuration"
3.1.4 Device Level Ring (DLR)
Device Level Ring Device Level Ring (DLR) is a protocol which allows media redundancy in a
(DLR) ring topology, e.g. for Ethernet/IP™.
A ring network consists of at least one ring supervisor and any desired number
of users.
To build up the topology and to detect cable breaks inside the ring, there are
two different methods:
a | Beacon-based
b | Announce-based
Users which support DLR must have implemented the DLR object (0x47) that
provides the methods for configuration and diagnostic.
The modules described in this manual support the beacon-based DLR tech-
nology.
The described modules do not support the ring supervisor function and can
therefore not be used as ring supervisor.
For further information, refer to chap. 7.4.5 "DLR configuration"

Description
3.2 IO-Link
IO-Link is a standardized link that enables connection of intelligent devices of
the sensor and actuator level to an automation system.
Communication takes place between a master and a device. A master module
has one or more ports. One device can be connected per port, which means
that the IO-Link is a point-to-point communication system and not a fieldbus.
The IO-Link master module builds the interface between the higher fieldbus
level and the IO-Link system.
The IO-Link device converts the data of the sensors/actuators into the IO-Link
format and passes the data on to the master. The device can be implemented
either directly into the sensor/actuator or as a separate device.
Fig. 3-1: IO-Link
For further information, refer to chap. 7.4.6 "IO-Link configuration"

Description
3.3 Module
3.3.1 Product Designation Code
Structure of the product The designation is based on a scheme that indicates the product's function.
designation Example Art.-No. 55144
IMPACT67 E DIO12 DIO4/IOL4 4P

IMPACT67 Product family
E Ethernet/IP
DIO12 12 digital I/O channels
IOL IO-Link
DIO4/IOL4 4x digital inputs/outputs
4x IO-Link
4P Power supply 7/8", 4-pin
Properties The IMPACT67 is a fully encapsulated fieldbus module in a plastic case. It is

particularly robust and designed for use in rough environments.
Property Description
Robust Versatile applications under very high
loads due to:
 robust plastic case,
 No formation of water of condensation
due to fully encapsulated case.
Vibration-proof Safety function also guaranteed when subjected to con-
tinuous vibration
Resistant Long service life despite exposure to aggressive media
due to a
high-quality surface finish.
Tight Tight up to degree of protection IP67 (EN 60529)

Description
3.3.2 Module structure
Articles 55138, 55139 and 55140

X0 ... X3 Digital inputs and outputs
X4 ... X7 Digital inputs and outputs or IO-Link
XD1 Power supply POWER IN
XD2 Power supply POWER OUT
XF1 Ethernet port 1
XF2 Ethernet port 2
1 DIP switch
2 Ground strap for functional ground

Description
Articles 55142, 55143 and 55144

X0 ... X3 Digital inputs and outputs
X4 ... X7 Digital inputs and outputs or IO-Link
XD1 Power supply POWER IN
XD2 Power supply POWER OUT
XF1 Ethernet port 1
XF2 Ethernet port 2
1 DIP switch
2 Ground strap for functional ground

Description
3.3.3 Display elements
Articles 55138, 55139 and 55140
Art.-No. 55138
X0 ... X7 LED digital inputs and digital outputs
Art.-No. 55139
X6, X7 LED digital outputs and digital inputs
or IO-Link
Art.-No. 55140
X4 ... X7 LED digital outputs and digital inputs
or IO-Link
1 LED MS
LED NS
LED LNK1/ACT1
LED LNK2/ACT2
LED POWER UA
LED POWER US
LED status (ST)
Fig. 3-2: Display elements

Description
Articles 55142, 55143 and 55144
Art.-No. 55142
Art.-No. 55143
X6, X7 LED digital outputs and digital inputs
or IO-Link
Art.-No. 55144
X4 ... X7 LED digital outputs and digital inputs
or IO-Link
1 LED MS
LED NS
LED LNK1/ACT1
LED LNK2/ACT2
LED POWER UA
LED POWER US
LED status (ST)
Fig. 3-3: Display elements

Description
3.3.4 Connections
Overview Art.-No. DIO IO-Link Class

A/B Hybrid
55138, 55142 X0 ... X7 -
55139, 55143 X0 ... X7 X6, X7
55140, 55144 X0 ... X7 X4 ... X7
Digital inputs / outputs DIO

M12 female connectors Pin 1 24 V
A-coded Pin 2 DI/DO
Pin 3 0V
Pin 4 DI/DO
Pin 5
IO-Link Art.-No. 55139, 55140, 55143, 55144

M12 female connectors
A-coded IO-Link Class B
Pin 1 24 V
Pin 2 DI/DO
Pin 3 0V
Pin 4 DI/DO/IO-Link
Pin 5 0V
POWER Art.-No. 55138, 55139, 55140

connection 7/8" 5-pin
XD1 XD2
Pin 1 0V
Pin 2 0V
Pin 3
Pin 4 24 V US, 9 A
Pin 5 24 V UA, 9 A
POWER Art.-No. 55142, 55143, 55144

connection 7/8" 4-pole
XD1 XD2
Pin 1 24 V UA, 9 A
Pin 2 24 V US, 9 A
Pin 3 0V
Pin 4 0V
Female BUS XF1, XF2

connector M12 Pin 1 TD +
D-coded Pin 2 RD +
Pin 3 TD -
Pin 4 RD -
Pin 5 n.c.

Description
3.3.5 DIP switch settings
Set the DIP switch in such a way that the desired function of the module is
achieved.
DIP switch
10-bit DIP switch
Function/bit Switch position Description

IP address
DIP 1 ... 8 0  Out-of-the-box/Factory Reset:
DHCP/BOOTP queries in 60 second intervals
 Network parameters have been saved pre-
viously:
The parameters saved last are applied.
1 ... 254 The last octet of the saved IP address is overwrit-
ten by the DIP switch setting and applied.
255 The IP address saved last is used.
Activate web server
9 ON Web server off
OFF Web server on
Operating mode
10 ON Factory reset
OFF Normal operation
NOTE
As-delivered: all switches are in the OFF position.
NOTICE
The saved default IP address is 192.168.1.6.
NOTICE
Switches 1 to 8 must be considered a binary number in which switch 1 rep-
resents 20 and switch 8 stands for 27 .
NOTICE
The IP address parameters are stored for all switch settings. This must be tak-
en into account in particular with the switch setting 0.

Technical Data
4 Technical Data
Module supply
Operating voltage US +24 V
Voltage range US 18 ... 30 V
Voltage range US 20.3 ... 30 V
(when using IO-Link)
Operating voltage UA 18 ... 30 V
Max. sensor current US 9A
Max. actuator current UA 9A
Current consumption ≤0.18 A
Cross-section of 7/8" connector ≤1.5 mm²
Reverse polarity protection for US and UA Yes
Reverse polarity protection Yes
Bus
Fieldbus protocol Ethernet/IP
Transfer rate 10/100 Mbit/s
EtherNet/IP addressing via DIP switches
RPI ≥1 ms
DLR Beacon-based Ring
Node
QuickConnect™ Class A
Inputs (DI)
Delay time 1 ms + t cycle
Input characteristic EN 61131-2, type 3
Sensor power supply port DIO ≤0.2 A load
Automatic start
Sensor power supply IO-Link port Art.-No. 55139, 55140, 55143, 55144 ≤1 A load
Automatic start
Short-circuit protection, sensor supply High-side switch with
overload protection
Connection M12
Conductor cross-section M12 ≤0.75 mm²
Outputs (DO)
Output current ≤1.6 A per channel
Frequency ≤50 Hz
Short-circuit protection actuator High-side switch with
overload protection
High-side switch with overload protection M12
Conductor cross-section M12 ≤0.75 mm²

Technical Data
IO-Link - Art.-No. 55139, 55140, 55143, 55144

IO-Link devices operating voltage +24 V
IO-Link devices voltage range 20 ... 30 V
Specification V 1.1
Transfer rate Com 1 / Com 2 / Com 3
Input specification IO-Link specification
EN61131-2, type 1
Transfer rate recognition Automatic
Derating DO output cur-

rent
Fig. 4-1: Derating DO output current
Derating
actuator supply total
current
Fig. 4-2: Derating actuator supply total current

Technical Data
Environmental conditions
Climatic
Operating temperature -25 °C ... +55 °C
Storage temperature -25 °C ... +70 °C
Degree of protection of the housing acc. to EN 60529 IP67
Relative humidity ≤95 %
Installation height ≤2000 m above mean
sea level
Mechanical
Vibration test EN 60068 Part 2-6 10 ... 60 Hz,
amplitude
0,35 mm,
60 ... 150 Hz; 5 g
Shock test EN 60068 Part 2-27 15 g,
duration 11 ms
Electrical safety
Degree of protection EN 60529 IP67
Protection class When using an SELV or PELV power supply III
Degree of pollution 2
Emitted EMC interference

Radio interference field strength EN 55016-2-3 Compliant
housing
Interference voltage EN 55016-1-2 Compliant
EMC immunity
Electrostatic discharge (ESD) EN 61000-4-2 Compliant
High-frequency electrical fields EN 61000-4-3 Compliant
Fast transient burst EN 61000-4-4 Compliant
Voltage surges EN 61000-4-5 Compliant
performed HF EN 61000-4-6 Compliant
Magnetic field 50/60 Hz EN 61000-4-8 Compliant
Power failures EN 61000-4-11 Compliant

Mounting
5 Mounting
5.1 Requirements
 Conditions for mounting:
 Even mounting surface to avoid mechanical tension
 Provide suitable grounding
 Suitable installation site in terms of vibration and shock load, temperature
and humidity (see chap. 4 "Technical Data" )
 Protected to avoid tearing off the connecting cables by personnel or de-
vice
5.2 Dimensions
Fig. 5-1: Dimensions in mm

Mounting
5.3 Mounting distance
Fig. 5-2: Distance in mm
NOTICE
 For correct installation and improved heat dissipation, we recommend
keeping a minimum distance of 3 mm when mounting the IMPACT67.
NOTE
 When using angled connectors, a minimum distance of 50 mm to the wall,
ceiling and between the modules must be kept.

Mounting
5.4 Installing the module
NOTICE
Material damage caused by wrong mounting
The fastening screws and tightening torques depend on the surface of the
mounting location.
 Use fastening screws that are appropriate for the condition of the mount-
ing surface!
 Tighten the screws carefully! The specified tightening torques must be ob-
served.
NOTICE
Material damage through improper use
Do not use the modules as climbing aids. Improper use can cause the mod-
ules to break off or to be damaged otherwise.
 Install the modules in such a way that they cannot be used as climbing aid!

Mounting
Module fastening
Fig. 5-3: Fastening dimensions in mm
Art.-No.
M6 3 Nm 7000-98001-0000000
NOTE
The screws and the grounding strap illustrated are not included in the scope
of delivery.
Mounting Mount the module in the order indicated below:

1 | Slightly tighten the top M6 bolt.
2 | Align housing.
3 | Slightly tighten the lower M6 bolt.
4 | Tighten screws M6 according to the torque.
5 | Grounding the module:
Attach the grounding strap (see chap. 5.4.1 "Functional ground")

Mounting
5.4.1 Functional ground
NOTE
Use a conductive screw to attach the ground strap.
Fig. 5-4: Grounding strap fastening
Art.-No.
M4 1,2 Nm
7000-98001-0000000
5.4.2 Addressing lid
Addressing lid
fastening
Fig. 5-5: Addressing lid fastening
M3 0,8 Nm Art.-No.
7000-98001-0000000

Installation
6 Installation
6.1 Electrical Installation of the Module
WARNING!
Danger due to electric voltage in the machine / system.
It may result in death or fatal injuries.
 1. Observe the five safety rules.
 2. Connect the device to the electrical system.
WARNING!
Fire risk from short-circuits!
Power supply lines and/or modules damaged by short-circuits may cause
overheating and fires.
 Provide an intelligent power monitoring system or fuse.
The fuse must be designed for max. 9 A.
CAUTION!
Loss of function!
 Only install cables and accessories which meet the requirements and reg-
ulations for safety, electromagnetic compatibility and, if necessary, tele-
communication terminal equipment specifications as well as the
specification data.
CAUTION!
Hot surface!
Minor injuries caused by a contact with the surface and damage to devices.
 Wear thermally suitable gloves.
 Use thermally suitable connecting cables only.
NOTICE
Damage in the machine/plant caused by incorrect switching on of volt-
age sources
When the module is switched on with separate actuator and sensor voltage,
the function of the digital inputs and outputs cannot be guaranteed.
 Always switch on voltage sources in the following order:
1 | Switch on sensor voltage.

2 | Switch on actuator voltage.

Installation
NOTE
Use only a power supply unit that allows max. 60 V DC or 25 V AC in case of
error. The power supply must comply with SELV or PELV.
6.1.1 Sensors and actuators
NOTICE
Damage to and failure of the device due to ingress of liquids!
The degree of protection IP67 is only guaranteed if all connections are sealed
with plug connectors, screw plugs or sealing caps.
 Seal unused male and female connectors.
Connection of
M12 female connector
Fig. 6-1: M12 input and output connection example
M12 0.6 Nm Art.-No.

7000-99102-0000000
NOTE
Feeding in an external mass via M12 female connectors can lead to faults.
 Do not feed external mass to the module via M12 female connectors.

Installation
Pin assignment digital Pin Assignment DIO IO-Link Description

ports Port Class
A/B
Pin 1 24 V US   Sensor supply
Pin 2 DI (US) / DO (UA) Freely programmable chan-
  nel (input or output).
Pin 3 0 V   Reference potential
Pin 4 DI (US) / DO (UA)   Freely programmable chan-
IO-Link nel (IO-Link, input/output)

communication Q
Pin 5 0V Reference potential
Sensor supply Please note:

 Sensors can be supplied via pin 1 (24 V) and pin 3 (0 V) of the M12 female
connectors.
 The maximum permissible current for the power supply of the sensors is
0.2 A for the digital I/O port and 1.0 A for the IO-Link port.
 In case of overcurrent or short circuit, the connected cable or sensor must
be disconnected from the M12 female connector.
NOTE
The cable length is limited to 20 m. The IMPACT67 automatically selects the
communication speed suitable for the IO-Link device.
Supported IO-Link The module supports the IO-Link communication using the following speeds:
communication  4,800 baud (COM 1)
 38,400 baud (COM 2)
 230,400 baud (COM 3)

Installation
6.1.2 Connecting Ethernet bus
Connecting the
M12 female connector
(bus)
Fig. 6-2: Example of M12 connection (Ethernet bus)
Art.-No.
M12 0.6 Nm 7000-99102-0000000
6.1.3 Connecting the power supply
Connecting
7/8" male connector
POWER IN
Connecting
7/8" female connector
POWER OUT
Fig. 6-3: Example of 7/8" connection (POWER)
Art.-No.
7/8’’ 1,5 Nm 7000-99104-0000000

Installation
6.2 Ensuring Tightness (IP67)
CAUTION!
Leaky housing!
Risk of personal injury and material damage due to failure caused by ingress
of conductive liquids.
 Seal unused connectors and sockets.
 Suitable sealing connectors/screw plugs for the network port, the POWER
OUT port and I/O female connectors are available as ACCESSORIES.
Cable
connection
Fig. 6-4: Cable connections
You will find a wide range of connecting wires in the catalog or in the online
shop of Murrelektronik GmbH at: http://shop.murrelektronik.com

Start-up
7 Start-up
CAUTION!
Uncontrolled processes
Personal injury and material damage due to incorrectly performed start-up
phases (for example first start-up, recommissioning and configuration chang-
es).
 Always perform start-up in this sequence:
1 | Insert the module.

2 | System check and approval by an expert.
3 | Put into operation.
NOTICE
Functional errors in residential areas
Devices of EMC Class A may cause interferences in residential areas.
 It is the operator's duty to take necessary precautions.

Start-up
7.1 Loading the EDS files

Tool used This chapter describes how to configure and parameterize a IMPACT67, using
the example of Studio5000 Logix Designer from Rockwell Automation Germa-
ny. Studio5000 Logix Designer version 30 is used in the description.
Loading the EDS files Installing the EDS files and/or the module description file.
Fig. 7-1: Loading the EDS files
In Project menu | Tools,

 click EDS Hardware Installation Tool.

Start-up
Fig. 7-2: EDS Wizard
 Click Next and follow the instructions of the dialog window.

 Finish the installation of the EDS files.
The modules can now be selected and added to the network.
Note
The EDS file can be found in the online shop of Murrelektronik GmbH under
the article number of the module.

Start-up
7.2 Adding a module to the network
Adding new modules
Fig. 7-3: New Module
In the Controller Organizer | Ethernet

 Click New Module.
In the following dialog window, modules are shown which
a | have been registered previously with an EDS or
b | have already been delivered with the installation of the engineering soft-
ware.

Start-up
Alternative The dialog window can also be called via the menu line Files/New Compo-
module selection nent/Module.
Fig. 7-4: Alternative module selection

Start-up
Searching a module Use the input mask to search for the module that you want to add to the net-
work.
a | Use search terms which describe the desired module, e.g. product num-
ber, product name or manufacturer.
b | Use a filter from the dialog window.
Fig. 7-5: Searching a module
 Mark the module.

 Double-click Create.

Start-up
General settings
Fig. 7-6: General settings
In New Module | General

 Assign a unique module name.
 Assign an IP address.
In New Module | Connection
 Assign further settings, e.g. the RPI settings.
 Add the module to the network by clicking OK.
Selecting the connec- In order to choose the best connection for every application, you can choose
tion from various connection options:
a | when adding the module to the network, select the right connection or
b | call the settings again by double-clicking the module.

Start-up
Fig. 7-7: Module Definition
In Module Definition
 Click Change.
A new window appears.
 Set the number or the type of connection
7.3.1.1 "Connection matrix" here.
 Click the preset connection (Exclusive Owner).
 Select the connection that meets the requirements.
The list of all connections that can be set is displayed.
NOTICE
The Murrelektronik modules support up to 3 connections at a time.
(1 Exclusive Owner and 2 Non-Exclusive-Owner connections)

Start-up
7.3 Commissioning without EDS
7.3.1 Connections, parameters and properties
NOTICE
Listen Only connections can only be established to Multicast Non-Listen
Only connections of the over EDS category.
This selects the configuration instance to be used for the instance of the Non-
Listen Only connection used.
NOTICE
In order to use connections of the
Configuration via web server assembly instance 175 category, set the
Configuration parameter to over web server.
NOTICE
Expert connections are listed with the minimum length and do not consider
configurations of IO-Link data lengths.
The final length of an assembly instance is the minimum length plus the sum
of all all configured IO-Link data lengths.
Calculate separately for input and output data.
Minimum length + ∑ IO-Link port Z data length
7.3.1.1 Connection matrix

Art.-No. 55142
Exclusive Owner connection
Assembly configuration Description Input assembly Output

over EDS over web server assembly
Instance Length Instance Length In- Length In- Length
170 26 175 0 stance stance
E01 WE01 Digital IOs 100 10 140 2
Tab. 7-1: Exclusive Owner connection
Input Only connection

I01 IE01 Digital IOs 100 10 193 0
Tab. 7-2: Input Only connection
Listen Only connection
Description Input assembly Output

assembly
In- Length In- Length
stance stance
I01 Digital IOs 100 10 192 0
Tab. 7-3: Listen Only connection

Start-up
Art.-No. 55143

E01 WE01 Digital IOs 100 10 140 2
E02 WE02 Digital IOs, IOL 2 bytes 101 14 141 6
E03 WE03 Digital IOs, IOL 2 bytes with status 102 26 141 6
diagnostics
diagnostics
diagnostics
diagnostics
diagnostics
Exclusive Owner connection in the expert mode
Assembly configuration Description Input Output

over EDS over web server
E17 WE17 Digital IOs, IOL X bytes 116 ≥10 151 ≥2
E18 WE18 Digital IOs, IOL X bytes with status 117 ≥20 151 ≥2
E19 WE19 Digital IOs, IOL 2 bytes with status 118 ≥86 152 ≥4
diagnostics
Tab. 7-5: Exclusive Owner connection in the expert mode

Start-up

I01 WI01 Digital IOs 100 10 193 0
I02 WI02 Digital IOs, IOL 2 bytes 101 14
I03 WI03 Digital IOs, IOL 2 bytes with status 102 26
diagnostics
diagnostics
diagnostics
diagnostics
diagnostics
Input Only connection in expert mode

E17 WE17 Digital IOs, IOL X bytes 116 ≥10 193 0
E18 WE18 Digital IOs, IOL X bytes with status 117 ≥22
E19 WE19 Digital IOs, IOL X bytes with status 118 ≥86
diagnostics
Tab. 7-7: Input Only connection in expert mode

Start-up
Connection Description Input assembly Output

assembly
stance stance
L01 Digital IOs 100 10 192 0
L02 Digital IOs, IOL 2 bytes 101 14
L03 Digital IOs, IOL 2 bytes with status 102 26
diagnostics
diagnostics
diagnostics
diagnostics
diagnostics
L17 Digital IOs, IOL X bytes 116 ≥10
L18 Digital IOs, IOL X bytes with status 117 ≥22
diagnostics

Start-up
Art.-No. 55144
Connection Description Input Output

Configuration over Configuration via
EDS web server
E01 WE01 Digital IOs 100 10 140 2
diagnostics
diagnostics
diagnostics
diagnostics
diagnostics
Exclusive Owner connection in expert mode

E17 WE17 Digital IOs, IOL X bytes 134 ≥10 163 ≥2
E18 WE18 Digital IOs, IOL X bytes with status 135 ≥34 163 ≥2
E19 WE19 Digital IOs, IOL 2 bytes with status 136 ≥98 164 ≥4
diagnostics
Tab. 7-10: Exclusive Owner connection in expert mode

Start-up

I01 WI01 Digital IOs 100 10 193 0
diagnostics
diagnostics
diagnostics
diagnostics
diagnostics
Input Only connection in expert mode

I17 WI17 Digital IOs, IOL X bytes 134 ≥10 193 0
I18 WI18 Digital IOs, IOL X bytes with status 135 ≥34
I19 WI19 Digital IOs, IOL 2 bytes with status 136 ≥98
diagnostics
Tab. 7-12: Input Only connection in expert mode

Start-up
Connection Description Input assembly Output

assembly
stance stance
L01 Digital IOs 100 10 192 0
diagnostics
diagnostics
diagnostics
diagnostics
diagnostics
L17 Digital IOs, IOL X bytes 134 ≥10
diagnostics

Start-up
7.3.1.2 Assemblies
Byte sequence configuration

Assembly Instance 170/171/1723/173/174/175
Parameters Instance Instance Instance Instance Instance Instance
170 171 172 173 174 175
Total size in bytes 26 86 146 90 154 0

Diagnostic 0 ... 7 0 ... 7 0 ... 7 0 ... 7 0 ... 7
General 8 ... 25 8 ... 25 8 ... 25 8 ... 25 8 ... 25
IO-Link port 1 26 ... 55 26 ... 51 26 ... 51 26 ... 51
IO-Link port 2 56 ... 85 56 ... 85 56 ... 85 56 ... 85
IO-Link port 3 86 ... 115 86 ... 115
IO-Link Port 4 116 ... 145 116 ... 145
IO-Link port 1 86 ... 87 146 .. 147
length
IO-Link port 2 88 .. 89 148 .. 149
length
IO-Link port 3 150 .. 151
length
IO-Link port 4 152 .. 153
length
Tab. 7-14: Instance:170/171/172/173/174/175
Sequence of input Input 100

bytes
Instance
100
Total length in bytes 10
Digital input 0 ... 1
DI Qualifier 2 ... 3
DO Qualifier 4 ... 5
System status 6 ... 9
Tab. 7-15: Input 100
Instance 101/104/107/110/113/116
101 104 107 110 113 116
Total length in 14 18 26 42 74 10 + ∑
bytes IO-Link input data
Digital inputs 0 ... 1 0 ... 1 0 ... 1 0 ... 1 0 ... 1 0 ... 1
DI Qualifier 2 ... 3 2 ... 3 2 ... 3 2 ... 3 2 ... 3 2 ... 3
DO Qualifier 4 ... 5 4 ... 5 4 ... 5 4 ... 5 4 ... 5 4 ... 5
System status 6 ... 9 6 ... 9 6 ... 9 6 ... 9 6 ... 9 6 ... 9
IO-Link port 1 10 ... 11 10 ... 13 10 ... 17 10 ... 25 10 ... 41 ...
input data (0 ... 32 bytes)
IO-Link port 2 12 ... 13 14 ... 17 18 ... 25 26 ... 41 42 ... 73 ...
Tab. 7-16: Instance 101/104/107/110/113/116

Start-up
Instance 102/105/108/111/114/117
102 105 108 111 114 117
Total length in 26 30 38 54 86 22 + ∑
Digital input 0 ... 1 0 ... 1 0 ... 1 0 ... 1 0 ... 1 0 ... 1
DI Qualifier 2 ... 3 2 ... 3 2 ... 3 2 ... 3 2 ... 3 2 ... 3
DO Qualifier 4 ... 5 4 ... 5 4 ... 5 4 ... 5 4 ... 5 4 ... 5
System status 6 ... 9 6 ... 9 6 ... 9 6 ... 9 6 ... 9 6 ... 9
IO-Link port 1 10 ... 11 10 ... 13 10 ... 17 10 ... 25 10 ... 41 ...
IO-Link port 1 12 ... 17 14 ... 19 18 ... 23 26 ... 41 42 ... 47 X ... X+5
status (6 bytes)
IO-Link port 2 18 ... 19 20 ... 23 24 ... 31 42 ... 47 48 ... 79 ...
IO-Link port 2 20 ... 25 24 ... 29 32 ... 37 48 ... 53 80 ... 85 Y ... Y+5
status (6 bytes)
Tab. 7-17: Instance 102/105/108/111/114/117
Instance 103/106/109/112/115/118
103 106 109 112 115 118
Total length in 90 94 102 118 150 86 + ∑
Digital input 0 ... 1 0 ... 1 0 ... 1 0 ... 1 0 ... 1
DI Qualifier 2 ... 3 2 ... 3 2 ... 3 2 ... 3 2 ... 3 2 ... 3
DO Qualifier 4 ... 5 4 ... 5 4 ... 5 4 ... 5 4 ... 5 4 ... 5
System status 6 ... 9 6 ... 9 6 ... 9 6 ... 9 6 ... 9 6 ... 9
IO-Link port 1 10 ... 11 10 ... 13 10 ... 17 10 ... 25 10 ... 41 ...
IO-Link port 1 12 ...17 14 ... 19 18 ... 23 26 ... 31 42 ... 47 X ... X+5
status (6 bytes)
IO-Link port 2 18 ... 19 20 ... 23 24 ... 31 32 ... 47 48 ... 47 ...
input data (0 ... 32 bytes).
IO-Link port 2 20 ... 25 24 ... 29 32 ... 37 48 ... 53 80 ... 85 Y ... Y+5
status (6 bytes)
Diagnostic 26 ... 89 30 ... 93 38 ... 101 54 ... 117 86 ... 149 ...
buffer (64 bytes)
Tab. 7-18: Instance 103/106/109/112/115/118
Instance 119/122/125/128/131/134
119 122 125 128 131 134
Total length in 18 26 42 74 138 10 + ∑
Digital input 0 ... 1 0 ... 1 0 ... 1 0 ... 1 0 ... 1 0 ... 1
DI Qualifier 2 ... 3 2 ... 3 2 ... 3 2 ... 3 2 ... 3 2 ... 3
DO Qualifier 4 ... 5 4 ... 5 4 ... 5 4 ... 5 4 ... 5 4 ... 5
System status 6 ... 9 6 ... 9 6 ... 9 6 ... 9 6 ... 9 6 ... 9
IO-Link port 1 10 ... 11 10 ... 13 10 .. 17 10 ... 25 10 ... 41 ...
IO-Link port 2 12 ... 13 14 ... 17 18 ... 25 26 ... 41 42 ... 73 ...
IO-Link port 3 14 ... 15 18 ... 21 26 ... 33 42 ... 57 74 ... 105 ...
IO-Link port 4 16 ... 17 22 ... 25 34 ... 41 58 ... 73 106 ... 137 ...
Tab. 7-19: Instance 119/122/125/128/131/134

Start-up
Instance 120/123/126/129/132/135
120 123 126 129 132 135
Total length in 42 50 66 98 162 34 + ∑
Digital input 0 ... 1 0 ... 1 0 ... 1 0 ... 1 0 ... 1 0 ... 1
DI Qualifier 2 ... 3 2 ... 3 2 ... 3 2 ... 3 2 ... 3 2 ... 3
DO Qualifier 4 ... 5 4 ... 5 4 ... 5 4 ... 5 4 ... 5 4 ... 5
System status 6 ... 9 6 ... 9 6 ... 9 6 ... 9 6 ... 9 6 ... 9
IO-Link port 1 10 ... 11 10 ... 13 10 ... 17 10 ... 25 10 ... 41 ...
IO-Link port 1 12 ...17 14 ... 19 18 ... 23 26 ... 41 42 ... 47 W ... W+5
status (6 bytes)
IO-Link port 2 18 ... 19 19 ... 23 24 ... 31 32 ... 47 48 ... 79 ...
IO-Link port 2 20 ... 25 24 ... 29 32 ... 37 48 ... 53 80 ... 85 X ... X+5
status (6 bytes)
IO-Link port 3 26 ... 27 30 ... 33 38 ... 45 54 ... 69 86 ... 117 ...
IO-Link port 3 28 ... 33 34 ... 39 46 ... 51 70 ... 75 118 ... 123 Y ... Y+5
status (6 bytes)
IO-Link port 4 34 ... 35 40 ... 43 52 ... 59 76 ... 91 124 ... 155 ...
IO-Link port 4 36 ... 41 44 ... 49 60 ... 65 92 ... 97 156 ... 161 Z ... Z+5
status (6 bytes)
Tab. 7-20: Instance 120/123/126/129/132/135
Instance 121/124/127/1230133/136
121 124 127 130 133 136
Total size in bytes 106 114 130 162 226 98 + ∑
IO-Link input data
Digital Input 0 ... 1 0 ... 1 0 ... 1 0 ... 1 0 ... 1 0 ... 1
DI Qualifier 2 ... 3 2 ... 3 2 ... 3 2 ... 3 2 ... 3 2 ... 3
DO Qualifier 4 ... 5 4 ... 5 4 ... 5 4 ... 5 4 ... 5 4 ... 5
System status 6 ... 9 6 ... 9 6 ... 9 6 ... 9 6 ... 9 6 ... 9
IO-Link port 1 in- 10 ... 11 10 ... 13 10 ... 17 10 ... 25 10 ... 41 (0 ... 32 bytes)
put data
IO-Link port 1 12 ...17 14 .. 19. 18 ... 23 26 ... 41 42 ... 47 W ... W+5 (6 bytes)
status
IO-Link port 2 in- 18 ... 19 19 ... 23 24 ... 31 42 ... 47 48 ... 79 (0 .. 32 bytes)
put data
IO-Link port 2 20 ... 25 24 ... 29 32 ... 37 48 ... 53 80 ... 85 X ... X+5 (6 bytes)
status
put data
IO-Link port 3 28 ... 33 34 ... 39 46 ... 51 70 ... 75 118 ... 123 Y ... Y+5 (6 bytes)
status
put data
IO-Link port 4 36 ... 41 44 ... 49 60 ... 65 92 ... 97 156 ... 161 Z ... Z+5 (6 bytes)
status
Diagnostic buffer 42 .. 105 50 ... 113 66 ... 129 98 ... 161 162 ... 225 (64 bytes)
Tab. 7-21: Instance 121/124/127/1230133/136

Start-up
Sequence of output output 140

bytes
Instance
140
Total size in bytes 2
Digital output 0 ... 1
Tab. 7-22: Instance 140
Instance 141/142/143/144/145/151
141 142 143 144 145 151
Total length in 6 10 18 34 66 2+∑
bytes IO-Link output data
Digital output 0 ... 1 0 ... 1 0 ... 1 0 ... 1 0 ... 1 0 ... 1
IO-Link port 1 2 ... 3 2 ... 5 2 ... 9 2 ... 17 2 ... 33 ...
output data (0 ... 32 bytes)
IO-Link port 2 4 ... 5 6 ... 9 10 ... 17 18 ... 33 34 ... 65 ...
Tab. 7-23: Instance 141/142/143/144/145/151
Instance 146/147/148/149/150/152
146 147 148 149 150 152
Total length in 8 12 20 36 68 4+∑
Digital output 0 ... 1 0 ... 1 0 ... 1 0 ... 1 0 ... 1 0 ... 1
IO-Link port 2 ... 3 2 ... 5 2 ... 9 2 ... 17 2 ... 33 ...
IO-Link port 2 4 ... 5 6 ... 9 10 ... 17 18 ... 33 34 ... 65 ...
Diagnostic 6 ... 7 10 ... 11 18 ... 19 34 ... 35 66 ... 67 ...
confirmation (2 bytes)
Tab. 7-24: Instance 146/147/148/149/150/152
Instance 153/154/155/156/157/163
153 154 155 156 157 163
Total length in 10 18 34 66 130 2+∑
Digital output 0 ... 1 0 ... 1 0 ... 1 0 ... 1 0 ... 1 0 ... 1
IO-Link port 1 out- 2 ... 3 2 ... 5 2 ... 9 2 ... 17 2 ... 33 ...
put data (0 ... 32 bytes)
IO-Link port 2 out- 4 ... 5 6 ... 9 10 ... 17 18 ... 33 34 ... 65 ...
IO-Link port 3 out- 6 ... 7 10 ... 13 18 ... 25 34 ... 49 66 ... 97 ...
IO-Link port 4 8 ... 9 14 ... 17 26 ... 33 50 ... 65 98 ... 129 ...
Tab. 7-25: Instance 153/154/155/156/157/163

Start-up
Instance 158/159/160/161/162/164
158 159 160 161 162 164
Total length in 12 20 36 68 132 4+∑
Digital output 0 ... 1 0 ... 1 0 ... 1 0 ... 1 0 ... 1 0 ... 1
IO-Link port 1 out- 2 ... 3 2 ... 5 2 ... 9 2 ... 17 2 ... 33 ...
IO-Link port 2 out- 4 ... 5 6 ... 9 10 ... 17 18 ... 33 34 ... 65 ...
IO-Link port 3 out- 6 ... 7 10 ... 13 18 ... 25 34 ... 49 66 ... 97 ...
IO-Link port 4 out- 8 ... 9 14 .. 17 26 ... 33 50 ... 65 98 ... 129 ...
Diagnostic 10 ... 11 18 ... 19 34 ... 35 66 ... 67 130 ... 131 ...
confirmation (2 bytes)
Tab. 7-26: Instance 158/159/160/161/162/164
7.4 Configuration/settings
WARNING!
Protection function may be impaired if the module configuration is
changed.
The person who makes the changes is responsible for maintaining the
protective function of the device.
 Make sure that only authorized persons change the configuration.
 If you change the configuration, use the password hierarchy provided by
your engineering software.
 After every change to the configuration, test the protection equipment for
efficiency.
7.4.1 Module configuration
Overview There are two options for configuring the devices.

On one hand, an EDS file can be downloaded from the online shop of Mur-
relektronik.
These files can be imported into your programming software as described in
chapter 7.1 "Loading the EDS files"
which allows you to benefit from the advantages of a preconfigured connection
at a later stage.
On the other hand, there is the possibility to configure the devices via an inte-
grated web server.

Start-up
Configuration via EDS After the import of the EDS in the programming software and the selection of
a connection suitable for the application, the configuration files can be found
in the controller tags.
The input and output tags associated with the device can be found next to it.
Fig. 7-8: Configuration via EDS
All configuration tags have a specific name that describes the function of the
areas.
 Enter the appropriate values for your application.
Each time when a connection with the control system is established, the
device is correctly configured
For more information on the adjustable values, please refer to chapter7.4.7

"Configuration values"

Start-up
Configuration via web The device can also be configured via web server if this is necessary. Howev-
server er, this requires some settings beforehand.
 Call up the web server of the device in your browser by entering the IP ad-
dress of the device in the address line.
 Navigate to the device parameters and change the
Configuration parameter to Over Web Server.
Fig. 7-9: Configuration via web server
 Restart the device to enable the modification of the parameters.

 After restart, select the device as described above and adjust the desired
parameters.
Chapter 7.5 "Web server" parameters.

Start-up
7.4.2 Setting parameters
Setting parameters  Navigate to the controller tags in the Controller Organizer program win-
dow, as shown in the figure.
Fig. 7-10: Controller Organizer window
 Double-click the Controller Tags entry.

The overview of the process and configuration data opens.
Fig. 7-11: Process and configuration data
 Click the plus symbol in the configuration data line

Name_Of_Module:C.
All parameters of the device are visible.
 Enter the values for the application.
NOTICE
Parameter are transmitted in Forward Open Telegram (power reset or separa-
tion of the connection is required).
For adjustable parameter values, refer to chapter 7.4.7 "Configuration values"

Start-up
7.4.3 RPI configuration
Setting the RPI values Searching the module

When setting up an EtherNet/IP system, the RPI value must be carefully set
in the controller.
To set the RPI values, the module properties must be selected.
In Controller Organizer:
1 | Double-click the module or
2 | Right-click the module and select Properties from the context menu.
Fig. 7-12: Searching a module

Start-up
Setting the RPI values
 Click the Connection tab.

 Set the desired RPI values in the column Requested Packet Interval
(RPI) (ms).
NOTICE
The minimum RPI is 1 ms.

Start-up
7.4.4 QuickConnect™-configuration
Use of Quickconnect™ QuickConnect™ is usually used on applications which require a fast integra-
tion of users, e.g. of an IO module, in an EtherNet/IP network in order to guar-
antee a correct functioning.
A typical application is, for example, a robot application during which the tool
to be used is often changed.
Prerequisites for Quick- To use QuickConnect™ the control system requires an electrical lock signal
Connect™ that signals the startup and the correct power supply to the device.
This signal is the trigger to start the QuickConnect™ sequence of the control
system.
This sequence and the directly wired signal to a digital input of the control sys-
tem must be implemented by the system builder.
NOTICE
Further information regarding the integration of QuickConnect can be found in
the manual of the control manufacturer.

Start-up
Activation To activate QuickConnect™ on the desired device, proceed as follows:

of QuickConnect™  Set the parameter correctly in the configuration data and connect the de-
vice to the control system in order to transmit the configuration to the mod-
ule.
 Restart the device so that QuickConnect™ can be used.
The QuickConnect™ setting is remanently saved but is only active after a
restart or a reset.
7.4.5 DLR configuration
Device Level Ring (DLR) is a protocol which allows a ring topology with Eth-
erNet/IP devices. The ring network consists of at least one ring supervisor and
any desired number of users. To build up the topology and to detect cable
breaks inside the ring, there are two different methods:
To build up the topology and to detect cable breaks inside the ring, there are
two different methods:
1 | Beacon-based
2 | Announce-based
Prerequisites for configuration and diagnostic:

 Users support the DLR
 The DLR object (0x47) is implemented by the user.
The use of modules which are not DLR-compliant in an EtherNet/IP ring net-
work is not excluded but results in a higher ring recovery time when the ring
topology is interrupted.
NOTICE
The modules described in this manual support the beacon-based DLR tech-
nology.

Start-up
7.4.6 IO-Link configuration
IO-Link configuration With the IMPACT67 module, the IO-Link devices can be configured and pa-
rameterized in two different ways:
1 | IO-Link device configuration Explicit Messages in EtherNet/IP
2 | Murrelektronik IO-Link Device Tool
IO-Link device configu- It is possible to parameterize the connected IO-Link devices through EtherNet/
ration through IP Explicit Messages.
EtherNet/IP Explicit
Messages
For further information, please refer to chapter 8.2 "Acyclic IO-Link device ac-
cess"
Murrelektronik The Murrelektronik IO-Link Device Tool enables parameterization of IO-

IO-Link Device Tool Link devices.
A hardware catalog is displayed via a graphical interface.
This is where you can assign and set an IO-Link device for the IMPACT67 IO-
Link port.
The parameterization can then be sent to the IO link device.

Start-up
7.4.7 Configuration values
NOTICE
Unexpected behavior of the device.
 Use only the values listed here.
Diagnostic parameters
Byte Parameters Value Default Description

value
0 Diag_Para_Disagnostic_Report Global diagnostics report: 0 Parameterizes the display
 0 = enabled of all diagnostics.
 1 = disabled
1 Diag_Para_Under_ US undervoltage report: 0 Parameterizes the US
Voltage_Sensor_Supply  0 = enabled undervoltage diagnostics.
 1 = disabled
2 Diag_Para_Under_ UA undervoltage report: 0 Parameterizes the UA
Voltage_Actuator_Supply  0 = enabled undervoltage diagnostics.
 1 = disabled
3 Diag_Para_No_ No actuator voltage report: 0 Parameterizes the display of UA
Actuator_Supply  0 = enabled no voltage diagnostics.
 1 = disabled
4 Diag_Para_LED_Indication_ LED indication for suppressed 0 Parameterizes the behavior of the
for_Suppressed diagnostics: status LEDs for voltage-
 0 = enabled relevant diagnostics.
 1 = disabled
5 Diag_Para_Diagnostic_Mes- Diagnose Acknowledgment: 0 Parameterizes the behavior of the
sage_Acknowledgment  0 = disabled shown diagnostics.
 1 = enabled Confirm activated diagnostics be-
fore they are deleted from the buf-
fer.
6 IO-Link_Event_Integration IO-Link event integration: 0 Parameterizes the way in which
 0 = IO-Link standard event IO-Link-Events are reported.
integration If IO-Link devices from Murrelek-
 1 = Murrelektronik event in- tronik are used, other events in ad-
tegration dition to the standard events can be
 2 = Murrelektronik extended reported.
event integration
7 Reserved 0 0 This parameter is hidden in the
EDS and is not displayed in the
scanner software
Tab. 7-27: Diagnostic parameters
General parameters

value
0 Pin_Port_based_IO_Layout IO layout 0 Parameterizes the layout of the
 0 = Port based I/O data.
 1 = Pin based
1 Quick_Connect QuickConnect: 0 Parameterizes QuickConnect.
 0 = disabled
 1 = enabled

Start-up

value
2 Function_port_0_pin_4_Ch00 Channel function: 0 Parameterizes the channel func-
 0 = Automatic tion.
 1 = NO input
 2 = NC input
 3 = Output
 1 = NO input
 2 = NC input
 3 = Output
 1 = NO input
 2 = NC input
 3 = Output
 1 = NO input
 2 = NC input
 3 = Output
 1 = NO input
 2 = NC input
 3 = Output
 1 = NO input
 2 = NC input
 3 = Output
 1 = NO input
 2 = NC input
 3 = Output
 1 = NO input
 2 = NC input
 3 = Output
 1 = NO input In 55144, this parameter has no
 2 = NC input function.
 3 = Output
 1 = NO input
 2 = NC input
 3 = Output
 1 = NO input In 55144, this parameter has no
 2 = NC input function.
 3 = Output

Start-up

value
 1 = NO input
 2 = NC input
 3 = Output
 1 = NO input In 55143 and 55144, this parameter
 2 = NC input has no function.
 3 = Output
 1 = NO input
 2 = NC input
 3 = Output
 1 = NO input In 55143 and 55144, this parameter
 2 = NC input has no function.
 3 = Output
 1 = NO input
 2 = NC input
 3 = Output
Tab. 7-28: General parameters
IO-Link port X parameters

value
0 IO_Link_Port_X_Function Function of the IO-Link master: 0 Parameterizes the function of the
 0 = IO-Link IO-Link master.
 7 = SIO, automatic
 8 = Deactivated
 9 = IO-Link Swap
 10 = IO-Link 16 bit swap
 11 = IO-Link 32 bit swap
1 IO_Link_Port_X_ IO-Link diagnostics report: 0 Parameterizes the display of
Diagnosen_Parameter  0 = All diagnostic messages IO-Link-Events
 1 = Only wire break
 2 = Reserved
 3 = No diagnostic messag-
es
2 IO_Link_Port_X_Cycle_Time_ Cycle Time Multiplier: 0 Value of the IO-Link Cycle Time
Multiplicator  0 = Automatic Multiplier
 1 .. 63 = factor 1 .. 63
3 IO_Link_Port_X_Cycle_Time_ IO-Link Cycle Time Base: 0 Value of the IO-Link Cycle Time
Value  0 = 0.1 ms Base
 1 = 0.4 ms
 2 = 1.6 ms
 3 = 6.4 ms
4 IO_Link_Port_X_Data_Storage Data Storage: 0 Parameterizes the IO-Link Data
 0 = Disabled Storage
 1 = Erase
 2 = Enabled

Start-up

value
5 IO_Link_Port_X_Data_ Data Storage Upload: 0 Parameterizes the data storage up-
Storage_Upload  0 = Disabled load from the IO-Link device to the
 1 = Enabled IO-Link master
6 IO_Link_Port_X_Data_ Data Storage Download: 0 Parameterizes the data storage
Storage_Download  0 = Enabled download from the IO-Link master
 1 = Disabled to the IO-Link device
7 IO_Link_Port_X_ Validation of the IO-Link device: 0 Parameterizes the validation of the
Validation  0 = No validation connected IO-Link device
 1 = Compatibility
 2 = Identical
8..9 IO_Link_Port_X_ IO-Link VendorID of the IO-Link 0 Value of the IO-Link device Vendor-
Validation_VendorID device ID.
10 IO_Link_Port_X_ First (LSB) octet of the IO-Link 0 Value of the first octet of the IO-Link
Validation_Device_ID_0 DeviceID of the IO-Link device device DeviceID
11 IO_Link_Port_X_ Second (LSB) octet of the IO- 0 Value of the second octet of the IO-
Validation_Device_ID_1 Link DeviceID of the IO-Link de- Link device DeviceID
vice
12 IO_Link_Port_X_ Third (LSB) octet of the IO-Link 0 Value of the third octet of the IO-
Validation_Device_ID_2 DeviceID of the IO-Link device Link device DeviceID
13 ... IO_Link_Port_X_ IO-Link SerialID of the 0 Value of the IO-Link device SerialID
28 Validation_Serial_ID IO-Link device
StringT[16]
Tab. 7-29: IO-Link port X parameters
IO-Link port X length parameters

value
0 IO_Link_Port_X_Input_Length IO-Link device 0 Value of IO-Link device
input length 0 ... 32 input length
1 IO_Link_Port_X_ IO-Link device 0 Value of the IO-Link device
Output_Length output length 0 ... 32 output length
Tab. 7-30: IO-Link port X length parameters

Start-up
7.5 Web server
7.5.1 The Murrelektronik web server
Fig. 7-13: The Murrelektronik web server
The Murrelektronik web server is a graphic tool that can be used to obtain in-
formation on the device quickly and intuitively and to configure or parameter-
ize it according to your needs.
Prerequisites Prerequisite for a correct graphic display of the web server:
 Install a current web browser on your PC.
 Mozilla Firefox from version 57 or
 Internet Explorer from version 11
 Google Chrome from version 64
To start the web server, proceed as follows:

 Start the web browser.
 Enter the IP address of the MVK module in the web browser.
The web server of the MVK module starts with the Status page.
General operation After calling up the web server, the status page of the bus node is displayed.
Operating areas
The web server is divided into 3 operating areas:
1 | System tree
• Shows the device and the available sub-functions.
2 | Navigation bar
• The navigation bar enables you to switch between the different pages
of the device or the sub-function. In addition, the white highlighting
shows which page is currently displayed.
3 | Page contents
• This area shows the contents of the page (selected in the navigation
bar).

Start-up
7.5.2 Device menu
Menu bar The menu bar comprises the following clickable menu items:
a | STATUS
b | IO-OVERVIEW
c | PARAMETERS
d | DIAGNOSTICS
e | MAINTENANCE
7.5.2.1 STATUS menu

The status page of the device is divided into 3 different areas:
 Identification
 Communication
 Status
Fig. 7-14: STATUS menu

Start-up
Identification This area contains the following information:

 Firmware Version:
 The current version of the firmware.
 Firmware Build Date:
 The firmware creation date.
 Firmware Build Time:
 The firmware creation time.
 WebUI Description Version (LIC):
 The version of the currently used description file.
The latest description file can be downloaded from the online shop to-
gether with the EDS file and the language files.
 Hardware version:
 The current hardware version of the bus node.
 Serial Number:
 The serial number of the device.
Communication This area contains the following information:

 MAC address:
 MAC address of the device.
 DIP-Switch Value At Startup:
 The value generated by the DIP switches when the device is booted.
This area contains the following information:

 System Uptime:
 Time elapsed since the device has been switched on.
 System Diagnostics:
 Displays whether the device has stored diagnostic information.
 "DLR: Topology-Status":
 Displays the topology detected by the device and the status of this to-
pology.
 Sensor Voltage (US):
 Displays the sensor voltage in V.
 Actuator Voltage (UA):
 Displays the actuator voltage in V.

Start-up
7.5.2.2 PARAMETERS menu

In this menu, the device parameters are displayed.
An overview of the parameters and their description can be found in chapter
7.3.1 "Connections, parameters and properties"
Prior to performing any settings, the following prerequisites must be fulfilled.
Prerequisite Parameters concerned Consequence

"Stored values" set via DIP IP address, subnet mask This parameters can only be
switch. and gateway address set if the "Stored values" are
set.
Parameter "Configuration" All parameters except IP ad- Parameters can now be set.
is set to "Over Webserver". dress, subnet mask and
gateway address
NOTICE
The settings are only applied after the device is restarted.

Start-up
7.5.2.3 DIAGNOSTICS menu
Fig. 7-15: DIAGNOSTICS menu
In the menu, there is an overview of the diagnostic messages in the diagnostic

buffer.
Depending on the setting selected for the
Diagnostic Message Acknowledgement parameter, the diagnostic messag-
es which are currently active or have ever occurred in the past are displayed.
Up to 8 diagnostics messages can be shown in the list at a time.
If the option "Diagnostic Message Acknowledgement" is selected, the page is
adapted accordingly.
Diagnostic messages can only be acknowledged by the web site when there
is no connection to a control system.
NOTICE
If there are more than 8 diagnostics, a diagnostic overflow is displayed.
Restarting the device will reset the diagnostics.
7.5.2.4 MAINTENANCE menu
Fig. 7-16: MAINTENANCE menu
The menu contains information on how to select the different functions of the
device (e.g. restart).

Start-up
Download System File  Load the configuration file from the online shop to the device.
To Device (.ZIP archive) The ZIP archive contains the latest description file (Lic file).
Language files for the web server and possibly required pictures.
 Enter the article number of the device in the Murrelektronik online shop.
 Download the configuration file with the extension ".zip".
 Save the file without unpacking it.
 In the web server, navigate to the Maintenance menu item.
 In the web server of the bus node, click the menu item
Download System File To Device.
 Click the "..." button. button.
 Select the .ZIP archive downloaded from the online shop in the file dialog.
 Click Download System File To Device.
Uploading the configuration data may take a few minutes.

The new configuration data are only applied after the bus node is restarted.
Export System Configu- Save a configuration file of the device.

ration (.CFG file)  Open the Export System Configuration menu item.
 Click the Export System Configuration button.
The currently set configuration and parameterization is saved to your default
download folder.
Import System Configu- Loading a saved configuration file to the current device.
ration (.CFG file)  Open the Import System Configuration menu item.
 To open, click the button "..." .
 Select the saved system configuration in the file dialog.
 Click Import System Configuration.
The configuration file is loaded to the current device.
NOTICE
The loaded configuration (all parameters) is only applied after the device is re-
started.
Malfunctions
Murrelektronik assumes no liability for malfunctions resulting from a manually
edited file.
 The configuration file must not be edited!
Device restart 1 | Open the Restart Device menu item.

2 | Click the Deactivated button.
3 | Click Restart Device.

Operation
8 Operation
8.1 Diagnostics
All IMPACT67 have separate and clearly arranged indicators:
 LED indication for inputs and outputs
 LED indication for bus
 LED indication POWER
 Extended LED indications
To identify the displayed information clearly, the LEDs on the front panel of the
module are labeled. The indication is performed by means of a continuous
light or flashing of the LEDs. The following figure shows the arrangement of
the LEDs and the table shows the functions.
8.1.1 LED indication for inputs and outputs
A separate status display is assigned to each in-

put and output.
LED indication Indica- State Voltage at input Logical

Digital inputs tion value
Continuously lit 24 V 1
Yellow
Continuously lit - 0
Red
0V 0
Off
Tab. 8-1: LED indication digital input
LED indication indica- state Voltage at Logical

Digital outputs tion output value
Yellow 24 V 1
continuously lit
Off 0V 0
Red 0V 1
continuously lit
Tab. 8-2: LED indication Digital output indication

Operation
Error at input or output In the event of an error (short circuit, overload or feedback) at the digital output
or the sensor power supply, the relevant LEDs light up in red at the M12 port.
LED display display state Description

IO-Link
Green IO-Link in status Operate
continuously lit
Green No IO-Link connection

flashing (2 Hz)
Green rapidly IO-Link in the Pre-Operate state during

flashing data storage
Off IO-Link connection deactivated
Red rapidly Validation failed.

flashing Incompatible module connected for
data storage.
Data storage failed
Tab. 8-3: LED display IO-Link indication
8.1.2 LED indication for state
LED indication Indica- State Description

ST tion
Continuously lit Error-free operation
Green
Continuously lit An error is active on the module
Red
Tab. 8-4: LED indication ST

Operation
8.1.3 LED display MS and NS
LED-Indication
Overview
 NS - indicates the state of the bus system.

 MS - indicates the state of the PLC configuration.

NS
Off Device is switched off.
Device does not have a configured IP
address. Device has no link.
Green IP address is available, however, no
flashing connection to master
Green Connection to master available

continuously lit
Red At least one connection timed out

flashing
Red The module has detected that anoth-

continuously lit er device is using its IP address.
Green/red Self-test
flashing
Tab. 8-5: LED display NS indication
LED display, red This is what you can do:

 Check for IP address conflict:

Operation

MS
Off Device is off
Green Operational, device in operation

continuously lit
Green/red Self-test
flashing
Red The module has detected that anoth-

flashing er device is already using its IP ad-
dress.
Tab. 8-6: LED display MS indication
LED display flashing This is what you can do:

red  Check for IP address conflict.
8.1.4 LED indication for LNK/ACT
LED-Indication
Overview
 The LNK/ACT LEDs indicate the state of the Ethernet communication at

each port.

LNK / ACT tion
Lit continuously Module has detected a link at the as-
sociated port
Green
Green: Link available
lit continuously
Green
Yellow: flash- Link and activity available
ing
yellow
Corresponding port is closed, no cable
connection available
Off
Tab. 8-7: LED indication LNK/ACT
LED display Off This is what to do:

 Check the line connections.

Operation
8.1.5 LED indicator power US and UA
LED-Indication
Overview

POWER US tion
Lit continuously 17.5 V ≤ US ≤30 V
Error-free operation
Green
Lit continuously 12.5 V ≤ US ≤17 V
Undervoltage
Red
Flashing 1 Hz 7.5 V ≤ US ≤12 V
No voltage
Red
Flashing 5 Hz US ≥30.5
Overvoltage
Red
US ≤7.5 V
No voltage
Off
Tab. 8-8: LED Indication POWER US
NOTE
At US <18 V, an error-free operation is no longer guaranteed.

POWER UA tion
Continuously lit 17.5 V ≤ UA ≤30 V
Error-free operation
Green
Continuously lit 12.5 V ≤ UA ≤17 V
Undervoltage
Red
Flashing 1 Hz UA ≤12 V
No voltage
Red
Flashing 5 Hz UA ≥30.5 V
Overvoltage
Red
UA ≤7.5 V
No LED indication
Off
Tab. 8-9: LED indication POWER UA

Operation
8.1.6 Extended LED indications
LED-Indication
Overview
Extended LED display, LED Indica- State Description

identification of the tion
module BUS RUN Flashing
ST 1 Hz
POWER UA Green
POWER US Identification of the module
Tab. 8-10: Extended LED display, identification of the module.
Extended LED Indica- LED Indica- State Description

tion tion
Update Update is being transmitted
MS
NS Yellow
ST Cascading se-
POWER UA quential light Update flashes
POWER US
Red
Tab. 8-11: Extended LED Indication, update
Extended LED display, LED Indica- State Description

update tion
ST Off
Off
MS Flashing alter- Update check in progress
POWER UA nately 1 Hz
POWER US Yellow
Rapid Update flashing interrupted

flashing
Red
Flashing alter- Update failed
nately 1 Hz
Red
Tab. 8-12: Extended LED display, update

Operation

tion tion
factory reset ST Off
Off
Left and right Factory reset in progress

sides are flash-
MS Yellow ing alternately
POWER UA at 1 Hz
POWER US Left and right Factory reset has been completed with
sides are flash- failure
Red ing alternately
at 1 Hz
Left and right Factory reset has been completed
sides are flash- successfully
Green ing alternately
at 1 Hz
Tab. 8-13: Extended LLED Indication, factory reset

tion tion
recovery firmware: ST Flash, flash,
system startup pause
Yellow (double flash)
Recovery firmware: system startup
BUS_NS Off
POWER UA Off
POWER US
Tab. 8-14: Extended LED Indication, recovery firmware: system startup

tion tion
recovery firmware: ST Flash, flash,
system initialization pause
NS Lights continu-
ously
Green Recovery firmware: system initializa-
tion
MS Flashing 1 Hz
Yellow
POWER UA Off
POWER US
Off
Tab. 8-15: Extended LED states, recovery firmware: system initialization

Operation
Extended LED Indica-

tion LED Indica- State Description
recovery firmware: sys- tion
tem run ST Flash, flash,
pause
MS Lights continu-
ously
Green Recovery firmware: system run
Flashing 1 Hz
POWER UA
Yellow
Off
POWER US
Off
Tab. 8-16: Extended LED Indication, recovery firmware: system run

tion tion
Firmware update: ST Flash, flash,
initialization of trans- pause
mission Yellow (double flash)
MS Lights continu-
ously
POWER UA Green Firmware update: initialization of trans-
mission
Flashing 1 Hz
POWER US
Yellow
Tab. 8-17: Extended LED Indication, firmware update: initialization of transmission

tion tion
Firmware update ST Flash, flash,
pause
Cascading se- The new firmware is being transmitted
quential light
Yellow
MS Flashing alter- The new firmware is being checked

nately 1 Hz
POWER UA Yellow
POWER US
Cascading se- The new firmware is being updated
quential light
Red
Short flash, Writing has been aborted
long pause
Red (single flash)
Flashing alter- Updating the firmware failed
nately 1 Hz
Red
Tab. 8-18: Extended LED Indication, firmware update

Operation
8.1.7 Diagnostics structure in the control system
Byte Description Value

0 Last octet of the IP address of the device Last octet of the IP address of the device
1 Reserved 0 = Default Code
0x40 = IO-Link Master Event Code
0x41 = IO-Link Device Event Code
0x42 = Murrelektronik IO-Link Device Event Code
2 IO-Link identification
3 Channel number where the error occurred
4 ErrorCode Byte1 In case of IO-Link, this is the LSB of the IO-Link ErrorCode,
otherwise it is the Global Error Code,
See Tab. 8-19: "Short-circuit diagnostics (Global Error Code 0x01)"
5 ErrorCode Byte2 In case of IO-Link, this is the MSB of the IO-Link ErrorCode,
otherwise it is the Specific Error Code,
See Tab. 8-19: "Short-circuit diagnostics (Global Error Code 0x01)"
6 Severity and active/inactive display Bit 0:
 0 = Inactive diagnostic
 1 = Active diagnostic
Bit 6 and 7:
 1 = Minor fault
 2 = Major fault
 3 = Information
7 Reserved 0
8.1.8 Diagnostics in the web server
Diagnostic monitoring Another possibility to monitor the diagnostics of the module is the diagnostic
page of the integrated web server.
Representation The diagnostics are shown in plain text as far as it is known:

1| Key: indicates the type of diagnostic
2| Description: shows a more detailed description of the error
3| Severity: distinguishes 3 error categories
a) Information
b) Warning
c) Defect
4| Type: this shows whether the diagnostic has just occurred or the fault has
already been eliminated.
There are two types of diagnostics.
Active
Inactive

Operation
8.1.9 Diagnostic values
8.1.9.1 Short-circuit diagnostics (Global Error Code 0x01)

Description Value
Sensor Short Circuit 0x01
Actuator Warning 0x17
Actuator Short Circuit 0x18
Tab. 8-19: Short-circuit diagnostics (Global Error Code 0x01)
8.1.9.2 Undervoltage diagnostics (Global Error Code 0x02)

Description Value
Undervoltage Actuator Power Supply 0x28
No Voltage Actuator Power Supply 0x29
Undervoltage External Actuator Power Supply 0x2A
No Voltage External Actuator Power Supply 0x2B
Undervoltage Sensor Power Supply 0x32
No Voltage Sensor Power Supply 0x33
Undervoltage U1 0xD0
Undervoltage U2 0xD1
Tab. 8-20: Undervoltage diagnostics (Global Error Code 0x02)
8.1.9.3 Overvoltage diagnostics (Global Error Code 0x03)

Description Value
Overvoltage Actuator Power Supply 0x2C
Overvoltage External Actuator Power Supply 0x2D
Overvoltage Sensor Power Supply 0x34
Overvoltage U1 0xD4
Overvoltage U2 0xD5
Tab. 8-21: Overvoltage diagnostics (Global Error Code 0x03)
8.1.9.4 General diagnostics (Global Error Code 0x09)

Description Value
Error 0x00
PLC Connection Of Exclusive Owner Timed Out 0x59
Tab. 8-22: General diagnostics (Global Error Code 0x09)
8.1.9.5 Buffer Overflow Diagnostics (Global Error Code 0xFF)

Description Value
Overflow 0xFF
Tab. 8-23: Buffer Overflow Diagnostics (Global Error Code 0xFF)

Operation
8.1.9.6 IO-Link master diagnostics (IO-Link identification 0x40)

Description Value
Error 0x0000
Error Fetching Extended Events 0x97FF
Startup Parameterization Error 0x9801
Wrong Device. Inspection Level Mismatch 0x9802
Process Data Mismatch 0x9803
Short Circuit At C/Q - Pin 4 0x9804
IO-Link PHY Overtemperature 0x9805
Short Circuit L+ - Pin1 0x9806
Undervoltage L+ - Pin1 0x9807
Device Event Overflow 0x9808
Backup Failed - Memory Out Of Range 2k 0x9809
Backup Inconsistency - Data Storage Index Not Available 0x980A
Backup Inconsistency - Data Storage Unspecific Error 0x980B
Backup Inconsistency - Upload Fault 0x980C
Parameter Inconsistency - Download Fault 0x980D
Port Class B Failure - Power Missing 0x980E
Short Circuit At Pin 2 0x980F
Revision Fault 0x9811
Compatibility Fault Vendor ID (IO-Link 1.0) 0x9812
Compatibility Fault Device ID (IO-Link 1.0) 0x9813
Compatibility Fault Vendor ID (IO-Link 1.1) 0x9814
Compatibility Fault Device ID (IO-Link 1.1) 0x9815
Serial Number Fault 0x9816
Generic Data Storage Fault 0x9817
Invalid Cycle Time 0xE000
Revision Fault- Incompatible Protocol Version 0xE001
Parameter Inconsistency - ISDU Batch Failed 0xE002
Device Not Available - Communication Lost 0xFF22
Invalid Backup - Data Storage Identification Mismatch 0xFF23
Invalid Backup - Data Storage Buffer Overflow 0xFF24
Invalid Backup - Data Storage Parameter Access Denied 0xFF25
Event Lost - Incorrect Event Signaling 0xFF31
Tab. 8-24: IO-Link master diagnostics (IO-Link identification 0x80)
8.1.9.7 IO-Link device diagnostics (IO-Link identification 0x41)

Description Value
Error 0x0000
General Malfunction 0x1000
Temperature Fault 0x4000
Ambient Temperature: General Error 0x4100
Ambient Temperature: Over-Run 0x4110
Ambient Temperature: Under-Run 0x4120
Device Temperature: General Error 0x4200
Device Temperature: Over-Run 0x4210
Device Temperature: Under-Run 0x4220
Outside Temperature: General Error 0x4300
Outside Temperature: Over-Run 0x4310
Outside Temperature: Under-Run 0x4320
Device Hardware Fault 0x5000
Component Malfunction 0x5010

Operation
Description Value
Non Volatile Memory Loss 0x5011
Batteries Low 0x5012
General Power Supply Fault 0x5100
Fuse Blown/Open 0x5101
Primary Supply Voltage Over-Run 0x5110
Primary Supply Voltage Under-Run 0x5111
Secondary Supply Voltage Fault 0x5112
Device Supply: Voltage Under-Run U3 0x5113
Device Supply: Short Circuit 0x5151
Device Supply: Error In Periphery 0x5160
Device Controller: General Error 0x5200
Device Control Section: General Error 0x5300
Device Power Section: General Error 0x5400
Device Power Section: Error In Output Driver 0x5410
Device Power Section: Fuse Blown/Open 0x5450
Device Power Section: Fuse Blown/Open S1 0x5451
Error In Additional Device Communication 0x5500
Error In Device Communication Interface 2 0x5510
Device Software Fault 0x6000
Device Software: Reset (Watchdog) 0x6010
Device Software: Internal Fault 0x6100
"Device Software: Dataset Error 0x6300
Loss Of Parameter 0x6310
Parameter Error 0x6320
Parameter Missing 0x6321
Parameter Not Initialized 0x6330
Parameter Not Specific 0x6340
Parameter Changed 0x6350
Wire Break Of A Subordinate Device 0x7700
Wire Break Of Subordinate Device 1 0x7701
Wire Break Of Subordinate Device 10 0x770A
Wire Break Of Subordinate Device 11 0x770B
Wire Break Of Subordinate Device 12 0x770C

Operation
Description Value
Wire Break Of Subordinate Device 13 0x770D
Wire Break Of Subordinate Device 14 0x770E
Wire Break Of Subordinate Device 15 0x770F
Short Circuit 0x7710
Ground Fault 0x7711
Communication Monitoring: General Error 0x8100
Process Data Monitoring: General Error 0x8110
Technology Specific Application Fault 0x8C00
Simulation Active 0x8C01
Process Variable Range Over-Run 0x8C10
Measurement Range Over-Run 0x8C20
Process Variable Range Under-Run 0x8C30
Maintenance Required - Cleaning 0x8C40
Maintenance Required - Refill 0x8C41
Maintenance Required - Wear And Tear 0x8C42
Tab. 8-25: IO-Link device diagnostics (IO-Link identification 0x41)

Operation
8.2 Acyclic IO-Link device access

The device offers the possibility to parameterize the connected IO-Link devic-
es through acyclic write and read access. For this, the object IO-Link param-
eter object (0x80) is used.
8.2.1 Reading an IO-Link device index
Read index of IO-Link device

1 | To read the index of a connected IO-Link device, use the EtherNet/IP ser-
vice Read_ISDU (0x4B).
2 | To do so, send the service to the correct attribute of the IO-Link parameter
object (0x80).
3 | An attribute represents the IO-Link port to which the IO-Link device is con-
nected.
Structure of a Read_ISDU Service
Name Value Type Description

Service 0x4B USINT Read_ISDU service
Class 0x80 USINT IO-Link Parameter Object
Instance 0x01 USINT IO-Link master
Instance attribute 0x01..0x02 or USINT IO-Link master port
0x01..0x04
Index … UINT IO-Link ISDU Object Index
Sub-index … USINT IO-Link ISDU object sub-in-
dex
Tab. 8-26: Structure of a Read_ISDU Service
Read_ISDU Service – Successful Response

If the service was performed without error (General Status of the CIP Service
Response is 0), the Service Response Payload contains the read data in the
following format:
Name Type Description

ISDU ARRAY of USINT IO-Link ISDU object sub-index
Read_ISDU Service – Unsuccessful Response
If the service was not performed without errors (General Status of the CIP Ser-
vice Response is 0x1E “Embedded service error“), the error codes can be
found in the Service Response Payload.
The structure of the error codes can be found in chapter 8.2.3.

Operation
8.2.2 Writing an IO-Link device index
Writing an IO-Link device index

1 | To read the index of a connected IO-Link device, use the EtherNet/IP ser-
vice Write_ISDU (0x4C).
2 | To do so, send the service to the correct attribute of the IO-Link parameter
object (0x80).
3 | An attribute represents the IO-Link port to which the IO-Link device is con-
nected.
Structure of a Write_ISDU Service
Name Value Type Description

Service 0x4C USINT Write_ISDU Service
Class 0x80 USINT IO-Link Parameter Object
Instance 0x01 USINT IO-Link master
Instance attribute 0x01..0x02 or USINT IO-Link master port
0x01..0x04
Index … UINT IO-Link ISDU Object Index
Sub-index … USINT IO-Link ISDU object sub-in-
dex
Data … ARRAY of IO-Link ISDU data (max.
USINT 232 bytes)
Tab. 8-27: Structure of a Write_ISDU Service
Write_ISDU Service – Successful Response

If the service was performed without error (General Status of the CIP Service
Response is 0), no further data can be found in the Service Response Pay-
load.
Write_ISDU Service – Unsuccessful Response
If the service was not performed without errors (General Status of the CIP Ser-
vice Response is 0x1E “Embedded service error“), the error codes can be
found in the Service Response Payload.
The structure of the error codes can be found in chapter Tab. 8-29: "IO-Link
master error codes"

Operation
8.2.3 Read/Write ISDU Service
Name Type Description Semantics

IO-Link Master Error UINT IO-Link master See table in chapter 8.2.4
error code
IO-Link Device Error USINT IO-Link device See IO-Link specification or IO-
error code Link device manual
IO-Link Device Addi- USINT Additional IO- See IO-Link specification or IO-
tional Error Link device er- Link device manual
ror code
Tab. 8-28: Structure of a Read_ISDU Service
8.2.4 IO-Link master error codes
Name Value
No Master Error 0
Service Not Available 1
Port Blocked 2
Timeout 3
Invalid Index 4
Invalid Sub-Index 5
Wrong Port 6
Wrong Port Function 7
Invalid Length 8
ISDU Not Supported 9
Tab. 8-29: IO-Link master error codes

Maintenance and cleaning
9 Maintenance and cleaning

NOTICE
Damage caused by defective or damaged devices!
The functioning of the modules is not guaranteed.
 Replace defective or damaged devices.
 Clean the soiled contacts with oil-free compressed air or with spirit and a
leather cloth only.
 Do not use contact spray.

Appendix
10 Appendix
10.1 Supported EtherNet / IP objects
This chapter is an enumeration of the CIP objects and services support-

ed by and implemented in this product. For more detailed descriptions
of the individual objects and attributes, please refer to the EtherNet/IP
specification.
10.2 Standards
10.2.1 Identity Object (Class Code: 0x01)
Class Attributes
Attribute Access Name Data Type Description of Attribute Semantics of Values
ID Rule
1 Get Revision UINT Revision of this object The current value assigned to
this attribute is one (01). If up-
dates that require an increase
in this value are made, then
the value of this attribute in-
creases by 1.
2 Get Max UINT Maximum instance number of The largest instance number of
Instance an object currently created in a created object at this class
this class level of the device. hierarchy level. This attribute
will show one (01).
6 Get Max ID UINT The attribute ID number of the The value of this attribute will
Class last class attribute of the class be seven (07).
Attribute definition implemented in the
device.
Instance last instance attribute of the differ by product variant. This
Attributes class definition implemented in attribute will show nine (09).
the device.
Tab. 10-1: Identity Object Class Attributes
Instance Attribute
Attribute Access Name Data Type Description of Attribute Value
ID Rule
1 Get Vendor ID UINT Identification of each vendor 640
by number
2 Get Devise UINT Indication of general type of 7
Type product
3 Get Prodict UINT Identification of a particular Example: 55142
Code product of an individual vendor
4 Get Revision STRUCT Revision of the item the Identi-
of: ty Object represents
Major USINT 1
Revision
Minor USINT 6
Revision
5 Get State WORD Summary status of device
6 Get Serial UDINT Serial number of device
Number
7 Get Prodict SHORT_ Human readable identification Example:
Name STRING IMPACT67 E DIO16 4P
8 Get State USINT Present state of the device as
represented by the state tran-
sition diagram

Appendix
Tab. 10-2: Identity Object Instance Attributes
Common Services
Service Code Implemented for Service Name Description of Service
Class Instance
0x01 No Yes Get_Attribute_All Returns a predefined listing of
this objects attributes.
0x05 No Yes Reset Invokes the Reset service for
the device. Option 0 restarts
the device. Option 1 invokes a
factory reset of the device.
0x0E Yes Yes Get_Attribute_Single Returns the contents of the
specified attribute.
Tab. 10-3: Common services of Identity Object
10.2.2 Message Router Object (Class Code: 0x02)
This Object has no accessible attributes.
10.2.3 Assembly Object (Class Code: 0x04)
Class Attributes
ID Rule
this attribute is two (02). If up-
creases by 1.
Tab. 10-4: Assembly Object Class Attributes
Instance Attribute
Attribute Access Name Data Type Description of Attribute
ID Rule
3 Set,Get Data ARRAY of BYTE
4 Get Size UINT Number of bytes in Attribute 3
Tab. 10-5: Assembly Object Class Attributes
Common Services
Class Instance
0x10 No Yes Set_Attribute_Single Modifies an attribute value.
Tab. 10-6: Common services of Assembly Object
10.2.4 Connection Manager Object (Class Code: 0x06)
Ethernet Link Object

Class Atributes
ID Rule
creases by 1.

Appendix

ID Rule
will show one (01).
Tab. 10-7: Ethernet Link Object Class Attributes
Instance Attribute There are no Instance Attributes implemented for this object.
Common Services Common services of Ethernet Link Object.
Class Instance
0x0E Yes No Get_Attribute_Single Returns the contents of the
Tab. 10-8: Common services of Ethernet Link Object
10.2.5 Discrete Input Point Object (Class Code: 0x08)
Class Attributes
ID Rule
1 Get Revision UINT Revision of this object. The current value assigned to
this attribute is two (02). If up-
creases by 1.
will show sixteen (16).
Tab. 10-9: Discrete Input Point Object Class Attributes
Instance Attribute
ID Rule
3 Get Value BOOL Input point value
Tab. 10-10: Discrete Input Point Object Instance Attributes

Appendix
Discrete Input Point Object Instance assignment

If a channel with IO-Link capabilities is set to any other mode than SIO-Mode
its corresponding instance will not be available in this object.
Port Pin Channel Instance

0 4 00 1
2 10 2
1 4 01 3
2 11 4
2 4 02 5
2 12 6
3 4 03 7
2 13 8
4 4 04 9
2 12 10
5 4 05 11
2 15 12
6 4 06 12
2 16 14
7 4 07 15
2 17 16
Tab. 10-11: Discrete Input Point Object Instance assignment table
Common Services
Class Instance
Tab. 10-12: Common services of Discrete Input Point Object
10.2.6 Discrete Output Point Object (Class Code: 0x09)
Class Attributes
ID Rule
1 Get Revision UINT Revision of this object Der Wert eins (01) istdiesem
Attribut aktuell zugeordnet.
Werden Updates gemacht,
dieeine Erhöhung dieses
Wertes erfordern, wird der
Wert dieses Attributs um 1 er-
höht.
will show sixteen (16).
Tab. 10-13: Discrete Output Point Object Class Attributes
Instance Attribute
ID Rule
3 Get Value BOOL Output point value
Tab. 10-14: Discrete Output Point Object Instance Attributes
Discrete Output Point Object Instance assignment

If a channel with IO-Link capabilities is set to any other mode than SIO-Mode
its corresponding instance will not be available in this object.

Appendix
Port Pin Channel Instance

0 4 00 1
2 10 2
1 4 01 3
2 11 4
2 4 02 5
2 12 6
3 4 03 7
2 13 8
4 4 04 9
2 12 10
5 4 05 11
2 15 12
6 4 06 12
2 16 14
7 4 07 15
2 17 16
Tab. 10-15: Discrete Output Point Object Instance assignment table
Common Services
Class Instance
0x10 No Yes Set_Attribute_Single Modifies the contents of the at-
tributes of the class or object.
Tab. 10-16: Common services of Discrete Output Point Object
10.2.7 Device Level Ring (DLR) Object (Class Code: 0x47)
Class Attributes
ID Rule
this attribute is three (03). If up-
creases by 1.
Tab. 10-17: Device Level Ring Object Class Attributes

Appendix
Instance Attribute
ID Rule
1 Get Network Topolo- USINT Current network topology mode.
gy
2 Get Network State USINT Current status of network.
10 Get Active Supervisor STRUCT of: IP and/or MAC address of the active ring
Address supervisor.
UDINT Supervisor IP Address
ARRAY of 6 Supervisor MAC Address
USINTs
12 Get Capability Flags USINT Describes the DLR capabilities of the de-
vice
Tab. 10-18: Device Level Ring Object Instance Attributes
Common Services
Class Instance
0x0E Yes Yes Set_Attribute_Single Returns the contents of the
Tab. 10-19: Common services of Device Level Ring Object
10.2.8 Quality of Service Object (Class Code: 0x48)
Class Attributes
ID Rule
creases by 1.
2 Get Max In- UINT Maximum instance number of The largest instance number of
stance an object currently created in a created object at this class
will show one (01).
Tab. 10-20: Quality of Service Object Class Attributes

Appendix
Instance Attribute
ID Rule
1 Set, Get 802.1Q Tag Enable USINT Enables or disables sending 802.1Q
frames on CIP and IEEE 1588 messages.
4 Set, Get DSCP Urgent USINT DSCP value for CIP transport class 0/1 Ur-
gent priority messages.
5 Set, Get DSCP Scheduled USINT DSCP value for CIP transport class 0/1
Scheduled priority messages.
6 Set, Get DSCP High USINT DSCP value for CIP transport class 0/1
High priority messages.
7 Set, Get DSCP Low USINT DSCP value for CIP transport class 0/1 low
priority messages.
8 Set, Get DSCP Explicit USINT DSCP value for CIP explicit messages
(transport class 2/3 and UCMM) and all
other EtherNet/IP encapsulation messag-
es.
Tab. 10-21: Quality of Service Object Instance Attributes
Common Services
Class Instance
0x10 No Yes Set_Attribute_Single Modifies the contents of the at-
tributes of the class or object.
Tab. 10-22: Common services of Quality of Service

Appendix
10.2.9 TCP/IP Interface Object (Class Code: 0xF5)
Class Attributes
ID Rule
this attribute is four (04). If up-
creases by 1.
2 Get Max In- UINT Maximum instance number of The largest instance number of
stance an object currently created in a created object at this class
this class level of the device, hierarchy level. This attribute
will show one (01).
Tab. 10-23: TCP/IP Interface Object Class Attributes
Instance Attribute
ID Rule
1 Get Status USINT Interface status
2 Get Configuration USINT Interface capability flags.
Capability
3 Set, Get Configuration USINT Interface control flags.
Capability
4 Get Physical Link Object STRUCT of Path to physical link object.
Path size UINT Size of Path
Path Padded Logical segments identifying the physi-
EPATH cal link object.
5 Set, Get Interface STRUCT of TCP/IP network interface configuration.
Configuration
IP Address UDINT The device’s IP address.
Network Mask UDINT The device’s network mask.
Gateway UDINT Default gateway address.
Address
Name Server UDINT Primary name server
Name Server 2 UDINT Secondary name server.
Domain Name STRING Default domain name.
6 Set, Get Host Name STRING Host name
10 Set, Get SelectAcd BOOL Activates the use of ACD.
11 Set, Get LastConflictDetected STRUCT of Structure containing information related
to the last conflict detected.
AcdActivity USINT State of ACD activity when last conflict
detected.
RemoteMAC Array of 6 USINT MAC address of remote node from the
ARP PDU in which a conflict was detect-
ed.
ArpPdu ARRAY of 28 Copy of the raw ARP PDU in which a
USINT conflict was detected.
12 Set, Get EtherNet/IP Quick- BOOL Enable/Disable of QuickConnect fea-
Connect ture.
13 Get Encapsulation Inac- UINT Number of seconds of inactivity before
tivity Timeout TCP connection or DTLS session is
closed.
Tab. 10-24: TCP/IP Interface Object Instance Attributes

Appendix
Common Services
Class Instance
0x0E Yes Yes Get_Attribute_Single Returns the contents of the spec-
ified attribute.
0x10 NO Yes Set_Attribute_Single Modifies a single attribute.
Tab. 10-25: Common services of TCP/IP Interface Object
10.2.10 Ethernet Link Object (Class Code: 0xF6)
Class Attributes
ID Rule
1 Get Revision UINT Revision of this object. The current value assigned to
this attribute is four (04). If up-
creases by 1.
will show two (02).
3 Get Number of UINT Number of object instances The number of object instanc-
Instances currently created at this class es at this class hierarchy level.
level of the device. This attribute will show two
(02).
Tab. 10-26: Ethernet Link Object Class Attributes
Instance Attribute
ID Rule
1 Get Interface Speed USINT Interface speed currently in use.
2 Get Interface Flags USINT Interface status flags.
3 Get Physical Address USINT MAC layer address.
4 Get Interface Counters STRUCT of
In Octets UDINT Octets received on the interface.
In Ucast Packets UDINT Unicast packets received on the inter-
face.
In NUcast Packets UDINT Non-unicast packets received on the in-
terface.
In Discards UDINT Inbound packets received on the inter-
face but discarded.
In Errors UDINT Inbound packets that contain errors
(does not include In Discards).
In Unknown Protos UDINT Inbound packets with unknown proto-
col.
Out Octets UDINT Octets sent on the interface.
Out Ucast Packets UDINT Unicast packets sent on the interface.
Out NUcast Packets UDINT Non-unicast packets sent on the inter-
face.
Out Discards UDINT Outbound packets discarded.
Out Errors UDINT Outbound packets that contain errors.

Appendix

ID Rule
5 Get Media Counters STRUCT of Media-specific counters
Alignment Errors UDINT Frames received that are not an inte-
gral number of octets in length.
FCS Errors UDINT Frames received that do not pass the
FCS check.
Single Collisions UDINT Successfully transmitted frames which
experienced exactly one collision.
Multiple Kollisionen UDINT Successfully transmitted frames which
experienced more than one collision.
SQE Test Errors UDINT Number of times SQE test error mes-
sage is generated.
Deferred Transmis- UDINT Frames for which first transmission at-
sions tempt is delayed because the medium
is busy.
Late Collisions UDINT Number of times a collision is detected
later than 512 bit-times into the trans-
mission of a packet.
Excessive Collisions UDINT Frames for which transmission fails due
to excessive collisions.
MAC Transmit Errors UDINT Frames for which transmission fails due
to an internal MAC sublayer transmit
error.
Carrier Sense Errors UDINT Times that the carrier sense condition
was lost or never asserted when at-
tempting to transmit a frame.
Frame Too Long UDINT Frames received that exceed the maxi-
mum permitted frame size.
MAC Receive Errors UDINT Frames for which reception on an inter-
face fails due to an internal MAC sub-
layer receive error.
6 Set, Get Interface Control STRUCT of Configuration for physical interface.
Control Bits WORD Interface Control Bits
Forced Interface UINT Speed at which the interface shall be
Speed forced to operate.
7 Get Interface Type USINT Type of interface: twisted pair, fiber, in-
ternal, etc.
8 Get Interface State USINT Current state of the interface: opera-
tional, disabled, etc.
9 Set, Get Admin State USINT Administrative state: enable, disable.
10 Set, Get Interface Label SHORT_STRING Human readable identification.
11 Get Interface Capability STRUCT of Indication of capabilities of the inter-
face.
Capability Bits DWORD Interface capabilities, other than speed/
duplex.
Speed/Duplex STRUCT of Indicates speed/duplex pairs supported
Options in the Interface Control attribute.
USINT Speed/Duplex Array Count.
ARRAY of Speed/Duplex Array
STRUCT of
UINT Interface Speed
UINT Interface Duplex Mode
Tab. 10-27: Ethernet Link Object Instance Attributes

Appendix
Common Services
Class Instance
ified attribute.
0x4C No Yes1 Set_Attribute_Single Gets then clears the specified at-
tribute.
1
The Get_and_Clear sevice is only implemented for the attributes 4 and 5.
Tab. 10-28: Common services of Ethernet Link Object
10.2.11 Vendor Specific Objects
10.2.11.1 IO-Link parameter object (class code: 0x80)
This Object is only implemented in the devices with part number 55143
and 55144.
Class Attributes
ID Rule
creases by 1.
will show one (01).
Class Attri- last class attribute of the class be seven (07).
bute definition implemented in the
device.
7 Get Max ID In- UINT The attribute ID number of the The value of this attribute will
stance Attri- last instance attribute of the differ by product variant. Part
butes class definition implemented in number 55143 will show 2 and
the device. 55144 will show 4.
Tab. 10-29: IO-Link Device Parameter Object Class Attributes
Instance Attribute
ID Rule
11 Get IO-Link Port 1 USINT State of IO-Link Port 1
1 Only available in 55143 or 55144
2 Only available in 55144
Tab. 10-30: IO-Link Device Parameter Object Instance Attributes

Appendix
Semantics IO-Link Port n

The following table shows the possible values of the attributes:
Value (dez) Definition

0 Scanmode
7 SIO-mode, automatic
3 Deactivated
Tab. 10-31: IO-Link Port n Attribute
Common Services The IO-Link Device Parameter Object provides the following common
services.
Class Instance
ified attribute.
Tab. 10-32: Common services of IO-Link Parameter Object
Object-Specific Ser- The following class-specific services are defined for the IO-Link Device
vices Parameter Object.
Class Instance
0x4B No Yes Read_ISDU Read the parameter in the IO-
Link Device in raw format. i.e. Big
Endian
0x4C No Yes Write_ISDU Write the parameter in the IO-
Link Device in raw format i.e. Big
Endian
Tab. 10-33: Common services of Object-Specific Services
Read_ISDU Service Name Data Type Description

Index UINT IO-Link device index
Subindex USINT IO-Link device subindex
Tab. 10-34: Read_ISDU Service structure
Write_ISDU Service Name Data Type Description

Index UINT IO-Link device index
Subindex USINT IO-Link device subindex
Data ARRAY of USINT IO-Link device ISDU data
Tab. 10-35: Write_ISDU Service Structure
Error Codes Error Codes for Read_ISDU and Write_ISDU

The following table defines the error codes that are used by the Read_ISDU
and Write_ISDU services. The returned error message contains two sections,
the standard EtherNet/IP error code construct of General Status Code and Ex-
tended Code, see tab.10-36, as well as an error code “payload”.
The “payloads” structure is described see tab. 10-37.
Error code structure
General Status Code Extended Status Explanation and Description
20hex 0000hex The additional error payload explains
the specific error. See section 1-2.4.2
Tab. 10-36: EtherNet/IP error code structure

Appendix
Error Message Name Data Type Description

“Payload” IO-Link Master Error UINT 1 = Service not available
2 = Port blocked
3 = Timeout
4 = Invalid index
5 = Invalid subindex
6 = Wrong Port
7 = Wrong Port function
8 = Invalid length
9 = ISDU not supported
IO-Link Master Error USINT Refer to IO-Link specification
IO-Link Device Addition- USINT Refer to IO-Link specification
al Error
Tab. 10-37: Error Message “Payload”

Appendix
10.3 Explanation of the process data
10.3.1 Digital Input
The order of the digital input data depends on the configuration parameter
"Pin_Port_based_IO_Layout". This is explained in the following tables:
Port Based
Byte 1 0
Bit 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0
Port X7 X7 X6 X6 X5 X5 X4 X4 X3 X3 X2 X2 X1 X1 X0 X0
Pin 2 4 2 4 2 4 2 4 2 4 2 4 2 4 2 4
Chan- 17 07 16 06 15 05 14 04 13 03 12 02 11 01 10 00
nel
Tab. 10-38: Port Based
Pin Based
Byte 1 0
Bit 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0
Port X7 X6 X5 X4 X3 X2 X1 X0 X7 X6 X5 X4 X3 X2 X1 X0
Pin 2 2 2 2 2 2 2 2 4 4 4 4 4 4 4 4
Chan- 17 16 15 14 13 12 11 10 07 06 05 04 03 02 01 00
nel
Tab. 10-39: Pin Based
NOTICE
The tables for Port and Pin Based are also applicable to Digital Input Qualifier,
Digital Output Qualifier and Digital Output.
10.3.2 DI Qualifier
The Digital Input Qualifiers inform you quickly about the integrity of the input
signal.
Bit value Description

0 Invalid
1 Valid
NOTICE
The bit order depends on the configuration parameter
"Pin_Port_based_IO_Layout". See chapter 10.3.1 "Digital Input"

Appendix
10.3.3 DO Qualifier
The Digital Output Qualifiers inform you quickly about the integrity of the out-
put signal.
Bit value Description

0 Invalid
1 Valid
NOTICE
The bit order depends on the configuration parameter
"Pin_Port_based_IO_Layout". See chapter 10.3 "Explanation of the process
data"
10.3.4 System Status
The system state bit string gives information about the entire device.
Byte Description
0 ... 3 Bit 0: Undervoltage bus/sensor supply
Bit 1: Undervoltage actuator supply
Bit 3: External error
Bit 4: At least one channel has a sensor short circuit
Bit 5: At least one channel has an actuator short circuit
Bit 6: At least one channel has an actuator warning
Bit 7: At least one analog channel has an error
Bit 8: Internal communication error
Bit 9: At least one IO-Link channel has an error (except wire-
break)
Bit 10: Overvoltage bus/sensor supply
Bit 11: Overvoltage actuator supply
Bit 12: At least one IO-Link channel has a wirebreak
Bit 13 ... 31: reserved, set to 0
10.3.5 IO-Link Port X Status
Byte Description
0 ... 3 Reserved
10.3.6 Diagnostic Buffer
The diagnostic buffer consists of an array of diagnostic structures and has a

length of 8 structures. A diagnostic structure has the size of 8 bytes. This gives
a total length of the diagnostic buffer of 64 bytes.
NOTICE
For further information on a diagnostic structure, please refer to chapter 8.1.7
"Diagnostics structure in the control system"

Appendix
10.3.7 Digital Output
NOTICE
The order of the digital output data depends on the configuration parameter
"Pin_Port_based_IO_Layout". See chapter 10.3.1 "Digital Input"
10.4 Accessories
10.4.1 System components
Description Type Art.-No. Packaging

unit
Metal screw plug M12 996049 1
Connection adapter, 3-pin M12 333138 1
Plastic screw plug M12 58627 10
Plastic screw plug, internal thread 7/8“ 55385 1
Grounding strap screw-down set M4 4000-71003-0101604 1
10.4.2 Tools
Fig. 10-1: Installation wrench
Designation Type Art.-No. Packaging

unit
6-part screwdriver set 7000-98001-0000000 1
Installation wrench set, wrench M12 7000-99102-0000000 1
size 13
Installation wrench set, wrench M12 7000-99102-0000000 1
size 13
Installation wrench set, wrench 7/8“ 7000-99104-0000000 1
size 22
PRODUCTS AND ACCESSORIES

You will find a wide range of products in our catalog or
in our Murrelektronik online shop http://shop.murrelektronik.com

Appendix
10.5 Glossary
Term Meaning
Ethernet/IP Ethernet Industrial Protocol
Open standard for industrial networks that supports both cyclic and acyclic transfer of
messages and uses standard Ethernet communication chips and physical media.
10Base-T - Transfer rate: 10 Mbits/s
- Physical structure: star topology
- Maximum cable length: 100 m
- Network cable: twisted-pair cable of category 5
100Base-TX - Transfer rate: 100 Mbits/s

- Physical structure: star topology
- Maximum cable length: 100 m
- Network cable: twisted-pair cable of category 5
100Base-TX is the next generation of 10Base-T. It has the same properties but a
transfer rate of 100 Mbit/s.
Address mapping Address mapping is mapping one address on another address system. Address map-
ping translates addresses of a protocol into addresses of another protocol. This al-
lows systems using two different protocols to work with each other.
API Application programming interface

Interface that a software system provides to other programs in order to interact with
them.
BASP BASP (= Befehlsausgabesperre, i.e. command output block) enabled means that all
module outputs will be disabled and inputs will not be read.
Broadcast Broadcast in a computer network is a message by means of which data packages are
transferred from one point to all network devices.
CIP Common Industrial Protocol
The Common Industrial Protocol is an application protocol used in automation tech-
nology. It supports the transition between fieldbuses and industrial Ethernet and IP
networks. This industrial protocol uses Ethernet/IP in the application layer as inter-
face between fieldbus and control, I/O, etc.
DHCP Dynamic Host Configuration Protocol

DHCP allows a server to dynamically distribute IP address and configuration informa-
tion to clients. Normally, the DHCP server provides at least the following basic infor-
mation to the client:
- IP address
- Subnet mask
- Standard gateway
EDS Electronic Data Sheet

An EDS file is an external file that contains information for a module. It provides nec-
essary information for access to and change of configurable parameters of a module.

Appendix
Term Meaning
Ethernet frame In each Ethernet frame (data package), there are addresses of transmitter (source)
and receiver (target). When a frame is received, the receiving unit of a receiving sta-
tion compares the MAC target address with its own MAC address. When the address-
es match, the receiving unit forwards the contents of the frame to a superior layer. If
they do not match, the frame is discarded.
Ethernet scanner A scanner (master) exchanges realtime I/O data with expansion modules and scan-
ners. It can answer connection requests and initialize connections.
IP Internet Protocol
Protocol used for transferring data within a network, e.g. internet or intranet, from one
computer to another. Each computer in the network can be clearly identified by
means of its IP address. If data is sent from one computer to another, it is subdivided
into small information packages containing each transmitter and receiver addresses.
These packages can be sent over the network using different routes and arrive at
their destination in a different order than the sequence of sending. Another protocol,
the transmission control protocol [TCP], then restores the original order.
IPv4 Internet Protocol Version

IPv4 uses 32-bit addresses. Therefore, maximum 4,294,967,296 unique addresses
are possible. IPv4 addresses are usually written in four blocks in dot-decimal nota-
tion. Each block consists of 8 bits, so that there is a value range of 0 to 255 for each
block. In development.
MAC address Media Access Control Address

Hardware address of network components used for clearly identifying devices in a
network.
Master/slave principle Master/slave principle

The master requests, and slaves follow the instructions of the master. For example,
an automation device, as master, grants access rights to the other components
(slave) in a decentralized bus control.
ODVA ODVA is an international association for open and compatible information and com-
munication technologies in automation systems.
e.g. EtherNet/IP, DeviceNet, CompoNet and ControlNet,....
OSI model Open Systems Interconnection Reference Model

The OSI layer model was published in 1972 by ISO with the aim to facilitate connec-
tion between networks of different manufacturers with different topologies. The OSI
model is a standard that classifies and defines according to which principles commu-
nication between the network components takes place using different protocols
(rules). It consists of seven layers in total:
Physical layer
Data link layer
Network layer
Transport Layer
Session layer
Presentation layer
Application Layer
Term Meaning
IO-Link Standardized communication system to connect
intelligent sensors and actuators to an automation system

Legal notes
11 Legal notes
Disclaimer
Murrelektronik GmbH has reviewed the contents of this technical documenta-
tion for conformity with the described hardware and software. It is possible that
certain details may not be correct. For this reason, we make no warranty re-
garding the accuracy of this technical documentation, and assume no liability
for any errors, in particular full conformity. This exclusion of liability shall not
apply if the damage was caused deliberately and/or due to gross negligence,
nor does it cover any claims based on the German Product Liability Act.
Should a major contractual obligation have been violated negligently, the lia-
bility of Murrelektronik GmbH shall be limited to typically occurring damage.
We reserve the right to make technical alterations and amend the content of
this documentation. We recommend to regularly check whether this documen-
tation has been updated because corrections that might be required due to
technical modifications will be included by Murrelektronik GmbH at regular in-
tervals. Please contact us if you would like to suggest any improvements.
Copyright
It is prohibited to transfer or photocopy the documentation either in paper or in
digital form, reuse or divulge its contents unless otherwise expressly permitted
by Murrelektronik GmbH or in conjunction with the production of documenta-
tion for third-party products that contain products made by Murrelektronik Gm-
bH. Compensation will be claimed if our copyright is violated. All rights
reserved, particularly in the event of a patent being granted or a utility model
being registered.
Usage rights
Murrelektronik GmbH grants its customers a non-exclusive right revocable at
any time and for an indefinite period of time to use this technical documenta-
tion to create their own technical documentation. For this purpose, the docu-
mentation produced by Murrelektronik GmbH may be changed in parts, or
amended, or copied, and transferred to the customer's users as part of the
customer's own technical documentation on paper or on electronic media. In
this case, the customers shall bear sole responsibility for the correctness of
the contents of the technical documentation produced by them.
If the technical documentation is integrated in part, or in full in the customer's
technical documentation, the customer shall refer to the copyright of Murrelek-
tronik GmbH. All safety instructions must be included.
Although the customer is obliged to make reference to the copyright of Mur-
relektronik GmbH, provided the technical documentation of Murrelektronik
GmbH is used, the customers shall market and/or use the technical documen-
tation on their sole responsibility. The reason is that we have no influence on
changes or applications of the technical documentation and even minor
changes to the initial product or deviations in the intended applications may
render incorrect the specifications contained in the technical documentation.
For this reason, the customer is obliged to label the technical documentation
provided by Murrelektronik GmbH if and the extent to which the documenta-
tion is amended by the customer. The customers shall undertake to exempt
Murrelektronik from claims for damages of third parties if the latter are attrib-
utable to any defects in the documentation. This shall not apply to damage to
the rights of third parties caused deliberately or by gross negligence.
The customers shall be entitled to use the company brands of Murrelektronik
GmbH exclusively for their product advertising, but only inasmuch as the prod-
ucts of Murrelektronik GmbH are integrated into the products marketed by the
customers. When using Murrelektronik GmbH brands, the customers shall so
state in an adequate manner.

Murrelektronik GmbH | Falkenstraße 3 | 71570 Oppenweiler | GERMANY
+49 7191 47-0 | +49 7191 47-491 000 | info@murrelektronik.com
www.murrelektronik.com
The information in the manual has been compiled with utmost care. Liability for the correctness,
completeness and topicality of the information is restricted to gross negligence.

English Manual: For 7/8" 4-Pin and 5-Pin Devices of The IMPACT67 Compact Series

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

English Manual: For 7/8" 4-Pin and 5-Pin Devices of The IMPACT67 Compact Series

Uploaded by

Copyright:

Available Formats

ENGLISH MANUAL

for 7/8“ 4-pin and 5-pin devices of the IMPACT67

Manual number 55142

Material short text Art.-No.

User manual 55142_hdb_en_12 3 / 112

2 For your safety 11

ENGLISH MANUAL 4 / 112

9 Maintenance and cleaning 92

ENGLISH MANUAL 5 / 112

11 Legal notes 111

ENGLISH MANUAL 6 / 112

1.1 Service and support

Service and support

User manual 55142_hdb_en_12 7 / 112

1.2 About this manual

Article name Article number

 fitting and electrical installation

Other applicable docu- Document Art.-No. Location

User manual 55142_hdb_en_12 8 / 112

PRODUCTS AND ACCESSORIES

Instruction for use  An arrow marks instructions.

User manual 55142_hdb_en_12 9 / 112

EtherNet/IP © ODVA, Inc.

IO-Link c/o PROFIBUS Nutzerorganisation e.V. (PNO)

User manual 55142_hdb_en_12 10 / 112

2 For your safety

2.1 General safety instructions

User manual 55142_hdb_en_12 11 / 112

Protective measures by  Pay absolute attention to the instructions in this manual.

2.2 Intended purpose

User manual 55142_hdb_en_12 12 / 112

2.3 Environmentally friendly disposal

User manual 55142_hdb_en_12 13 / 112

EtherNet/IP is based on a generator/receiver communication model for which

The EtherNet/IP Unmanaged Switches should only be used in small isolated

User manual 55142_hdb_en_12 14 / 112

For further information, refer to chap. 7.4.3 "RPI configuration"

User manual 55142_hdb_en_12 15 / 112

QuickConnect™ QuickConnect™ describes the functional ability to quickly connect a device to

For further information, refer to chap. 7.4.4 "QuickConnect™-configuration"

3.1.4 Device Level Ring (DLR)

For further information, refer to chap. 7.4.5 "DLR configuration"

User manual 55142_hdb_en_12 16 / 112

Fig. 3-1: IO-Link

For further information, refer to chap. 7.4.6 "IO-Link configuration"

User manual 55142_hdb_en_12 17 / 112

3.3.1 Product Designation Code

IMPACT67 E DIO12 DIO4/IOL4 4P

Properties The IMPACT67 is a fully encapsulated fieldbus module in a plastic case. It is

User manual 55142_hdb_en_12 18 / 112

3.3.2 Module structure

Articles 55138, 55139 and 55140

User manual 55142_hdb_en_12 19 / 112

Articles 55142, 55143 and 55144

User manual 55142_hdb_en_12 20 / 112

3.3.3 Display elements

Articles 55138, 55139 and 55140

Fig. 3-2: Display elements

User manual 55142_hdb_en_12 21 / 112

Articles 55142, 55143 and 55144

Fig. 3-3: Display elements

User manual 55142_hdb_en_12 22 / 112

Overview Art.-No. DIO IO-Link Class