Codesys Profinet Controller with ctrlx core will not work after cable interruption

[cc2go]

Hello,

we figure an issue with the Codesys Profinet Controller with ctrlX core X3 after replugging, when we unplug the Proifnet cable between the core XF51 and the Profinet Device. It will not work anymore.

Logger see screenshot and XML. Interesting the order is different to normal case, in normal case the Init Device with Local IP setting occur at nearly the same time than the link up message came. In error case the Profinet controller came with link up and 5s later the IP / Interface settings are applied. It seems the Profinet controller try to work with "Local IP - suite changed to 0.0.0.0 / 0.0.0.0" instead of "Local IP - suite changed to 172.168.10.1 / 255.255.255.0". It looks for us like a timing issue. How can we get rid of this issue.

What does the message "Controller-Status: currently active IP does not match the controller's configuration" mean, is there any possibility to check this, if yes, how?

[watchdog · Accepted solution]

The problem was the configuration of the two network interfaces. The two network interfaces eth1 (XF51 Profinet) and tap0 (XF50 EtherCAT) were in the same network 172.168.10.XXX. When establishing the connection after the interruption, the Profinet soft stack probably went out on the wrong network interface and was thus unable to establish a connection.

Solution: Configure eth1 (XF51 Profinet) IP in a network other than tap0, e.g. 176.168.10.xx. Then, the connection is re-established properly after the cable interruption.