-
Notifications
You must be signed in to change notification settings - Fork 18
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
ergoCubGazeboV1 - joints l_shoulder_yaw and l_wrist_yaw joints go in hardware fault #60
Comments
Hi @xEnVrE!
Sure! For the time being we can fix this issue like you said. |
I probably found out the problem, I will submit the fix soon @xEnVrE |
Thanks @Nicogene |
Hi @Nicogene, I have updated and installed the latest When launching this gazebo world: ergoCub_lifting_40.zip I immediately get failure of left wrist and shoulder yaw:
|
Removing the derivative gains as mentioned in #60 (comment) solves the issue also for this case. @Nicogene let me know if you want me to open a new issue or re-open this one |
I will double check again if the corrected model was loaded in my test |
While testing the simulation using the
ergoCubGazeboV1
model, I noticed that often the jointsl_shoulder_yaw
andl_wrist_yaw
go in hardware fault, especially when thel_elbow
joint is moved.By playing a bit with the tuning of the PID in simulation, I noticed that the problem seems to disappear by removing the derivative action for joints
l_shoulder_yaw
andl_wrist_yaw
- not saying this is the cause, maybe the derivative action is just emphasizing the effect caused by the real problem, e.g. wrongly scaled inertias, etc..Is it ok to open a PR in order to change them in the file used by the urdf generator, i.e. https://github.com/icub-tech-iit/ergocub-software/blob/master/urdf/simmechanics/data/ergocub/conf/gazebo_ergocub_left_arm.ini? Otherwise, at the moment, the left arm is quite not usable.
Have the current values of the PID been inherited from iCub2.x simulated models or have they been tuned somehow?
Thanks
The text was updated successfully, but these errors were encountered: