RobotStudio event

Problems with IRC5 controller

Hello, we own a IRC5 M2004 controller with IRB120 M2004 robotic arm, it was previously used by others from our institution for years, then it was put in storage. By the way we are a University so no industrial use has it seen. Now we want to bring it back to life, but when we turn it ON, we get an error that we can't figure out why, we did change the broken SMB cable between the robot and controller, but still problems. Also when its on its in system failure mode, and almost all option are greyed out and can't be interacted with. 

Answers

  • lemster68
    lemster68 ✭✭✭
    Check the connection inside the controller to the SMB.  See if there are status lights indicating failure.  Exercise caution with the controller door open while power is on, high voltages are present.
    Lee Justice
  • There's a lot of reasons it could be in system failure. Can you share a screenshot of the event log in robot studio? Or provide details about the errors? One of the errors will likely contain a "Consequences" section that says something like "Controller goes into system failure". This will probably be the error to start with, but there might be other errors that take place before this one which can be the real root cause. If it sat for a few years without prior issues, it could be a loose connection inside the IRC5 like lemster68 says. A module might not be communicating or powered on.
  • when we turn the controller on the only error that shows up on the pendant and on robot studio is the error 38103.
  • But for what lemster68 suggested we will try to look in the SMB connection inside if its loose or something 
  • we had to replace our smb board before. Same errors