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
For some reason the right shoulder roll joints of the robot seems to "shift" it's lower limit bringing the arm closer to the torso.
Detailed context
It appears that the right shoulder roll joints randomly changes its lower limits. This results in the arm going closer to the torso and, when this happens during scripted movements, in unforseen collisions between the forearm/hand and the torso. This has already happend at least 3 times but we weren't able to determine the exact conditions that triggered this strange behavior.
Additional context
No response
How does it affect you?
This issue can lead to issues during tests and demos and can easily damage the robot. We have an event from the 10 to the 12 of April in Genova and we would need this problem addressed by then in order to be as safe as possible during the demos with the guests.
The text was updated successfully, but these errors were encountered:
hi @elandini84, on friday it happened that the roll suddenly went to zero while the encoder was still at 50, it seems a problem related to the wrong encoder value as #2104
Robot Name 🤖
R1 S/N:003
Request/Failure description
For some reason the right shoulder roll joints of the robot seems to "shift" it's lower limit bringing the arm closer to the torso.
Detailed context
It appears that the right shoulder roll joints randomly changes its lower limits. This results in the arm going closer to the torso and, when this happens during scripted movements, in unforseen collisions between the forearm/hand and the torso. This has already happend at least 3 times but we weren't able to determine the exact conditions that triggered this strange behavior.
Additional context
No response
How does it affect you?
This issue can lead to issues during tests and demos and can easily damage the robot. We have an event from the 10 to the 12 of April in Genova and we would need this problem addressed by then in order to be as safe as possible during the demos with the guests.
The text was updated successfully, but these errors were encountered: