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
What is the preferred way to handle a watchdog timeout on a SoftPLC? According to the documentation the timed out task will be suspended and that is fine but is there some way to determine this from the code to handle the event by e.g. raising an alarm or restarting the SoftPLC?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
So now the exception handler is working I can set a global variable. But when the exception is called my visualization is made unavailable. I can see the tasks not halted by the watchdog keeps increasing the cycle count but the IEC-cycle count stops increasing.
Shouldn't the watchdog only halt the task causing problems and letting the rest of the system continue working?
I tried creating a sub-application to my main application and move the visualization there. This results in the sub-application being stopped when the exception occurs as well but this can be restarted which is adequate for testing but not really for production.
Any suggestions?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
What is the preferred way to handle a watchdog timeout on a SoftPLC? According to the documentation the timed out task will be suspended and that is fine but is there some way to determine this from the code to handle the event by e.g. raising an alarm or restarting the SoftPLC?
You can add an exception handler by double clicking the Task Configuration, see attached.
Thank you. That helped me move forward.
So now the exception handler is working I can set a global variable. But when the exception is called my visualization is made unavailable. I can see the tasks not halted by the watchdog keeps increasing the cycle count but the IEC-cycle count stops increasing.
Shouldn't the watchdog only halt the task causing problems and letting the rest of the system continue working?
I tried creating a sub-application to my main application and move the visualization there. This results in the sub-application being stopped when the exception occurs as well but this can be restarted which is adequate for testing but not really for production.
Any suggestions?