Customer has 2 sister lines built a year apart. They stopped running one and use it for spare parts.
Have an E2S453SM-UL robot and DU520 motion controller.
Description of failure from the customer was that the robot "lost postion and lost all the comms lights"
We walked into the RC+ software reporting SPEL driver faults. Uninstalled and reinstalled the software.
Estop safety circuit error was the follow up that prevented us from opening the robot manager.
At this point I have swapped the Epson PC, the DU520, and the cable package in question.
These actions have resolved the comms faults and the estop circuit fault.
After loading the configs in the motion screen and trying to get motors on, we have error 5002 that is the DMB board fault. Given that we've replaced everything, it would lead you to believe that we have something wrong with the cfgs. I doubt this is true based upon the fact that they were numbered according to the serial numbers on the equipment.
Can anyone claim that you might still have this error 5002 based upon damage to the robot motors/encoders?