hi.
My plc is weidmuller UC20-WL200-AC, IDE CODESYS 3.5.20.40, see picture for task settings.
sometime i've got the plc stop.
Reading the log, I find: EXCEPTIONPOSITION : IP=0x(nil) (no IECcontext could be retrieved) component CmpIecTask EXCEPTION[Watchdog] occurred: App=[Application], Task=[TASK_O_MAIN] component CmpIecTask
Monitor what your current cycle time is (in the Task Configuration when you are online).
If this is sometimes close to 200ms, then change your code (e.g. limit the loops, or prevent copying a lot of data between objects).
Or just set the Watchdog time (or sensitivity) higher if you don't care that it sometimes takes longer than 200ms.
If you want to find out which objects in your application consume the most time, then buy a PDE (Professional Developer Edition) license. With this you get a license for the Profiler. This can help you a lot to find the root cause, because it will create a nice overview of all objects, their calls and the time (percentage) it takes to execute it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
hi.
My plc is weidmuller UC20-WL200-AC, IDE CODESYS 3.5.20.40, see picture for task settings.
sometime i've got the plc stop.
Reading the log, I find:
EXCEPTIONPOSITION : IP=0x(nil) (no IECcontext could be retrieved) component CmpIecTask
EXCEPTION [Watchdog] occurred: App=[Application], Task=[TASK_O_MAIN] component CmpIecTask
How to find the position of problem?
Monitor what your current cycle time is (in the Task Configuration when you are online).
If this is sometimes close to 200ms, then change your code (e.g. limit the loops, or prevent copying a lot of data between objects).
Or just set the Watchdog time (or sensitivity) higher if you don't care that it sometimes takes longer than 200ms.
If you want to find out which objects in your application consume the most time, then buy a PDE (Professional Developer Edition) license. With this you get a license for the Profiler. This can help you a lot to find the root cause, because it will create a nice overview of all objects, their calls and the time (percentage) it takes to execute it.