Change IP address of PLCnext

PLCnext Technology & PLCnext Controls
1

The default IP address of our PLCnext AXC F 2152 is 192.168.1.10 which is not in the subnet of our office Network so I needed to Change it. Since it wasn’t possible to find the device with the PLCnext Engineer Software, I changed it manually through SSH, from the static to dhcp Setting. Now the device is accessible in the Network through SSH, but the web Server doesn’t serve pages, and PLCnext Engineer still can’t find the device in a scan. Additionally, I found this error message repeatedly in the syslog:

Mar 22 12:36:32 axcf2152 user.err Arp.System.Application: Arp.Io.ProfinetStack.System.Internal.Adaption ERROR - Event Archive Entry, Module ID: 8b, Message: IP address of interface MAC= [eth0] isn’t set to 192.168.1.10 !

Does it have to do with the malfunction of the other Features? PS: Sorry for the misspelling, the Edge browser did that and it can’t be turned off. Firefox and Chrome cannot load any of the PLCnext community Websites at the Moment.

2

Hello ygoe,

you have detected a known problem: Currently we support DHCP on the Linux side, but not from the perspective of the PLCnext firmware. The Profinet stack tries to parse the / etc / network / interfaces file; is there, for example, “dhcp” instead of an IP address. As long as the defect is not resolved, the use of DHCP can only be discouraged! Please use the external ethernet adapter (with the needed IP/subnet settings) for IP-assignment in PLCnext Engineer or NetNames. If you have additionally questions, please don’t hesitate to ask! Best Regards Eduard

3

I too am needing DHCP for an application. Am I understanding that with the addition of the 2403115 extension module I can utilize DHCP on one interface and Static on another? This would be ideal to provide profinet remote I/O connections and an IOT connection. Thank you, Josh

4

Hi Josh, I checked the solution with the 2403115 ETH extension module, but the DHCP functionality is not supported by this AXL module. The support of DHCP-functionality should be first supported by AXCF2152 Controller for providing to 2403115 ETH extention module. Workaround: You can use the MGuard. With external DHCP-IP-Configuration and static IP-address for internal Network (connection to PLCnext AXCF2152 Controller). Best Regards

Eduard

5

Thank you Eduard. I went ahead and ordered the 2403115 in the hopes that the AXCF2152 will support DHCP in the near future. An mGuard for this application is overkill and expensive. My application will ideally connect to Profinet I/O via a static port and a Garmin Multi-Function Display via the DHCP connection. The Garmin connects via mDNS and my goal is to make a zero configuration control box. Connect power, connect an ethernet cable and let the PLC and MFD negotiate the routing. The application is currently working with some modifications to the NGINX server config file and a static address. In the future, I would like to eliminate the subnet determination step presently necessary to assign the PLC static address. This makes for an easier sale, because no networking knowledge is required by the system installer. Josh

6

Hello Josh, Thanks for your feedback, I’ll check if it is possible to add the timeline for DHCP feature to PLCnext Controls - Implementation Roadmap overwiev. Best Regards -Eduard-

7

Eduard, I received the 2403115 today. Unfortunately I didn’t realize that you must also order the 1064312 connector for the controller. Surprised this connector doesn’t ship with the 2403115 or the controller. Might be good to make a tech note for those ordering the comm module. Josh

8

Hi Josh, it will be later possible to add more than one left side extension the the PLCnext Controls, therefore we decided to leave the connector (1064312) as an option. But you’re absolutely right, a note would be helpful ?. I’ll speak with the product manager and I guess it will be fast possible to change this… Take care Frank