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
After a few days of running/powering on, I have started seeing the following exception occurring on one or two of the 11 Raspberry Pi's I am testing:
EXCEPTION[OmittedCycle watchdog] occurred: App=[Application], Task=[Task_HighSpeed] in the CmpIecTask component.
I cannot find any reference to what "OmittedCycle watchdog" is. I have searched the Codesys help, fulltext search through the library manager checking any relevant library/components, Googled every combination I can think of and the only reference I can find to OmittedCycle is the following release notes:
I log into the PLC and find it has stopped with that error. I do not have a screenshot of the Task Configuration monitor page but I will next time it occurs. Checking the Task Configuration monitor page shows the max cycle time for that task is well below the watchdog time set for it. Looking at the Task Configuration monitor in the attached screenshot, this currently running fine Pi's max cycle time did hit 3.3ms but is still running fine.
I have included screenshots of the current tasks configurations. Every few days (2 or 3) I will have a random Pi stop. Restarting the codesyscontrol runtime or a Reset Warm and a Start will get it going again.
Does anyone know where I can find more information on this exception?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The high speed task is configured to 1ms. And the cycle time which has been shown in the monitor is much higher. This is what has been detected by the "omitted cycle watchdog".
The simple reason can be that you need an rt preempt patched kernel if you have such high timing constraints. If your timing requirements are more weak it might be enough to disable the task watchdog. AFAIK the omitted cycle is only detected when the task watchdog is enabled.
Gesendet von meinem LG-H870 mit Tapatalk
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
After a few days of running/powering on, I have started seeing the following exception occurring on one or two of the 11 Raspberry Pi's I am testing:
EXCEPTION [OmittedCycle watchdog] occurred: App=[Application], Task=[Task_HighSpeed] in the CmpIecTask component.
I cannot find any reference to what "OmittedCycle watchdog" is. I have searched the Codesys help, fulltext search through the library manager checking any relevant library/components, Googled every combination I can think of and the only reference I can find to OmittedCycle is the following release notes:
I log into the PLC and find it has stopped with that error. I do not have a screenshot of the Task Configuration monitor page but I will next time it occurs. Checking the Task Configuration monitor page shows the max cycle time for that task is well below the watchdog time set for it. Looking at the Task Configuration monitor in the attached screenshot, this currently running fine Pi's max cycle time did hit 3.3ms but is still running fine.
I have included screenshots of the current tasks configurations. Every few days (2 or 3) I will have a random Pi stop. Restarting the codesyscontrol runtime or a Reset Warm and a Start will get it going again.
Does anyone know where I can find more information on this exception?
After some discussions with Edwin, this is one possible solution should you not need realtime:
/etc/CODESYSControl_User.cfg
[CmpSchedule]
ProcessorLoad.Enable=1
ProcessorLoad.Maximum=95
ProcessorLoad.Interval=5000
DisableOmittedCycleWatchdog=1
Just to lit the fog a bit.
The high speed task is configured to 1ms. And the cycle time which has been shown in the monitor is much higher. This is what has been detected by the "omitted cycle watchdog".
The simple reason can be that you need an rt preempt patched kernel if you have such high timing constraints. If your timing requirements are more weak it might be enough to disable the task watchdog. AFAIK the omitted cycle is only detected when the task watchdog is enabled.
Gesendet von meinem LG-H870 mit Tapatalk