Hello,
We are having an issue where our UR controllers will self reboot with no error given. We are under the impression that it might be an ESD issue. This has happened a few times and normally they restart without any hassle. Today we had it happen again, the only issue this time is that all of our latest program revisions were stored locally on the controller and our last several revisions were lost and we had to start from the beginning. (it was a fairly new program and no backups had been made). Has anyone else seen this issue or have a fix for this.
I have not heard of that happening before, and I have been providing service and support for UR robots for more than 6 years now.
So sounds like a special case.
What makes you think it’s related to ESD? Are you handling plastic objects off conveyors or something else generating a lot of charge?
Regarding your lost program: Did you check the .old files for an internal backups of the program? If you go to Open Program and show all files, you will see hidden backups of programs, which Polyscope automatically creates when you save a program.
Yes, I apologize for not being more clear in my first post. We are handling plastic parts from a conveyor, and producing plastic dust through a secondary process near the robot. This is what leads us to believe that there is an ESD. I did check my .old files and nothing with our current iteration of program was findable. This issue is something we are seeing on all 3 of the UR 5e’s that are running in our system. I wanted to check the forums and see if anyone had this same issue that was unrelated to ESD.
I hope someone gets back to you with something useful, then.
You could maybe run a proper gauge wire from ground somewhere and to the robot flange/tool, if you have not already. It could help with discharges. If you have not already.
And make 100% sure that the robot controller is connected to ground, too (measure continuity between controller case and ground somewhere else).
It’s a quick way to rule out ESD being the culprit.
I am also having the same issue as presented here. We have a UR10e running 5.17.2 software that is in a machine tending cell. This has prevented lights out running as the cobot will restart itself and then not start the program again until someone comes over to fix it. I’ve only seen it occur once in person. The pendant screen went black and the cobot continued to move until it was finished with the program and waiting for the CNC cycle to end. Once it was at this part, the cobot completely rebooted itself and did not resume the program.
Hi…
Just made a reply on another post please see:
But for convenience sake I have also copy pasted my answer down below.
I used to be an Urcap developer and the only time Ive have ever seen this behavior was when I by accident completly used up the RAM of the robot controler. If you are using an URCap this might indicate, what is in programming terms are called, a “memory leak” from said URCap.
And I would try and suggest to your URCap provider that they might have a memory leak issue.
Best Regards
Note: if I’m right about the memory leak problem a regular planed reboot might help releave your problems as a reboot should clear all the memory stored in the RAM. So you are basically swapping your “unexpected reboots” out with expected reboots. Not really a solution but might help anyway.
