I have a problem with plantsimulation 14.2 using OPC UA interface.
I setup it with read and write interval to 100 and I have more than 50 triggers on points that just set plantsimulation variable.
I'm connected to simulated OPC point via softing OPC. The link works perfectly during a time and suddenly it stop.
I look for task manager and I see that 100% of my processor is used by plant simulation on all core.
Plantsimulation process is in status not response. I get the wait chain and a plant simulation thread is waiting for an other plant simulation thread. as you can see below
Does anyone else have the same bug ?
Solved! Go to Solution.
This is possibly a known bug that was discovered a couple of weeks ago.
To check if this is actually the same bug, please use the Process Explorer (by Mark Russinovich) that you can freely download from Microsoft.
Start the Process Explorer, look for the "PlantSimulation14_2.exe" process and select "Properties..." from the context menu. Activate the tab "Threads". Select the "PlantSimulation14_2!..." thread and then click the button "Stack". Please post a screenshot of the stack window.
For the known bug the call stack looks something like this:
We are still trying to find the reason for the deadlock. The deadlock happens in the OPC UA Client Stack from the OPC Foundation. It is still unclear if the bug is in the Client Stack or is caused by Plant Simulation. We are currently working hard on finding the cause for the problem. More information could be helpful. Does the deadlock only happen when the 3D viewer is running, or does it also happen in a 2D-only model?
He, thanks for reply,
I have this :
My model is a 2D only so I don't test it with 3D.
Another customer has a very similar problem that we are looking into for quite a while now. We are now finally able to reproduce this issue in or environment, and we're working on isolating to issue and hopfully fixing the bug. It's likely that this fix will also resolve your issue. We'll keep you posted.
We finally fixed the bug. If you cannot wait for the next maintenance pack, you can get a hotfix. For this please contact your local support.
We plan to release the next maintenance packs by the end of April.