RFC 4072S
60 / 272
PHOENIX CONTACT 108580_en_02
2.11.2 Connection example of the Ethernet interfaces
At present the RFC 4072S supports the following connection in a PROFINET system.
In the following example, the RFC 4072S is operated as a lower-level PROFINET device
connected to a higher-level PROFINET controller (optional). In this case, the connection is
established via the LAN3.2 interface. To operate the RFC 4072S as a PROFINET controller,
PROFINET devices are connected to the LAN1 interface (see Figure 2-28).
Figure 2-28 PROFINET example installation
A PC can be operated on each Ethernet interface of the RFC. Depending on the configu-
ration of the interfaces, this may not be possible in individual cases (see Section “Ethernet
connection” on page 59).
Please note:
– The IP addresses of interfaces LAN1 / LAN2 / LAN3.1/3.2 must be in different sub-
nets.
– The PROFINET controller function of the RFC is available at interface LAN1. This
interface must then be assigned an IP address if the PROFINET controller function of
the device is to be used in the application.
– An IP address must be assigned to interfaces LAN3.1/3.2 if you want to use the
PROFINET device function of the RFC at either of these interfaces.
– The LAN2 and LAN3.1/3.2 interfaces do not necessarily have to be assigned an IP
address if, for example, communication between a PC with PLCnext Engineer and
the RFC is also implemented via the LAN1 interface. Nevertheless, we recommend
that appropriate IP addresses are assigned to all interfaces.
LAN1 LAN2
PROFINET-
Controller
(optional)
PROFINET-
Devices
108580A001
LAN3.1 LAN3.2
PLCnext
Engineer
To Next Page
Loading...
Need help?
General
