We have a problem in the runtime of a PLC that frequently crashes for no apparent reason, both the PLC outputs and Webvisu do not respond.

The only anomaly that we observed in the Codemeter diagnostics are the recurring messages below. Anyone have a guess?

2022-05-13 14:56:44: Handle 668 released
2022-05-13 14:56:44: Access from local(IPV4) to FC:PC=5000304:305021 with Exclusive Mode (Handle 670) 
2022-05-13 14:57:44: Entry (101597:305021) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4) with Exclusive Mode
2022-05-13 14:57:44: API Error 200 (ENTRY NOT FOUND) occurred!
2022-05-13 14:57:44: Handle 670 released
2022-05-13 14:57:44: Access from local(IPV4) to FC:PC=5000304:305021 with Exclusive Mode (Handle 672) 
2022-05-13 14:58:44: Entry (101597:305021) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4) with Exclusive Mode
2022-05-13 14:58:44: API Error 200 (ENTRY NOT FOUND) occurred!
2022-05-13 14:58:44: Handle 672 released
2022-05-13 14:58:44: Access from local(IPV4) to FC:PC=5000304:305021 with Exclusive Mode (Handle 674) 
2022-05-13 14:59:44: Entry (101597:305021) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4) with Exclusive Mode
2022-05-13 14:59:44: API Error 200 (ENTRY NOT FOUND) occurred!
2022-05-13 14:59:44: Handle 674 released

plaese check the plclogger for this situation..enable log in file in case the runtime stops.

Hi @eschwellinger,

We had to wait a time to face to another lock issue with the runtime at which the logger procedure were applied, and just today at 19/05/2022 02:29:15 (GMT-3) it happened again.

However from the log files, at first sight, we could not find any entry that could give any tip; could you see that please?

Kind regards,
Andre.

yes agree nothing interesting in,
please change it in that way that you get one huge log file:

[CmpLog]
Logger.0.Name=PlcLog
;Logger.0.Filter=0xFFFFFFFF
Logger.0.Enable=1
Logger.0.MaxEntries=400000
Logger.0.MaxFileSize=500000
Logger.0.MaxFiles=3
Logger.0.Backend.1.ClassId=0x00000104 ;writes logger messages in a file

Hi @eschwellinger,

After a short wait, we were able to capture a crash event, apparently occurring at 2022-05-23T07:38; our application automatically STOP/START the Codesys runtime in case of connection loss - which is the systemically tangible symptom of the problem; electrically, all outputs are cleared.

And, again, log entries are not inteligible for us, could you have a see on that ?

2022-05-23T07:38:14Z, 0x00000019, 16, 4112, 16, EXCEPTION Omitted cycle <excpt>OmittedCycle watchdog</excpt> <app>Application</app> <task>Task_1</task>
2022-05-23T07:38:14Z, 0x00000019, 16, 4112, 17, IecTask state: flags=0x0, state=0x2041, tCycleStart=743816204996, tActTime=743816199429
2022-05-23T07:38:14Z, 0x00000019, 16, 4112, 14, SchedTask state: state=0x2, tLastActivate=743816204933
2022-05-23T07:38:14Z, 0x00000011, 8, 4112, 3, #### Exception: EXCEPTION [<excpt>OmittedCycle watchdog</excpt>] occurred: App=[<app>Application</app>], Task=[<task>Task_1</task>]
2022-05-23T07:38:14Z, 0x00000011, 8, 4112, 3, #### Exception: SOURCEPOSITION App=[<app>Application</app>] area=0, offset=<off>0</off>

what happens in your Task_1 - anything special?
You could try:

[CmpSchedule]
DisableOmittedCycleWatchdog=1
in your PLC configuration file.

Thanks for your support, we'll try as you recommnded.

BTW, Task1 is just for low speed procedures, not critical timmming constraints, whereas Task0 is for 'realtime' jobs.