Regarding the Codesys Error
Our SCADA application is running on a 64-bit Windows-7 Professional, Service Pack-1 PC with Control Builder Plus v2.2.0 and CoDeSys OPC Server v3.4 SP4 Patch-1 that has been configured with our SCADA.The application keeps running smoothly most of the time but a dialogue box with the message 'WinCoDeSysOPC.EXE has stopped working' (Image attached) appears on the screen and the SCADA becomes inoperable untill the 'Close the program' option is selected which results in stopping of the OPC server and the connection resumes automatically after a few seconds.We have reinstalled the OPC Server a month ago still the issue is repeating.
The reasons could be several.
The first thing you should do is check the OPC Server's log at C:\Programdata\CodesysOPC\OPCserver.log. You may find the cause in the log itself.
The SCADA OPC client's log may also provide valuable information.
Since the OPC Server application runs smoothly most of the time,may be the SCADA OPC client overloads the OPC Server w.r.t service requirement, for a short duration.
If the SCADA can be kept offline/disconnected from the OPC Server for say 24 hours or for the duration within which the issue is generally observed, you could then use a 3rd party OPC test client to connect to the OPC server and subscribe to a few tags from the controller.
If the issue is not observed, you could then mainly concentrate on the frquency of data collection and the amount of data being fetched/updated from the controller.
Try to keep the size of the Symbol file below 1.5MB or aprroximately 15000 items. Also try to verify for the re-occurance of the issue, by increasing the OPC Server's UPDATE RATE (OPC Configurator parameter) from its default value of 200ms to 400ms or more, with the SCADA OPC client connected to the CodesysOPCServer.