Phoenix Contact RFC 4072S, Руководство пользователя, Страница: 93 / 272

Startup and validation
108580_en_02 PHOENIX CONTACT
93 / 272
4.5 Configuring the controller IP settings
4.5.1 General information
In the delivery state, the preset IP address of the RFC on the LAN1 interface is 192.168.1.10.
You can manually change the IP addresses using the PLCnext Engineer software via the
Ethernet interface or via the display.
PC/network adapter To determine whether your network permits the IP settings used in the example project, pro-
ceed as follows:
• In the Windows Control Panel, check the settings for your PC network adapter.
• If necessary, adjust these settings so that the RFC 4072S can be accessed in your net-
work via the IP address used in the example project.
If your network does not permit the use of the IP addresses used in the example project,
adjust the settings accordingly.
4.5.2 Important information
Setting IP addresses via the display
Refer to Section 7.2 on page 164 for how to change the IP address settings via the display
directly on the RFC.
Please note that the RFC has several MAC addresses . The LAN1 and LAN2 interfaces
are each assigned a separate MAC address. A common third MAC address is assigned
to the LAN3.1 and LAN3.2 interfaces that are switched internally in the device.
LAN1 is preconfigured as the PROFINET controller interface.
The LAN3.1 and LAN3.2 interfaces are preconfigured as the device interface.
Depending on the connected interface, the RFC can then be accessed in the Ethernet via
three different IP addresses .
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.