02 12-2019 MANU en UR67-MP

Remote-I/O-System u-remote UR67
I/O-Modules IP67 Multiprotocol

Manual
Letʼs connect.
UR67-MP-HP-16DI-12-60M 2426270000 UR67-MP-78-16DI-12-60M 2426300000

UR67-MP-HP-16DO-12-60M 2426280000 UR67-MP-78-16DO-12-60M 2426310000
UR67-MP-HP-8DIDO-12-60M 2426290000 UR67-MP-78-8DIDO-12-60M 2426320000
UR67-MP-HP-16DIO-12-60M 2512840000 UR67-MP-78-16DIO-12-60M 2512830000

Content
1 About this documentation 5

1.1 Symbols and notes 5
1.2 Complete documentation 5
1.3 Standard data structure 6
1.4 Software releases described 6
2 Safety 7
2.1 General safety notice 7
2.2 Intended use 7
2.3 Legal notice 8
3 System overview 9
3.1 Fieldbus features 10
3.2 Web server 11
3.3 Galvanic isolation 11
3.4 Accessories 11
4 Module descriptions 13
4.1 UR67-MP-HP-16DI-12-60M and UR67-MP-78-16DI-12-60M 13
4.2 UR67-MP-HP-16DO-12-60M and UR67-MP-78-16DO-12-60M 14
4.3 UR67-MP-HP-8DIDO-12-60M and UR67-MP-78-8DIDO-12-60M 15
4.4 UR67-MP-HP-16DIO-12-60M and UR67-MP-78-16DIO-12-60M 16
4.5 Connection assignments 17
4.6 Technical Data 18
4.7 Derating 21
5 Installation and wiring 23
5.1 Preparing for installation 23
5.2 Installing a module 23
5.3 Earthing the module 23
5.4 Attaching the marker 26
5.5 Wiring 26
5.6 Insulation test 26
5.7 Restoring factory settings using the rotary switch 26
5.8 Setting the fieldbus protocol 27
6 Commissioning with Ethernet/IP 29
6.1 Requirements 29
6.2 Installing the EDS file 29
6.3 Connecting a module to the Ethernet/IP network 29
6.4 Connections and assembly object 31
6.5 Initial connection parameter settings 34
6.6 Parameterising the module with Ethernet/IP 35
6.7 Parameterising the process data structure for 16DIO modules 36
6.8 Setting up QuickConnect 37
6.9 Configuration assembly instance 38
6.10 Adjustable parameters with Ethernet/IP 42
Manufacturer
Weidmüller Interface GmbH & Co. KG
Klingenbergstraße 26
D-32758 Detmold
T +49 5231 14-0
F +49 5231 14-292083
www.weidmueller.com
Document No. 2484940000

Revision 02/December 2019
2 Manual UR67-Multiprotokoll 2484940000/02/12.2019

7 Commissioning with PROFINET 45 12 Diagnostics 77
7.1 Requirements 45 12.1 Descriptions of errors 77
7.2 Installing a GSDML file 45 12.2 EtherNet/IP diagnoses 78
7.3 Connecting a module to the PROFINET network 46 12.3 PROFINET diagnoses 78
7.4 Changing the module profile for 16DIO modules 48 12.4 EtherCAT diagnostics 79
7.5 Parameterising the module with PROFINET 48 12.5 LED indicators and troubleshooting 80
7.6 Parameterising process data mapping with 16DIO modules 48
13 Web server 83
7.7 Assigning an IP address to a module 49
13.1 Connecting and starting up the web server 83
7.8 Viewing and changing device names 49
13.2 Getting to know and arranging the web server 83
7.9 Assigning a device name to a UR67-MP module 50
13.3 Module settings and diagnostics 85
7.10 Setting up fast start-up 50
13.4 Web server in Force mode 87
7.11 Configuring the topology 51
13.5 Updating firmware 88
7.12 Setting up device replacement without interchangeable medium/PG 51
7.13 Setting up MRP 51 14 Disassembly and disposal 91
7.14 Simple Network Management Protocol (SNMP) 52 14.1 Disassembling the u-remote module 91
7.15 Adjustable parameters with PROFINET 52 14.2 Disposing of the u-remote module 91
8 Commissioning with EtherCAT 55
8.1 Requirements 55
8.2 Installing an ESI file 55
8.3 Connecting a module to the EtherCAT network 55
8.4 Setting an IP address for EoE protocols 56
8.5 Selecting Process Data 56
8.6 Parameterising a module with EtherCAT 57
8.7 Parameterising the process data structure for 16DIO modules 57
8.8 Firmware updates with FoE 59
8.9 Adjustable parameters with EtherCAT 59
9 Process data with EtherNet/IP 63
9.1 UR67-MP-xx-16DI-12-60M process data 63
9.2 UR67-MP-xx-16DO-12-60M process data 63
9.3 UR67-MP-xx-8DIDO-12-60M process data 64
9.4 UR67-MP-xx-16DIO-12-60M process data 64
9.5 Legend 65
10 Process data with PROFINET 67
10.5 Legend 68
11 Process data with EtherCAT 69
11.5 Legend 75
2484940000/02/12.2019 Manual UR67-Multiprotokoll 3

1 About this documentation | Symbols and notes
1 About this documentation
1.1 Symbols and notes The situation-dependent safety notices may contain the fol-
lowing warning symbols:
The safety notices in this documentation are designed ac-
cording to the severity of the danger. Symbol Meaning
Warning against dangerous electrical voltage
DANGER
Imminent danger to life!
Notes with the signal word “Danger” warn Warning against electrostatically charged
you of situations that will result in serious in- components
jury or death if you do not follow the instruc-
tions given in this manual. Warning against hot surfaces
WARNING
Warning against automatic startup
Possible danger to life!
Notes with the signal word “Warning” warn
you of situations that may result in serious in- Observe the documentation
jury or death if you do not follow the instruc-
tions given in this manual.
▶▶ All instructions can be identified by the black triangles

next to the text.
CAUTION –– Lists are marked with a tick.
Risk of injury!
Notes with the signal word “Caution” warn
you of situations that may result in injury if
1 2 Female connections with sockets are illustrated
you do not follow the instructions given in 4 3
using empty circles.
this manual.
4 3 Male connections with pins are illustrated using
filled circles.
1 2
ATTENTION
Material damage!
Notes with the signal word “Attention” warn you of hazards
that may result in material damage.
1.2 Complete documentation
The documentation is intended for trained elec-
tricians who are familiar with national and inter-
Text next to this arrow are notes that are not
national laws, provisions and standards.
relevant to safety, but provide important infor-
mation about proper and effective work proce-
dures. All documents can also be downloaded from
the Weidmüller website.

1 About this documentation | Standard data structure
1.3 Standard data structure 1.4 Software releases described

All information about the structure of data
(e.g. process data and parameters) refers to the The present manual describes the following firmware re-
standard data format settings in the module leases:
parameters. These are shown in the Motorola
Firmware releases
format.
Order No. Module Release
2426270000 UR67-MP-HP-16DI-12-60M F10017
2426280000 UR67-MP-HP-16DO-12-60M F10017
2426290000 UR67-MP-HP-8DIDO-12-60M F10017
2512840000 UR67-MP-HP-16DIO-12-60M F10017
2426300000 UR67-MP-78-16DI-12-60M F10017
2426310000 UR67-MP-78-16DO-12-60M F10017
2426320000 UR67-MP-78-8DIDO-12-60M F10017
2512830000 UR67-MP-78-16DIO-12-60M F10017
Device description files

Fieldbus protokoll Release
EtherNet/IP 1.0
PROFINET 20190830
EtherCAT 1.2
Language files Webserver

Language Release Availability
Deutsch 01.00.00 On delivery
Englisch 01.00.00 On delivery
Chinesisch 01.00.00 On delivery

2 Safety | General safety notice
2 Safety
This chapter includes general safety instructions on handling Fusing

the UR67 modules. Specific safety instructions for specific The operator must set up the equipment so that it is pro-
tasks and situations are given at the appropriate places in tected against overloading. The upstream fuse must be
the documentation. designed so that it does not exceed the maximum load cur-
rent. The maximum permissible load current can be found
All work may only be carried out by trained in the technical data. The operator must decide whether ad-
electricians who are familiar with the safety ditional surge protection is required according to IEC 62305.
standards that apply to automation technol- Voltages that exceed +/-30 V may cause the destruction of
ogy. the modules. A power supply with secure isolation must be
The documentation must be stored in such a used.
way that it is accessible to operating staff at
all times. Earthing (functional earth FE)
Every UR67-MP module is equipped with an earth connec-
tion, with the connection point labelled “XE”. Further infor-
mation is available in chapter 5.
2.1 General safety notice Shielding

Shielded lines are to be connected with shielded plugs in
When working during ongoing operations, the emergency compliance with the relevant standard.
stop mechanisms must not be made ineffective.
If faults connected to a u-remote product cannot be rectified,
the product in question must be sent to Weidmüller. Wei-
dmüller assumes no liability if the module is tampered with!
All connected devices must comply with the requirements
2.2 Intended use
set out in EN 61558-2-4 and EN 61558-2-6. Only cables The UR67-MP modules are decentral input and output de-
and accessories that meet the requirements and provisions vices in an EtherNet/IP, PROFINET or EtherCAT network.
regarding safety, electromagnetic compatibility and, if neces- The products are designed for use in industrial automa-
sary, telecommunications terminal equipment, as well as the tion and may only be used within the scope of the stated
specifications, may be installed. Information on the specific technical specifications. The devices to be connected must
cables and accessories that are permitted to be installed is comply with the requirements set out in EN 61558-2-4 and
provided in this manual or can be requested from Weidmül- EN 61558-2-6.
ler. The industrial environment is labelled as such to ensure that
consumers are not directly connected to the public low-volt-
Electrostatic Discharge age network. Additional measures must be taken for use in
u-remote products can be damaged or destroyed by electro- the home, and in the business and commercial sectors.
static discharge. When handling the products, the neces- For UL applications, the following restrictions also apply:
sary safety measures against electrostatic discharge (ESD) –– use only in enclosed areas
according to IEC 61340-5-1 and IEC 61340-5-2 must be –– use only at heights of less than 2,000 m
observed. The packing and unpacking as well as the installa- –– max. pollution degree II
tion and disassembly of a device may only be carried out by
qualified personnel. Any intervention in the products hardware or software other
than described in this manual may only be realised by Wei-
dmüller.
Malfunction-free operation is only guaranteed if the housing
is fully assembled. Observance of the documentation is also
part of the intended use.

2 Safety | Legal notice
2.3 Legal notice

The UR67-series products comply with the EU Directive
2014/30/EU (EMC Directive).
Components of the following free software products are inte-

grated into the modules:
Component License Link

https://github.com/jquery/jquery/blob/master/
jQuery MIT
LICENSE.txt
jQuery-custom- https://github.com/jquery/jquery/blob/master/
MIT
Select LICENSE.txt
jQuery-i18n MIT
LICENSE.txt
jQuery-over- https://github.com/jquery/jquery/blob/master/
MIT
scroll LICENSE.txt
jQuery-ui MIT
LICENSE.txt
https://github.com/Stuk/jszip/blob/master/
JSZip MIT
LICENSE.markdown
md5 (as part https://code.google.com/archive/p/crypto-js/
MIT
of CryptoJS) wikis/License.wiki
Apache https://github.com/adobe-webplatform/Snap.
snap-svg
license 2.0 svg/blob/master/LICENSE
https://github.com/jashkenas/underscore/blob/
underscore MIT
master/LICENSE

3 System overview
3 System overview
UR67-MP-HP-X (2426270000, 2426280000, 2426290000, 2512840000) UR67-MP-78-X (2426300000, 2426310000, 2426320000, 2512830000)
u-remote IP67 modules for Ethernet/IP, PROFINET and EtherCAT
The UR67-MP modules are multiprotocol modules that All connections are colour and mechanically coded:
communicate via EtherNet/IP, PROFINET or EtherCAT. The –– 2 × power supply connections (grey):
required protocol is selected on the module using the rotary –– UR67-MP-HP-xx: M12, L-coded, 5-pole
switch. –– UR67-MP-78-xx: 7/8“, 5-pole
The fully encapsulated metal housing means that the mod- –– 2 × fieldbus networks (green): M12, D-coded, 4-pole
ules comply with degree of protection IP67. –– 8 × I/O connections (black): M12, A-coded, 5-pole
The output current is up to 2 A per channel.
The modules with output functionality support a fail-safe Each I/O connection is assigned two status LEDs which
function, which can be used to set how a channel configured change colour and the frequency at which they flash is ac-
as an output is to respond to impaired or interrupted fieldbus cording to the status of the respective connection (see Sec-
communication. tion 12).
The UR67-MP modules differ in terms of their I/O functional-
ity and connections for the power supply.
Module designation Order number Power supply connection Number of digital inputs Number of digital outputs
UR67-MP-HP-16DI-12-60M 2426270000 M12 16 0
UR67-MP-HP-16DO-12-60M 2426280000 M12 0 16
UR67-MP-HP-8DIDO-12-60M 2426290000 M12 8 8
UR67-MP-HP-16DIO-12-60M 2512840000 M12 max. 16 (configurable) max. 16 (configurable)
UR67-MP-78-16DI-12-60M 2426300000 7/8“ 16 0
UR67-MP-78-16DO-12-60M 2426310000 7/8“ 0 16
UR67-MP-78-8DIDO-12-60M 2426320000 7/8“ 8 8
UR67-MP-78-16DIO-12-60M 2512830000 7/8“ max. 16 (configurable) max. 16 (configurable)

3 System overview | Fieldbus features
3.1 Fieldbus features Alarm and diagnostic messages

The modules offer expanded Ethernet/IP, PROFINET and Eth-
erCAT alarm and diagnostic messages.
MAC addresses
Each module has a unique MAC address allocated by the
manufacturer and which cannot be changed by the user. The Device description files
MAC address is printed on the module. A device description file is needed for the configuration and
parameterisation of the module in the engineering tool.
–– Ethernet/IP: EDS file
Integrated Ethernet switch –– PROFINET: GSDML file
The integrated Ethernet switch with two connections ena- –– EtherCAT: ESI file
bles the creation of different topologies:
You can download the current device description
–– Ethernet/IP: ring or line topology
files from the Weidmüller website.
–– PROFINET: ring or line topology
–– EtherCAT: line topology
Ethernet/IP product features Configurable process data for 16DIO modules

The UR67-MP modules support the following Ethernet/IP With the UR67-MP-XX-16DIO modules, you can parameter-
functions: ise the process data mapping and the data direction of the
–– Device Level Ring protocol (DLR) for simple ring topolo- channels. In doing so, the existing devices are replaced by
gies in accordance with the Ethernet/IP specification. UR67-MP-XX-16DIO modules without changing the map-
–– QuickConnect for quick start-up ping or process data.
For simplified commissioning, the device-describing files
PROFINET product features contain pre-configured module profiles.
The UR67-MP modules support the PROFINET IO device IRT
(Isochronous Real-Time). This means that process data can Module profile Description
be transferred in real time.
The UR67-MP modules support the following PROFINET 16DI/DO 16 combined inputs and outputs
functions: 8DI/DO 8 combined inputs and outputs (only pin 4)
–– DCP: for the automatic allocation of IP addresses
–– Fast start-up for prioritised start-up 16DI 16 inputs
–– Device replacement without interchangeable medium / 8DI 8 inputs (only pin 4)
PG for the replacement of devices without re-configura-
tion 16DO 16 outputs
–– LLDP for the detection of devices in the vicinity (neigh- 8DO 8 outputs (only pin 4)
bouring device detection)
–– MRP for the implementation of redundant PROFINET net- 8DI/8DO 8 inputs, 8 outputs
works without additional switches
–– SNMP for the monitoring of network components
EtherCAT product features

The UR67-MP modules support the following mailbox proto-
cols:
–– Ethernet over EtherCAT (EoE): for accessing the web
server function
–– CANopen over EtherCAT (CoE): for transmitting process,
diagnostic and parameter data
–– File access over EtherCAT (FoE): for firmware updates

3 System overview | Web server
3.2 Web server 3.4 Accessories

The web server can be used to display the UR67-MP module
on a connected PC. This allows you to execute the following Protective caps
functions for test purposes or during commissioning or ser- Degree of protection IP67 is only achieved when the module
vice work: is fully installed. Therefore, all connections not being used
–– Query the module status must be fitted with protective caps.
–– Display and change the module parameters
–– Retrieve diagnostic information Size Usage Protective cap Order No.
–– Operate the module in Force mode for testing purposes M12 Sensor connection SAI-SK M12 9456050000
A description of the web server can be found in Chapter 13. M12 Bus-out, power-out SAI-SK-M12-UNI 2330260000
M12 Bus-in, power-in SAI-SK M12 connector 1781520000
7/8“ Power-out SAI-7/8-SK-P-F 1422760000
7/8“ Power-in SAI-7/8-SK-P-M 2007270000
3.3 Galvanic isolation
If you use modules with galvanic isolation togeth-
er with modules without galvanic isolation, the
Markers
galvanic isolation of these modules is cancelled
Module and connection markers are available to label equip-
out.
ment. All of the markers can be printed using the Weidmüller
PrintJet ADVANCED (Order No. 1324380000).
For some modules, the output power circuit is galvanically
isolated from the system current path with the sensor sup-
Module Markers Order No.
ply:
UR67-MP-xx-xxx-60M ESG-M8/20 MC NE WS 1027290000
Module designation Galvanic isolation
UR67-MP-HP-16DI-12-60M yes
Cables and connections
UR67-MP-HP-16DO-12-60M yes
In order to select suitable cables, we recommend referring to
UR67-MP-HP-8DIDO-12-60M yes Weidmüller Catalogue 8 or the Product Configurator on the
Weidmüller website.
UR67-MP-HP-16DIO-12-60M no
UR67-MP-78-16DI-12-60M yes
UR67-MP-78-16DO-12-60M yes
UR67-MP-78-8DIDO-12-60M yes
UR67-MP-78-16DIO-12-60M no

4 Module descriptions | UR67-MP-HP-16DI-12-60M and UR67-MP-78-16DI-12-60M
4 Module descriptions
4.1 UR67-MP-HP-16DI-12-60M and

UR67-MP-78-16DI-12-60M 1
2 1
A
5
DIA
B
UR67-MP-xx-16DI-12-60M
3
2 A 6
DIA
B
MAC: XXXXXXXXXXXXXXXXX
3 7
A
DIA
Left: UR67-MP-HP-16DI-12-60M input module (Order No. 2426270000) B
Right: UR67-MP-78-16DI-12-60M input module (Order No. 2426300000)
Each module has eight connections (M12, 5-pole, A-coded) 4 4 8

A
for signal lines as well as connections for the fieldbus (M12, DIA
4-pole, D-coded). The power supply is connected via 5-pole, B
L-coded M12 or 7/8" connections. 5 E/IP: MS NS 10

PN: Link/Act BF DIA UL US
The UR67-MP-xx-16DI-12-60M modules have 16 digital in-
EC: X01 X02 RUN ERR
puts (sourcing output). 0 E/IP 0 0
PN
6 x100
EC
x10 x1 11
Diagnostic and status LEDs
7
LED Display Meaning IN BUS OUT
US green/red System/sensor power supply status

X01 X02
1 to 8 A yellow/red Channel A status
1 to 8 B white/red Channel B status
8 IN OUT
green/
Lnk/Act X01 Connection/X01 connection activity
yellow
green/
yellow 12
9 16DI
XE
Module status (Ethernet/IP)
MS/BF/RUN green/red Bus status (PROFINET)
current status (EtherCAT)
Product details for UR67-MP-HP-16DI-12-60M and UR67-MP-78-16DI-12-60M
Network status (Ethernet/IP)
NS/DIA/ERR green/red Diagnosis indicator (PROFINET) 1 Marker connection 1
Error display (EtherCAT) 2 I/O connection 1
LED displays, error messages, see section 12.5 3 Status LED connection 1, channel A/channel B
4 Fieldbus and module status LEDs
5 Lnk/Act status LEDs
6 Rotary switch (for setting the protocol)
7 Fieldbus connection
8 M12 or 7/8" power supply connection
9 Module marker
10 Power supply status LED (US system/sensor power supply)
11 Micro-USB port (not to be used by the customer)
12 Earth connection (M4 thread)

4 Module descriptions | UR67-MP-HP-16DO-12-60M and UR67-MP-78-16DO-12-60M
4.2 UR67-MP-HP-16DO-12-60M and

UR67-MP-78-16DO-12-60M 1
2 1
A
5
DIA
B
UR67-MP-xx-16DO-12-60M
3
2 A 6
DIA
B
3 7
A
DIA
Left: Output module UR67-MP-HP-16DO-12-60M (Order No. 2426280000) B
Right: Output module UR67-MP-78-16DO-12-60M (Order No. 2426310000)

A
L-coded M12 or 7/8" connections. 5 E/IP: MS NS 10

PN: Link/Act BF DIA UL US
The UR67-MP-xx-16DO-12-60M modules have 16 digital
EC: X01 X02 RUN ERR
outputs (sourcing output). 0 E/IP 0 0
PN
6 x100
EC
x10 x1 11
7
UL green/red Actuator supply status

X01 X02
8 IN OUT
green/
yellow
Lnk/Act X02
green/
Connection/X02 connection activity
9 16DO
XE
12
yellow
Product details for UR67-MP-HP-16DO-12-60M and UR67-MP-78-16DO-12-60M
Network status (Ethernet/IP) 1 Marker connection 1
NS/DIA/ERR green/red Diagnosis indicator (PROFINET) 2 I/O connection 1
Error display (EtherCAT) 3 Status LED connection 1, channel A/channel B
LED displays, error messages, see section 12.5
9 Module marker
10 Power supply status LED (UL actuator power supply, US system/sensor
power supply)

4 Module descriptions | UR67-MP-HP-8DIDO-12-60M and UR67-MP-78-8DIDO-12-60M
4.3 UR67-MP-HP-8DIDO-12-60M and

UR67-MP-78-8DIDO-12-60M 1
2 1
A
5
DIA
B
UR67-MP-xx-8DIDO-12-60M
3
2 A 6
DIA
B
3 7
A
DIA
Left: Input/Output module UR67-MP-HP-8DIDO-12-60M (Order No. 2426290000) B
Right: Input/Output module UR67-MP-78-8DIDO-12-60M (Order No. 2426320000)

A
L-coded M12 or 7/8" connections. 5 E/IP:

PN: Link/Act
MS NS
BF DIA UL US
10
The UR67-MP-xx-8DIDO-12-60M modules have 8 digital in-
EC: X01 X02 RUN ERR
puts and 8 digital outputs (sourcing output). 0 E/IP 0 0
PN
6 x100
EC
x10 x1 11
7

X01 X02
8 IN OUT
green/
yellow
Lnk/Act X02
green/
9 8DIDO
XE
12
yellow
Product details for UR67-MP-HP-8DIDO-12-60M and UR67-MP-78-8DIDO-12-60M
9 Module marker
power supply)

4 Module descriptions | UR67-MP-HP-16DIO-12-60M and UR67-MP-78-16DIO-12-60M
4.4 UR67-MP-HP-16DIO-12-60M and

UR67-MP-78-16DIO-12-60M 1
2 1
A
5
DIA
B
UR67-MP-xx-16DIO-12-60M
3
2 A 6
DIA
B
3 7
A
DIA
Left: Input/Output module UR67-MP-HP-16DIO-12-60M (Order No. 2512840000) B
Right: Input/Output module UR67-MP-78-16DIO-12-60M (Order No. 2512830000)

A
L-coded M12 or 7/8" connections. 5 E/IP:

PN: Link/Act
MS NS
BF DIA UL US
10
The UR67-MP-xx-16DIO-12-60M modules have 16 configur-
EC: X01 X02 RUN ERR
able digital inputs and outputs (sourcing output). 0 E/IP 0 0
PN
6 x100
EC
x10 x1 11
7

X01 X02
8 IN OUT
green/
yellow
Lnk/Act X02
green/
9 16DIO
XE
12
yellow
Product details for UR67-MP-HP-16DIO-12-60M and UR67-MP-78-16DIO-12-60M
9 Module marker
power supply)

4 Module descriptions | Connection assignments
4.5 Connection assignments

I/O connections (black): Ethernet/IP, PROFINET, EtherCAT (green)
M12, A-coded 16DI 16DO 8DIDO 16DIO M12, 4-pole, D-coded Signal Role
+24 V US (connections 1 1 TD+ Transmission data +
1 +24 V US n.c. to 4) +24 V US/L
n.c. (connections 5 to 8)
1 2
2 RD+ Received data +
DIB (connections 1 to 4)
2 DIB DOB DIB/DOB
4 3
3 TD– Transmission data –
3 4 DOB (connections 5 to 8)
GND US (connections 1 to 4) 4 RD– Received data –
2 1 3 GND US GND UL GND US/L
GND UL (connections 5 to 8)
5
DIA (connections 1 to 4)
4 DIA DOA
DOA (connections 5 to 8)
DIA/DOA ATTENTION
5 FE FE FE FE Product can be destroyed!
▶▶ Never place the power supply (24 V DC) on the signal
or data lines.
ATTENTION
For the system/sensor power supply and the actuator
power supply, only use power supplies that conform to
PELV (Protective Extra Low Voltage) or SELV (Safety Extra
Low Voltage) requirements. Power supplies in accord-
ance with EN 61558-2-6 (transformer) or EN 60950-1
(switched-mode power supply) meet these requirements.
Power supply connection (grey)

M12, 5-pole, L-coded Signal Role
System/sensor power
5
1
1 +24 V US
supply
2
4
3
2 GND UL Earth/reference potential UL
OUT
3 GND US Earth/reference potential US
1
5
Actuator power supply
4 +24 V UL
2
4 (electrogalvanised)
3
5 FE (PE) Functional earthing
IN
7/8" Signal Role
3 1 GND UL Earth/reference potential UL
4 2
2 GND US Earth/reference potential US

5 1
3 FE (PE) Functional earthing

3
2 4 System/sensor power
4 +24 V US
supply
1 5 Actuator power supply
5 +24 V UL
(electrogalvanised)

4 Module descriptions | Technical Data
4.6 Technical Data

Technical data
Bus system
Protocol Ethernet/IP, PROFINET, EtherCAT
Vendor name (Ethernet/IP) 1015
Product type (for Ethernet/IP) Number: 7
String: General Purpose Discrete I/O
Product code (Ethernet/IP) 34000 (UR67-MP-78-16DI-12-60M)
34001 (UR67-MP-78-16DO-12-60M)
34002 (UR67-MP-78-8DIDO-12-60M)
34006 (UR67-MP-78-16DIO-12-60M)
34003 (UR67-MP-HP-16DI-12-60M)
34004 (UR67-MP-HP-16DO-12-60M)
34005 (UR67-MP-HP-8DIDO-12-60M)
34007 (UR67-MP-HP-16DIO-12-60M)
VendorID (PROFINET) 0x0134 hex
DeviceID (PROFINET) 0x18C6 hex
Vendor ID (EtherCAT) 0x00000230 hex
Product code (EtherCAT) 0xE763D70 (UR67-MP-78-16DI-12-60M)
0xE764158 (UR67-MP-78-16DO-12-60M)
0xE764540 (UR67-MP-78-8DIDO-12-60M)
0x95C6BE30 (UR67-MP-78-16DIO-12-60M)
0xE7631B8 (UR67-MP-HP-16DI-12-60M)
0xE7635A0 (UR67-MP-HP-16DO-12-60M)
0xE763988 (UR67-MP-HP-8DIDO-12-60M)
0x95C6E540 (UR67-MP-HP-16DIO-12-60M)
EDS file (Ethernet/IP) WM_xx_Vz_z_z_yyyymmdd.eds
GSDML file (PROFINET) GSDML-Vx.x-WI-UR67-yyyymmdd.xml
ESI file (EtherCAT) Weidmueller-UR67-Digital-IO.xml
Data transmission rate 100 Mbps full duplex
Transmission method 100BASE-TX
Auto-negotiation Supported
Addressing type (EtherCAT) Auto-incremental addressing, fixed addressing
Cycle time (EtherCAT) min. 250 µs
Ethernet protocols supported ICMP, ARP, DHCP, HTTP, TCP/ IP, BOOTP, beacon-based DLR (Ethernet/IP)
ICMP, ARP, LLDP, DCP, HTTP, TCP/ IP, SNMP, MRP (PROFINET)
ICMP, ARP, HTTP, TCP/IP (EtherCAT)
Switch functionality Integrated, 2 connections
RT and IRT are supported (PROFINET)
Autocrossing Supported
Connection M12, 4-pole, D-coded
1) In the case of inductive loads in utilisation category DC13 (in acc. with EN 60947-5-1), the outputs can operate with currents of 1.6 A and a frequency of 1 Hz.
2) The total current of connection groups 1 and 2, 3 and 4, 5 and 6, and 7 and 8 most not exceed 6.5 A in each case.
3) Technically possible and approved on the following conditions: looped system/sensor power supply US max. 2.5 A; minimum cross-section of power supply cable:
5 x 1.0 mm²; max. ambient temperature 40°C (104°F)
4) The degree of protection IP 69 is achieved exclusively from modules with an M12 power supply connection (UR67-MP-HP-xxx-12-60M).

Technical data
Inputs
Channel type NO contact, sourcing output
Input wiring Type 3 in acc. with IEC 61131-2
Rated input voltage 24 V DC
Input current at 24 V DC typically 5 mA
Short-circuit-proof yes
Status indicator Yellow LED (channel A), white LED (channel B)
Diagnosis indicator Red LED for every M12 socket
Connection M12, 5-pole, A-coded
Outputs
Channel type NO contact, sourcing output
Output wiring typically 2 A in acc. with IEC 61131-2
Output current per channel 1)
Signal status “1” max. 2 A2)
Signal status “0” max. 1 mA (specification as per standard)
Signal level of the outputs
Signal status “1” min. (UL – 1 V)
Signal status “0” max. 2 V
Output current per module 9 A, see derating curve (see section 4.7)
Short-circuit-proof yes
Overload-proof yes
Status indicator Yellow LED (channel A), white LED (channel B)
Diagnosis indicator Red LED, for each channel
Connection M12 socket, 5-pole, A-coded
Electronics/sensor system supply
Rated voltage US 24 V DC (SELV/PELV)
Voltage range 24 V DC ± 25%
Current-carrying capacity US UR67-MP-78-xx: max. 9 A (12 A3))
UR67-MP-HP-xx: max. 16 A
Electronics current consumption typically 95 mA at 24 V
typically 120 mA at 30 V
Sensor system voltage min. (US – 1.5 V)
Sensor system current consumption max. 200 mA per connection (at Tu 30°C)
Reverse polarity protection yes
Operating display (US) Green/red LED
Connection 7/8" plug and socket, 5-pole (UR67-MP-78-X)
M-12, 5-pole, L-coded (UR67-MP-HP-X)

Technical data
Actuator power supply
Rated voltage UL 24 V DC (SELV/PELV)
Voltage range 24 V DC ± 25%
Current-carrying capacity UL UR67-MP-78-xx: max. 9.0 A (12 A3))
UR67-MP-HP-xx: max. 16 A
Potential isolation yes
Undervoltage threshold typically 18 V
Undervoltage < 20 ms
detection delay
Reverse polarity protection yes
Actuator power display (UL) Green/red LED
Connection 7/8" plug and socket, 5-pole (UR67-MP-78-X)
M-12, 5-pole, L-coded (UR67-MP-HP-X)
General data
Type of protection when screwed in: IP 65, IP 67, IP 69(4)
Ambient temperature -20°C to +70°C
Humidity max. 98% (at UL: 80%)
Weight 500 g (UR67-MP-HP-X)
520 g (UR67-MP-78-X)
Enclosure material Die-cast zinc, matt nickel surface
Vibration resistance – vibration 15 g / 5 … 500 Hz
Vibration resistance – impact 50 g/11 ms
Tightening torques
M4 mounting screw 1 Nm
M4 earth connection 1 Nm
M12 plug-in connector 0.5 Nm
Approvals and standards
cULus UL 508
EMC EN 61000-6-2:2005/AC:2005,
EN 61000-6-4:2007/A1:2001

4 Module descriptions | Derating
4.7 Derating
The permissible total output current depends on the
ambient temperature.
IL
9A
3A
55 °C 70 °C TA
Derating: Total output current IL via ambient temperature TA

5 Installation and wiring | Preparing for installation
5 Installation and wiring
WARNING 5.2 Installing a module

Dangerous contact voltage! The installation surface must be level.
▶▶ All installation and wiring work must be ▶▶ Drill the holes for the fixings (for the drilling dimensions,
carried out with the power supply discon- see the installation drawings on the following pages).
nected. ▶▶ Attach each module with two screws and a washer (in
▶▶ Make sure that the place of installation accordance with DIN EN ISO 7089).
has been disconnected from the power ▶▶ Observe the screw dimension and tightening torques indi-
supply! cated (see technical data).
CAUTION
Hot surface!
The device can become very hot when in 5.3 Earthing the module
operation.
▶▶ Allow the device to cool down before The module must be earthed in order to discharge interfer-
touching it! ence currents and for EMC stability.
▶▶ Connect the XE earth connection to the reference earth
via a low-impedance connection (see installation draw-
ing).
5.1 Preparing for installation If the mounting surface is earthed, you can produce the con-
nection directly with a mounting screw.
Make sure that the permitted environmental conditions for
installation and operation are observed (see technical data). If the installation surface is not earthed, use an earthing
strap or a suitable cable with cable lug!
Installation dimensions
The installation dimensions are provided in the installation
drawings on the following pages.
Unpacking the delivery

▶▶ Please check the delivery for completeness and transport
damage.
▶▶ Please report any transport damage immediately to the
respective transport company.
ATTENTION
The product can be destroyed by
electrostatic discharge!
u-remote products can be destroyed by elec-
trostatic discharge.
▶▶ Make sure that persons and work equip-
ment are sufficiently earthed!
▶▶ Unpack all of the parts.

▶▶ Dispose of all packaging in accordance with the local dis-
posal guidelines. The cardboard packaging can be sent
for paper recycling.

5 Installation and wiring | Earthing the module
59.6
17.6 29.8
3 4
M4x25/30
1 5
A
female
2
5
1 DIA
M12 I/0 B
Function Pin
24V 1 UR67-MP-HP-xx-12-60M
In B 2
GND 0V 3
In A 4
FE 5
2 A 6
DIA
B
M12
-20° ... +70°C / -4° ... +158°F
24V 2A (PD max. 9A)
I/O
24V 0.12A
24V 0.2A
3 A 7
DIA
B
Output Power Supply:
System Power Supply:
Sensor Power Supply:
Max. Amblent Temp.:
4 8
191.0
A
200.0
DIA
E/IP
B
901
2
P PN E/IP: MS NS
EC PN: Link/Act BF DIA UL US
9 01
8 2
7 3
6 5 4
EC: X01 X02 RUN ERR
01
8
7
9
2
3
0 E/IP 0 0
6 5 4
3 4 PN
EC
x100 x10 x1
female
2 1
Bus
Function Pin
TD+ 1
RD+ 2 IN BUS OUT
TD- 3
RD- 4
X01 X02
M12
Power
M4x25/30
FunctionPin
BUS +24V
GND UL
1
2
GND 0V 3
+24V UL 4
FE 5
1
IN OUT
2
5
M12
female
4 3 16DI
Power XE
M4
30.7 20.0
Installation dimensions UR67-MP-HP-16DI-12-60M, UR67-MP-HP-16DO-12-60M, UR67-MP-HP-8DIDO-12-60M, UR67-MP-HP-16DIO-12-60M

5 Installation and wiring | Earthing the module
59.6
17.3 29.8
M4x25/30
3 4 1 5
A
DIA
female
2 1
5 B
M12 I/0 UR67-MP-78-xx-12-60M
Function Pin
24V 1
In B 2
GND 0V 3
In A 4 2 6
FE 5 A
DIA
B
M12
I/O
-20° ... +70°C / -4° ... +158°F
24V 2A (PD max. 9A)
3 7
A
24V 0.12A
DIA
24V 0.2A
B
Output Power Supply:
System Power Supply:
Sensor Power Supply:
Max. Amblent Temp.:
4 8
A
197.5
206.0
DIA
B
E/IP: MS NS
E/IP
901
2 PN: Link/Act BF DIA UL US
P PN
EC
8
901
2 EC: X01 X02 RUN ERR
7
6 5 4
3
0 E/IP 0 0
901
8 2
7
6 5 4
3 PN
EC
3 4 x100 x10 x1
female
2 1
Bus
Function Pin IN BUS OUT
TD+ 1
RD+ 2
TD- 3
X01 X02
M12
RD- 4
BUS
Power
FunctionPin M4x25/30
GND UL 1 IN OUT
GND 0V 2
FE 3
+24V 4
+24V UL 5
1 2
7/8" 3
female
Power 5 4 16DI
XE
M4
26.2 20.0
Installation dimensions UR67-MP-78-16DI-12-60M, UR67-MP-78-16DO-12-60M, UR67-MP-78-8DIDO-12-60M, UR67-MP-78-16DIO-12-60M

5 Installation and wiring | Attaching the marker
5.4 Attaching the marker 5.6 Insulation test

The module and all ports can be labelled using markers. Insulation tests must always be carried out before each com-
missioning and in accordance with the respective national
▶▶ Press the labelled marker into the corresponding fixture provisions.
opening.
▶▶ To remove a marker, lever it out carefully using a screw- ATTENTION
driver (2.5 or 3 mm).
The product can be destroyed as a
result of excessive test voltage!
Please observe the following during insula-
5.5 Wiring tion tests:
–– The test voltage within a channel must
not exceed 30 V between 24 V and GND!*
WARNING –– A max. test voltage of 500 V can be
Dangerous contact voltage! applied to all other connection points.
▶▶ All installation and wiring work must be
carried out with the power supply discon-
nected.
▶▶ Make sure that the place of installation * We recommend connecting 24 V and GND at the power
has been disconnected from the power supply plug.
supply!
Once the module has been mechanically installed, the wiring

can be carried out in accordance with the wiring plan. 5.7 Restoring factory settings using the rotary
switch
Element Torque
M12 plug-in connectors 0.5 Nm The module's factory settings can be restored via the rotary
switch. The protocol settings can be reset in the same way.
M12 protective cap 0.5 Nm
The Factory settings web server function
Ensure compliance with the minimum permissi- does not reset the protocol settings.
ble cable bending radius.
▶▶ Turn the left rotary switch (“x100”) to the value “9”.

All unused ports must be sealed with protective ▶▶ Turn the middle rotary switch (“x10”) to the value “7”.
caps in order to achieve protection class IP67. ▶▶ Turn the right rotary switch (“x1”) to the value “9”.
▶▶ Switch the power supply off and back on again 10 sec-
onds later.
At ambient temperatures hotter than 55°C: The module is reset to factory settings.
▶▶ Use cables with a cross-section of 2.5 mm² for
the power supply.
9 7 9
For UL applications:
▶▶ Use only UL-certified cables with appropriate 0 E/IP 0 0
ratings (CYJV or PVVA).
▶▶ Use temperature-resistant cables:
–– UR67-MP-xx-16DI-12-60M: up to 85°C PN
–– UR67-MP-xx-16DO-12-60M: up to 96°C EC
–– UR67-MP-xx-8DIDO-12-60M: up to 96°C x100 x10 x1
–– UR67-MP-xx-16DIO-12-60M: up to 96°C
Restoring factory settings using the rotary switch

5 Installation and wiring | Setting the fieldbus protocol
5.8 Setting the fieldbus protocol Only use DHCP/BOOTP if a relevant server is in
the network that can assign the network param-
eters to the module.
The fieldbus protocol and the module behaviour in the net-
work are set using the rotary switch. The module adopts
and saves these settings the next time the power supply is ▶ Restore the factory settings using the rotary switch
switched back on. (see Section 5.7).
▶ Turn the left rotary switch (“x100”) to a value from 0 to 4.
The fieldbus protocol can only be changed after
▶ Turn the middle rotary switch (“x10”) to a value from 0 to
the module has been reset to factory settings.
9.
▶ Turn the right switch (“x1”) to a value from 0 to 9.
▶ Switch the power supply off and back on again 10 sec-
Any changes made to the position of the rotary
onds later.
switch only take effect once the power supply
The modules adopts the news settings.
has been switched off and back on again. Wait
at least ten seconds before switching the power
If you make an invalid setting, the BF/MS/RUN LED will flash
supply back on to ensure the changes take ef-
red three times.
fect.
2 1 0
0 E/IP 0 0
PN
EC
x100 x10 x1
Example: Setting the value of “210” (IP address 192.168.1.210 for Ethernet/IP)
The following table shows the possible rotary switch

settings.
Setting Protocol Description
The previously saved network settings are used.
000 Ethernet/IP When in the delivered condition, the network
parameters are requested via DHCP/BOOTP.
The last octet of the IP address is overwritten with
001 to 254 Ethernet/IP
the set value (192.168.1.XXX).
The network parameters are requested via DHCP/
255 to 298 Ethernet/IP
BOOTP, but are not saved.
The factory settings for the IP address are used
299 Ethernet/IP
(192.168.1.1).
300 to 399 PROFINET Network parameters are allocated via DCP.
Network parameters are allocated via the
400 to 499 EtherCAT
engineering tool.
900 to 999
– Invalid setting
(Exception: 979)
979 – Restoring factory settings

6 Commissioning with Ethernet/IP | Requirements
6 Commissioning with Ethernet/IP
WARNING! 6.2 Installing the EDS file

Manipulation of the controller! All of the module variants are described in files named
During commissioning, the system may be WM_xx_Vz_z_z_yyyymmdd.eds. (where xx stands
manipulated to such an extent that can result for the ten-digit module order number, z_z_z for the soft-
in risks to life and material damage. ware version, and yyyymmdd for the file issue date). All
▶▶ Make sure that system components can- EDS files are grouped together in an archive file named
not start up unintentionally! IP67_GSDML_EDS_ESI_Weidmueller.zip.
▶▶ Open the Studio 5000 software.

▶▶ Download and unpack the archive file from the Weidmül-
ler website.
CAUTION ▶▶ In the Tools menu within the Studio 5000 software,
select the EDS Hardware Installation Tool option
Hot surface!
▶▶ Follow the installation wizard.
The device can become very hot when in
operation.
▶▶ Allow the device to cool down before
touching it!
6.3 Connecting a module to the Ethernet/IP
The procedures applied during commissioning depend on
which fieldbus protocol has been chosen and which control- network
ler is being used.
▶▶ Open the Studio 5000 software.
The description in this section uses the commissioning of ▶▶ Create a new project or open an existing project.
Studio 5000 Logix Designer from Rockwell Automation in
online operation as an example. If the communication path for the controller is out-of-date or
has not been specified, this must be specified before estab-
lishing the first connection.
▶▶ Click on the Connections menu and select Who
Active.
▶▶ In the Who Active dialogue box, select the controller
6.1 Requirements used.
▶▶ Establish a connection to the controller (Go Online).
Before you start the commissioning work, the following re- If your project does not match the project on the controller,
quirements must be fulfilled. load your project onto the controller (Download) or transfer
–– The controller must be in operation. the project from the controller to Studio 5000 (Upload). The
–– The UR67 modules must be completely installed and controller must be in programming mode in both cases.
wired up.
–– The controller and all UR67 modules must be connected All projects downloaded from Studio 5000 to the
via Ethernet, and a PC/laptop must be likewise connected controller irrevocably overwrite any projects saved
using the controller software. on the controller.
–– The module must be set to Ethernet/IP with a unique IP
address using the rotary switch (see Section 5.8). ▶▶ Use the mouse to right-click on I/O Configuration/... in
–– The power supply must be turned on. the Controller Organiser or the Backplane subfolder.
▶▶ Click on Discover Modules.
The Select Module Type window opens.

6 Commissioning with Ethernet/IP | Connecting a module to the Ethernet/IP network
Selecting the Ethernet/IP interface Selecting the module
▶▶ Select the required Ethernet/IP interface and click on Cre- ▶▶ Select the required UR67-MP module and click on Cre-
ate. ate.
The New Module window opens. The New Module window opens.
Configuring the Ethernet/IP interface Entering the module name
▶▶ Enter a name for the interface and define the required IP ▶▶ Enter a name for the module.
address settings. ▶▶ Click on Change.
▶▶ Click on OK. The Module Definition window opens.
The Ethernet/IP interface is created in the Controller Or-
ganiser.
▶▶ In the Controller Organiser, right-click on Ethernet in

the Ethernet/IP interface that you have just created.
▶▶ Click on Discover Modules.
The Select Module Type window opens.

6 Commissioning with Ethernet/IP | Connections and assembly object
6.4 Connections and assembly object

The UR67 MP modules support the connection types Exclu-
sive Owner, Input Only and Listen Only.
Exclusive Owner
▶▶ Select the Exclusive Owner connection type for independ-
ent connections, which are to be used to transfer both
input and output data.
An Exclusive Owner connection is independent of all other
connections. A UR67-MP module can only accept an Exclu-
sive Owner connection.
The Exclusive Owner connection type is available solely for
modules with output functionality (UR67-MP-xx-16DO-12-
60M, UR67-MP-xx-8DIDO-12-60M, UR67-MP-xx-16DIO-12-
60M).
Selecting the connection type
Input Only
▶▶ Select the connection.
▶▶ Select the Input Only connection type for independent
The connection type determines which process connections which are to be used to solely transfer input
and diagnostic data is provided by the module data.
(see. Section 6.4). An Input Only connection is independent of all other connec-
tions. A UR67-MP module can accept multiple Input Only
connections.
The Input Only connection type is available for all modules.
▶▶ Click on OK. Listen Only

The Module Definition window is closed. ▶▶ Select the Listen Only connection type for dependent
connections which are to be used to solely transfer input
▶▶ Click on the Connections tab in the New Module win- data.
dow. A Listen Only connection is dependent on other connections
that are not of the Listen Only type. If the last connection on
which a Listen Only connection is dependent is terminated,
this Listen Only connection will likewise be terminated. A
UR67-MP module can accept multiple Listen Only connec-
tions.
The Listen Only connection type is available for all modules
Select the instance ID of the assembly object to decide

whether the module also adds diagnostic data to the process
data.
Connections tab
▶▶ Set the Requested Packet Interval (RPI) and the form of

communication (unicast or multicast) and confirm by
clicking on OK.
The RPI selected must be greater than 1 ms.

UR67-MP-xx-16DI-12-60M UR67-MP-xx-8DIDO-12-60M
Connection Diagnos- Connection Diagnos-
Connection Instance ID Length Connection Instance ID Length
type tics type tics
Input: 101 4 bytes Input: 101 6 bytes
16 Bit In + Dia Input Only yes Output: 193 0 bytes 8 Bit In / Out +Dia Exclusive Owner yes Output: 100 1 bytes
Configuration: 105 2 bytes Configuration: 105 34 bytes
16 Bit In Input Only no Output: 193 0 bytes 8 Bit In / Out Exclusive Owner no Output: 100 1 bytes
16 Bit In + Dia Listen Only yes Output: 192 0 bytes 8 Bit In / Out +Dia Input Only yes Output: 193 0 bytes
Configuration: – – Configuration: 105 34 bytes
16 Bit In Listen Only no Output: 192 0 bytes 8 Bit In / Out Input Only no Output: 193 0 bytes
Configuration: – – Configuration: 105 34 bytes
Input: 101 6 bytes
UR67-MP-xx-16DO-12-60M 8 Bit In / Out +Dia Listen Only yes Output: 192 0 bytes
Configuration: – –
Connection Diagnos-
Connection Instance ID Length
type tics Input: 102 3 bytes
Input: 101 7 bytes 8 Bit In / Out Listen Only no Output: 192 0 bytes
16 Bit Out + Dia Exclusive Owner yes Output: 100 2 bytes Configuration: – –
Configuration: 105 66 bytes
Input: 102 3 bytes
16 Bit Out Exclusive Owner no Output: 100 2 bytes
Input: 101 7 bytes
16 Bit Out + Dia Input Only yes Output: 193 0 bytes
Input: 102 3 bytes
16 Bit Out Input Only no Output: 193 0 bytes
Input: 101 7 bytes
16 Bit Out + Dia Listen Only yes Output: 192 0 bytes
Input: 102 3 bytes
16 Bit Out Listen Only no Output: 192 0 bytes

UR67-MP-xx-16DIO-12-60M 16DI module profiles

16DI/DO module profile Connection Diagnos-
Connection Diagnos- type tics
Connection Instance ID Length Input: 101 7 bytes
type tics
Input: 101 7 bytes 16DI + DIA Input Only yes Output: 193 0 bytes
16DI/DO + DIA Exclusive Owner yes Output: 100 2 bytes Configuration: 112 66 bytes
Configuration: 110 130 bytes Input: 102 3 bytes
Input: 102 3 bytes 16DI Input Only no Output: 193 0 bytes
16DI/DO Exclusive Owner no Output: 100 2 bytes Configuration: 112 66 bytes
Input: 108 8 bytes 8DI module profiles
16DI/DO + DIA
Exclusive Owner yes Output: 100 2 bytes Connection Diagnos-
(Even DI/DO bytes) Connection Instance ID Length
Configuration: 110 130 bytes type tics
16 DI/DO + DIA 8DI + DIA Input Only yes Output: 193 0 bytes
Exclusive Owner yes Output: 100 2 bytes
(Default Config)1
16DI/DO + DIA Input Only yes Output: 193 0 bytes 8DI Input Only no Output: 193 0 bytes
Input: 102 3 bytes
16DI/DO Input Only no Output: 193 0 bytes 16DO module profiles
Configuration: 110 130 bytes Connection Diagnos-
Input: 108 8 bytes type tics
16DI/DO + DIA Input: 106 5 bytes
Input Only yes Output: 193 0 bytes
(Even DI/DO bytes)
Configuration: 110 130 bytes 16DO + DIA Exclusive Owner yes Output: 100 2 bytes
1) No parameters are transferred with this connection. Configuration: 114 130 bytes
Input: 107 1 byte
16DO Exclusive Owner no Output: 100 2 bytes
8DI/DO module profile
Connection Diagnos-
type tics
Input: 104 6 bytes 8DO module profiles
8DI/DO + DIA Exclusive Owner yes Output: 103 1 bytes Connection Diagnos-
Configuration: 111 130 bytes type tics
8DI/DO Exclusive Owner no Output: 103 1 bytes 8DO + DIA Exclusive Owner yes Output: 103 1 bytes
Input: 104 6 bytes Input: 107 1 byte
8DI/DO + DIA Input Only yes Output: 193 0 bytes 8DO Exclusive Owner no Output: 103 1 byte
Input: 105 2 bytes
8DI/DO Input Only no Output: 193 0 bytes

6 Commissioning with Ethernet/IP | Initial connection parameter settings
8DI/8DO module profiles UR67-MP-xx16DI-12-60M with diagnostics

Connection Diagnos- General
type tics Transport type Input Only
Input: 104 6 bytes
Trigger mode Cyclic
8DI/8DO + DIA Exclusive Owner yes Output: 103 1 bytes
Requested Packet Interval (RPI) Minimum 1 ms
Output data (O➔T) connection parameters
Input: 105 2 bytes
Real-time transfer format Heartbeat
8DI/8DO Exclusive Owner no Output: 103 1 byte
Connection type POINT2POINT
Assembly instance ID 193
Input: 104 6 bytes
Data type USINT
8DI/8DO + DIA Input Only yes Output: 193 0 bytes
Data size 1 byte
Data length 0 bytes
Input: 105 2 bytes
Input data (T➔O) connection parameters
8DI/8DO Input Only no Output: 193 0 bytes
Real-time transfer format Connection is pure data and modeless
Connection type MULTICAST
Generic DI module profiles Data type USINT
Connection Diagnos- Data size 1 byte
type tics
Data length 4 bytes
Input: 101 7 bytes
Generic 16DI + DIA Listen Only yes Output: 192 0 bytes
UR67-MP-xx16DO-12-60M with diagnostics
Input: 102 3 bytes General
Generic 16DI Listen Only no Output: 192 0 bytes Transport type Exclusive Owner
Configuration: – – Trigger mode Cyclic
Input: 108 8 bytes Requested Packet Interval (RPI) Minimum 1 ms

Generic 16DI + DIA Output data (O➔T) connection parameters
Listen Only yes Output: 192 0 bytes
(Even DI/DO bytes)
Configuration: – – Real-time transfer format 32-bit run/idle header
Input: 104 6 bytes Connection type POINT2POINT
Generic 8DI + DIA Listen Only yes Output: 192 0 bytes Assembly instance ID 100
Configuration: – – Data type USINT
Input: 105 2 bytes Data size 1 byte
Generic 8DI Listen Only no Output: 192 0 bytes Data length 2 bytes
Configuration: – – Input data (T➔O) connection parameters

6.5 Initial connection parameter settings Data type USINT
The configuration tools produced by other controller manu- Data size 1 byte
facturers may also request that users enter other parameters Data length 7 bytes
in order to set up a communication connection between the
I/O scanner and the module.

6 Commissioning with Ethernet/IP | Parameterising the module with Ethernet/IP
UR67-MP-xx-8DIDO-12-60M with diagnostics 6.6 Parameterising the module with Ethernet/

General IP
Transport type Exclusive Owner
▶▶ In the Controller Organiser, switch to .../Controller Tags.
Trigger mode Cyclic
The controller tags for the parameters bear the name of the
Requested Packet Interval (RPI) Minimum 1 ms module, followed by ":C", the parameter name, the connec-
Output data (O➔T) connection parameters tion code and the PIN.
Real-time transfer format 32-bit run/idle header
Data type USINT
Data size 1 byte
Data length 1 byte
Data type USINT
Data size 1 byte
Data length 6 bytes
Controller tags
UR67-MP-xx16DIO-12-60M with 16DI/DO profile and diagnostics
General ▶▶ Enter the required parameter values for each output chan-
Transport type Exclusive Owner nel.
Trigger mode Cyclic
A detailed description of the individual parameters and their
Requested Packet Interval (RPI) Minimum 1 ms
availability can be found in Section 6.9 and Section 6.10.
Output data (O➔T) connection parameters
Real-time transfer format 32-bit run/idle header
Data type USINT
Data size 1 byte
Data length 2 bytes
Data type USINT
Data size 1 byte
Data length 7 bytes

6 Commissioning with Ethernet/IP | Parameterising the process data structure for 16DIO modules
6.7 Parameterising the process data structure The default setting and the permitted value range of the pa-
rameter depend on the selected module profile.
for 16DIO modules
Process Data Direction (default settings)
WARNING! Channel 16DI/DO 8DI/DO 16DI 8DI 16DO 8DO 8DI/8DO
Unexpected controller behaviour! 1-A 0 0 1 1 2 2 1
Actuators and sensors can be activated or de-
1-B 0 0 1 1 2 2 1
activated unintentionally when you incorrect-
ly parameterise the process data structure. 2-B 0 0 1 1 2 2 1
▶▶ Check the parameterised process data 2-B 0 0 1 1 2 2 1
structure before you transfer the parame- 3-A 0 0 1 1 2 2 1
ters to the device!
3-B 0 0 1 1 2 2 1
4-A 0 0 1 1 2 2 1
4-B 0 0 1 1 2 2 1
5-A 0 0 1 1 2 2 2
Parameterising the data direction of the channels 5-B 0 0 1 1 2 2 2
If you are using a UR67-MP-xx-16DIO-12-60M module, you 6-A 0 0 1 1 2 2 2
can parameterise the data direction of the individual chan- 6-B 0 0 1 1 2 2 2
nels.
7-A 0 0 1 1 2 2 2
▶▶ Select the module profile 16DI/DO if you are adding the 7-B 0 0 1 1 2 2 2
module for configuration. 8-A 0 0 1 1 2 2 2
8-B 0 0 1 1 2 2 2
If you want to parameterise the channel as a bi-directional
0: input and output, 1: only input, 2: only output
input and output:
▶▶ Set the “Process Data Direction” parameter of the associ-
ated channel to 0. Parameterising process data mapping
You can assign a position in the respective process data to
If you want to parameterise the channel as an input: each physical input bit and each physical output bit. For bi-di-
▶▶ Set the “Process Data Direction” parameter of the associ- rectional channels, the assignment applies in both the input
ated channel to 1. and the output direction.
If you want to parameterise the channel as an output: If you would like to assign a new bit position to the process
▶▶ Set the “Process Data Direction” parameter of the associ- data bits of a new channel:
ated channel to 2. ▶▶ Set the “IO Mapping” parameter of the associated chan-
nel to the required bit position.
If you want to deactivate the channel:

▶▶ Set the “IO Mapping” parameter of the associated chan-
nel to “255”.

6 Commissioning with Ethernet/IP | Setting up QuickConnect
The default setting and the permitted value range of the pa-
rameter depend on the selected module profile.
6.8 Setting up QuickConnect
With QuickConnect, there is less than 500 ms between
IO Mapping (default settings) switching on a device and establishing the Ethernet/IP com-
Channel 16DI/DO 8DI/DO 16DI 8DI 16DO 8DO 8DI/8DO munication.
1-A 0 0 0 0 0 0 0
To use QuickConnect, the following requirements must be
1-B 1 255 1 255 1 255 1 met:
2-B 2 1 2 1 2 1 2 –– The network must have a star topology or a line topology.
2-B 3 255 3 255 3 255 3 Ring topologies are not permitted.
–– The device must have a static IP address. DHCP/BOOTP is
3-A 4 2 4 2 4 2 4
not supported.
3-B 5 255 5 255 5 255 5
4-A 6 3 6 3 6 3 6 If you use QuickConnect, the following parameters for the
4-B 7 255 7 255 7 255 7 Ethernet interface are fixed and cannot be changed:
–– Transmission speed 100 Mbit/s.
5-A 8 4 8 4 8 4 0
–– Full duplex connection.
5-B 9 255 9 255 9 255 1 –– Autonegation deactivated.
6-A 10 5 10 5 10 5 2 –– Auto MDI-X deactivated.
6-B 11 255 11 255 11 255 3
You can activate QuickConnect via the configuration assem-
7-A 12 6 12 6 12 6 4
bly instance.
7-B 13 255 13 255 13 255 5 ▶▶ Set the QuickConnect parameter to 1.
8-A 14 7 14 7 14 7 6
8-B 15 255 15 255 15 255 7 Alternatively you can activate QuickConnect during runtime
0 to 15: bit position in the process data (input data or output data)
via the TCP/IP interface object. The change requires the de-
255: deactivated vice to be restarted.
–– CIP Class ID: 0xF5
–– Attributes: 0x0C
–– Value: 0x01
For details on QuickConnect, refer to document

ENET-AT001C-ENP from Rockwell Automation.
You can download the document from the Rock-
well Automation website.

6 Commissioning with Ethernet/IP | Configuration assembly instance
6.9 Configuration assembly instance UR67-MP-xx-8DIDO-12-60M (assembly ID 105)

Parameter Connection Channel Values
You can define the parameters with the configuration assem-
Word 0 Surveillance Timeout Connection 5 A (Pin 4) 0 to 255
bly instance. A detailed description of the individual param-
eters and their availability can be found in Section 6.10. Word 1 Surveillance Timeout Connection 5 B (Pin 2) 0 to 255
Structure of the configuration assembly instance ... ... ... ... ...
The structure and length of the configuration assembly
Word 5 Surveillance Timeout Connection 7 B (Pin 2) 0 to 255
instance depend on the module used or the module profile
used. Word 6 Surveillance Timeout Connection 8 A (Pin 4) 0 to 255
UR67-MP-xx-16DI-12-60M (assembly ID 105) Word 8 Fail Safe Connection 5 A (Pin 4) 0 to 2
Parameter Connection Channel Values Word 9 Fail Safe Connection 5 B (Pin 2) 0 to 2
Word 0 General Settings, QuickConnect – – see below Word 10 Fail Safe Connection 6 A (Pin 4) 0 to 2
... ... ... ... ...
Word 13 Fail Safe Connection 7 B (Pin 2) 0 to 2
UR67-MP-xx-16DO-12-60M (assembly ID 105)
Word 14 Fail Safe Connection 8 A (Pin 4) 0 to 2
Word 16 General Settings, QuickConnect – – see below
... ... ... ... ...
... ... ... ... ...
Word 32 General Settings, QuickConnect – – see below

UR67-MP-xx-16DIO-12-60M with module profile 16DI/DO UR67-MP-xx-16DIO-12-60M with module profile 8DI/DO
(assembly ID 110) (assembly ID 111)
Parameter Connection Channel Values Parameter Connection Channel Values
Word 0 Surveillance Timeout Connection 1 A (Pin 4) 0 to 255 Word 0 Surveillance Timeout Connection 1 A (Pin 4) 0 to 255
Word 1 Surveillance Timeout Connection 1 B (Pin 2) 0 to 255 Word 1 Surveillance Timeout Connection 1 B (Pin 2) 0 to 255
... ... ... ... ... ... ... ... ... ...
Word 16 Fail Safe Connection 1 A (Pin 4) 0 to 2 Word 16 Fail Safe Connection 1 A (Pin 4) 0 to 2
Word 17 Fail Safe Connection 1 B (Pin 2) 0 to 2 Word 17 Fail Safe Connection 1 B (Pin 2) 0 to 2
... ... ... ... ... ... ... ... ... ...
General Settings, General Settings,
Word 32 – – see below Word 32 – – see below
QuickConnect QuickConnect
Word 33 Process Data Direction Connection 1 A (Pin 4) 0 to 2 Word 33 Process Data Direction Connection 1 A (Pin 4) 0 to 2
Word 34 Process Data Direction Connection 1 B (Pin 2) 0 to 2 Word 34 Process Data Direction Connection 1 B (Pin 2) 0 to 2
... ... ... ... ... ... ... ... ... ...
Word 49 IO Mapping Connection 1 A (Pin 4) 0 to 15, 255 Word 49 IO Mapping Connection 1 A (Pin 4) 0 to 7, 255
Word 50 IO Mapping Connection 1 B (Pin 2) 0 to 15, 255 Word 50 IO Mapping Connection 1 B (Pin 2) 0 to 7, 255
... ... ... ... ... ... ... ... ... ...

UR67-MP-xx-16DIO-12-60M with module profile 16DI (assembly ID 112) UR67-MP-xx-16DIO-12-60M with module profile 16DO (assembly ID 114)
Parameter Connection Channel Values Parameter Connection Channel Values
General Settings, Word 0 Surveillance Timeout Connection 1 A (Pin 4) 0 to 255
Word 0 – – see below
QuickConnect
Word 1 Process Data Direction Connection 1 A (Pin 4) 1
Word 2 Process Data Direction Connection 1 B (Pin 2) 1
... ... ... ... ...
... ... ... ... ...
Word 17 IO Mapping Connection 1 A (Pin 4) 0 to 15, 255
Word 18 IO Mapping Connection 1 B (Pin 2) 0 to 15, 255
... ... ... ... ...
... ... ... ... ...
General Settings,
Word 32 IO Mapping Connection 8 B (Pin 2) 0 to 15, 255 Word 32 – – see below
QuickConnect
UR67-MP-xx-16DIO-12-60M with module profile 8DI (assembly ID 113) Word 34 Process Data Direction Connection 1 B (Pin 2) 2
General Settings, ... ... ... ... ...
Word 0 – – see below
QuickConnect Word 46 Process Data Direction Connection 7 B (Pin 2) 2
Word 1 Process Data Direction Connection 1 A (Pin 4) 1 Word 47 Process Data Direction Connection 8 A (Pin 4) 2
Word 2 Process Data Direction Connection 1 B (Pin 2) 1 Word 48 Process Data Direction Connection 8 B (Pin 2) 2
Word 3 Process Data Direction Connection 2 A (Pin 4) 1 Word 49 IO Mapping Connection 1 A (Pin 4) 0 to 15, 255
... ... ... ... ... Word 50 IO Mapping Connection 1 B (Pin 2) 0 to 15, 255
Word 14 Process Data Direction Connection 7 B (Pin 2) 1 Word 51 IO Mapping Connection 2 A (Pin 4) 0 to 15, 255
Word 15 Process Data Direction Connection 8 A (Pin 4) 1 ... ... ... ... ...
Word 16 Process Data Direction Connection 8 B (Pin 2) 1 Word 62 IO Mapping Connection 7 B (Pin 2) 0 to 15, 255
... ... ... ... ...

UR67-MP-xx-16DIO-12-60M with module profile 8DO (assembly ID 115) UR67-MP-xx-16DIO-12-60M with module profile 8DI/8DO (assembly ID
116)
... ... ... ... ...
... ... ... ... ...
... ... ... ... ...
... ... ... ... ...
General Settings,
Word 32 – – see below General Settings,
QuickConnect Word 32 – – see below
QuickConnect
Word 33 Process Data Direction Connection 1 A (Pin 4) 1 to 2
Word 34 Process Data Direction Connection 1 B (Pin 2) 1 to 2
... ... ... ... ...
... ... ... ... ...
... ... ... ... ...
... ... ... ... ...

6 Commissioning with Ethernet/IP | Adjustable parameters with Ethernet/IP
False (0)
General Settings parameter and QuickConnect parameter
The web server application is not locked.
General Settings, QuickConnect
True (1)
MSB LSB
The web server application is locked.
Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
– DOR – – RDO RUL WIL FML QuickConnect (values: 0, 1)
“Force Mode Locked” parameter
This parameter can be used to lock the force mode on the
Abbreviation Meaning
web server application.
DOR Digital Out Restart Mode
False (0)
RDO Report DO Fault without UL
The force mode of the web server application is not locked.
RUL Report UL Supply Voltage Fault
True (1)
WIL Web Interface Locked
The force mode of the web server application is locked.
FML Force Mode Locked
“Quick Connect” parameter

This parameter activates QuickConnect.
6.10 Adjustable parameters with Ethernet/IP False (0)
QuickConnect is deactivated.
“Digital-Out Restart Mode” parameter True (1)
This parameter defines the behaviour of the outputs follow- QuickConnect is activated.
ing a channel error or an actuator supply error.
False (0)
Channel diagnostics is reset after an output reset.
“Surveillance Timeout” parameter
This parameter is used to set the delay time for output moni-
True (1) toring. The delay time starts after the state of the output has
The output automatically restarts after a failure/error. been changed. Once this period of time has expired, the out-
put is monitored and error states are reported as diagnoses.
If the output is permanently switched on or off, the monitor-
“Report DO Fault without UL” parameter ing time is 100 ms.
Diagnostics can be activated or deactivated via this param-
0 to255 (default: 80)
eter for controlling an output and defective actuator supply.
The monitoring of the output begins with 0 to255 ms follow-
False (0) ing the change of a channel state.
The diagnostics are deactivated.
True (1) “Fail Safe” parameter
The diagnostics are activated. This parameter is used to set the behaviour of the associated
output in the event of disrupted fieldbus communication.
Set Low (0)
“Report UL Supply Voltage Fault” parameter The output is inactive in the event of disrupted fieldbus com-
Diagnostics can be activated via this parameter as a result of
munication.
an actuator supply fault.
Set High (1)
False (0)
The output is active in the event of disrupted fieldbus com-
munication.
True (1)
Hold Last (2)
The diagnostics are activated.
The output is held at the last value in the event of disrupted
fieldbus communication.
“Web Interface Locked” parameter
This parameter can be used to lock the web server applica-
tion.

6 Commissioning with Ethernet/IP | Adjustable parameters with Ethernet/IP
“Process Data Direction” parameter

This parameter is used to set the data direction of the chan-
nel.
Input/Output (0)
The channel functions as a bi-directional input and output.
Input (1)
The channel functions as an input.
Output (2)
The channel functions as an output.
“IO Mapping” parameter

This parameter is used to set the position of the physical pro-
cess data bits of the channel in the process data telegrams.
For bi-directional channels, the assignment applies in both
the input and the output direction.
0 to 15
The physical process data bit of the channel is in position
0 to 15 of the process data.
255
The channel is deactivated.

7 Commissioning with PROFINET | Requirements
7 Commissioning with PROFINET
WARNING! 7.2 Installing a GSDML file

Manipulation of the controller! The naming convention for GSDML files always follows this
During commissioning, the system may be pattern: GSDML_V2.33-WI-UR67-yyyymmdd.xml. The date
manipulated to such an extent that can result in the file name (dd.mm.yyyy) indicates the version of the
in risks to life and material damage. GSDML file and helps to determine whether you are already
▶▶ Make sure that system components can- using the latest version.
not start up unintentionally!
▶▶ Download the files describing the device from the Wei-
dmüller website.
▶▶ Store the supplied bitmap files for visualising
the modules in the same folder as the
CAUTION GSDML file.
Hot surface!
The device can become very hot when in Projects must not be open in the hardware
operation. configuration tool while the GSDML file is being
▶▶ Allow the device to cool down before installed!
touching it! ▶▶ Close any open projects before installing the
GSDML files!
The procedures applied during commissioning depend on
which fieldbus protocol has been chosen and which control- ▶▶ Start SIMATIC Manager.
ler is being used. ▶▶ In the hardware configuration tool, navigate to Options/
Install GSD File.
The description in this section uses commissioning with the ▶▶ Select the directory in which you have stored the file
Siemens SIMATIC Manager Step7 as an example. (V5.5 SP2 describing the device.
and higher). The available files are displayed.
7.1 Requirements
Before you start the commissioning work, the following re-
quirements must be fulfilled:
–– The controller must be in operation.
–– The UR67 modules must be completely installed and
wired up.
–– The controller and all UR67 modules must be connected
via Ethernet, and a PC/laptop must be likewise connected
using the controller software.
–– The module must be set to PROFINET using the rotary
switch (see Section 5.8).
–– The power supply must be turned on.
Selecting the GSDML file
▶▶ Select the file that you would like to install.

▶▶ Click on Install.
▶▶ When the installation is complete, click on Close.
▶▶ Update the device catalogue via Options/Update Cata-
log.
The UR67 MP modules associated with the current file de-
scribing the device are now listed in the device catalogue.

7 Commissioning with PROFINET | Connecting a module to the PROFINET network
7.3 Connecting a module to the PROFINET

network
▶▶ To set up a new project, click on File/New in SIMATIC
Manager.
The “New Project” window opens.
▶▶ Enter a name for the new project (e.g. UR67_Station1)

and click on OK.
The new project is displayed in SIMATIC Manager.
Hardware configurator
▶▶ The device catalogue is displayed on the right-hand side

of this window. If this does not occur, open the catalogue
via View/Catalog.
▶▶ In the device catalogue, select the mounting rail in use

(e.g. SIMATIC 300/RACK-300).
Creating a new project
▶▶ Select the project in SIMATIC Manager.

▶▶ Select the controller type via Insert/Station (e.g.
SIMATIC 300).
Selecting a mounting rail
▶▶ Double-click on the mounting rail or drag it to the left-

hand side of the window using the mouse.
The mounting rail (UR) is displayed with the open positions.
Inserting a station
▶▶ Double-click on the project name so that the station

(SIMATIC 300) is displayed below in the directory tree.
▶▶ Click on the station (SIMATIC 300).
▶▶ Double-click Hardware on the right-hand side of the win-
dow.
The hardware configuration tool (HW Config) opens.

7 Commissioning with PROFINET | Connecting a module to the PROFINET network
Mounting rail with open positions
▶▶ Click on the second line of the UR table.

▶▶ From the catalogue, select the controller in use and its
version (inscription on the controller, e.g. 314-GEH04-...). Ethernet interface properties
▶▶ Enter the designated IP address and the subnet mask for

the controller.
▶▶ Click on New.
The Properties – New subnet Industrial Ethernet win-
dow opens.
▶▶ Enter a name for the subnet and confirm by clicking on

OK.
▶▶ Select the new subnet in the Properties – Ethernet
interface window and confirm by clicking on OK.
▶▶ Click on the network line in the configuration window.

▶▶ In the device catalogue, select the module under PROFI-
NET IO/Other field devices/ I/O /WI UR67.
Selecting the controller version ▶▶ Double-click on the module or drag it to the exact subnet
line.
▶▶ Double-click on the respective version, or use the mouse The module is inserted in the subnet.
to drag it to the second position in the table on the left-
hand side of the window.
The Properties - Ethernet interface window opens.
Connecting the UR67-MP module

7 Commissioning with PROFINET | Changing the module profile for 16DIO modules
7.4 Changing the module profile for 16DIO 7.6 Parameterising process data mapping with
modules 16DIO modules
If you are using a UR67-MP-xx-16DIO-12-60M module, you You can assign a position in the respective process data to
can select different module profiles. A module profile deter- each physical input bit and each physical output bit. For bi-di-
mines the input and output functionality of the module. rectional channels, the assignment applies in both the input
and the output direction.
▶▶ Delete the submodule in plug-in station 1.
▶▶ Insert the required module profile from the hardware cat- If you would like to assign a new bit position to the process
alogue in plug-in station 1. data bits of a new channel:
▶▶ Set the “IO Mapping Configuration” parameter of the
associated channel to the required bit position.
7.5 Parameterising the module with PROFINET If you want to deactivate the channel:
▶▶ In the hardware configuration tool, double-click on plug-in associated channel to “Not used”.
station 0.
The Properties... window opens. The default setting of the parameter depends on the selected
▶▶ Select the Parameters tab. module profile.
A list of all module parameters is displayed.
IO Mapping Configuration (default settings)

Channel 16DI/DO 8DI/DO 16DI 8DI 16DO 8DO 8DI/8DO
1-A IQ 0.0 IQ 0.0 I 0.0 I 0.0 Q 0.0 Q 0.0 I 0.0

1-B IQ 0.1 – I 0.1 – Q 0.1 – I 0.1
2-B IQ 0.2 IQ 0.1 I 0.2 I 0.1 Q 0.2 Q 0.1 I 0.2
2-B IQ 0.3 – I 0.3 – Q 0.3 – I 0.3
3-A IQ 0.4 IQ 0.2 I 0.4 I 0.2 Q 0.4 Q 0.2 I 0.4
3-B IQ 0.5 – I 0.5 – Q 0.5 – I 0.5
4-A IQ 0.6 IQ 0.3 I 0.6 I 0.3 Q 0.6 Q 0.3 I 0.6
4-B IQ 0.7 – I 0.7 – Q 0.7 – I 0.7
5-A IQ 1.0 IQ 0.4 I 1.0 I 0.4 Q 1.0 Q 0.5 Q 0.0
5-B IQ 1.1 – I 1.1 – Q 1.1 – Q 0.1
Parameterising the module 6-A IQ 1.2 IQ 0.5 I 1.2 I 0.5 Q 1.2 Q 0.4 Q 0.2
6-B IQ 1.3 – I 1.3 – Q 1.3 – Q 0.3
▶▶ Click on the parameter that you would like to change and 7-A IQ 1.4 IQ 0.6 I 1.4 I 0.6 Q 1.4 Q 0.6 Q 0.4
amend the setting as required.
▶▶ Use this method to edit all of the parameters that you 7-B IQ 1.5 – I 1.5 – Q 1.5 – Q 0.5
would like to change. 8-A IQ 1.6 IQ 0.7 I 1.6 I 0.7 Q 1.6 Q 0.7 Q 0.6
▶▶ Save the settings by clicking on OK. 8-B IQ 1.7 – I 1.7 – Q 1.7 – Q 0.7
I X.Y: byte X, bit Y of input data
A detailed description of the individual parameters and their Q X.Y: byte X, bit Y of output data
availability can be found in Section 7.15. IQ X.Y: byte X, bit Y of input data and output data
– : deactivated
All settings only take effect once they have been
loaded into the component/controller.

7 Commissioning with PROFINET | Assigning an IP address to a module
7.7 Assigning an IP address to a module

You can assign an IP address to a module in order to access
the web server, for example.
▶ In the device manager select PLC/Ethernet/Edit

Ethernet node.
Entering an IP address and subnet mask
These settings are sent directly to the devices.
Editing Ethernet nodes
▶ Enter the MAC address of the module or click on Browse

to look for all connected nodes.
The MAC address is printed on the module.
7.8 Viewing and changing device names
▶ Select the required module and click on OK.
PROFINET devices are addressed in PROFINET via a unique
The MAC address of the module will appear in the MAC ad- device name. These names can be freely assigned; however,
dress field. they can only be used once in the network.
▶ Compare the MAC address with the MAC address on the
module. ▶ Double-click on the module.
The Properties... window opens.
▶ Select Use IP parameters.
▶ Enter the required IP address and subnet mask.
▶ Click on Assign IP Configuration.

7 Commissioning with PROFINET | Assigning a device name to a UR67-MP module
Assigning a device name
▶▶ Select the UR67-MP module required.

Module properties ▶▶ Click on Assign Name.
▶▶ Close the dialogue box.
The device name must match the name that has
been assigned to the module.
7.10 Setting up fast start-up

▶▶ Change the device names as required.
▶▶ Check whether the displayed IP address is correct and With fast start-up, there is less than 500 ms between switch-
whether the controller and module are in the same Ether- ing on a device and the first exchange of process data.
net subnet.
▶▶ Confirm the settings by clicking OK. The device must be connected to the PROFINET network to
set up fast start-up.
All settings only take effect once they have been
loaded into the component/controller.
Activate fast start-up for the module:
▶▶ In the hardware configuration tool, double-click on plug-in
station X1.
▶▶ Select the General tab.
▶▶ Activate prioritised start-up.
▶▶ Confirm the settings by clicking on OK.
7.9 Assigning a device name to a UR67-MP
module Parameterise the fieldbus connections:
▶▶ In the hardware configuration tool, double-click on plug-in
To assign a device name to a module, the PC must be con- station X1P1.
nected to the module via a PROFINET connection. ▶▶ Select the Options tab.
▶▶ Select the module. ▶▶ Under Transmission medium / duplex, select TP
▶▶ Open the dialogue box PLC/Ethernet/Assign device 100 Mbps full duplex.
name. ▶▶ Activate Disable autonegation.
▶▶ Repeat the procedure for plug-in station X1P2.
For devices that are connected to the module via
the fieldbus connections, autonegation must also
be disabled and 100 Mbps full duplex must be
activated.

7 Commissioning with PROFINET | Configuring the topology
7.11 Configuring the topology ▶▶ Activate Support device exchange without interchangea-
ble medium and close the window by clicking on OK.
The PROFINET network topology must be configured. Plan
the connection of the PROFINET port for the individual de-
vices.
▶▶ In the hardware configuration tool, double click on the 7.13 Setting up MRP
PROFINET port of a device whose connection you want
to configure. With the UR67-MP modules, redundant PROFINET commu-
▶▶ Switch to the Topology tab. nication can be achieved with a ring topology and no need
▶▶ In the Partner Port menu, select the port for the neigh- for additional switches. In this instance, an MRP redundancy
bouring device and confirm by clicking on OK. manager closes the ring, detects individual outages and
▶▶ Repeat this process until all of the connections have been sends data packages via the redundant path in the event of
configured. an error.
Alternatively, you can configure the topology using the
SIMATIC Topology Editor. To use MRP, the following requirements must be met:
–– All devices must support MRP.
–– The devices must only be connected via the ring ports – a
meshed topology is not permitted.
–– The ring must contain a maximum of 50 devices.
7.12 Setting up device replacement without –– All of the devices must have the same redundancy
interchangeable medium/PG domains.
–– A prioritised start-up (PSU) is not permitted.
The UR67-MP modules support the “Device replacement –– The automatic network setting must be used on all
without interchangeable medium/PG” function. Modules in a devices.
PROFINET network can be exchanged for identical modules
without having to reassign the device name using a program- Configure a device as a redundancy manager:
ming device. The IO controllerassigns the exchanged module ▶▶ In the hardware configuration tool, double click on the
the device name based on the configured topology and the PROFINET port of a device that you want to configure as
real neighbour relationships determined by the IO devices. a redundancy manager.
▶▶ Switch to the Media redundancy tab.
The “Device replacement without interchangeable medium/ ▶▶ In the Domain menu, select the required redundancy
PG” function can be used if the following requirements are domains.
met: ▶▶ In the Role menu, select the Manager (Auto) option.
–– The IO controller must support “Device replacement with- ▶▶ In the Ring port 1 and Ring port 2 menus, select the
out interchangeable medium/PG”. ring ports.
–– The neighbouring PROFINET devices of the module to be ▶▶ Switch to the IO cycle tab.
exchanged must support the “Device replacement with- ▶▶ Set the update time.
out interchangeable medium/PG” function. ▶▶ Set the response monitoring time. The response monitor-
–– The function must be activated for the IO controller. ing time must be longer than the reconfiguration time
–– The PROFINET network topology must be configured. (typically 200 ms).
–– The substitute device must be set to the factory settings. ▶▶ Confirm the settings by clicking on OK.
If the user intends to use the “Device replacement Configure all other devices as redundancy clients:
without interchangeable medium/PG” function, ▶▶ In the hardware configuration tool, double click on the
the substitute device must be reset to its factory PROFINET port of a device that you want to configure as
settings before being swapped in. a redundancy client.
▶▶ Switch to the Media redundancy tab.
▶▶ In the Domain menu, select the redundancy domain for
You can configure “Device replacement without interchange- the redundancy manager.
able medium/PG” in STEP 7. ▶▶ In the Role menu, select the Client option.
▶▶ Switch to the IO cycle tab.
▶▶ In the hardware configuration tool, double-click on the ▶▶ Set the update time.
PROFINET IO port (PN-IO) for the controller in order to
open the Properties – PN-IO... window.

7 Commissioning with PROFINET | Simple Network Management Protocol (SNMP)
▶▶ Set the response monitoring time. The response monitor-

“Force mode” parameter
ing time must be longer than the reconfiguration time
This parameter can be used to lock the force mode on the
(typically 200 ms).
web server application.
▶▶ Confirm the settings by clicking on OK.
▶▶ Repeat the procedure for all devices in the ring. Enabled
Disabled
7.14 Simple Network Management Protocol
(SNMP) “Web interface” parameter
The UR67 MP modules support the objects listed in the This parameter can be used to lock the web server applica-
PROFINET specification in accordance with the SNMP v1 tion.
protocol standard. This includes objects from RFC 1213 MIB- Enabled
II (system group and interfaces group) and from LLDP-MIB. The web server application is not locked.
The community strings are: Disabled

–– Read Community: public The web server application is locked.
–– Write Community: private
“Digital-Out Restart Mode” parameter
This parameter defines the behaviour of the outputs follow-
7.15 Adjustable parameters with PROFINET ing a channel error or an actuator supply error.
Automatic Restart after Failure
The output automatically restarts after a failure/error.
“Report Alarms” parameter
Diagnostics can be activated via this parameter. Restart after Output Reset
Channel diagnostics is reset after an output reset.
On
Off “Fail Safe” parameter
The diagnostics are deactivated. This parameter is used to set the behaviour of the associated
Set Low
“Report Alarm UL” parameter The output is inactive in the event of disrupted fieldbus com-
Diagnostics can be activated via this parameter as a result of
munication.
an actuator supply fault.
Set High
Enabled
The output is active in the event of disrupted fieldbus com-
munication.
Disabled
Hold Last
The output is held at the last value in the event of disrupted
fieldbus communication.
Parameter “Report UL Supply Voltage Fault”
Diagnostics can be activated or deactivated via this param-
eter for controlling an output and defective actuator supply.
On
Off

7 Commissioning with PROFINET | Adjustable parameters with PROFINET
“Surveillance Timeout Configuration” parameter

This parameter is used to set the delay time for output moni-
toring. The delay time starts after the state of the output has
been changed. Once this period of time has expired, the out-
ing time is 100 ms.
0 to255 (default: 80)
The monitoring of the output begins with 0 to255 ms follow-
ing the change of a channel state.
“IO Mapping Configuration” parameter

cess data bits of the channel in the process data.
IN Byte 0 to 1 / Bit 0 to 7
The physical input bit of the channel is in Byte 0 to 1 Bit
0 to 7 of the associated process input data.
OUT Byte 0 to 1 / Bit 0 to 7
The physical output bit of the channel is in Byte 0 to 1 Bit
0 to 7 of the process output data.
IN/OUT Byte 0 to 1 / Bit 0 to 7
The physical process data bit of the channel is in Byte 0 to 1
Bit 0 to 7 of the process data.
Not used

8 Commissioning with EtherCAT | Requirements
8 Commissioning with EtherCAT
The UR67-MP modules will now be available in the hard-

WARNING! ware catalogue.
Manipulation of the controller!
During commissioning, the system may be
manipulated to such an extent that can result
in risks to life and material damage. 8.3 Connecting a module to the EtherCAT
▶▶ Make sure that system components can-
not start up unintentionally! network
▶▶ Open TwinCAT 3.
▶▶ Create a new project.
▶▶ Switch to Solution Explorer.
▶▶ Under I/O, right-click on Devices.
CAUTION ▶▶ Select Scan...
Hot surface! An EtherCAT master will be added. You may need to choose
The device can become very hot when in from several devices.
operation. ▶▶ Right-click on the EtherCAT master.
▶▶ Allow the device to cool down before ▶▶ Select Scan...
touching it! The UR67 MP module will be added. You may need to
choose from several devices.
The procedures applied during commissioning depend on The EtherCAT station alias of the module is set
which fieldbus protocol has been chosen and which control- to 0 in the factory settings. For TwinCAT, it is not
ler is being used. used by default.
If you are using the configuration software of a
The description in this section uses the commissioning of different manufacturer, you may need to assign a
TwinCAT 3 from Beckhoff Automation as an example. separate EtherCAT station alias to each module
before commissioning. The station alias will be
permanently stored in the module until the next
factory reset. Please observe the instructions of
the controller manufacturer.
8.1 Requirements
Before you start the commissioning work, the following re- If you add a UR67-MP-xx-16DIO-12-60M module:
quirements must be fulfilled. ▶▶ Select the required module profile in the Select Box dia-
–– The controller must be in operation. logue box.
–– The UR67 modules must be completely installed and
wired up.
–– The controller and UR67 module must be connected via
Ethernet, and a PC/laptop must also be connected.
–– The module must be set to EtherCAT using the rotary
switch (see Section 5.8).
–– The power supply must be turned on.
Select module profile

8.2 Installing an ESI file
▶▶ Download and unzip the archive file from the Weidmüller
website.
▶▶ Copy the ESI file into the TwinCAT installation folder
(e.g. C:\TwinCAT\3.1\Config\Io\EtherCAT)
▶▶ Restart TwinCAT.

8 Commissioning with EtherCAT | Setting an IP address for EoE protocols
Advanced Settings dialogue box
8.5 Selecting Process Data

Adding a module in Solution Explorer ▶▶ Switch to Process Data.
▶▶ In the Sync Manager field, select Inputs.
▶▶ In the PDO Assignment field, select the required PDOs
for input data.
▶▶ In the Sync Manager field, select Outputs.
8.4 Setting an IP address for EoE protocols ▶▶ In the PDO Assignment field, select the required PDOs
for output data.
To use the web server function, an IP address must be set for A detailed description of the individual PDOs can be found in
the module. Section 11.
▶▶ Switch to EtherCAT.
▶▶ Click on Advanced Settings.
The Advanced Settings dialogue box will open.
▶▶ Click on Mailbox/EoE.
▶▶ Select Virtual Ethernet Port.
▶▶ Select IP Port.
▶▶ Select IP Address.
▶▶ Enter the required network parameters in the fields.
▶▶ Click on OK to close the dialogue box.
You can now use the web server function.
You may need to install an Ethernet loopback
adapter on the host system of TwinCAT runtime.
Please observe the instructions of the controller
manufacturer.
The modules are set to DHCP at the factory.
Process Data tab

8 Commissioning with EtherCAT | Parameterising a module with EtherCAT
8.6 Parameterising a module with EtherCAT 8.7 Parameterising the process data structure
▶▶ Switch to Startup.
for 16DIO modules
The current parameter setting is displayed.
WARNING!
Unexpected controller behaviour!
Actuators and sensors can be activated or de-
activated unintentionally when you incorrect-
ly parameterise the process data structure.
▶▶ Check the parameterised process data
structure before you transfer the parame-
ters to the device!
Parameterising the data direction of the channels

If you are using a UR67-MP-xx-16DIO-12-60M module, you
can parameterise the data direction of the individual chan-
nels.
Startup tab
▶▶ Select the module profile 16DI/DO if you are adding the
You can edit the parameter setting. module for configuration.
▶▶ Double-click on the parameter you want to edit.
The Edit dialogue box will open. If you want to parameterise the channel as a bi-directional
▶▶ Enter a new value for the parameter in the Data field. input and output:
▶▶ Set the “IO Direction Configuration” parameter of the
associated channel to “0”.
If you want to parameterise the channel as an input:

If you want to parameterise the channel as an output:

The default setting of the parameter depends on the selected

module profile.
Edit CANopen startup entry dialogue box
Service Data Objects (SDO) can only be written

during startup. SDOs can not be written during
operation.

8 Commissioning with EtherCAT | Parameterising the process data structure for 16DIO modules
IO Direction Configuration (default settings) IO Mapping Configuration (default settings)

Index (bit) Channel 16DI/DO 8DI/DO 16DI 8DI 16DO 8DO 8DI/8DO Index (bit) Channel 16DI/DO 8DI/DO 16DI 8DI 16DO 8DO 8DI/8DO
0x2303:01 1-A 0 0 1 1 2 2 1 0x2304:01 1-A 0 0 0 0 0 0 0

0x2303:02 1-B 0 0 1 1 2 2 1 0x2304:02 1-B 1 255 1 255 1 255 1
0x2303:03 2-B 0 0 1 1 2 2 1 0x2304:03 2-B 2 1 2 1 2 1 2
0x2303:04 2-B 0 0 1 1 2 2 1 0x2304:04 2-B 3 255 3 255 3 255 3
0x2303:05 3-A 0 0 1 1 2 2 1 0x2304:05 3-A 4 2 4 2 4 2 4
0x2303:06 3-B 0 0 1 1 2 2 1 0x2304:06 3-B 5 255 5 255 5 255 5
0x2303:07 4-A 0 0 1 1 2 2 1 0x2304:07 4-A 6 3 6 3 6 3 6
0x2303:08 4-B 0 0 1 1 2 2 1 0x2304:08 4-B 7 255 7 255 7 255 7
0x2303:09 5-A 0 0 1 1 2 2 2 0x2304:09 5-A 8 4 8 4 8 4 0
0x2303:0A 5-B 0 0 1 1 2 2 2 0x2304:0A 5-B 9 255 9 255 9 255 1
0x2303:0B 6-A 0 0 1 1 2 2 2 0x2304:0B 6-A 10 5 10 5 10 5 2
0x2303:0C 6-B 0 0 1 1 2 2 2 0x2304:0C 6-B 11 255 11 255 11 255 3
0x2303:0D 7-A 0 0 1 1 2 2 2 0x2304:0D 7-A 12 6 12 6 12 6 4
0x2303:0E 7-B 0 0 1 1 2 2 2 0x2304:0E 7-B 13 255 13 255 13 255 5
0x2303:0F 8-A 0 0 1 1 2 2 2 0x2304:0F 8-A 14 7 14 7 14 7 6
0x2303:10 8-B 0 0 1 1 2 2 2 0x2304:10 8-B 15 255 15 255 15 255 7
0: input and output, 1: only input, 2: only output 0 to15: bit position in the process data telegram (input data or output data)
255: deactivated
Parameterising process data mapping

You can assign a position in the respective process data to
each physical input bit and each physical output bit. For bi-di-
rectional channels, the assignment applies in both the input
and the output direction.
If you would like to assign a new bit position to the process

data bits of a new channel:
associated channel to the required bit position.
If you want to deactivate the channel:

The default setting of the parameter depends on the selected

module profile.

8 Commissioning with EtherCAT | Firmware updates with FoE
8.8 Firmware updates with FoE 8.9 Adjustable parameters with EtherCAT
Firmware updates with FoE are possible under the following
conditions: Parameters: module settings
–– The controller supports FoE.
Index (bit) Parameter Values
–– FoE is set up.
–– The module is in pre-op status. 0x2300:01 Web Interface Locked 0 = false, 1 = true
0x2300:02 Force Mode Locked 0 = false, 1 = true
▶▶ Download the latest firmware from the Weidmüller web-
0x2300:03 Disable All Emergency Messages 0 = false, 1 = true
site.
0x2300:04 Disable UL Emergency Messages 0 = false, 1 = true
You can launch the firmware update from TwinCAT 3. 0x2300:05 Disable Actuator Emergency Messages 0 = false, 1 = true
0x2300:06 –
▶▶ Switch to Online.
0x2300:07 Automatic Output Restart After Failure 0 = false, 1 = true
▶▶ In the File Access over EtherCAT field, click on Down-
load.
▶▶ Select the firmware update from Weidmüller. Parameters: UR67-MP-xx-16DO-12-60M
▶▶ Check that the file name in the String field has the cor-
Index (bit) Parameter Connection Channel Values
rect file extension and add the file extension .zip if neces-
sary. 0x2301:01 Surveillance Timeout Connection 1 A (Pin 4) 0 to 255
▶▶ Click on OK to transfer the file. 0x2301:02 Surveillance Timeout Connection 1 B (Pin 2) 0 to 255
▶▶ Once the file has been successfully transferred, restart 0x2301:03 Surveillance Timeout Connection 2 A (Pin 4) 0 to 255
the module to install the firmware update.
... ... ... ... ...
Once restarted, the update file will be unzipped and the old 0x2301:0E Surveillance Timeout Connection 7 B (Pin 2) 0 to 255
firmware will be replaced by the new version. During the up- 0x2301:0F Surveillance Timeout Connection 8 A (Pin 4) 0 to 255
date, the unlabelled LED will flash red. 0x2301:10 Surveillance Timeout Connection 8 B (Pin 2) 0 to 255
Following the successful installation, the US and UL LEDs will
0x2302:01 Fail Safe Connection 1 A (Pin 4) 0 to 2
flash green twice. The module will then restart to complete
the firmware update. 0x2302:02 Fail Safe Connection 1 B (Pin 2) 0 to 2
0x2302:03 Fail Safe Connection 2 A (Pin 4) 0 to 2
... ... ... ... ...
0x2302:0E Fail Safe Connection 7 B (Pin 2) 0 to 2
0x2302:0F Fail Safe Connection 8 A (Pin 4) 0 to 2
0x2302:10 Fail Safe Connection 8 B (Pin 2) 0 to 2

8 Commissioning with EtherCAT | Adjustable parameters with EtherCAT
Parameters: UR67-MP-xx-8DIDO-12-60M Parameters: UR67-MP-xx-16DIO-12-60M

Index (bit) Parameter Connection Channel Values Index (bit) Parameter Connection Channel Values
0x2301:01 Surveillance Timeout Connection 5 A (Pin 4) 0 to 255 0x2301:01 Surveillance Timeout Connection 1 A (Pin 4) 0 to 255
0x2301:02 Surveillance Timeout Connection 5 B (Pin 2) 0 to 255 0x2301:02 Surveillance Timeout Connection 1 B (Pin 2) 0 to 255
0x2301:03 Surveillance Timeout Connection 6 A (Pin 4) 0 to 255 0x2301:03 Surveillance Timeout Connection 2 A (Pin 4) 0 to 255
... ... ... ... ... ... ... ... ... ...
0x2301:06 Surveillance Timeout Connection 7 B (Pin 2) 0 to 255 0x2301:0E Surveillance Timeout Connection 7 B (Pin 2) 0 to 255
0x2301:07 Surveillance Timeout Connection 8 A (Pin 4) 0 to 255 0x2301:0F Surveillance Timeout Connection 8 A (Pin 4) 0 to 255
0x2301:08 Surveillance Timeout Connection 8 B (Pin 2) 0 to 255 0x2301:10 Surveillance Timeout Connection 8 B (Pin 2) 0 to 255
0x2302:01 Fail Safe Connection 5 A (Pin 4) 0 to 2 0x2302:01 Fail Safe Connection 1 A (Pin 4) 0 to 2
0x2302:02 Fail Safe Connection 5 B (Pin 2) 0 to 2 0x2302:02 Fail Safe Connection 1 B (Pin 2) 0 to 2
0x2302:03 Fail Safe Connection 6 A (Pin 4) 0 to 2 0x2302:03 Fail Safe Connection 2 A (Pin 4) 0 to 2
... ... ... ... ... ... ... ... ... ...
0x2302:06 Fail Safe Connection 7 B (Pin 2) 0 to 2 0x2302:0E Fail Safe Connection 7 B (Pin 2) 0 to 2
0x2302:07 Fail Safe Connection 8 A (Pin 4) 0 to 2 0x2302:0F Fail Safe Connection 8 A (Pin 4) 0 to 2
0x2302:08 Fail Safe Connection 8 B (Pin 2) 0 to 2 0x2302:10 Fail Safe Connection 8 B (Pin 2) 0 to 2
0x2303:01 IO Direction Configuration Connection 1 A (Pin 4) 0 to 2
0x2303:02 IO Direction Configuration Connection 1 B (Pin 2) 0 to 2
0x2303:03 IO Direction Configuration Connection 2 A (Pin 4) 0 to 2
... ... ... ... ...
0x2303:0E IO Direction Configuration Connection 7 B (Pin 2) 0 to 2
0x2303:0F IO Direction Configuration Connection 8 A (Pin 4) 0 to 2
0x2303:10 IO Direction Configuration Connection 8 B (Pin 2) 0 to 2
0 to 15,
0x2304:01 IO Mapping Configuration Connection 1 A (Pin 4)
255
0 to 15,
0x2304:02 IO Mapping Configuration Connection 1 B (Pin 2)
255
0 to 15,
0x2304:03 IO Mapping Configuration Connection 2 A (Pin 4)
255
... ... ... ... ...
0 to 15,
0x2304:0E IO Mapping Configuration Connection 7 B (Pin 2)
255
0 to 15,
0x2304:0F IO Mapping Configuration Connection 8 A (Pin 4)
255
0 to 15,
0x2304:10 IO Mapping Configuration Connection 8 B (Pin 2)
255
The “Timeout” and “Fail Safe” parameters are

only available for output channels. Observe the
parameterised data direction of the channel.

“Web Interface Locked” parameter “Automatic Output Restart After Failure” parameter
This parameter can be used to lock the web server applica- This parameter defines the behaviour of the outputs follow-
tion. ing a channel error or an actuator supply error.
False (0) False (0)
The web server application is not locked. The output remains inactive after an error.
True (1) True (1)
The web server application is locked. The output automatically restarts after a failure/error.
“Force Mode Locked” parameter “Surveillance Timeout” parameter

This parameter can be used to lock the force mode on the This parameter is used to set the delay time for output moni-
web server application. toring. The delay time starts after the state of the output has
been changed. Once this period of time has expired, the out-
False (0)
True (1) ing time is 100 ms.
0 to 255 (default: 80)
The monitoring of the output begins with 0 to 255 ms fol-
lowing the change of a channel state.
“Disable All Emergency Messages” parameter
This parameter can be used to deactivate all emergency mes-
sages. “Fail Safe” parameter
This parameter is used to set the behaviour of the associated
False (0)
The emergency messages are activated.
Set Low (0)
True (1)
The output is inactive in the event of disrupted fieldbus com-
The emergency messages are deactivated.
munication.
Set High (1)
“Disable UL Emergency Messages” parameter The output is active in the event of disrupted fieldbus com-
You can use this parameter to deactivate all emergency mes- munication.
sages as a result of an actuator supply error.
Hold Last (2)
False (0) The output is held at the last value in the event of disrupted
The emergency messages are activated. fieldbus communication.
True (1)
The emergency messages are deactivated. “IO Direction Configuration” parameter
This parameter is used to set the data direction of the chan-
nel.
“Disable Actuator Emergency Messages” parameter Input/Output (0)
You can use this parameter to deactivate all emergency mes-
The channel functions as a bi-directional input and output.
sages as a result of a channel error.
Input (1)
False (0)
The channel functions as an input.
The emergency messages are activated.
Output (2)
True (1)
The channel functions as an output.
The emergency messages are deactivated.

“IO Mapping Configuration” parameter

cess data bits of the channel in the process data telegrams.
For bi-directional channels, the assignment applies in both
the input and the output direction.
0 to 15
The physical process data bit of the channel is in position
0 to 15 of the associated process data telegrams.
255

9 Process data with EtherNet/IP | UR67-MP-xx-16DI-12-60M process data
9 Process data with EtherNet/IP
The length of the input data varies depending on whether

channel-related diagnostic data is being transferred. The di-
9.2 UR67-MP-xx-16DO-12-60M process data
agnostic data supplements the process input data.
Assembly instance ID 100: output data
Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
Byte 0 4-B 4-A 3-B 3-A 2-B 2-A 1-B 1-A

9.1 UR67-MP-xx-16DI-12-60M process data Byte 1 8-B 8-A 7-B 7-A 6-B 6-A 5-B 5-A
Assembly instance ID 101: input data with diagnosis Assembly instance ID 101: input data with diagnosis
Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
Byte 0 4-B 4-A 3-B 3-A 2-B 2-A 1-B 1-A Byte 0 4-B 4-A 3-B 3-A 2-B 2-A 1-B 1-A
Byte 2 MI-IME 0 0 0 0 MI-SCS 0 MI-LVS Byte 2 MI-IME 0 0 0 MI-SCA 0 MI-LVA MI-LVS
Byte 3 SCS-8 SCS-7 SCS-6 SCS-5 SCS-4 SCS-3 SCS-2 SCS-1 Byte 3 0 0 0 0 0 0 0 0
Byte 4 0 0 0 0 0 0 0 0
Assembly instance ID 102: input data without diagnosis Byte 5 CE-4-B CE-4-A CE-3-B CE-3-A CE-2-B CE-2-A CE-1-B CE-1-A
Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Byte 6 CE-8-B CE-8-A CE-7-B CE-7-A CE-6-B CE-6-A CE-5-B CE-5-A
Byte 0 4-B 4-A 3-B 3-A 2-B 2-A 1-B 1-A
Byte 1 8-B 8-A 7-B 7-A 6-B 6-A 5-B 5-A Assembly instance ID 102: input data without diagnosis
Byte 2 MI-IME 0 0 0 0 MI-SCS 0 MI-LVS Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
Byte 0 4-B 4-A 3-B 3-A 2-B 2-A 1-B 1-A

Byte 1 8-B 8-A 7-B 7-A 6-B 6-A 5-B 5-A
Byte 2 MI-IME 0 0 0 MI-SCA 0 MI-LVA MI-LVS

9 Process data with EtherNet/IP | UR67-MP-xx-8DIDO-12-60M process data
9.3 UR67-MP-xx-8DIDO-12-60M process data 9.4 UR67-MP-xx-16DIO-12-60M process data

Assembly instance ID 100: output data The tables illustrate the default mapping of the UR67-MP-xx-
16DIO-12-60M modules. You can parameterise the process
data mapping (see Section 6.7).
Byte 0 8-B 8-A 7-B 7-A 6-B 6-A 5-B 5-A
Assembly instance ID 100: 16 bit output data

Assembly instance ID 101: input data with diagnosis Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Byte 0 4-B 4-A 3-B 3-A 2-B 2-A 1-B 1-A
Byte 1 8-B 8-A 7-B 7-A 6-B 6-A 5-B 5-A
Byte 2 MI-IME 0 0 0 MI-SCA MI-SCS MI-LVA MI-LVS Assembly instance ID 101: 16 bit input data with diagnosis
Byte 3 0 0 0 0 SCS-4 SCS-3 SCS-2 SCS-1 Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
Byte 4 0 0 0 0 0 0 0 0 Byte 0 4-B 4-A 3-B 3-A 2-B 2-A 1-B 1-A
Byte 5 CE-8-B CE-8-A CE-7-B CE-7-A CE-6-B CE-6-A CE-5-B CE-5-A Byte 1 8-B 8-A 7-B 7-A 6-B 6-A 5-B 5-A
Byte 2 MI-IME 0 0 0 MI-SCA MI-SCS MI-LVA MI-LVS
Assembly instance ID 102: input data without diagnosis Byte 3 SCS-8 SCS-7 SCS-6 SCS-5 SCS-4 SCS-3 SCS-2 SCS-1
Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Byte 4 0 0 0 0 0 0 0 0
Byte 0 4-B 4-A 3-B 3-A 2-B 2-A 1-B 1-A Byte 5 CE-4-B CE-4-A CE-3-B CE-3-A CE-2-B CE-2-A CE-1-B CE-1-A
Byte 1 8-B 8-A 7-B 7-A 6-B 6-A 5-B 5-A Byte 6 CE-8-B CE-8-A CE-7-B CE-7-A CE-6-B CE-6-A CE-5-B CE-5-A
Assembly instance ID 102: 16 bit input data

Byte 0 4-B 4-A 3-B 3-A 2-B 2-A 1-B 1-A

Byte 1 8-B 8-A 7-B 7-A 6-B 6-A 5-B 5-A
Assembly instance ID 103: 8 bit output data, not for 8DIDO

Byte 0 8-A 7-A 6-A 5-A 4-A 3-A 2-A 1-A
Assembly instance ID 103: 8 bit output data, only for 8DIDO

Byte 0 8-B 8-A 7-B 7-A 6-B 6-A 5-B 5-A
Assembly instance ID 104: 8 bit input data with diagnosis, not for 8DIDO
Byte 0 8-A 7-A 6-A 5-A 4-A 3-A 2-A 1-A

Byte 2 SCS-8 SCS-7 SCS-6 SCS-5 SCS-4 SCS-3 SCS-2 SCS-1
Byte 3 0 0 0 0 0 0 0 0
Byte 4 CE-4-B CE-4-A CE-3-B CE-3-A CE-2-B CE-2-A CE-1-B CE-1-A

9 Process data with EtherNet/IP | Legend
Assembly instance ID 104: 8 bit input data with diagnosis, only for 8DIDO 9.5 Legend
Byte 0 4-B 4-A 3-B 3-A 2-B 2-A 1-B 1-A Abbreviation Meaning
Byte 1 MI-IME 0 0 0 MI-SCA MI-SCS MI-LVA MI-LVS Actual value (for input data) / target value (for output data) channel A
1-A to 8-A
Byte 2 SCS-8 SCS-7 SCS-6 SCS-5 SCS-4 SCS-3 SCS-2 SCS-1 (pin 4), connection 1 to 8
Actual value (for input data) / target value (for output data) channel B
Byte 3 0 0 0 0 0 0 0 0 1-B to 8-B
(pin 2), connection 1 to 8
MI-IME Module information – internal module error
MI-SCA Module information – actuator short circuit
MI-SCS Module information – sensor short circuit
Assembly instance ID 105: 8 bit input data, not for 8DIDO MI-LVA Module information – actuator low voltage
Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 MI-LVS Module information – system-/sensor low voltage
Byte 0 8-A 7-A 6-A 5-A 4-A 3-A 2-A 1-A SCS-1 to 8 Sensor short circuit at connection 1 to 8
Byte 1 MI-IME 0 0 0 MI-SCA MI-SCS MI-LVA MI-LVS CE-1-A to CE-8-A Channel error on channel A (pin 4) at connection 1 to 8
CE-1-B to CE-8-B Channel error on channel B (pin 2) at connection 1 to 8
Assembly instance ID 105: 8 bit input data, only for 8DIDO

Byte 0 4-B 4-A 3-B 3-A 2-B 2-A 1-B 1-A

Assembly instance ID 106: 0 bit input data with diagnosis


Byte 2 0 0 0 0 0 0 0 0
Assembly instance ID 107: 0 bit input data

Assembly instance ID 108: 16 bit input data with diagnosis, padding byte
Byte 0 4-B 4-A 3-B 3-A 2-B 2-A 1-B 1-A

Byte 1 8-B 8-A 7-B 7-A 6-B 6-A 5-B 5-A
Byte 4 0 0 0 0 0 0 0 0
Byte 7 0 0 0 0 0 0 0 0

10 Process data with PROFINET | UR67-MP-xx-16DI-12-60M process data
10 Process data with PROFINET
10.1 UR67-MP-xx-16DI-12-60M process data 10.4 UR67-MP-xx-16DIO-12-60M process data
Input data
16DIO module profile
Input data
Byte n 4-B 4-A 3-B 3-A 2-B 2-A 1-B 1-A
Byte n+1 8-B 8-A 7-B 7-A 6-B 6-A 5-B 5-A
Byte n 4-B 4-A 3-B 3-A 2-B 2-A 1-B 1-A
Byte n+1 8-B 8-A 7-B 7-A 6-B 6-A 5-B 5-A

Output data
Input data Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Byte n 4-B 4-A 3-B 3-A 2-B 2-A 1-B 1-A
Byte n 4-B 4-A 3-B 3-A 2-B 2-A 1-B 1-A Byte n+1 8-B 8-A 7-B 7-A 6-B 6-A 5-B 5-A
Byte n+1 8-B 8-A 7-B 7-A 6-B 6-A 5-B 5-A
8DIO module profile

Output data Input data
Byte n 4-B 4-A 3-B 3-A 2-B 2-A 1-B 1-A Byte n 8-A 7-A 6-A 5-A 4-A 3-A 2-A 1-A
Byte n+1 8-B 8-A 7-B 7-A 6-B 6-A 5-B 5-A
Output data
10.3 UR67-MP-xx-8DIDO-12-60M process data Byte n 8-A 7-A 6-A 5-A 4-A 3-A 2-A 1-A
Input data
16DI module profile
Input data
Byte n 4-B 4-A 3-B 3-A 2-B 2-A 1-B 1-A
Byte n+1 8-B 8-A 7-B 7-A 6-B 6-A 5-B 5-A
Byte n 4-B 4-A 3-B 3-A 2-B 2-A 1-B 1-A
Byte n+1 8-B 8-A 7-B 7-A 6-B 6-A 5-B 5-A
Output data
8DI module profile
Byte n 8-B 8-A 7-B 7-A 6-B 6-A 5-B 5-A
Profil 8DI: Input data
Byte n 8-A 7-A 6-A 5-A 4-A 3-A 2-A 1-A
16DO module profile

Profil 16DO : Output data
Byte n 4-B 4-A 3-B 3-A 2-B 2-A 1-B 1-A

Byte n+1 8-B 8-A 7-B 7-A 6-B 6-A 5-B 5-A

10 Process data with PROFINET | Legend
8DO module profile 10.5 Legend

Profil 8DI: Input data
Actual value (for input data) / target value (for output data) channel A
1-A to 8-A
Byte n 8-A 7-A 6-A 5-A 4-A 3-A 2-A 1-A (pin 4), connection 1 to 8
1-B to 8-B
8DIDO module profile
Input data
Byte n 4-B 4-A 3-B 3-A 2-B 2-A 1-B 1-A
Output data
Byte n 8-B 8-A 7-B 7-A 6-B 6-A 5-B 5-A

11 Process data with EtherCAT | UR67-MP-xx-16DI-12-60M process data
11 Process data with EtherCAT
Process data is transmitted as PDOs in byte format or bit

format. Input process data can be supplemented with diag-
nostic data.
11.1 UR67-MP-xx-16DI-12-60M process data
0x1A00 TxPDO mapping (byte) 0x1A04 TxPDO error register

Index Type Length Data Index Type Length Data
0x6000:01 USINT 1 bytes 1-A to 4-B 0 x 1001 USINT 1 bytes Error

0x6000:02 USINT 1 bytes 5-A to 8-B Error Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
Index Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 No error 0 0 0 0 0 0 0 0
0x6000:01 4-B 4-A 3-A 3-B 2-B 2-A 1-B 1-A MI-SCS 0 0 0 0 0 0 1)
1 1
0x6000:02 8-B 8-A 7-B 7-A 6-B 6-A 5-B 5-A MI-LVS 0 0 0 0 0 1 01) 1
MI-FC 1 0 0 0 0 01) 01) 1
MI-IME 1 0 0 0 0 0 1)
01)
1
0x1A01 TxPDO mapping (bit)
1) Can be 1, if more than one error is active
0x6020:01 BIT 1 bit 1-A 0x6020:09 BIT 1 bit 5-A

0x6020:02 BIT 1 bit 1-B 0x6020:0A BIT 1 bit 5-B 0x1A05 TxPDO diagnostic register
0x6020:03 BIT 1 bit 2-A 0x6020:0B BIT 1 bit 6-A Index Type Length Data
0x6020:04 BIT 1 bit 2-B 0x6020:0C BIT 1 bit 6-B 0 x 2001 UDINT 4 bytes Diagnostics
0x6020:05 BIT 1 bit 3-A 0x6020:0D BIT 1 bit 7-A Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
0x6020:06 BIT 1 bit 3-B 0x6020:0E BIT 1 bit 7-B Byte 1 MI-IME MI-FC 0 0 0 MI-SCS 0 MI-LVS
0x6020:07 BIT 1 bit 4-A 0x6020:0F BIT 1 bit 8-A Byte 2 SCS-8 SCS-7 SCS-6 SCS-5 SCS-4 SCS-3 SCS-2 SCS-1
0x6020:08 BIT 1 bit 4-B 0x6020:10 BIT 1 bit 8-B Byte 3 0 0 0 0 0 0 0 0
Byte 4 0 0 0 0 0 0 0 0

11 Process data with EtherCAT | UR67-MP-xx-16DO-12-60M process data
0x1600 RxPDO mapping (byte) 0x1A04 TxPDO error register


0x6200:02 USINT 1 bytes 5-A to 8-B Error Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
Index Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 No error 0 0 0 0 0 0 0 0
0x6200:01 4-B 4-A 3-A 3-B 2-B 2-A 1-B 1-A MI-SCA 0 0 0 0 0 01)
1 1
0x6200:02 8-B 8-A 7-B 7-A 6-B 6-A 5-B 5-A MI-LVS 0 0 0 0 0 1 01) 1
MI-LVA 0 0 0 0 0 1 01) 1
MI-FC 1 0 0 0 0 01) 01) 1
0x1601 RxPDO mapping (bit)
MI-IME 1 0 0 0 0 01)
01)
1
1) Can be 1, if more than one error is active
0x6220:02 BIT 1 bit 1-B 0x6220:0A BIT 1 bit 5-B
0x6220:03 BIT 1 bit 2-A 0x6220:0B BIT 1 bit 6-A 0x1A05 TxPDO diagnostic register
0x6220:04 BIT 1 bit 2-B 0x6220:0C BIT 1 bit 6-B Index Type Length Data
0x6220:05 BIT 1 bit 3-A 0x6220:0D BIT 1 bit 7-A 0 x 2001 UDINT 4 bytes Diagnostics
0x6220:06 BIT 1 bit 3-B 0x6220:0E BIT 1 bit 7-B Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
0x6220:07 BIT 1 bit 4-A 0x6220:0F BIT 1 bit 8-A Byte 1 MI-IME MI-FC 0 0 MI-SCA 0 MI-LVA MI-LVS
0x6220:08 BIT 1 bit 4-B 0x6220:10 BIT 1 bit 8-B Byte 2 0 0 0 0 0 0 0 0
0x1A02 TxPDO output mirrors (byte)
Index Type Length Data
0x2200:01 USINT 1 bytes 1-A to 4-B

Index Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
0x2200:01 4-B 4-A 3-A 3-B 2-B 2-A 1-B 1-A

0x2200:02 8-B 8-A 7-B 7-A 6-B 6-A 5-B 5-A
0x1A03 TxPDO output mirrors (bit)


0x2220:03 BIT 1 bit 2-A 0x2220:0B BIT 1 bit 6-A
0x2220:04 BIT 1 bit 2-B 0x2220:0C BIT 1 bit 6-B
0x2220:05 BIT 1 bit 3-A 0x2220:0D BIT 1 bit 7-A
0x2220:06 BIT 1 bit 3-B 0x2220:0E BIT 1 bit 7-B
0x2220:07 BIT 1 bit 4-A 0x2220:0F BIT 1 bit 8-A
0x2220:08 BIT 1 bit 4-B 0x2220:10 BIT 1 bit 8-B

11 Process data with EtherCAT | UR67-MP-xx-8DIDO-12-60M process data
11.3 UR67-MP-xx-8DIDO-12-60M process data
0x1600 RxPDO mapping (byte) 0x1A04 TxPDO error register


Index Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Error Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
0x6200:01 8-B 8-A 7-B 7-A 6-B 6-A 5-B 5-A No error 0 0 0 0 0 0 0 0
MI-SCS
0 0 0 0 0 01) 1 1
MI-SCA
0x1601 RxPDO mapping (bit) MI-LVS 0 0 0 0 0 1 01) 1
MI-LVA 0 0 0 0 0 1 01)
1
0x6220:01 BIT 1 bit 5-A 0x6220:05 BIT 1 bit 7-A MI-FC 1 0 0 0 0 01) 01) 1
0x6220:02 BIT 1 bit 5-B 0x6220:06 BIT 1 bit 7-B MI-IME 1 0 0 0 0 01)
01)
1
0x6220:03 BIT 1 bit 6-A 0x6220:07 BIT 1 bit 8-A 1) Can be 1, if more than one error is active.
0x1A05 TxPDO diagnostic register

0x1A00 TxPDO mapping (byte) Index Type Length Data
0 x 2001 UDINT 4 bytes Diagnostics
0x6000:01 USINT 1 bytes 1-A to 4-B Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
Byte 1 MI-IME MI-FC 0 0 MI-SCA MI-SCS MI-LVA MI-LVS
0x6000:01 4-B 4-A 3-A 3-B 2-B 2-A 1-B 1-A Byte 2 0 0 0 0 SCS-4 SCS-3 SCS-2 SCS-1
Byte 3 0 0 0 0 0 0 0 0
0x1A01 TxPDO mapping (bit) Byte 4 CE-8-B CE-8-A CE-7-B CE-7-A CE-6-B CE-6-A CE-5-B CE-5-A

0x1A02 TxPDO output mirrors (byte)


0x2200:01 8-B 8-A 7-B 7-A 6-B 6-A 5-B 5-A
0x1A03 TxPDO output mirrors (bit)



11 Process data with EtherCAT | UR67-MP-xx-16DIO-12-60M process data
11.4 UR67-MP-xx-16DIO-12-60M process data

The tables illustrate the default mapping of the UR67-MP-xx-
16DIO-12-60M modules. You can parameterise the process
data mapping (see Section 8.7).
Module profile 16DI/DO Module profile 8DI/DO

0x1A00 TxPDO mapping (byte) 0x1A10 TxPDO mapping (byte)
0x6000:01 USINT 1 bytes 1-A to 4-B 0x6000:01 USINT 1 bytes 1-A to8-A

0x6000:02 USINT 1 bytes 5-A to 8-B Index Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
Index Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 0x6000:01 8-A 7-A 6-A 5-A 4-A 3-A 2-A 1-A
0x6000:01 4-B 4-A 3-A 3-B 2-B 2-A 1-B 1-A
0x6000:02 8-B 8-A 7-B 7-A 6-B 6-A 5-B 5-A
0x1A11 TxPDO mapping (bit)
0x1A01 TxPDO mapping (bit) 0x6020:01 BIT 1 bit 1-A 0x6020:05 BIT 1 bit 5-A
Index Type Length Data Index Type Length Data 0x6020:02 BIT 1 bit 2-A 0x6020:06 BIT 1 bit 6-A
0x6020:01 BIT 1 bit 1-A 0x6020:09 BIT 1 bit 5-A 0x6020:03 BIT 1 bit 3-A 0x6020:07 BIT 1 bit 7-A
0x6020:02 BIT 1 bit 1-B 0x6020:0A BIT 1 bit 5-B 0x6020:04 BIT 1 bit 4-A 0x6020:08 BIT 1 bit 8-A
0x1610 RxPDO mapping (byte)
0x6200:01 USINT 1 bytes 1-A to8-A
0x6200:01 8-A 7-A 6-A 5-A 4-A 3-A 2-A 1-A

0x6200:01 4-B 4-A 3-A 3-B 2-B 2-A 1-B 1-A
0x6200:02 8-B 8-A 7-B 7-A 6-B 6-A 5-B 5-A



Module profile 16DI Module profile 16DO

0x1A00 TxPDO mapping (byte) 0x1600 RxPDO mapping (byte)
0x6000:01 USINT 1 bytes 1-A to 4-B 0x6200:01 USINT 1 bytes 1-A to 4-B

0x6000:02 USINT 1 bytes 5-A to 8-B 0x6200:02 USINT 1 bytes 5-A to 8-B
Index Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Index Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
0x6000:01 4-B 4-A 3-A 3-B 2-B 2-A 1-B 1-A 0x6200:01 4-B 4-A 3-A 3-B 2-B 2-A 1-B 1-A
0x6000:02 8-B 8-A 7-B 7-A 6-B 6-A 5-B 5-A 0x6200:02 8-B 8-A 7-B 7-A 6-B 6-A 5-B 5-A
0x1A01 TxPDO mapping (bit) 0x1601 RxPDO mapping (bit)

Index Type Length Data Index Type Length Data Index Type Length Data Index Type Length Data
0x6020:02 BIT 1 bit 1-B 0x6020:0A BIT 1 bit 5-B 0x6220:02 BIT 1 bit 1-B 0x6220:0A BIT 1 bit 5-B
0x6020:03 BIT 1 bit 2-A 0x6020:0B BIT 1 bit 6-A 0x6220:03 BIT 1 bit 2-A 0x6220:0B BIT 1 bit 6-A
0x6020:04 BIT 1 bit 2-B 0x6020:0C BIT 1 bit 6-B 0x6220:04 BIT 1 bit 2-B 0x6220:0C BIT 1 bit 6-B
0x6020:05 BIT 1 bit 3-A 0x6020:0D BIT 1 bit 7-A 0x6220:05 BIT 1 bit 3-A 0x6220:0D BIT 1 bit 7-A
0x6020:06 BIT 1 bit 3-B 0x6020:0E BIT 1 bit 7-B 0x6220:06 BIT 1 bit 3-B 0x6220:0E BIT 1 bit 7-B
0x6020:07 BIT 1 bit 4-A 0x6020:0F BIT 1 bit 8-A 0x6220:07 BIT 1 bit 4-A 0x6220:0F BIT 1 bit 8-A
0x6020:08 BIT 1 bit 4-B 0x6020:10 BIT 1 bit 8-B 0x6220:08 BIT 1 bit 4-B 0x6220:10 BIT 1 bit 8-B
Module profile 8DI Module profile 8DO

0x1A10 TxPDO mapping (byte) 0x1610 RxPDO mapping (byte)
0x6000:01 USINT 1 bytes 1-A to8-A 0x6200:01 USINT 1 bytes 1-A to8-A

Index Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Index Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
0x6000:01 8-A 7-A 6-A 5-A 4-A 3-A 2-A 1-A 0x6200:01 8-A 7-A 6-A 5-A 4-A 3-A 2-A 1-A
0x1A11 TxPDO mapping (bit) 0x1611 RxPDO mapping (bit)

Index Type Length Data Index Type Length Data Index Type Length Data Index Type Length Data

Module profile 8DI/8DO Diagnostics

0x1A10 TxPDO mapping (byte) 0x1A04 TxPDO error register
0x6000:01 USINT 1 bytes 1-A to 4-B 0x1001:01 USINT 1 bytes Error

Index Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Error Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
0x6000:01 4-B 4-A 3-A 3-B 2-B 2-A 1-B 1-A No error 0 0 0 0 0 0 0 0
MI-SCS
01) 0 0 0 0 01) 1 1
MI-SCA
0x1A11 TxPDO mapping (bit) MI-LVS 01) 0 0 0 0 1 01) 1
MI-LVA 0 1)
0 0 0 0 1 01)
1
0x6020:01 BIT 1 bit 1-A 0x6020:05 BIT 1 bit 3-A MI-PRM 1 0 0 0 0 01) 01) 1
0x6020:02 BIT 1 bit 1-B 0x6020:06 BIT 1 bit 3-B MI-FC 1 0 0 0 0 01)
01)
1
0x6020:03 BIT 1 bit 2-A 0x6020:07 BIT 1 bit 4-A MI-IME 1 0 0 0 0 01)
01)
1
0x6020:04 BIT 1 bit 2-B 0x6020:08 BIT 1 bit 4-B 1) Can be 1, if more than one error is active

Index Type Length Data 0x1A05 TxPDO diagnostic register
0x6200:01 USINT 1 bytes 5-A to8-A Index Type Length Data
Index Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 0x2001:01 UDINT 4 bytes Diagnostics
0x6200:01 8-B 8-A 7-B 7-A 6-B 6-A 5-B 5-A Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
Byte 1 MI-IME MI-FC MI-PRM 0 MI-SCA MI-SCS MI-LVA MI-LVS
0x1611 RxPDO mapping (bit) Byte 2 SCS-8 SCS-7 SCS-6 SCS-5 SCS-4 SCS-3 SCS-2 SCS-1
Index Type Length Data Index Type Length Data Byte 3 CE-4-B CE-4-A CE-3-B CE-3-A CE-2-B CE-2-A CE-1-B CE-1-A
0x6220:01 BIT 1 bit 5-A 0x6220:05 BIT 1 bit 7-A Byte 4 CE-8-B CE-8-A CE-7-B CE-7-A CE-6-B CE-6-A CE-5-B CE-5-A


11 Process data with EtherCAT | Legend
11.5 Legend
Actual value (for input data) / target value (for output data) channel A
1-A to 8-A
1-B to 8-B
MI-IME Module information – internal module error
MI-SCA Module information – actuator short circuit
MI-SCS Module information – sensor short circuit
MI-LVA Module information – actuator undervoltage
MI-LVS Module information – system/sensor undervoltage
MI-PRM Module information – parameter error
MI-FC Module information – force active
SCS-1 to 8 Sensor short circuit at connection 1 to 8
CE-1-A to CE-8-A Channel error on channel A (pin 4) at connection 1 to 8
CE-1-B to CE-8-B Channel error on channel B (pin 2) at connection 1 to 8

12 Diagnostics | Descriptions of errors
12 Diagnostics
12.1 Descriptions of errors System/sensor power supply error
Channel error ATTENTION

Channel errors are discrepancies between the target value
set by a control unit and the actual value of an output chan- Make sure that the power supply voltage for the system/
nel. In the event of a short circuit or overload, the output driv- sensor power supply does not fall below 18 V DC when
ers likewise signal a channel error. taking the measurement at the furthest-away participant.
The voltage value of the system /sensor power supply is

Target value Actual value Comment
monitored globally. If the voltage falls below 18 V or exceeds
On On Ok, no diagnostic message 30 V, an error message is generated and the US LED lights
Off Off Ok, no diagnostic message up red. The error message does not affect the outputs.
Short circuit/overload
On Off
Channel LED: red Actuator power supply error
Diagnostic message The voltage value of the actuator power supply for modules
Channel is blocked after troubleshooting with output functionality is monitored globally. If the voltage
Voltage feedback falls below 18 V or exceeds 30 V, an error message is gener-
Channel LED: red and yellow/white
Off On ated and the UL LED lights up red.
Diagnostic message
Channel is not blocked after troubleshooting Should an actuator power supply error occur, all
of the activated output channels are blocked. In-
Should a channel error occur, all of the activated activated channels are not blocked.
output channels are blocked on the affected con-
nection. Inactivated channels are not blocked.
Blocked channels are deactivated and remain deactivated
until they are reset via the control unit.
Blocked channels are deactivated and remain deactivated
until they are reset via the control unit. In the event that a channel is blocked, diagnostics
(channel error) will be initiated for every active
A delay time (“Surveillance Timeout”) can be configured us- output channel once the supply voltage returns to
ing the “Surveillance Timeout” parameter. Once this period a normal level.
of time has expired, the output is monitored and error states ▶▶ In order to prevent the diagnostic messages
are reported as diagnoses. When an output channel is in from being displayed, deactivate all output
a static state (switched permanently on or off), the delay channels via the control unit as soon as an
time is 100 ms. A detailed description can be found in Sec- undervoltage is detected.
tion 7.6 “Parameter settings”.
A fixed delay time of 300 ms is preconfigured from actua-
Sensor short circuit tor power supply diagnoses. Once this period of time has
Pin 1 supplies a monitored 24 V potential for the sensor expired, the actuator power supply is monitored and error
power supply to every I/O connection with input functional- states are reported as diagnoses.
ity.
In the event of a sensor short circuit, a voltage error is re-
ported. Both channel LEDs for the affected connection light
up red.

12 Diagnostics | EtherNet/IP diagnoses
12.2 EtherNet/IP diagnoses is called up. The SFB 54 module also has to be called up in
every error OB.
Diagnostic information supplement the input process data.
Byte 2 provides module-related diagnostic data. The subse- In OB1, diagnostic data sets can be called up with
quent bytes provide channel-relted diagnostic data. A de- SFB52 RDREC via their data set number.
tailed description can be found in Chapter 9.
Structure of the diagnostic data sets
Bits set –– Block version: 0x0101
Diagnosis –– USI (User Structure Identifier): 0x8000
Module-related Channel-related
where applicable
Channel error CE-1-A/B to CE-8-A/B Error type Reference ChannelNumber ChannelErrorType
MI-SCA
Sensor short circuit MI-SCS SCS-1 to 8 Undervoltage in
sensor or actuator Module 0x8000 0x0002
System/sensor power supply error MI-LVS – power supply
where applicable CE-1-A/B 0x0001–0x0008
Actuator power supply error MI-LVA Sensor short
to CE-8-A/B I/O connection Number of the I/O 0x0102
circuit
connection
0x0001–0x0008
Actuator short Channel A of an
12.3 PROFINET diagnoses circuit I/O connection
Number of the I/O
connection
0x0100
▶▶ Activate the “Report Alarms” parameter when 0x0001–0x0008

Actuator short Channel B of an
parameterising the modules in order to trans- circuit I/O connection
Number of the I/O 0x0101
fer diagnostic messages via PROFINET. connection
When the module detects an error, an alarm message is trig-

gered. The modules support diagnostic alarms.
An alarm is triggered for an upcoming event as well as an

event coming to an end.
Alarm evaluation depends on the PROFINET IO controller

used.
Alarm evaluation in STEP 7

In Step 7, the processing of the user program (OB1) is inter-
rupted by triggering a diagnostic alarm and an error organi-
sation block (error OB) is called up.
Cause of the alarms Called up error OB

Peripheral error (short circuit/overload,
OB82 Diagnostics alarm
wire breakage, undervoltage)
Complete system outage OB86 Subrack failure
If the error OB called up is not available in the

CPU, the CPU enters the STOP operating status.
The error OB called up and its start information already

provide information about the cause and type of the error.
Detailed information about the error is provided in the re-
spective error OB when the SFB 54 RALRM system module

12 Diagnostics | EtherCAT diagnostics
12.4 EtherCAT diagnostics

Diagnostic information supplements the input process data.
The PDO 0x1001 delivers module-related diagnostic data.
The PDO 0x2001 delivers module-related and channel-
related diagnostic data. A detailed description can be found
in Chapter 11.
The modules can also send emergency notifications to the

master if an error is detected.
▶▶ Select “All Emergency Notifications” when parameterising

the modules to enable emergency notifications.
Structure of an emergency notification

Byte 1 to 2 Byte 3 Byte 4 to7 Byte 8
Emergency error code Error register Diagnostic register Empty
Emergency error code Description

0x0000 No error
Sensor short circuit
0x2300
Actuator short circuit
0x3100 System/sensor power supply error
0x3300 Actuator power supply error
0xF000 Forcing active
0xFF00 Internal device error
0xFF01 Parameter error (only for UR67-MP-xx-16DIO-12-60M)
The error register corresponds to the content of the

PDO 0x1001 of the module. The diagnostic register corre-
sponds to the content of the PDO 0x2001 of the module.

12 Diagnostics | LED indicators and troubleshooting
12.5 LED indicators and troubleshooting
LED Display Description Recommended action

General
UL Green Actuator voltage OK –
Red Actuator voltage < 18 V or > 30 V Check supply voltage
Off No actuator power supply Check supply voltage, check power supply cable
US Green System/sensor voltage OK –
Red System/sensor voltage < 18 V or > 30 V Check supply voltage
Off No system/sensor power supply Check supply voltage, check power supply cable
1 to 8 A Yellow Channel A status “on” –
Red Peripheral error (sensor or actuator overload/short circuit) Check peripheral equipment for short circuit or overload
Off Channel A status “off” or not connected Check cable connected to peripheral equipment
1 to 8 B White Channel B status “on” –
Red Peripheral error (sensor or actuator overload/short circuit) Check peripheral equipment for short circuit or overload
Off Channel B status “off” or not connected Check cable connected to peripheral equipment
X01 Lnk/Act Green Connected to next X01 participant, link detected –
Yellow flashing Data being exchanged with another participant –
Off No connection to X01 Check connection to next X01 participant
X02 Lnk/Act Green Connected to next X02 participant, link detected –
Yellow flashing Data being exchanged with another participant –
Off No connection to X02 Check connection to next X02 participant
With Ethernet/IP
MS Green Device operational –
Green flashing Device operational but not configured –
Red Critical and non-correctable error –
Red flashing Minor, correctable error Check configuration, read out diagnostic message, check LEDs
of I/O connections
Alternating red-green flashing Device running self-test –
Off Device switched off Check supply voltage
NS Green Connected: at least one existing connection –
Green flashing Not connected, IP address available Check fieldbus cable, check PLC configuration
Red Duplicate IP address Check IP address or assign via DHCP
Red flashing Connection timeout or Check fieldbus cable, check PLC configuration
connection interrupted
Alternating red-green flashing Device running self-test –
Off Device switched off or no IP address assigned Check supply voltage, check IP address

12 Diagnostics | LED indicators and troubleshooting
LED Display Description Recommended action

With PROFINET
BF Red No connection to fieldbus Check fieldbus cable, check PLC configuration
Red flashing (2 Hz) No data being exchanged –
Off Connected to control unit –
DIA Red Watchdog timeout, diagnosis available, system error Check configuration, read out diagnostic message, check LEDs
of I/O connections
Red flashing (2 Hz, 3 sec) DCP signal service triggered via bus –
Off No diagnosis available –
With EtherCAT
RUN Green Status: OPERATIONAL –
Green flashing briefly Status: SAFE-OPERATIONAL –
Green flashing Status: PRE-OPERATIONAL –
Off Status: INIT –
Green flickering Device starting up or –
status: BOOTSTRAP
ERR Red Critical error in module –
Red flickering Start-up error –
Red flashing Configuration error Check configuration, check that the ESI file is up to date
Red flashing briefly Local error or unsolicited status change –
Red flashes briefly twice Watchdog error Compare master cycle time with watchdog time
Off No error –

13 Web server | Connecting and starting up the web server
13 Web server
The web server is used to display the UR67 module on a 13.2 Getting to know and arranging the web
connected PC. This allows you to do the following for test
purposes or during commissioning or service work: server
–– Query the module status
–– Display and change the module parameters Module overview
–– Access diagnostic information The overview page is displayed every time the web server is
–– Operate the module in Force mode for testing purposes started up.
13.1 Connecting and starting up the web server

Requirements:
Web browser
The web server can be used with the following web brows-
ers:
–– Mozilla Firefox 4.0 or higher
–– Google Chrome 9.0 or higher
–– Opera 10.61 or higher
–– Microsoft Internet Explorer 9, 10 and 11
Screen resolution Overview page with operating elements

When working with the web server, we recommend using
a screen resolution of 1280 x 800 or higher, but at least 1 Module detailed view
1024 x 768. The operator front-end is displayed optimally 2 Show or hide details
when the browser window is maximised. 3 Access to overview page
4 Access to web server functions
Starting up the web server 5 Menu bar
The module must be completely assembled and supplied 6 Open help dialogue box
with power. 7 Reset the module to factory settings
▶▶ Make sure that the PC and the module are connected via 8 Restart the web server
Ethernet. You can access the overview page at any time by clicking
Overview.
The modules are distributed with the IP adress
0.0.0.0. A free IP address must be assigned to the
module, before you can use the web server (e.g. Operating instructions
via an engineering tool). The PC and the module Single mouse clicks (left mouse button) are sufficient for
must be in the same subnet. operating the web server. Some areas of the interface are
mouse-sensitive, i.e. they change when the cursor is moved
▶▶ Open one of the browsers listed above. over these areas and without clicking the mouse (“mouse-
▶▶ In the address line, enter the IP address of the module. over”).
When the cursor changes to this icon, the user is
The web server will then be started up. The connected mod- expected to click the mouse.
ule will be displayed.
If the web server does not start up: When the cursor changes to this icon, you can
▶▶ Clear the browser cache. Deleting only the his- move the screen view by pressing and holding
tory is not a sufficient measure in this the left mouse button while moving the mouse.
instance.
▶▶ Restart the web server.
▶▶ Check the module IP address and whether the
right subnet has been selected.

13 Web server | Getting to know and arranging the web server
Show or hide content Setting the language

All entries that are marked with a square plus symbol can be ▶▶ To change the language, click on Language in the menu
opened and the content displayed with a single mouse click. bar and then on the required setting.
Showing content
Setting the language
Conversely, content can be hidden by clicking on the square
minus symbol. Entering a password
Access to the following functions is restricted by means of
password protection:
–– Changing parameters
–– Operating the module in Force mode
–– Downloading firmware updates
–– Changing a password
Users without a user ID have read-only rights, but no write

access. They cannot use the specified functions. A password
is requested the first time an attempt is made in a session to
access these functions.
Hiding content
▶▶ Enter the username and password and confirm by click-
Tracking changes ing on OK
Any settings changed will be marked with a green symbol.
Changes marked with symbol
In this state, you can revert each individual change that has Entering the username and password
not yet been accepted by the module back to its original set-
ting. All changes are only accepted when you click on Apply In the original state as at delivery, the login credentials are as
changes. All changes are reset when you click on Restore. follows:
Once you have applied or restored the changes, the markers User name: admin
will be removed. Password: Detmold

13 Web server | Module settings and diagnostics
In order to prevent unauthorised access, the login

details must be changed when setting up the
web server. The local data security provisions
must subsequently be observed.
Once you have successfully entered the username and pass-

word, you will not have to do it again for the same session.
You cannot log out.
To prevent unauthorised access, make sure to
always close the browser once you have finished
working and when you leave your workstation for
a short period of time.
Changing the password

▶▶ Click on Change password.
The “Change password window opens. You may be prompt-
ed beforehand to enter your username and password. Help dialogue box
▶▶ Click on the link to open the Weidmüller website.

You will be connected to the Weidmüller website in a new
browser window.
13.3 Module settings and diagnostics

▶▶ Open the overview page.
Change password
The new password must contain at least three characters

and is case-sensitive.
▶▶ Enter a new password.
▶▶ Re-enter the password and click on Change password.
Documentation
▶▶ Click on Help.
Overview page
Here you can:

–– Access and change module parameters
–– Display diagnoses
–– Show general information on the module
–– Change a password
–– Reset changes
–– Reset the module to factory settings

13 Web server | Module settings and diagnostics
Module settings can only be accessed when The module is restarted during the reset process!
Force mode is not enabled. All data that is not protected against power failure
is reset.
Status data can be displayed at any time regard-

less of the fieldbus connection. Any changes to
▶▶ Click on Reset and then on Yes.
settings can only be saved when the fieldbus is
not active.
Accessing and editing parameters

▶▶ Click on Parameter.
The parameters are displayed.
For parameters that can be edited, you can enter the chang-
es in the respective entry field or choose alternative settings
from a dropdown menu.
Restarting the web server and module
The module and the web server are restarted.
Resetting the module to factory settings

This function allows you to reset the module to its original
state upon delivery. The following data is reset as part of this
process:
–– All module parameters
–– Login data and password protection
–– Changes to module parameters that have been saved in
Accessing and editing module parameters the module
The module is restarted during the reset process!
▶▶ Enter the required changes.
Each change is labelled with a green symbol until it has been
applied.
▶▶ Click on Apply changes to save the changes. ▶▶ Open the overview page.
▶▶ Click on Factory settings and then on Yes.
All changes are only accepted when you click on Apply
changes. All changes are reset when you click on Restore.
The changes are then transferred to the module and the
green labels removed.
Resetting the web server

Performing a reset allows you to undo all the changes that
have been made since the last time that the web server was
started up.

13 Web server | Web server in Force mode
If Force mode is enabled when the fieldbus is

connected, a diagnostic alarm is triggered. De-
pending on the parameterised alarm behaviour,
output process data may continue to be trans-
ferred by the PLC and processed by the module
for all unforced output channels. All of the forced
output channels ignore the process data and pro-
ceed exclusively according to the forced values.
Input process data is always transferred regard-
less of whether it is simulated through forced op-
erations or has been imported via physical inputs.
If Force mode is enabled without a fieldbus con-

nection being established, the fieldbus interface
Resetting the module to factory settings
will be deactivated for the duration of forced
operations. A new fieldbus connection may only
The module and the web server are restarted. The module
be established again once Force mode has been
will once again be in the same state as it was when it was
terminated.
initially delivered.
Displaying diagnostic data Force mode allows you to carry out functional tests or pre-
▶▶ Click on Diagnostic data. configure the module prior to commissioning, even if sensors
All of the current diagnostic messages are displayed. or actuators have not yet been connected. To do so, you
must change the operating mode of the web server.
▶▶ Click on Force and Enable.
Display of diagnostic data
Enabling Force mode
13.4 Web server in Force mode The web server is now in Force mode, which can be identi-
fied by the red bar. Forced channels can be identified by a
Enabling Force mode red border.
WARNING!
Manipulation of the control unit!
In Force mode, the system may be manipu-
lated to such an extent that life-threatening
personal injury and damage to materials may
occur.
Only use Force mode if you are very familiar
with the connected system and know at all
times the consequences that your actions
will have!

13 Web server | Updating firmware
13.5 Updating firmware

A firmware update cannot be reversed. The old
firmware in the module is overwritten.
▶▶ Download the current firmware for the components to be

updated from the Weidmüller website.
Firmware files have the “bsc” file extension. The file for the
UR67-MP modules, for example, is named UR67-MP-00XX.
bsc.
▶▶ Make sure that the power supply is not inter-
Display in Force mode rupted during the firmware update.
▶▶ Do not make any changes to the module dur-
Force mode is terminated when the connection ing the firmware update.
between the web server and the module is inter-
rupted.
You cannot access the module via the web server while the
Forcing channels firmware files are being loaded.
▶▶ To force a channel, click on the slider button and then on
Apply changes. ▶▶ To carry out a firmware update, click on Firmware in the
menu bar.
Firmware update menu

Forcing a channel
Disabling Force mode

▶▶ To disable Force mode, click on Force and Disable.
Disabling Force mode
The station is put back into the status it was in prior to forced
operations.

13 Web server | Updating firmware
The name of the firmware is displayed along with the version

that is currently being run.
Updating firmware
▶▶ Click on Select firmware.

▶▶ Select the firmware file from the storage location on your
computer and click Open.
▶▶ Click on Update now.
The firmware is updated. Once the update has finished, you
will be prompted to restart the coupler.
▶▶ Click Reset.
▶▶ Wait until the coupler has restarted and the station over-
view is displayed in the web server.
If the web server does not restart, delete the
temporary browser data (clear the cache; delet-
ing only the history is not a sufficient measure
in this instance) and try to access the web
server again.

14 Disassembly and disposal | Disassembling the u-remote module
14 Disassembly and disposal
WARNING
Dangerous contact voltage!
▶▶ All installation and wiring work must be
carried out with the power supply discon-
nected.
▶▶ Make sure that the place of installation
has been disconnected from the power
supply!
CAUTION
Hot surface!
The module can become very hot when in
operation (over 60 °C).
▶▶ Allow the module to cool before touching
it.
14.1 Disassembling the u-remote module

▶▶ Remove all cables and lines.
▶▶ Unscrew the mounting screws on the module.
▶▶ Please observe the instructions for proper disposal.
14.2 Disposing of the u-remote module

ATTENTION
Products in the u-remote series are subject
to WEEE (EU Directive 2012/19 EU), which
regulates the collection and recycling of elec-
trical and electronic equipment.
▶▶ Make sure that disassembled products are
properly disposed of!
When all u-remote products reach the end of their life cycle,
you can return them to Weidmüller, and we will arrange for
their proper disposal. This also applies to countries outside
the European Union.
▶▶ Please pack the products properly and send them to your
responsible distributor.
You can find the address of your respective country repre-

sentative on the Weidmüller website.

Weidmüller – Your
Ihr Partner
Partnerder
in Industrial
Industrial Connectivity
Connectivity
As experienced experts we support our customers and partners around the world
with products, solutions and services in the industrial environment of power,
signal and data. We are at home in their industries and markets and know the
technological challenges of tomorrow. We are therefore continuously developing
innovative, sustainable and useful solutions for their individual needs. Together we
set standards in Industrial Connectivity.
Weidmüller Interface GmbH & Co. KG

Klingenbergstraße 26
32758 Detmold, Germany
T +49 5231 14-0 Your local Weidmüller partner can
F +49 5231 14-292083 be found on our website:
www.weidmueller.com www.weidmueller.com/countries Order No.: 2484940000/02/12.2019

02 12-2019 MANU en UR67-MP

Uploaded by

Copyright:

Available Formats

02 12-2019 MANU en UR67-MP

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

02 12-2019 MANU en UR67-MP

Uploaded by

Copyright:

Available Formats

Remote-I/O-System u-remote UR67

I/O-Modules IP67 Multiprotocol

UR67-MP-HP-16DI-12-60M 2426270000 UR67-MP-78-16DI-12-60M 2426300000

1 About this documentation 5

Document No. 2484940000

2 Manual UR67-Multiprotokoll 2484940000/02/12.2019

2484940000/02/12.2019 Manual UR67-Multiprotokoll 3

1 About this documentation

▶▶ All instructions can be identified by the black triangles

2484940000/02/12.2019 Manual UR67-Multiprotokoll 5

1.3 Standard data structure 1.4 Software releases described

Device description files

Language files Webserver

6 Manual UR67-Multiprotokoll 2484940000/02/12.2019

This chapter includes general safety instructions on handling Fusing

2.1 General safety notice Shielding

2484940000/02/12.2019 Manual UR67-Multiprotokoll 7

2.3 Legal notice

Components of the following free software products are inte-

Component License Link

8 Manual UR67-Multiprotokoll 2484940000/02/12.2019

u-remote IP67 modules for Ethernet/IP, PROFINET and EtherCAT

2484940000/02/12.2019 Manual UR67-Multiprotokoll 9

3.1 Fieldbus features Alarm and diagnostic messages

Ethernet/IP product features Configurable process data for 16DIO modules

EtherCAT product features

10 Manual UR67-Multiprotokoll 2484940000/02/12.2019

3.2 Web server 3.4 Accessories

2484940000/02/12.2019 Manual UR67-Multiprotokoll 11

4.1 UR67-MP-HP-16DI-12-60M and

Each module has eight connections (M12, 5-pole, A-coded) 4 4 8

L-coded M12 or 7/8" connections. 5 E/IP: MS NS 10

US green/red System/sensor power supply status

2484940000/02/12.2019 Manual UR67-Multiprotokoll 13

4.2 UR67-MP-HP-16DO-12-60M and

Each module has eight connections (M12, 5-pole, A-coded) 4 4 8

L-coded M12 or 7/8" connections. 5 E/IP: MS NS 10

UL green/red Actuator supply status

14 Manual UR67-Multiprotokoll 2484940000/02/12.2019

4.3 UR67-MP-HP-8DIDO-12-60M and

Each module has eight connections (M12, 5-pole, A-coded) 4 4 8

L-coded M12 or 7/8" connections. 5 E/IP:

UL green/red Actuator supply status

2484940000/02/12.2019 Manual UR67-Multiprotokoll 15

4.4 UR67-MP-HP-16DIO-12-60M and

Each module has eight connections (M12, 5-pole, A-coded) 4 4 8

L-coded M12 or 7/8" connections. 5 E/IP:

UL green/red Actuator supply status

16 Manual UR67-Multiprotokoll 2484940000/02/12.2019

4.5 Connection assignments

Power supply connection (grey)

2 GND US Earth/reference potential US

3 FE (PE) Functional earthing

2484940000/02/12.2019 Manual UR67-Multiprotokoll 17

4.6 Technical Data

18 Manual UR67-Multiprotokoll 2484940000/02/12.2019

2484940000/02/12.2019 Manual UR67-Multiprotokoll 19

20 Manual UR67-Multiprotokoll 2484940000/02/12.2019

Derating: Total output current IL via ambient temperature TA