We have seen that error on the e-series, its generally when we have some calculation that is running and taking up too many resources. A lot of times we will also see a protective stop that says something like "real-time thread getting too far behind process" and that is an indication that the issue is in a thread and can't keep up with the main process thread. Generally we can find something in the program that is using too many resources.
We have had it happen when we had a bad calculation of motion and asked the robot to basically do something that it could not compute fast enough, once we fixed the motion calculation the issue went away.
hello
I am using UR3e and I get the following error.
Anyone know this problem?