The manual is part of the product and contains important information on operation and
service. The manual is written for all employees who assemble, install, startup, and
service the product.
The manual 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 manual carefully and understood it. If you are unclear about any of the
information in this documentation, or if you require further information, contact SEWEURODRIVE.
1.2Structure of the safety notes
The safety notes in this manual are structured as follows:
PictogramSIGNAL WORD
Type and source of danger.
Possible consequence(s) if the safety notes are disregarded.
•Measure(s) to prevent the danger.
PictogramSignal wordMeaningConsequences if
disregarded
Example:
General danger
Specific danger,
e.g. electric shock
DANGERImminent dangerSevere or fatal injuries
WARNINGPossible dangerous situationSevere or fatal injuries
CAUTIONPossible dangerous situationMinor injuries
NOTICEPossible damage to propertyDamage to the drive system or its environ-
ment
TIPUseful information or tip.
Simplifies the handling of the
drive system.
Manual – Fieldbus Gateway UFR41B EtherNet/IP, Modbus/TCP and PROFINET IO
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 manual. Therefore, read the manual
before you start operating the device.
1.4Exclusion of liability
You must comply with the information in the manual and the documentation of the units
connected to the fieldbus gateway to ensure safe operation and to achieve the specified
product characteristics and performance features. SEW-EURODRIVE assumes no
liability for injury to persons or damage to equipment or property resulting from nonobservance of the operating instructions. In such cases, any liability for defects is
excluded.
•Installation and startup may be carried out only by trained personnel observing the
relevant accident prevention regulations and the following documents:
– "MOVIDRIVE
– "MOVITRAC
– "MOVIAXIS
•Read through these documents carefully before you commence installation and
startup of the UFR41B fieldbus gateway.
•As a prerequisite to fault-free operation and fulfillment of warranty claims, you must
adhere to the information in the documentation.
2.2General safety notes for bus systems
This communication system lets you adjust inverters and servo inverters to a variety of
different applications. As with all bus systems, there is a danger of invisible, external (as
far as the inverter is concerned) modifications to the parameters which give rise to
changes in the unit behavior. This may result in unexpected (not uncontrolled) system
behavior.
®
MDX60B/61B" operating instructions
®
B" operating instructions
®
" operating instructions
Safety Notes
2
2.3Safety functions
The inverters and servo drives are not allowed to perform any safety functions unless
they are subordinate to other safety systems. Use higher-level safety systems to ensure
protection of equipment and personnel.
For safety applications, ensure that the information in the following publications is
observed: "Safe Disconnection for MOVIDRIVE
2.4Hoist applications
MOVIDRIVE® MDX60B/61B, MOVITRAC® B and MOVIAXIS® 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.
2.5Product names and trademarks
The brands and product names contained within this manual are trademarks or
registered trademarks of the titleholders.
®
B / MOVITRAC® B / MOVIAXIS®".
Manual – Fieldbus Gateway UFR41B EtherNet/IP, Modbus/TCP and PROFINET IO
•Connect the UFR41B fieldbus gateway to MOVIDRIVE
and to the MOVIAXIS
•Startup MOVIDRIVE
•Startup the fieldbus gateway UFR41B on the fieldbus system EtherNet/IP,
Modbus/TCP and PROFINET IO.
•Configure the EtherNet/IP master with EDS files.
•Configure the Modbus/TCP master.
•Configure the PROFINET IO master using GSD files.
3.2Characteristics
Introduction
Content of the manual
®
®
servo inverter.
®
B, MOVITRAC® B and MOVIAXIS® for gateway operation.
B, MOVITRAC® B inverters
3
The powerful, universal fieldbus interfaces of the UFR41B fieldbus gateway enable you
to use the option to connect to higher-level automation systems via EtherNet/IP,
Modbus/TCP and PROFINET IO.
3.2.1Process data exchange
The UFR41B fieldbus gateway allows for digital access to most parameters and
functions via EthernetNet/IP, Modbus/TCP, and PROFINET IO interfaces. Control is
performed via fast, cyclic process data. Via this process data channel, you can enter
setpoints and trigger various control functions, such as enable, normal stop, rapid stop,
etc. At the same time you can also use this channel to read back actual values, such as
actual speed, current, unit status, error number or reference signals.
3.2.2Parameter access
In EtherNet/IP operation, the parameters of the inverter are set solely via explicit
messages.
In Modbus/TCP operation, the controller can access the parameters via the 8 byte
MOVILINK
In PROFINET operation, two parameter access options are available:
•The PROFIDRIVE data record 47 offers access to all unit information also in
PROFINET operation
•The parameter mechanism offers universal access to any unit information
®
parameter channel.
Manual – Fieldbus Gateway UFR41B EtherNet/IP, Modbus/TCP and PROFINET IO
Using a fieldbus system requires additional monitoring functions, for example, time
monitoring of the fieldbus (fieldbus timeout) or rapid stop concepts. You can determine,
for instance, which fault responses should be triggered in the event of a bus error. The
parameters for the fault response can be set in the servo inverter / inverter. A rapid stop
is useful for many applications. This is why the fieldbus gateway will stop the lower-level
drives in the event of a fieldbus timeout. 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 servo inverters/inverters connected to the fieldbus gateway.
12
Manual – Fieldbus Gateway UFR41B EtherNet/IP, Modbus/TCP and PROFINET IO
Voltage supply, system bus and fieldbus interfaces as well as the engineering interface
are located at different potential levels (see chapter 13.1).
4.2.1Voltage supply in the MOVIAXIS
®
master module
TIP
The MOVIAXIS® master module MXM provides additional connections, which are
described in the following section.
Functional description of the terminals, X5a/X5b (MOVIAXIS
MOVIAXIS® master
module MXM
1
X5b
2
3
4
1
X5a
2
3
4
59233AXX
•The X5a and X5b connectors are connected in parallel. In this way, the voltage
supply of the MOVIAXIS
from below to X5a. With connection to X5a, further modules can be connected via
X5b (e.g. supply module, axis module). The voltage supply for the brake (X5a/b:3, 4)
is fed through the MOVIAXIS
•The UFR41B fieldbus gateway can be supplied from the MOVIAXIS
power supply (MXS) or from an external voltage source. To do so, connect X5
between the individual units.
•If the UFR41B fieldbus gateway is connected with DC 24 V from the MOVIAXIS
switched-mode power supply, the functioning of the option is maintained after disconnection from the power supply. This is the case if the DC link voltage is maintained or an external DC 24 V supply is present from the MOVIAXIS
power supply.
DesignationTerminalFunction
X5b connectorX5b:1
X5a connectorX5a:1
®
X5b:2
X5b:3
X5b:4
X5a:2
X5a:3
X5a:4
master module can be provided from the right to X5b or
®
master module.
®
master module)
DC 24 V
DGND
DC 24 V
BGND
DC 24 V
DGND
DC 24 V
BGND
Voltage supply for control electronics
E
Reference potential for control
electronics
B
Voltage supply for brake
Reference potential for brake
connection
Voltage supply for control electronics
E
Reference potential for control
electronics
B
Voltage supply for brake
Reference potential for brake
connection
®
switched-mode
®
switched-mode
®
14
Manual – Fieldbus Gateway UFR41B EtherNet/IP, Modbus/TCP and PROFINET IO
System bus CAN 1 high
System bus CAN 1 low
Reference potential control/CAN1
-
Reference potential for UFx41B
Voltage supply for controller
Designation
LEDH1
X24 connector:
RJ10 socket
DesignationTerminalFunction
X26 connector:
CAN 1 and
voltage supply
(plug-in terminal)
Connection of CAN 1 system bus / voltage supply (X26 connector)
The connections for CAN 1 (X26:1/2/3 and connector X33) are connected in parallel.
The UFR41B fieldbus gateway is supplied with voltage in the UOH21B gateway housing
via X26:6/7.
16
Manual – Fieldbus Gateway UFR41B EtherNet/IP, Modbus/TCP and PROFINET IO
4.3.1Functional description of the terminals, DIP switch es and LED of the UFR41B option
Connectors, LEDs and DIP switches in the upper area of the UFR41B fieldbus gateway
allow for connection to EtherNet/IP (see chapter "Connecting the UFR41B fieldbus system to an EtherNet/IP network"), Modbus/TCP (see chapter "Connecting the UFR41B
fieldbus to a Modbus/TCP network") and PROFINET IO fieldbus systems (see chapter
"Connecting the UFR41B fieldbus gateway to a PROFINET IO network")
4
Front view
UFR41B fieldbus
gateway
64418AXX
LED
Designation
DIP switch
Terminal
LEDLED 1
LED 2
LED 3
LED 4
LED 5
X35 connector:
USB connection
X35:1
X35:2
X35:3
X35:4
X36 connector:
X36
Connection of an EtherCAT based
system bus (RJ45 socket)
X37 connector:
X37Ethernet for engineering
Ethernet connection
(RJ45 socket)
X32 connector:
System bus CAN 2
(electrically isolated)
X32:1
X32:2
X32:3
(plug-in terminals)
X33 connector:
System bus CAN 1
(plug-in terminals)
X33:1
X33:2
X33:3
DIP switchS1
Memory cardM1
ButtonT1
CAN 1 status
CAN 2 status
Program status
Gateway status
Gateway error
USB+5 V
USBUSB+
DGND
Standard Ethernet
assignment
BZG_CAN 2
CAN 2H
CAN 2L
DGND
CAN 1H
CAN 1L
To p
Bottom
Function
Status of CAN 1 system bus
Status of CAN 2 system bus
Status of gateway program
Status of gateway firmware
Status of gateway error (see section "Error messages of the fieldbus gateway")
DC 5 V voltage supply
USB- signal
USB+ signal
Reference potential
plus
System bus SBUS
(in preparation)
Reference potential for system bus CAN 2
System bus CAN 2 high
System bus CAN 2 low
Reference potential for system bus CAN 1
System bus CAN 1 high
System bus CAN 1 low
Default IP address (192.168.10.4)
IP parameter from SD memory card
Memory for firmware, gateway application,
gateway configuration, and inverter parameters
For Bootloader update
(see section "SD memory card OMG4.B")
Manual – Fieldbus Gateway UFR41B EtherNet/IP, Modbus/TCP and PROFINET IO
4.3.2Connecting CAN 1 system bus (X33 connector)/ CAN 2 (X32 connector)
Do not connect more than 16 units to the CAN 1 or CAN 2 system bus in gateway
operation.
TIPS
•The CAN 1 system bus is not electrically isolated. Therefore, it is recommended to
use the CAN 1(X33 or X26 with UFR41B/UOH21B) interface to connect inverters
via the system bus in the control cabinet. Set the P881 SBus address parameter in
increasing order to values 1 - 16 if the slave unit is connected to CAN 1 or the fieldbus gateway.
•The CAN 2 system bus is electrically isolated. Therefore, preferably use interface
CAN 2 (X32) for connecting field units or units in other control cabinets. Set the
P881 SBus address parameter in increasing order to values 17 - 34 if the unit is
connected to CAN 2 or the fieldbus gateway.
The CAN system bus supports transmission systems compliant with ISO 11898. For
detailed information on the CAN system bus, refer to the "MOVIDRIVE
®
Communication
and Fieldbus Device Profile" manual. You can order this manual from SEWEURODRIVE.
®
Wiring diagram for MOVIDRIVE
B, MOVITRAC® B on CAN 1 system bus
64714AXX
Cable specification•Use a 2 x 2-core twisted and shielded copper cable (data transmission cable with
braided copper shield). Clamping without conductor end sleeves is possible in accordance with IEC 60999. The cable must meet the following specifications:
2
– Cable cross-section 0.2 to 1.0 mm
(AWG 24 - AWG 18)
– Cable resistance 120 Ω at 1 MHz
Cable length•The permitted total cable length depends on the baud rate setting of the system bus:
– Capacitance per unit length = 40 pF/m at 1 kHz
Suitable cables include CAN bus or DeviceNet cables.
– 125 kBd→ 500 m
– 250 kBd→ 250 m
– 500 kBaud→ 100 m
– 1000 kBd→ 40 m
18
Manual – Fieldbus Gateway UFR41B EtherNet/IP, Modbus/TCP and PROFINET IO
•Switch on the system bus terminating resistor at the start and end of the CAN system
bus connection (MOVIDRIVE
S1 = ON). For all other devices, switch off the terminating resistor (MOVIDRIVE
DIP switch S12 = OFF; MOVITRAC
way is, for example, located at the end of the CAN 2 system bus, you have to connect
a terminating resistor of 120 Ω between pins X32:2 and X32:3 (for CAN 1: terminating
resistor between pins X33:2 and X33:23).
®
B, DIP switch S12 = ON; MOVITRAC® B, DIP switch
®
B, DIP switch S1 = OFF). If the fieldbus gate-
®
B,
CAUTION
•There must not be any potential displacement between the units connected via the
CAN 2 system bus.
•There must not be any potential displacement between the units connected via the
CAN 1 system bus.
•Take suitable measures to avoid potential displacement, such as connecting the
unit ground connectors using a separate cable.
Manual – Fieldbus Gateway UFR41B EtherNet/IP, Modbus/TCP and PROFINET IO
Terminal X36 is intended for connecting a system bus based on EtherCAT (SBUS
4.3.4Ethernet interface terminal (terminal X37)
You can connect an engineering PC to the Ethernet interface (terminal X37).
UFF41B
UFR41B
X35
342
1
Version
X36
S1
X37
1
1
XML4
2
2
X32X33
3
3
1
1
2
2
3
3
L1L2L3L5
plus
).
65057AXX
The Ethernet interface (X37) supports auto crossing auto negotiation for baud rate and
duplex mode. The IP parameters are defined depending on DIP switch S1 (see section
"DIP switches S1 default IP address").
In addition to the engineering access via terminal X37, there is another engineering
access via PROFIBUS (see section "Operation of MOVITOOLS
®
MotionStudio").
22
Manual – Fieldbus Gateway UFR41B EtherNet/IP, Modbus/TCP and PROFINET IO
The LED L1 indicates the status of the CAN 1 system bus.
Status of the L1
LED
OrangeThe CAN 1 system bus is being
GreenThe CAN 1 system bus is initialized.
Flashing green
(0.5 Hz)
Flashing green
(1 Hz)
RedThe CAN 1 system bus is off (BUS-
Flashing red
(1 Hz)
DiagnosticsRemedy
initialized.
The CAN 1 system bus is currently in
SCOM suspend mode.
The CAN 1 system bus is currently in
SCOM On mode.
OFF).
Warning on the CAN 1 system bus.1. Check and correct the cabling of the
-
1. Check and correct the cabling of the
CAN 1 system bus.
2. Check and correct the baud rate set
for the CAN 1 system bus.
3. Check and correct the terminating
resistors of the CAN 1 system bus.
CAN 1 system bus.
2. Check and correct the baud rate set
for the CAN 1 system bus.
The LED L2 indicates the status of the CAN 2 system bus.
Status of the L2
LED
OrangeThe CAN 2 system bus is being
GreenThe CAN 2 system bus is initialized.-
Flashing green
(0.5 Hz)
Flashing green
(1 Hz)
RedThe CAN 2 system bus is off (BUS-
Flashing red
(1 Hz)
DiagnosticsRemedy
initialized.
The CAN 2 system bus is currently in
SCOM suspend mode.
The CAN 2 system bus is currently in
SCOM On mode.
OFF).
Warning on the CAN 2 system bus.1. Check and correct the cabling of the
-
-
-
1. Check and correct the cabling of the
CAN 2 system bus.
2. Check and correct the baud rate set
for the CAN 2 system bus.
3. Check and correct the terminating
resistors of the CAN 2 system bus.
CAN 2 system bus.
2. Check and correct the baud rate set
for the CAN 2 system bus.
LED L3 (program
status)
LED L3 indicates the status of the gateway program.
Status of L3DiagnosticsRemedy
GreenGateway program is running.-
OffNo gateway program is loaded.Load a gateway program into the controller.
Flashing orange
(1 Hz)
Program has stopped.Bootloader update required (see section
"SD memory card type OMG4.B")
Manual – Fieldbus Gateway UFR41B EtherNet/IP, Modbus/TCP and PROFINET IO
LED L4 indicates the firmware status of the fieldbus gateway.
Status of the L4 LED DiagnosticsRemedy
Flashing green
(1 Hz)
Red•No SD card plugged in.
Flashing orange
(1 Hz)
The firmware of the fieldbus gateway
is running properly.
-
•File system of the SD card
corrupt.
Program has stopped.Bootloader update required (see section
"SD memory card type OMG4.B")
LED L5 (user)LED L5 is lit up red if the gateway program has detected an error and if this error can
®
only be eliminated after diagnostics with MOVITOOLS
MotionStudio.
4.5DIP switch S1 default IP address
With DIP switch S1, you can set a default IP address for the Ethernet connection (X37).
The set IP address is applied in the next boot process.
S1 switch settingMeaning
TopIP p a r am e t e r :
BottomThe IP parameters defined on the memory card of the UFR41B gateway are used.
•IP address: 192.168.10.4
•Subnet mask: 255.255.255.0
•Standard gateway: 1.0.0.0
The IP parameters for engineering interface X37 are entered in the file '...\System\NetConfig.cfg' in section 'Ethernet 2'. You can adjust the file using a text editor
(e.g. Notepad).
4.6SD memory card type OMG4.B
The SD memory card type OMG4.B is required for operating the UFR41B fieldbus gate-
Bootloader
update
way and contains the firmware, the gateway program, and the gateway configuration.
With a MOVIAXIS
terization in case an axis needs to be replaced.
The SD memory card type OMG4.B is included in the scope of delivery of the UFR41B
fieldbus gateway.
Only use type OMG4.B memory cards in a UFR41B fieldbus gateway.
When the LEDs L3 and L4 flash orange at a 1 Hz frequency after power-on, a bootloader
update is required. Proceed as follows:
•Do not switch off the power supply during the entire process.
•Press the reset button T1 on the front of the UFR41B fieldbus gateway for 3 seconds.
When the bootloader update starts, only LED 4 is flashing.
•The bootloader update has been successful when L4 flashes green.
®
axis module, it is also used for data backup and automatic parame-
24
Manual – Fieldbus Gateway UFR41B EtherNet/IP, Modbus/TCP and PROFINET IO
To connect UFR41B to the Ethernet, connect the Ethernet interface (X30-1, X30-2 or
X37) to the other network stations using a category 5, class D shielded twisted-pair
cable in accordance with IEC 11801 edition 2.0. The integrated switch provides support
for implementing a line topology using X30-1 and X30-2, and offers auto crossing
functions.
TIPS
•According to IEC 802.3, the maximum cable length for 10/100 MBaud Ethernet
(10BaseT / 100BaseT), e.g. between two network stations, is 100 m.
•We recommend that you do not directly connect non-SEW end devices to the
UFR41B option 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 functionality (e.g. managed
switch).
Managed switches with IGMP snooping functionality is not required for PROFINET
IO and Modbus TCP networks.
4.9Shielding and routing bus cables
Only use shielded cables and connection elements that meet the requirements of
category 5, class D according to IEC 11801 edition 2.0.
Correct shielding of the bus cable attenuates electrical interference that can occur in
industrial 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 metallized 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.
CAUTION
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 according in accordance with relevant
VDE regulations in such a case.
26
Manual – Fieldbus Gateway UFR41B EtherNet/IP, Modbus/TCP and PROFINET IO
You can use the integrated Ethernet switch to implement line topologies using X30-1
and X30-2 known from the fieldbus technology. Other bus topologies, such as star or
tree, are also possible. Ring topologies are not supported.
TIP
The number of Industrial Ethernet switches connected in line impacts on 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 that the more units a telegram has to pass through, the higher the telegram
runtime is.
Auto crossingThe 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 Ethernet station.
4
Auto negotiationThe baud rate and the duplex mode is negotiated by both Ethernet nodes when
establishing 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.
Notes on multicast handling
•The integrated Ethernet switch does not provide a filter function for Ethernet multicast telegrams. Multicast telegrams that are usually sent in Ethernet/IP networks
from the adapters to the scanners (PLC) are passed on to all switch ports.
•IGMP snooping (managed switch) is not supported.
•SEW-EURODRIVE therefore recommends to connect the UFR41B option 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. This restriction does not apply to
PROFINET IO or MODBUS TCP networks.
Manual – Fieldbus Gateway UFR41B EtherNet/IP, Modbus/TCP and PROFINET IO
The LEDs of the UFR41B fieldbus gateway indicate the current status of the UFR41B
option and the fieldbus system. The LEDs have a different meaning depending on the
set protocol.
UFR41B
L14
L13
4.12.1 Status LED in EtherNet/IP and Modbus/TCP operation
4
65054AXX
LED L13
(NETWORK
STATUS)
LED L14
(MODULE
STATUS)
Chapter 9 provides a summary of the status of the fieldbus interface corresponding to
the LED status.
The LED L13 (NETWORK STATUS) indicates the state of the fieldbus system.
States of the
NETWORK STA TUS
LED
OffThe UFR41B option does not yet have any IP parameters.
Flashing green/redThe UFR41B option card performs an LED test.
Flashing greenThere is no controlling IO connection.
GreenThere is a controlling EtherNet/IP or Modbus/TCP connection.
RedConflict detected in the assigned IP addresses. Another station in the network uses
Flashing redThe previously established controlling IO connection is in timeout status. The status
Meaning
the same IP address.
is reset by restarting communication.
LED L14 (MODULE STATUS) indicates that the bus electronics are operating correctly.
States of the
MODULE STATUS
LED
OffThe UFR41B option card is either not supplied with voltage or it is faulty.
Flashing green•If the NETWORK STATUS LED is off at the same time, the TCP/IP stack of the
Flashing green/redThe UFR41B option card performs an LED test.
GreenThe UFR41B option card is in normal operating state.
RedThe UFR41B option card is in fault state.
Flashing red Conflict detected in the assigned IP addresses. Another station in the network uses
Meaning
UFR41B option card will be started. If this status continues and DHCP is
activated, the UFR41B option card waits for data from the DHCP server.
•If the NETWORK STATUS LED is flashing green at the same time, the
application of the UFR41B option card is started.
the same IP address.
Manual – Fieldbus Gateway UFR41B EtherNet/IP, Modbus/TCP and PROFINET IO