-
Notifications
You must be signed in to change notification settings - Fork 23
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
new tuned pidParams
for icub3 gazebo model for walking simulations
#219
Conversation
pidParams
for icub3 gazebo model for walking simulations
Do not worry, this repo only have a master branch. |
ki 0.35 0.35 0.35 | ||
kp 70.0 0.17 0.15 | ||
kd 70.0 0.17 0.15 | ||
ki 70.0 0.17 0.15 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just to double check: is this intentional? For all other limbs kd and ki are smaller then kp, here instead they are equal.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot for catching that. Its indeed a typo due to using multiple versions locally of the repo to do the changes and tests. Fixed the typos and tested.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a small comment on icub3 icub torso.
Ok for me, not sure if @GiulioRomualdi or @lrapetti want to double check. |
For me are fine as well, I would leave the last word to @GiulioRomualdi if he has any comment on it |
@mebbaid is the |
No. This is because the |
Friendly ping @GiulioRomualdi . |
Fine to me 😀 |
With reference to this pull request and the corresponding one in the walking-controllers (i.e this PR ). I am updating the values of the low-level position-control pid gains. These new values seems to work on several machines and also for the
stickBot
. see also this issue.P.S.
I opened the PR directly on master since the interested people are limited and the PR should not, in theory, break any other simulation related activity. Feel free to suggest a different approach.