iCubGenova11 S/N:050 – Left arm wrist does not calibrate

[PasMarra]

Robot Name 🤖

iCubGenova11 S/N:050

Request/Failure description

Today I tried to start up the robot, but the left wrist did not calibrate.
After opening the yarpmotorgui I realized that the encoder of the wrist are not working or seems to be. Moreover, the shoulder and other parts are not calibrating as well.

Detailed context

I have attached the log from the yarprobotinterface.
log_icub-head_yarprobotinterface_1775.txt

Additional context

No response

How does it affect you?

No response

[sgiraz]

/remind 24 October Maintenance activity scheduled for the day after tomorrow

cc @GiacomoVassallo13 @AntonioAzocar @Fabrizio69 @xEnVrE @PasMarra

[xEnVrE]

24 October Maintenance activity scheduled for tomorrow

Is the maintenance scheduled for October 25 then? Is not the robot involved in the demos for the PI16? cc @sgiraz

Thank you

[pattacini]

Is not the robot involved in the demos for the PI16?

Yes!

cc @martinaxgloria

[martinaxgloria]

@xEnVrE the demos for the PI16 are on October 25th during the afternoon and iCubGenova11 is involved.

@sgiraz could you move the maintenance activity to the day after, please?

[AntonioAzocar]

Hi @xEnVrE, I found the black cable of the AEA2 (Name: AE6 2S2) broken, so I re-soldered it.

The left arm wrist is working properly again, but we've found other problems.
As you can see in this photo, the thumb oppose has a problem to encoder that reads very high values.
We should do more test to understand better the problem.

Thanks @martinaxgloria for your help!

cc @sgiraz @AntonioConsilvio

[xEnVrE]

Thanks for the update @AntonioAzocar.

Do you want me to open a dedicated issue in order to fix that so that we can close this one - as the wrist is now working as expected?

Thanks

[AntonioAzocar]

Yes, perhaps it would be better to have a dedicated issue, thanks!

cc @sgiraz

[sgiraz]

The left arm wrist is working properly again, but we've found other problems.
As you can see in this photo, the thumb oppose has a problem to encoder that reads very high values.
We should do more test to understand better the problem.

Hi @xEnVrE feel free to open a new issue in order to track the problemi mentioned by @AntonioAzocar in the comment above.
I proceed to close this issue.

cc @AntonioConsilvio