Welcome to our new forum
All users of the legacy CODESYS Forums, please create a new account at account.codesys.com. But make sure to use the same E-Mail address as in the old Forum. Then your posts will be matched.
Close
Runtime : CODESYS Control for emPC-A-iMX6 SL 3.5.16.20 and 3.5.15.30
Error in codesyscontrol.log:
2023-07-17T08:32:28Z, 0x00000103, 65544, 1, 0, runtime received SIGABRT - system may be in an inconsistent state * We recommend a reboot of the controller now! *
I am experiencing an intermittent issue where the above exception is generated. It also occurs on two different runtime versions at intervals ranging from minutes to days after start up. I have two issues with it.
I am unable locate the source of the problem. I am only able to see that one of the PLC tasks is in "Active, Exception" state. Generating a core dump or project archive is not helping as I believe the variables in the exception task are within bounds and behaving as expected.
I have a System Event for Exception that I hope should reboot on exception. "Event is sent, if an exception occurred in the context of an application". Is SIGABRT not a system exception? Is this system event limited to exceptions generated by the function SysExceptGenerateException in the SysExcept library?
Currently it is not rebooting nor is a watchdog function forcing a reboot. The watchdog is still triggered due to a watchdog service task still running. The main application functionality is halted at this exception point also.
Any help tracing the source of the problem or recovering from it automatically would be appreciated.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Runtime : CODESYS Control for emPC-A-iMX6 SL 3.5.16.20 and 3.5.15.30
Error in codesyscontrol.log:
2023-07-17T08:32:28Z, 0x00000103, 65544, 1, 0, runtime received SIGABRT - system may be in an inconsistent state
* We recommend a reboot of the controller now! *
I am experiencing an intermittent issue where the above exception is generated. It also occurs on two different runtime versions at intervals ranging from minutes to days after start up. I have two issues with it.
Currently it is not rebooting nor is a watchdog function forcing a reboot. The watchdog is still triggered due to a watchdog service task still running. The main application functionality is halted at this exception point also.
Any help tracing the source of the problem or recovering from it automatically would be appreciated.