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
We noticed it on the left pitch and roll shoulder in ergoCub1.1 S/N:001. The two joints are controlled in position and after a while even if there aren't any position commands the joint goes toward an HW limit. While moving the AMO reading seems to be blocked.
Sometimes the joint doesn't reach the HW limit, but it remains quite far from the previous position while reading a similar angular position.
Hypothesis
The AMO stops reading for some reason and the PID to reduce the error from the setpoint and the current position generates a PWM that moves the joint trying to reduce the error, but since the AMO is stuck to a fixed value, the error remains constant and the motor keeps moving.
Possible reasons:
the reading of the AMO is interpreted as a spike and the value is kept constant for a long period of time.
the AMO is not reading for some cable issues
the position of the AMO is too far or not well aligned with the magnetic target causing spikes.
The text was updated successfully, but these errors were encountered:
@AntonioConsilvio would be very helpful if you could log the encoder and motor position while this phenomenon occurs.
maggia80
changed the title
joint controlled with AMO boards used as incremental encoder stop reading going to a HW limit
joint controlled with AMO boards used as incremental encoder
Oct 18, 2023
Description
We noticed it on the left pitch and roll shoulder in ergoCub1.1 S/N:001. The two joints are controlled in position and after a while even if there aren't any position commands the joint goes toward an HW limit. While moving the AMO reading seems to be blocked.
Sometimes the joint doesn't reach the HW limit, but it remains quite far from the previous position while reading a similar angular position.
Hypothesis
The AMO stops reading for some reason and the PID to reduce the error from the setpoint and the current position generates a PWM that moves the joint trying to reduce the error, but since the AMO is stuck to a fixed value, the error remains constant and the motor keeps moving.
Possible reasons:
The text was updated successfully, but these errors were encountered: