Hi, everyone!
I repeatly encounter a crash of the OPC server, which forces a reboot of the controller with frequent connect/disconnect to the server.
Have any of you encountered this before? And is it a workaround?
ie. deny that particular client connection by timeout or similar instead of crashing the PLC?
This is during a development phase of the user interface. Up to 3 others connect/disconnect to the OPC server frequently to test their code. It is a bit troublesome that the PLC crashes several times a day because of this 
I greatly appreciate all comments. I hope it exists a fix for this, or something I can implement that hinders the crash.
I attached the logfile for the crash
I will recommend to contact the WAGO Technical support of your country.
It will be able to help faster that what can we do here.
Is that a PFC100 G2 ?
There is a similar known issue which has been fixed in FW28.
If possible try upgrading. Otherwise contact WAGO support, they can provide an IPK that fixes this issue.
1 Like
Thanks for your answer, @quenorha 
appreciate it!
Yes this is a PFC100 G2.
The firmware is fw 28. This upgrade was the suggestion from support, but the problem is similar as before. Was hoping that there was some kind of temporary fix I could do before SP21 fix. Was told there was a plan to fix this issue in a new SP release, and that there was little that could be done before that.
Thanks for the information.
I was not aware that the problem could remain despite the update.
Let us know if you get further information.
I think we just have to have some constraints on the client side to not connect and disconnect to often.
Do you know if it is possible to end a connection to an OPC client inside the Codesys Environment? Maybe define it in the program?
ie. if I detect too many connects/disconnects within a timeframe, I can disconnect the client from the server (maybe also for a limited amount of time)? That would fix this issue, before Codesys/Wago implement fixes in their firmware.
