You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The robot currently can't receive an orientation command relative to the hole. Changing orientations is dangerous, causing fast unplanned motion of the wrist as it orbits around the TCP. To enable this feature while mitigating the risk of damaging collision, we need a reliable and transparent system for setting the desired position command and controlling the motion speed. A new motion command system is probably needed.
The text was updated successfully, but these errors were encountered:
Task has been recentered about target position as [0,0,0] for X and Y. Expected TCP orientation has been changed to have Z point up, matching the target's frame orientation, and the robot now rotates the TCP to match this orientation. Important: Make sure you flip your TCP orientations so Z points up! This is the opposite of the normal "robot flange Z = forward" convention.
The robot currently can't receive an orientation command relative to the hole. Changing orientations is dangerous, causing fast unplanned motion of the wrist as it orbits around the TCP. To enable this feature while mitigating the risk of damaging collision, we need a reliable and transparent system for setting the desired position command and controlling the motion speed. A new motion command system is probably needed.
The text was updated successfully, but these errors were encountered: