SEW-Eurodrive DH 41B Series - Startup of the Fieldbus at the DHR21 B;41 B Controller

7
Project planning and startup with MOVITOOLS
®
MotionStudio
Startup of the fieldbus at the DHR21B/41B controller
Manual – DHE/DHF/DHR21B (standard) and DHE/DHF/DHR41B (advanced)
54
7.4.3 Communication ports used
The following table shows the communication ports that are used by the
MOVITOOLS
®
MotionStudio engineering software:
Application
Number of the
communication port
Description
ETH server 300 (TCP/UDP)
For the services of the SMLP and
for using a PC as Ethernet gate-
way.
SEW Communication
Server
301 (TCP)
For communication between
MOVITOOLS
®
MotionStudio and
the SEW Communication Server.
Offline data server 302 (TCP)
For communication of
MOVITOOLS
®
MotionStudio in off-
line mode.
MOVIVISION
®
server 303 (TCP)
For communication with a PC with
active MOVIVISION
®
server
Reserved
304 –
TCI server 305 (TCP)
For communication via TCI (Tool
Calling Interface by Siemens)
EcEngineeringServer-
RemoteControl
306 (UDP)
For direct communication (without
master) with the slaves
EcEngineeringServer
mailbox gateway
307 (UDP)
For direct communication (without
master) with the slaves and for
communication via a mailbox gate-
way
MOVI‑PLC
®
visualiza-
tion
308 (TCP/UDP)
For communication between
MOVI‑PLC
®
and the 3D simulation
of MOVITOOLS
®
MotionStudio
7.5 Startup of the fieldbus at the DHR21B/41B controller
The following section comprises detailed information regarding setup of the fieldbus of
the DHR21/41B controller.
7.5.1 The integrated Ethernet switch
You can use the integrated Ethernet switch to achieve line topologies known from the
fieldbus technology via X30-1 and X30-2. Other bus topologies, such as star or tree,
are also possible. Ring topologies are not supported.
INFORMATION
The number of industrial Ethernet switches connected in line impacts the telegram
runtime. If a telegram passes through the devices, the telegram runtime is delayed by
the store & forward function of the Ethernet switch:
This means the more devices a telegram has to pass through, the higher the tele-
gram runtime is.
• 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)
22900055/EN – 08/2016