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

ergoCub 1.1 S/N:001 – Left shoulder roll overcurrrent #1830

Closed
evelyd opened this issue Jun 18, 2024 · 7 comments
Closed

ergoCub 1.1 S/N:001 – Left shoulder roll overcurrrent #1830

evelyd opened this issue Jun 18, 2024 · 7 comments
Assignees
Labels
ergoCub 1.1 S/N:001 ergoCub1.1 platform

Comments

@evelyd
Copy link

evelyd commented Jun 18, 2024

Robot Name πŸ€–

ergoCub 1.0 S/N:001

Request/Failure description

The left shoulder roll failed two separate times in the span of an hour.

Detailed context

The error it gives is that the i2c limit is exceeded, and we saw in the logged data that the current for the left shoulder roll motor is much higher than that of the right shoulder roll. Touching the motor shows that it is very hot.

@S-Dafarra mentioned that there was a similar issue during the demo last week in Bologna.

Additional context

l_shoulder_roll_overcurrent

How does it affect you?

I can't test walking trajectories without risking burning this motor.

@evelyd evelyd added the ergoCub 1.1 S/N:001 ergoCub1.1 platform label Jun 18, 2024
@github-actions github-actions bot changed the title Left shoulder roll overcurrrent ergoCub 1.0 S/N:000 – Left shoulder roll overcurrrent Jun 18, 2024
@github-actions github-actions bot added the ergoCub 1.0 S/N:000 ergoCub robot (prototype) label Jun 18, 2024
@evelyd evelyd removed the ergoCub 1.0 S/N:000 ergoCub robot (prototype) label Jun 18, 2024
@evelyd evelyd changed the title ergoCub 1.0 S/N:000 – Left shoulder roll overcurrrent ergoCub 1.0 S/N:001 – Left shoulder roll overcurrrent Jun 18, 2024
@maggia80
Copy link
Contributor

thanks @evelyd, could you please add the log of the yarprobotinterface?

@AntonioConsilvio
Copy link
Contributor

Hi! I would like to add the interventions that we did in Bologna to try to solve the problem (clearly not enough):

  • 2FOC replacement

  • LCORE5 replacement

  • Optical disc cleaning

The robot worked correctly during the demo, but the problem reoccurred when we returned.

@evelyd
Copy link
Author

evelyd commented Jun 18, 2024

thanks @evelyd, could you please add the log of the yarprobotinterface?

Hi, unfortunately I don't have that log. But here is the logged data from the last test before the shoulder faulted (the fault happened while the robot was just hanging in the air afterward): mat file in case it helps.

@evelyd
Copy link
Author

evelyd commented Jun 19, 2024

Hi, as an update, I tried to use the robot again today, and after running the calibration this motor kept faulting, so it seems like it's burned.

Here is the yarprobotinterface log from this event @maggia80:
l_shoulder_roll_fault_log.txt

@AntonioConsilvio AntonioConsilvio moved this from Triage to In Progress in iCub Tech Support Jun 19, 2024
@isorrentino
Copy link

isorrentino commented Jun 20, 2024

Today I started the yarprobotinterface with the modifications introduced by @AntonioConsilvio to recalibrate the motor

image

but the motor went in the opposite direction and the arm broke the neck tendons.

Here is the log

log_ergocub-torso_yarprobotinterface_7194.txt

The next two runs the shoulder pitch went to hardware fault and the shoulder roll did not calibrate.

log_ergocub-torso_yarprobotinterface_15692.txt

trim.84262281-08F1-4178-A386-34B42364D631.MOV

@AntonioConsilvio AntonioConsilvio changed the title ergoCub 1.0 S/N:001 – Left shoulder roll overcurrrent ergoCub 1.1 S/N:001 – Left shoulder roll overcurrrent Jun 21, 2024
@AntonioConsilvio
Copy link
Contributor

Hi! @fbiggi opened the coupling and cleaned the motor and gearbox.

Also replaced the optical disc and then recalibrated the joint, see PR:

This intervention was not enough, so we tested the motor phases and they were fine. We also tried to move the motor with a motor test tool and it worked properly.

Then we tried testing the LCORE5 and it was giving some problems. So I tested the cables from the connector that came out of the crimp.

Now I fixed the wiring, and put a new cover on the sensor to prevent it from getting damaged again.

I tested the robot for a while and it seems to be working properly!

I leave the issue still open for any feedback.

cc @maggia80 @evelyd @isorrentino @S-Dafarra

@AntonioConsilvio AntonioConsilvio moved this from In Progress to Review/QA in iCub Tech Support Jun 21, 2024
@AntonioConsilvio
Copy link
Contributor

Since the problem did not reappeared, I proceed with closing the issue!

@github-project-automation github-project-automation bot moved this from Review/QA to Done in iCub Tech Support Jul 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ergoCub 1.1 S/N:001 ergoCub1.1 platform
Projects
Status: Done
Development

No branches or pull requests

5 participants