Why would M3iA/R30iB fall into occasional "Limit error J1,J2,J3", after starting tracking motion?
Not "Position not reachable" nor "Track destination gone", but "Limit".
When this happens, the robot is far from the downstream boundary, and not on any joint limit, even after stop by the error.
This is a single item tracking, no vision, no queue.
Limit error on tracking motion start
-
Sergei Troizky -
March 4, 2018 at 1:18 AM -
Thread is Resolved
-
-
Maybe the trigger got moved? Maybe it has always been on the close side and someone remastered? Maybe someone touched up the start tracking point? Now it just cannot get there in time? Just throwing out stuff I have seen.
-
The problem is intermittent and appears only on some items during operation, with no any changes in the setup.
The robot is far from boundaries and its own reach limits at the moment.And should "cannot get there in time" cause the "Limit error"?