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.
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.
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.
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.
Sometimes this is OPC UA unhandled exception, sometimes this is SIGABRT signal.
The probable cause is that the OPC UA client stops working without deleting the subscription and disconnecting from the server.
The exception occurs after several successful connections to the server without a correct disconnection.
Now I am looking for a solution to make PFC200 PLC work 24 hours a day without rebooting…
I have recently been trying to help troubleshoot a similar error. I believe it is related to a known CODESYS issue:
“CDS-90067: OPC UA Stack: dangling SecureListener pointer leads to crash during SecureChannel timout handling”
In my particular case, it appears to be exacerbated by a Browse command from NodeRed; Subscribe and Write commands from the same palette appear stable. But also, my log file does not follow the same pattern as SigurdRB’s, even though the end result (unhandled exception) is the same.
Any resolution to this issue? This appears to be a major issue still. An OPCUA connection reset/disconnect resulting in a crashed controller should be a High Priority for CODESys…
Last I heard, there are several OPCUA improvements expected with SP21 from CODESYS. I don’t have any information about when SP21 will be released, nor when a matching FW from WAGO is scheduled.
I was able to test an alpha version of the SP21 runtime, and it appeared to fix the specific issue I was having, but again, I do not have any details about a release timeframe.
Since the FW28 use the codesys runtime 3.5.19.70 i don’t think the report is relevant.
You need to wait for the FW29 which will be with the runtime 3.5.21.xx
Hi, my issue is in CC100. But the sam thing. When can I expected FW29 to be released. Are there any other options you recommend to connect to a system like Ignition SCADA.
I understand Wago is dependent on CodeSys release of SP21 to release newer firmwares. However, this initial incident was brought to the table back in November 2024. 6 months of consistent OPCUA crashing on a controller is not acceptable and removes a lot of confidence in the system by our end users who rely on an industry standard OPCUA connection.
What is the resolution and are we sure FW29 is going to resolve the issue?
Please let me know what we can do to help Wago troubleshoot and resolve this issue.
Indeed this problem was found late in 2024.
Unfortunately this problem wasn’t in WAGO hands since it needed to be fixed by Codesys.
Because of this our hand where tied and we needed the fix by Codesys.
Then after Codesys release the updated runtime and IDE there is a development time needed to integrate them into the different Firmware.
Have you tried to ask directly WAGO Technical support ?
Here we can only share our knowledge and do the best we can and take additional time on our workload to try to help you the best we can.
Unfortunately we aren’t directly related to the WAGO technical support and don’t have access to their tools.
appreciate it!
in the CODESYS V3.5 SP21