ID 442426.04
266
WE KEEP THINGS MOVING
Communication
14
Manual SD6
You can also set up communication to a controller via the fieldbus in parallel to
the IGB. Observe the fieldbus documentation for this (see section 1.2 Further
14.2.1
Basics of IGB communication
The following requirements apply
•
Communication with remote maintenance and without a proxy server uses
the HTTP protocol via port 80 and TCP/IP port 37915. For remote
maintenance with a proxy server the HTTP protocol uses the proxy port.
•
Communication with a direct connection must be possible with TCP/IP and
UDP/IP via ports 37915 and 37916.
You may be asked to share this port by the personal firewall. Share these ports
in your firewall for the following programs:
•
for DriveControlSuite (default installation directory: C:/Windows/
Programme/STOEBER ANTRIEBSTECHNIK/DriveControlSuite (V6.0)/
bin/DS6A.exe)
•
for the communication service
SATMICLSVC.exe
in:
–
Windows 32 bit: C:/Windows/System
–
Windows 64 bit: C:/Windows/SysWOW64
To do this, contact your network administrator.
The IGB network must meet the following conditions:
•
A maximum of 32 SD6s may be connected in one network.
•
All drive controllers involved in the IGB network must be directly connected
with each other. No other components such as hubs and switches are
permitted between them in the circuit.
•
The overall resulting layout must be a line topology.
Information
Remember that when a fieldbus and the IGB-Motion bus are used
at the same time, the fieldbus communication cannot be
synchronized on the controller.
Information
Remember that an IGB network can never be accessed by remote
maintenance and direct connection (PC) at the same time.
