What would cause this error?
Could it be software or hardware?
Or programming?
IRB2400 S4 controller basic 2.0
50056 IRB1 Joint Collision Error
-
Rob H. -
June 30, 2016 at 9:57 PM -
Thread is marked as Resolved.
-
-
It should be related with mechanical or drive problem. Also, be sure all cable and connectors are ok !
-
I have usually found that some part of the tooling or dress pack has got between two joints on the robot during a movement, and the robot has hit itself. When it happens, take a careful look at all axes, to find where something the robot is holding may have hit the robot.
Stop hitting yourself, stop hitting yourself!
-
What's on the end-of-arm?
How fast is the robot moving?
Rapid direction change CAN cause the error. -
There is nothing in the way for it to hit.
And it is being used to weld, I run it at 60% on rapids, and it's a simple straight in circular pattern and straight out the same way in. The reason i'm asking as it does this on every program I run. -
You probably already have, but check the load/tool definition.
How heavy is it, and how fast is it trying to move?
Does it fault if you slow down the motion?
Is it always the same axis? (Which one?) -
You probably already have, but check the load/tool definition.
How heavy is it, and how fast is it trying to move?
Does it fault if you slow down the motion?
Is it always the same axis? (Which one?)Thanks I will check the load/tool definition,
Not always the same joint sometimes irb2
It only does it when it sits idle in automatic mode for about 4 to 6 minutes. it drop down abot 5 inches. -
I've had brakes slip when the motor seals leak, but they usually generate a different error.
Does the motor get hot? (I presume the robot isn't pushing against a limit switch.) -
I've had brakes slip when the motor seals leak, but they usually generate a different error.
Does the motor get hot? (I presume the robot isn't pushing against a limit switch.)Load/definition tool seems fine
will check limit switch today.
Thanks for your help.
Much appreciated -
If it faults sitting still, I'd wonder about a drive. Errors on different axes doesn't sound promising. Replacing the axis computer guarantees a system reload (never painless).