Hello, we are having troubles with a few Core X3 devices that were recently updated to the firmware version 2.6 LTS. After the update, some PLC Online Change procedures are ending with an unknown exception. On the IWE side it looks like the code transfer halted at 0kB of transfer and it says that connection to the PLC was lost. On the CoreX web interface, I can see there is an error 502 when I try to open the PLC app page. Also, there is a PLC app exception "0A0F0002 PLC: Exception", but without any detailed diagnostic code provided (please see attached screenshot)! After the complete reboot then error "080F60B0 Condition detected that triggered a safe machine state" occurs, but this is probably secondary to the 0A0F0002. After the reboot everything is working fine. As 080F60B0 description suggested, I downloaded the diagnostic log and also the exception log from the DataLayer/Framework/Exceptions (both attached). Also, once I was also able to see the exception log from the IWE (attached). This error never occurs when the PLC code is Downloaded instead of Online Changed, so it is kind of a workaround. On some days it can never occur, and on other days it occurs during almost every other Online Change. As for now, I cannot see any pattern here. How can we debug this? Why there is no detailed code provided for 0A0F0002? What is the cause of "Error on IO update of instance [...]" exceptions in IWE? Is it a known issue?
... View more
