-
Notifications
You must be signed in to change notification settings - Fork 176
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
Allow dynamically configure PID controller gains #249
Comments
Why do we need this? Did you experience issues with varying loads? |
Was a Bill's suggestion. We don't need it by now, really. But is a nice feature for advanced users. For example to climb slopes, haul heavy loads or simply customize robot operation. |
Btw, my robot provides it and is much crappier than kobuki! |
Are you trying to tease us? 2013/5/22 corot [email protected]
Marcus Liebhardt |
Another idea, have split pid's in the robot, on for low speeds, another for high speeds. Actually maybe not such a great idea, it's the payload that causes the problems. PID's for kobuki are currently well tuned, for turtlebot not. |
Target:
|
updating firmware protocol documentation remains. |
Also we need to check that firmware's minor version is >= 2. If not, show a warning with the Kobuki firmware updates URL. if (firmware.check_minor_version() < 0) .... |
And add the same message in the wiki! |
…m PID gain setting. Issue yujinrobot#249.
Updated doxygen script and firmware specification about custom pid gain setting. Issue #249.
Also add notes on the wiki and in the doxygen specifying what the default values are so people have a reference point for experimentation. |
Factory default value of PID gains added on doxygen by 3a0bf5e. |
Version of updated firmware is 1.2.0. It is not released yet on http://files.yujinrobot.com/kobuki/firmware. |
firmware released, changelog also updated. |
roswiki also updated on http://wiki.ros.osuosl.org/kobuki_node/hydro |
We need to change firmware, driver and node.
Don't forget a huge warning in the doc to prevent beginners to play with this!
The text was updated successfully, but these errors were encountered: