robotology / icub-tech-support

Virtual repository that provides support requests for individual robots
GNU General Public License v2.0
20 stars 1 forks source link

ergoCub 1.1 S/N:001 – Fingers cannot reach the upper limits and have jerky motions #1703

Open PasMarra opened 6 months ago

PasMarra commented 6 months ago

Robot Name 🤖

ergoCub 1.1 S/N:001

Request/Failure description

While testing the aperture and closure of the fingers, I've noticed the following:

Detailed context

I'll provide some plots, each one shows the desired trajectory vs the joint actual trajectory for both the hands, the joints values are in radian.

Additional context

thumb_add

thumb_add

thumb_add_zoom thumb_add

thumb_oc

thumb_oc thumb_oc

index_add

index_add index_add

index_oc

index_oc index_oc

middle_oc

middle_oc middle_oc

ring_pinky_oc

ring_pinky_oc ring_pinky_oc

How does it affect you?

No response

AntonioConsilvio commented 6 months ago

Hi @PasMarra, thanks for the feedback. We are already aware of the problems present on the fingers and have an internal issue where we are planning how to take corrective action.

maggia80 commented 6 months ago

Thanks, @PasMarra for the detailed analysis. it's interesting to see also the motor position, the PWM output and the current while performing the movements.

lornat75 commented 6 months ago

@maggia80 it is not a problem for us to run the experiments again - but it seems the problem is already known and under investigation from iCub Tech. are you sure you need additional data?

maggia80 commented 6 months ago

@lornat75 yes, as @AntonioConsilvio mentioned we know that there are some problems in the fingers and we are working on it. In the experiments above I see different issues and some more data could help iCub Tech and @PasMarra too to have more awareness of the system. But of course, those are data we can collect and report here in this issue.

sgiraz commented 4 months ago

Hi guys,

just an update to say that team-dev w/ the support of @PasMarra is working on finding a solution to fix this issue.

cc @AntonioConsilvio @Fabrizio69 @fbiggi @fiorisi