SEW-Eurodrive UHX71B User manual

Drive Technology \ Drive Automation \ System Integration \ Services
Manual
UHX71B Controller (Performance Class power)
with OSR71B Fieldbus Interface (EtherNet/IP, Modbus/TCP
and PROFINET)
Edition 04/2013 20101341 / EN

SEW-EURODRIVE—Driving the world

Manual – UHX71B Controller with OSR71B Fieldbus Interface 3
Contents
Contents
1 General information ............................................................................................ 7
1.1 How to use this documentation................................................................... 7
1.2 Structure of the safety notes ....................................................................... 7
1.2.1 Meaning of signal words .............................................................. 7
1.2.2 Structure of the section safety notes ........................................... 7
1.2.3 Structure of the embedded safety notes...................................... 7
1.3 Rights to claim under warranty ................................................................... 8
1.4 Content of the documentation..................................................................... 8
1.5 Exclusion of liability..................................................................................... 8
1.6 Other applicable documentation ................................................................. 8
1.7 Product names and trademarks.................................................................. 8
1.8 Copyright..................................................................................................... 9
2 Safety Notes ...................................................................................................... 10
2.1 General information .................................................................................. 10
2.2 Target group ............................................................................................. 10
2.3 Bus systems.............................................................................................. 11
2.4 Functional safety technology .................................................................... 11
2.5 Hoist applications...................................................................................... 11
3 Introduction ....................................................................................................... 12
3.1 Content of this manual .............................................................................. 12
3.2 Characteristics .......................................................................................... 12
3.2.1 Process data exchange ............................................................. 12
3.2.2 Parameter access...................................................................... 12
3.2.3 Monitoring functions................................................................... 12
4 Assembly and Installation Notes for Ethernet ............................................... 13
4.1 Connecting the UHX71B-OSR71B controller to an Ethernet network ...... 13
4.2 Pin assignment X21 and X22.................................................................... 13
4.2.1 Connection controller / Ethernet ................................................ 14
4.3 Shielding and routing bus cables .............................................................. 14
4.4 The integrated Ethernet switch ................................................................. 15
4.4.1 Auto-crossing............................................................................. 15
4.4.2 Auto-negotiation......................................................................... 15
4.4.3 Notes on multicast handling....................................................... 15
4.5 Status LED ............................................................................................... 15
4.5.1 Status LED in EtherNet/IP operation ......................................... 15
4.5.2 Status LED in PROFINET operation.......................................... 16
4.5.3 Link/Activity LED........................................................................ 17

4Manual – UHX71B Controller with OSR71B Fieldbus Interface
Contents
4.6 TCP/IP addressing and subnetworks........................................................ 18
4.6.1 Introduction ................................................................................ 18
4.6.2 MAC address ............................................................................. 18
4.6.3 IP address.................................................................................. 18
4.6.4 Network classes......................................................................... 19
4.6.5 Subnet mask.............................................................................. 19
4.6.6 Standard gateway...................................................................... 20
4.6.7 DHCP (Dynamic Host Configuration Protocol) .......................... 20
4.7 Setting the IP address parameters ........................................................... 20
4.7.1 Initial startup .............................................................................. 20
4.7.2 Changing the IP address parameters after successful
initial startup............................................................................... 20
4.7.3 Deactivating / activating the DHCP............................................ 21
4.8 Replacing the unit ..................................................................................... 21
5 Configuration and Startup (EtherNet/IP)......................................................... 22
5.1 Validity of the EDS file for UHX71B-OSR71B........................................... 22
5.2 Configuring the master (EtherNet/IP scanner).......................................... 22
5.2.1 Process data exchange ............................................................. 23
5.2.2 Other settings ............................................................................ 25
5.3 Settings in the UHX71B-OSR71B controller ............................................. 25
5.3.1 Process data configuration Ethernet/IP slave and
modbus/TCP.............................................................................. 25
5.3.2 Status of the Ethernet/IP fieldbus interface .............................. 26
5.3.3 Checking the process data communication ............................... 27
5.4 Configuration examples in RSLogix5000 .................................................. 27
5.4.1 UHX71B-OSR71B with 16 PD data exchange .......................... 27
6 Ethernet Industrial Protocol (EtherNet/IP) ...................................................... 29
6.1 Introduction ............................................................................................... 29
6.2 Process data exchange ............................................................................ 29
6.2.1 Timeout response ...................................................................... 29
6.3 CIP object directory................................................................................... 30
6.3.1 Identity object............................................................................. 30
6.3.2 Message router object ............................................................... 31
6.3.3 Assembly object......................................................................... 32
6.3.4 TCP/IP interface object.............................................................. 33
6.3.5 Ethernet link object .................................................................... 33
6.4 General Error Codes................................................................................. 35
7 Configuration and Startup (Modbus/TCP) ...................................................... 36
7.1 Configuration for the master (Modbus scanner) ....................................... 36
7.1.1 Hardware configuration.............................................................. 36
7.1.2 Settings for the Ethernet component ......................................... 37
7.1.3 Addressing the drive using I/O scanning ................................... 38
7.2 Settings in the UHX71B-OSR71B controller ............................................. 39
7.2.1 Process data configuration ........................................................ 39

Manual – UHX71B Controller with OSR71B Fieldbus Interface 5
Contents
7.3 Project planning example in PL7 PRO...................................................... 39
7.3.1 UHX71B-OSR71B controller with 16 PD data exchange........... 39
7.4 Examples for data exchange via Modbus/TCP......................................... 41
7.4.1 Writing and reading process data .............................................. 42
8 Modbus Protocol (Modbus/TCP) ..................................................................... 44
8.1 Introduction ............................................................................................... 44
8.1.1 Mapping and addressing ........................................................... 44
8.1.2 Services (function codes) .......................................................... 45
8.1.3 Access ....................................................................................... 45
8.2 Protocol structure ...................................................................................... 45
8.2.1 Header ....................................................................................... 46
8.2.2 Service FC3 – Read Holding Registers ..................................... 47
8.2.3 FC16 – Write Multiple Registers ................................................ 48
8.2.4 Service FC23 – Read/Write Multiple Registers ......................... 49
8.2.5 Service FC43 - Read Device Identification ................................ 50
8.3 Connection management.......................................................................... 51
8.3.1 Sending process output data (requesting controlling
connection) ................................................................................ 51
8.3.2 Dropping connections ................................................................ 51
8.3.3 Timeout monitoring .................................................................... 51
9 Error Diagnostics for Operation on EtherNet/IP and Modbus/TCP .............. 52
9.1 Diagnostic procedure ................................................................................ 52
9.1.1 Step 1: Checking the LED status............................................... 52
9.1.2 Step 2: Check the Status LED and the Status display of the
master (scanner)........................................................................ 52
9.1.3 Step 3: Error diagnostics ........................................................... 52
10 PROFINET IO Configuration............................................................................. 54
10.1 Installing the GSDML file for UHX71B-OSR71B ....................................... 54
10.2 Assigning a PROFINET device name ....................................................... 55
10.3 Configuring the PROFINET interface for the UHX71B-OSR71B
controller ................................................................................................... 56
10.3.1 Creating a new project............................................................... 56
10.3.2 Configuring a node .................................................................... 58
10.4 PROFINET configuration with topology detection..................................... 59
10.4.1 Introduction ................................................................................ 59
10.4.2 Creating a PROFINET IO project and starting the topology
editor.......................................................................................... 59
10.4.3 Specifying the topology and detecting faulty connections ......... 60
10.4.4 Changing port properties ........................................................... 62
10.4.5 Topology diagnostics ................................................................. 64
10.4.6 Port statistics ............................................................................. 65
11 Operating Behavior on PROFINET IO ............................................................. 67
11.1 Process data exchange with the SEW controller ...................................... 67
11.1.1 Control example for SIMATIC S7 .............................................. 67

6Manual – UHX71B Controller with OSR71B Fieldbus Interface
Contents
11.2 Settings in the UHX71B-OSR71B controller ............................................. 69
11.2.1 Process data configuration of the PROFINET slave.................. 69
11.2.2 Status of the PROFINET fieldbus interface .............................. 69
11.2.3 Checking the process data communication ............................... 70
12 Error Diagnostics on PROFINET ..................................................................... 71
12.1 Diagnostic procedures .............................................................................. 71
12.1.1 Diagnostic problem 1: UHX71B-OSR71B does not work on
PROFINET IO............................................................................ 72
12.1.2 Diagnostic problem 2: No process data exchange with the I/O
controller .................................................................................... 73
13 Appendix............................................................................................................ 74
13.1 Overview of parameters ........................................................................... 74
13.1.1 Bus independent parameters..................................................... 74
13.1.2 Bus dependent parameters ....................................................... 75
Index................................................................................................................... 76

Manual – UHX71B Controller with OSR71B Fieldbus Interface 7
1
How to use this documentation
General information
1 General information
1.1 How to use this documentation
The documentation is an integral part of the product and contains important information
on operation and service. The documentation is written for all employees who assemble,
install, start up, and service this product.
The documentation must be accessible and legible. Make sure that persons responsible
for the system and its operation, as well as persons who work independently on the unit,
have read through the documentation carefully and understood it. If you are unclear
about any of the information in this documentation, or if you require further information,
contact SEW-EURODRIVE.
1.2 Structure of the safety notes
1.2.1 Meaning of signal words
The following table shows the grading and meaning of the signal words for safety notes,
warnings regarding potential risks of damage to property, and other notes.
1.2.2 Structure of the section safety notes
Section safety notes do not apply to a specific action but to several actions pertaining to
one subject. The symbols used either indicate a general hazard or a specific hazard.
This is the formal structure of a section safety note:
1.2.3 Structure of the embedded safety notes
Embedded safety notes are directly integrated in the instructions just before the descrip-
tion of the dangerous action.
This is the formal structure of an embedded safety note:
•SIGNAL WORD Type and source of danger.
Possible consequence(s) if disregarded.
– Measure(s) to prevent the danger.
Signal word Meaning Consequences if disregarded
DANGER Imminent danger Severe or fatal injuries
WARNING Possible dangerous situation Severe or fatal injuries
CAUTION Possible dangerous situation Minor injuries
NOTICE Possible damage to property Damage to the drive system or its envi-
ronment
INFORMATION Useful information or tip: Simpli-
fies the handling of the drive
system.
SIGNAL WORD
Type and source of danger.
Possible consequence(s) if disregarded.
• Measure(s) to prevent the danger.

8Manual – UHX71B Controller with OSR71B Fieldbus Interface
1Rights to claim under warranty
General information
1.3 Rights to claim under warranty
A requirement of fault-free operation and fulfillment of any rights to claim under limited
warranty is that you adhere to the information in the documentation. Therefore read the
documentation before you start working with the unit.
1.4 Content of the documentation
This document contains additional safety-related information and conditions for opera-
tion in safety-related applications.
1.5 Exclusion of liability
You must comply with the information contained in this documentation to ensure safe
operation and to achieve the specified product characteristics and performance fea-
tures. SEW-EURODRIVE assumes no liability for injury to persons or damage to equip-
ment or property resulting from non-observance of these operating instructions. In such
cases, any liability for defects is excluded.
1.6 Other applicable documentation
Observe the following applicable documents:
• "Controller UHX71B (performance class power)" manual
•"MOVI-PLC
®Programming in the PLC Editor" manual
The following publications and documents apply to the connected units:
• Operating instructions of the units
(Units are, for example, MOVIDRIVE®B, MOVITRAC®B, MOVIAXIS®)
• For units with functional safety technology, also the respective
"Functional Safety" manuals
Make sure you always use the latest documentation.
Our documentation is available in various languages for download from the SEW
homepage (www.sew-eurodrive.com). If you are unclear about any of the information in
this documentation or if you require further information, consult SEW-EURODRIVE.
If required, you can order printed copies of the documentation from SEW-EURODRIVE.
1.7 Product names and trademarks
All product names in this documentation are trademarks or registered trademarks of
their respective titleholders.

Manual – UHX71B Controller with OSR71B Fieldbus Interface 9
1
Copyright
General information
1.8 Copyright
© 2013 – SEW-EURODRIVE. All rights reserved.
Unauthorized duplication, modification, distribution or any other use of the whole or any
part of this documentation is strictly prohibited.

10 Manual – UHX71B Controller with OSR71B Fieldbus Interface
2General information
Safety Notes
2 Safety Notes
2.1 General information
The following basic safety notes must be read carefully to prevent injury to persons and
damage to property. The operator must ensure that the basic safety notes are read and
adhered to.
Ensure that persons responsible for the machinery and its operation as well as persons
who work independently have read through the documentation carefully and understood
it. If you are unclear about any of the information in this documentation or if you require
further information, please contact SEW-EURODRIVE.
The following safety notes refer to the use of the software. Also adhere to the supple-
mentary safety notes in this document and in the documentation of the connected
devices from SEW-EURODRIVE.
This document does not replace the detailed documentation of the connected devices.
This document assumes that the user has access to and is familiar with the documen-
tation for all connected devices from SEW-EURODRIVE.
Never install or start up damaged products. Submit a complaint to the shipping company
immediately in the event of damage.
During operation, the devices may have live, uninsulated, and sometimes moving or
rotating parts as well as hot surfaces depending on their degree of protection.
Removing covers without authorization, improper use as well as incorrect installation or
operation may result in severe injuries to persons or damage to property. Refer to the
documentation for additional information.
2.2 Target group
Any work with the software may only be performed by adequately qualified personnel.
Qualified personnel in this context are persons who have the following qualifications:
• Appropriate instruction.
• Knowledge of this documentation and other applicable documentation.
• SEW-EURODRIVE recommends additional product training for products that are
operated using this software.
Any mechanical work on connected units may only be performed by adequately quali-
fied personnel. Qualified personnel in the context of this documentation are persons
familiar with the design, mechanical installation, troubleshooting and servicing of the
product who possess the following qualifications:
• Training in mechanical engineering, e.g. as a mechanic or mechatronics technician
(final examinations must have been passed).
• Knowledge of this documentation and other applicable documentation.

Manual – UHX71B Controller with OSR71B Fieldbus Interface 11
2
Bus systems
Safety Notes
Any electrical work on connected units may only be performed by adequately qualified
electricians. Qualified electricians in the context of this documentation are persons
familiar with electrical installation, startup, troubleshooting and servicing of the product
who possess the following qualifications:
• Training in electrical engineering, e.g. as an electrician or mechatronics technician
(final examinations must have been passed).
• Knowledge of this documentation and other applicable documentation.
• Knowledge of the relevant safety regulations and laws.
• Knowledge of the other standards, guidelines, and laws mentioned in this documen-
tation.
The above mentioned persons must have the authorization expressly issued by the
company to operate, program, configure, label and ground units, systems and circuits in
accordance with the standards of safety technology.
All work in further areas of transportation, storage, operation and waste disposal must
only be carried out by persons who are trained appropriately.
2.3 Bus systems
A bus system makes it is possible to adapt frequency inverters and/or motor starters to
the specific conditions of the machinery within wide limits. This results in the risk that a
change of parameters that cannot be detected externally can result in unexpected,
though not uncontrolled, system behavior.
2.4 Functional safety technology
The inverters and servo drives controlled by the SEW controller may not execute any
safety functions without higher-level safety systems unless they are described in the rel-
evant documentation and expressly approved.
Use higher-level safety systems to ensure protection of equipment and personnel.
2.5 Hoist applications
MOVIDRIVE®B, MOVITRAC®B, MOVIAXIS®, MOVIPRO®and MOVIFIT®must not be
used as a safety device in hoist applications.
Use monitoring systems or mechanical protection devices as safety equipment to avoid
possible damage to property or injury to people.

12 Manual – UHX71B Controller with OSR71B Fieldbus Interface
3Content of this manual
Introduction
3 Introduction
3.1 Content of this manual
This user manual illustrates:
• Startup of the UHX71B-OSR71B controller on the fieldbus systems EtherNet/IP,
Modbus/TCP and PROFINET IO.
• The configuration of the EtherNet/IP master with EDS files.
• The configuration of the Modbus/TCP master.
• The configuration of the PROFINET master using GSDML files.
The creation of IEC programs or the connection of SEW drives to the system bus inter-
faces of the controller is not described.
3.2 Characteristics
Due to its powerful universal fieldbus interfaces, the UHX71B-OSR71B controller allows
for the connection to higher-level automation systems via EtherNet/IP, Modbus/TCP
and PROFINET IO.
3.2.1 Process data exchange
Via the PROFIBUS interface, the UHX71B-OSR71B controller provides digital access
to a special data section the IEC 61131-3 evaluates as process input and output data to
a higher-level controller. The meaning of the transferred data depends on the IEC pro-
gram.
3.2.2 Parameter access
The UHX71B-OSR71B controller does not support the MOVILINK®parameter channel.
The "MultiMotion" program provides a bus-dependent, cyclical parameter channel. For
further information refer to the publication "MultiMotion for MOVI-PLC®".
3.2.3 Monitoring functions
Using a fieldbus system requires additional monitoring functions, for example, time mon-
itoring of the fieldbus (fieldbus timeout) or rapid stop concepts. For example, you can
adapt the monitoring functions specifically to your application in the IEC program. You
can determine, for instance, which error responses should be triggered in the event of a
bus error. For many applications, a rapid stop function is useful. However, you can also
freeze the last setpoints so that the drive continues to operate with the most recently
valid setpoints. As the range of functions for the control terminals is also guaranteed in
fieldbus mode, you can continue to implement rapid stop concepts using the terminals
of the UHX71B-OSR71B controller, irrespective of the fieldbus used.
P
i
f
kVA
Hz
n

Manual – UHX71B Controller with OSR71B Fieldbus Interface 13
4
Connecting the UHX71B-OSR71B controller to an Ethernet network
Assembly and Installation Notes for Ethernet
4 Assembly and Installation Notes for Ethernet
4.1 Connecting the UHX71B-OSR71B controller to an Ethernet network
This chapter only describes the connection to Ethernet networks via X21 and X22. Con-
nection and functionality via X37 (engineering) are described in the "UHX71B (Perfor-
mance Class power)" manual.
4.2 Pin assignment X21 and X22
Use prefabricated, shielded RJ45 plug connectors compliant with IEC 11801, edition
2.0, category 5.
Front view
UHX71B with OSR71B (Ethernet) Designation LED Terminal Function
7995857803
LED LED 23.1
LED 23.2
LED 23.3
LED 23.4
Reserved
Reserved
Ethernet Communication status
System status
X21: Ethernet connection
LED Link (green)
LED Activity (yellow)
X22: Ethernet connection
LED Link (green)
LED Activity (yellow)
LAN3 LAN4
USB1 USB2 USB3
X1
On M
-24+
L23.1 L23.4
X21 X22 L23.1
L23.4
X21 X22
6139704459
A View from front B View from back
[1] Pin 1 TX+ Transmit Plus [2] Pin 2 TX– Transmit Minus
[3] Pin 3 RX+ Receive Plus [6] Pin 6 RX– Receive Minus
[3] [2] [1]
236
1
[6]
AB

14 Manual – UHX71B Controller with OSR71B Fieldbus Interface
4Shielding and routing bus cables
Assembly and Installation Notes for Ethernet
4.2.1 Connection controller / Ethernet
To connect the UHX71B-OSR71B controller to the Ethernet network, connect the Ether-
net interface X21 or X22 (RJ45 plug connector) to the other network stations using a cat-
egory 5, class D twisted-pair cable in accordance with IEC 11801 edition 2.0. The inte-
grated switch assists you in implementing a line topology and provides auto-crossing
functions.
4.3 Shielding and routing bus cables
Only use shielded cables and connection elements that meet the requirements of cate-
gory 5, class D according to IEC 11801 edition 2.0.
Correct shielding of the bus cable attenuates electrical interference that can occur in in-
dustrial environments. The following measures ensure the best possible shielding:
• Manually tighten the mounting screws on the connectors, modules, and equipotential
bonding conductors.
• Use only connectors with a metal housing or a metalized housing.
• Connect the shielding in the connector over a wide surface area.
• Apply the shielding of the bus cable on both ends.
• Route signal and bus cables in separate cable ducts. Do not route them parallel to
power cables (motor leads).
• Use metallic, grounded cable racks in industrial environments.
• Route the signal cable and the corresponding equipotential bonding close to each
other using the shortest possible route.
• Avoid using plug connectors to extend bus cables.
• Route the bus cables closely along existing grounding surfaces.
INFORMATION
• According to IEC 802.3, the maximum cable length for 10/100 MBaud Ethernet
(10BaseT / 100BaseT), e.g. between 2 network stations, is 100 m.
• We recommend that you do not directly connect non-SEW end devices to the
UHX71B-OSR71B controller in order to minimize the load on the end devices in
EtherNet/IP networks caused by undesired multicast data traffic. Connect non-
SEW devices via a network component that supports the IGMP snooping function-
ality (e.g. managed switch).
INFORMATION
In case of fluctuations in the ground potential, a compensating current may flow via the
bilaterally connected shield that is also connected to the protective earth (PE). Make
sure you supply adequate equipotential bonding in accordance with relevant VDE reg-
ulations in such a case.

Manual – UHX71B Controller with OSR71B Fieldbus Interface 15
4
The integrated Ethernet switch
Assembly and Installation Notes for Ethernet
4.4 The integrated Ethernet switch
You can use the integrated Ethernet switch to achieve line topologies known from the
fieldbus technology. Other bus topologies, such as star or tree, are also possible. Ring
topologies are not supported.
4.4.1 Auto-crossing
The two ports leading out of the Ethernet switch have auto-crossing functionality. This
means that they can use both patch and cross-over cables to connect to the next Ether-
net node.
4.4.2 Auto-negotiation
The baud rate and duplex mode are negotiated by both Ethernet nodes when establish-
ing the connection. For this purpose, both Ethernet ports of the EtherNet/IP connection
support an auto-negotiation functionality and work with a baud rate of either 100 Mbit or
10 Mbit in full duplex or half-duplex mode.
4.4.3 Notes on multicast handling
• The integrated Ethernet switch does not provide a filter function for Ethernet multi-
cast telegrams. Multicast telegrams that are usually sent in Ethernet/IP networks
from the adapters (UHX71B-OSR71B controller) to the scanners (PLC) are passed
on to all switch ports.
• IGMP Snooping (e.g. Managed Switches) is not supported.
• SEW-EURODRIVE therefore recommends to connect the UHX71B-OSR71B con-
troller in EtherNet/IP networks only with network components that support IGMP
snooping (e.g. managed switch) or that have safety mechanisms integrated against
excess multicast load (e.g. units from SEW-EURODRIVE). Units that do not have
this integrated function can fail due to high network loads.
4.5 Status LED
The LEDs of the UHX71B-OSR71B controller indicate the current status of the UFR41B
option and the fieldbus system. Depending on the set protocol, the LEDs have the fol-
lowing meaning.
4.5.1 Status LED in EtherNet/IP operation
LED L23.2 The LED L23.2 (NETWORK STATUS) indicates the state of the fieldbus system.
INFORMATION
The number of industrial Ethernet switches connected in line impacts the telegram
runtime. If a telegram passes through the units, the telegram runtime is delayed by the
store & forward function of the Ethernet switch:
• For a telegram length of 64 bytes by approximately 10 µs (at 100 Mbit/s)
• For a telegram length of 1500 bytes by approximately 130 µs (at 100 Mbit/s)
This means the more units a telegram has to pass through, the higher the telegram
runtime is.
State of LED 23.2 Meaning
Off The UHX-OSR71B controller does not yet have any IP parameters.

16 Manual – UHX71B Controller with OSR71B Fieldbus Interface
4Status LED
Assembly and Installation Notes for Ethernet
LED L23.3 LED L23.3 (MODULE STATUS) indicates that the bus electronics are operating cor-
rectly.
LED L23.4 LED 23.4 (SYS) indicates the proper functioning of the fieldbus electronics (hardware).
4.5.2 Status LED in PROFINET operation
LED L23.2 The LED L23.2 (BUS FAULT) shows the status of the PROFINET.
LED L23.3 LED L23.3 (SYS FAULT) indicates that the bus electronics are operating correctly.
Flashing green/red The UHX-OSR71B performs a self test.
Flashing green There is no controlling IO connection.
Green There is a controlling EtherNet/IP connection.
Red Conflict detected in the assigned IP addresses. Another station in the network
uses the same IP address.
Flashing red The previously established controlling IO connection is in timeout state. The state
is reset by restarting communication.
State of LED 23.2 Meaning
State of LED 23.3 Meaning
Off The UHX71B-OSR71B controller is either not supplied with voltage or it is faulty.
Flashing green Device has not been configured yet and is in "Standby" state.
Flashing green/red The UHX71B-OSR71B controller performs a self test.
Green The UHX71B-OSR71B controller is in normal operating state.
Red The UHX71B-OSR71B controller is in error state.
Flashing red Conflict detected in the assigned IP addresses. Another station in the network
uses the same IP address.
State of LED 23.4 Diagnostics Troubleshooting
Green The fieldbus hardware is OK. -
Orange Hardware is being initialized. -
State of LED L23.2 Cause of error Troubleshooting
Off PROFINET IO device is currently
exchanging data with the PROFINET
IO controller (Data Exchange).
-
Flashing red at 2 Hz No data exchange. -
Red • Connection to the PROFINET IO
controller has failed.
• PROFINET IO device does not
detect a link.
• Bus interruption
• PROFINET IO controller is not in
operation
• Check the PROFINET connection
of the UHX71B-OSR71B controller
• Check the PROFINET IO control-
ler.
• Check the cabling of your PROFI-
NET network
State of LED L23.3 Cause of error Troubleshooting
Off No error
Switch the unit on again. Consult SEW
Service if the error occurs again.
Red Error in the UHX71B-OSR71B con-
troller hardware.
Flashing red 2 Hz, for 3
s
DCP Signal Service is triggered via
fieldbus. The flashing function in the
PROFINET IO controller configura-
tion is activated to visually localize
the stations.

Manual – UHX71B Controller with OSR71B Fieldbus Interface 17
4
Status LED
Assembly and Installation Notes for Ethernet
LED L23.4 LED 23.4 (SYS) indicates the proper functioning of the fieldbus electronics (hardware).
4.5.3 Link/Activity LED
The two LEDs Link (green) and Activity (yellow) integrated in the RJ45 plug connec-
tors (X21, X22) display the state of the Ethernet connection.
State of LED 23.4 Diagnostics Troubleshooting
Green The fieldbus hardware is OK. -
Orange Hardware is being initialized. -
7869987467
LED/state Meaning
Link/green There is an Ethernet connection.
Link/off There is no Ethernet connection.
Link/flashes Locating function of SEW Address Editor (see chapter 4.8)
Activity/yel-
low
Data is currently being exchanged via Ethernet.
X22
X21
LED "Link"
LED "Activity"

18 Manual – UHX71B Controller with OSR71B Fieldbus Interface
4TCP/IP addressing and subnetworks
Assembly and Installation Notes for Ethernet
4.6 TCP/IP addressing and subnetworks
4.6.1 Introduction
The settings for the address of the IP protocol are made using the following parameters:
• MAC address
• IP address
• Subnet mask
• Standard gateway
The addressing mechanisms and subdivision of the IP networks into subnetworks are
explained in this chapter to help you set the parameters correctly.
4.6.2 MAC address
The MAC address (Media Access Controller) is the basis for all address settings. The
MAC address of an Ethernet device is a worldwide unique 6-byte value (48 bits). The
MAC address of SEW Ethernet devices is 00-0F-69-xx-xx-xx. The MAC address is dif-
ficult to handle for larger networks. This is why freely assignable IP addresses are used.
4.6.3 IP address
The IP address is a 32-bit value that uniquely identifies a node in the network. An IP ad-
dress is represented by 4 decimal numbers separated by decimal points.
Example: 192.168.10.4
Each decimal number stands for one byte (= 8 bits) of the address and can also be rep-
resented using binary code (see following table).
The IP address comprises a network address and a node address (→following table).
The part of the IP address that denotes the network and the part that identifies the node
is determined by the network class and the subnet mask.
Node addresses cannot consist of only zeros or ones (binary) because they represent
the network itself or a broadcast address.
Byte 1 Byte 2 Byte 3 Byte 4
11000000 . 10101000 . 00001010 . 00000100
Network address Node address
192.168.10 4

Manual – UHX71B Controller with OSR71B Fieldbus Interface 19
4
TCP/IP addressing and subnetworks
Assembly and Installation Notes for Ethernet
4.6.4 Network classes
The first byte of the IP address determines the network class and as such represents
the division into network addresses and node addresses.
This rough division is not sufficient for a number of networks. They also use an explicit,
adjustable subnet mask.
4.6.5 Subnet mask
A subnet mask is used to divide the network classes into even finer sections. Like the
IP address, the subnet mask is represented by 4 decimal numbers separated by decimal
points.
Example: 255,255,255,128
Each decimal number stands for one byte (= 8 bits) of the subnet mask and can also be
represented using binary code (→following table).
If you compare the IP addresses with the subnet masks, you see that in the binary rep-
resentation of the subnet mask all ones determine the network address and all the zeros
determine the station address (see following table).
The class C network with the address 192.168.10. is further subdivided by the subnet
mask 255.255.255.128. 2 networks are created with the address 192.168.10.0 and
192.168.10.128.
The following node addresses are permitted in the two networks:
• 192.168.10.1 ... 192.168.10,126
• 192.168.10,129 ... 192.168.10,254
The network nodes use a logical AND operation for the IP address and the subnet mask
to determine whether there is a communication partner in the same network or in a dif-
ferent network. If the communication partner is in a different network, the standard gate-
way is addressed for passing on the data.
Value range Network class Complete network address
(Example) Meaning
Byte 1
0 ... 127 A 101.22.3 10 = Network address
1.22.3 = Node address
128 ... 191 B 17216.52.4 172.16 = Network address
52.4 = Node address
192 ... 223 C 192.168.10.4 192.168.10 = Network address
4 = Node address
Byte 1 Byte 2 Byte 3 Byte 4
11111111 . 11111111 . 11111111 . 10000000
Byte 1 Byte 2 Byte 3 Byte 4
IP address decimal 192 . 168. . 10 . 129
binary 11000000 . 10101000 . 00001010 . 10000001
Subnet mask decimal 255 . 255 . 255 . 128
binary 11111111 . 11111111 . 11111111 . 10000000

20 Manual – UHX71B Controller with OSR71B Fieldbus Interface
4Setting the IP address parameters
Assembly and Installation Notes for Ethernet
4.6.6 Standard gateway
The standard gateway is also addressed via a 32-bit address. The 32-bit address is rep-
resented by 4 decimal numbers separated by decimal points.
Example: 192.168.10.1
The standard gateway establishes a connection to other networks. In this way, a net-
work station that wants to address another station can use a logical AND operation with
the IP address and the subnet mask to determine whether the desired station is located
in the same network. If this is not the case, the node addresses the standard gateway
(router), which must be part of the actual network. The standard gateway then takes on
the job of transmitting the data packages.
If for the standard gateway, the same address is set as for the IP address, the standard
gateway is deactivated. The address of the standard gateway and the IP address must
be in the same subnetwork.
4.6.7 DHCP (Dynamic Host Configuration Protocol)
Instead of setting the 3 parameters IP address, subnet mask and standard gateway
manually, they can be assigned automatically by a DHCP server in the Ethernet net-
work.
This means the IP address is assigned from a table, which contains the allocation of
MAC address to IP address.
Parameter P785 indicates whether the UHX71B-OSR71B controller expects the IP pa-
rameters to be assigned manually or via DHCP.
4.7 Setting the IP address parameters
4.7.1 Initial startup
The "DHCP" protocol (Dynamic Host Configuration Protocol) is activated as the default
setting for the UHX71B-OSR71B controller. This means that the option card expects its
IP address parameters from a DHCP server.
Once the DHCP server has been configured and the settings have been made for the
subnetwork screen and the standard gateway, the UHX71B-OSR71B controller must be
inserted in the assignment list of the DHCP server. The MAC ID of the UHX71B-
OSR71B controller is allocated a valid IP address.
4.7.2 Changing the IP address parameters after successful initial startup
If the UHX71B-OSR71B controller was started using a valid IP address, you can also
access the IP address parameters via the Ethernet interface.
INFORMATION
There is a free DHCP server available on the Rockwell Automation homepage. The
tool is known as "BOOTP Utility" and can be downloaded from the following website:
http://www.ab.com/networks/bootp.html.
INFORMATION
The configured IP address parameters are permanently adopted into the parameter
set if DHCP is deactivated after the IP address has been assigned.