Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

iCubWaterloo01 S/N:044 – Mechanical issue with robot's neck #1926

Open
paliasgh opened this issue Oct 8, 2024 · 3 comments
Open

iCubWaterloo01 S/N:044 – Mechanical issue with robot's neck #1926

paliasgh opened this issue Oct 8, 2024 · 3 comments

Comments

@paliasgh
Copy link

paliasgh commented Oct 8, 2024

Robot Name 🤖

iCubWaterloo01 S/N:044

Request/Failure description

Hello, we are having an issue with the neck of our robot. When the head moves to certain positions, pitch and roll motors get disabled as the roll DOF gets stuck (is difficult to move physically).

Detailed context

When the problem happens, we can hear a clinking sound from pitch and roll motors (not sure if both or only one). Joint 0 (pitch) gives this "i2t limit exceeded" error and goes to HWF fault mode. Joint 1 goes to idle (second picture, sorry the photo is blurred).

Image
Image

When this happens Joint 1 is difficult to move at a certain point (near 0). The mechanism in the neck gets mechanically stuck somehow. You can see the issue and hear a noise in these videos. We took the belt out to see if it was the motor or the other side. It was the other side (the neck). The movement is not smooth, is noisy, and it may fully get stuck, requiring us to move it back and again forward to pass that point.

IMG_8491.mov
IMG_8492.mov
IMG_8490.mov

Thanks for your assistance!

Additional context

No response

How does it affect you?

We are in the middle of running an HRI experiment that is getting affected.

@github-actions github-actions bot changed the title Mechanical issue with robot's neck iCubWaterloo01 S/N:044 – Mechanical issue with robot's neck Oct 8, 2024
@paliasgh
Copy link
Author

Hello @AntonioConsilvio, I just wanted to follow up on this issue and see if there is any update. Thank you very much!

@paliasgh
Copy link
Author

Hello @AntonioConsilvio and @pattacini, sorry for bothering you again, we are still looking forward to hearing from you about this issue. This has significantly limited our robot's functionality. We appreciate your help.

@AntonioConsilvio
Copy link
Contributor

Hi @paliasgh sorry for the late reply.
Considering the several problems presented by your robot, we were thinking that the best solution might be to either come to you to work on the robot directly or have the robot come back to us so that we can fix it.

We will provide you with more information on this in the near future, I mean to ask you if you would agree to intervene with one of these two options. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Triage
Development

No branches or pull requests

2 participants