Still problems with the IP address of the PLC Next

PLCnext Technology & PLCnext Controls
1

Good evening, as my colleague Robo already described a few days ago, we have problems with the IP Config of PLC Next. Unfortunately their answers under his mail could not lead to a solution.

Therefore we have now made a smaller test setup to analyze and clean up the problem.
With the request to find a quick solution for us, because our work is stagnating because of this problem. Our PG is connected to PLC Next via PN, as soon as we connect the Siemens ET 200 SP 1500 CPU (PN Controller) the IP address changes to 10.10.10.1 . Here I would like to mention that you can see this IP address change only directly via WIN SCP in /etc/interface/networks, or directly via the WEB browser (with the actual IP address 192.168.100.110) under the device information! How can it be that you can see the old IP address in PLC Next Engineer under Online Device Parameters??? Both CPU’s were completely reset to factory defaults, and with empty projects that only contain the hardware configuration and IP addressing. Nevertheless the IP of the PLC Next changes every time !! as soon as the Siemens CPU is connected. Please have a look at the pictures I have attached. Very funny is the aspect that you can access your CPU via the webbrowser with the actual IP address 192.168.100.110, but then the IP address 10.10.10.1 is set under the device information and 10.10.10.1 is set as default gateway. I will add records on Wireshark, also I can send you the TIA and PLC NEXT E. project file, please let me know how this can happen. With kind regards Nils

2

Hello Nils, this issue will be analyzed via Ticket System. Please find the information under your received emails. ~Eduard

3

Hello Nils,

I would like to close this request with following results (as allready discussed via E-Mail):

Short description:
The network / interfaces file only contains the IP addresses that are to be retained retentively, e.g. after a reboot.
However, it is possible to change the IP address of a device via Profinet-DCP, but specify as a parameter that this IP address should NOT be retentive, i.e. This IP address should NOT be retained during the next reboot. Explanation/Cause of this issue:
The IP address 10.10.10.1 is an internal IP address that is set when a “ResetToFactory” is executed via Profinet mechanisms. The IP addresses are stored retentively, i.e. the network / interfaces file is adapted. The higher-level controller then assigns the correct IP, but not retentively. And from this point on, the two representations in WBM(remanent IP address) and currently setted (the correct IP) diverge. Summary:
Up to FW 2020.6, the WBM only reproduced the contents of the / network / interfaces file and not the actual, current IP address.
From FW 2021.0 in the WBM will be showed the correct IP and this case can no longer occur. Best Regards Eduard