-
Notifications
You must be signed in to change notification settings - Fork 48
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
ControlBoard configuration #6
Comments
ros_control basically implement what is implemented in the .ini files of iCub. |
Perfect, my idea is doing something like:
I was wondering where to include the simulator specific information (so the mapping between the joint names and the controlBoard axis. I prefer to use as much as possible the same .ini file used in the original robot (to separate control parameters from simulation parameters), so the possibilities are:
|
I resorted to put all the configuration in the same .ini file, using only groups starting with GAZEBO for gazebo specific configuration. I guess we can consider this issue closed with #8 . |
I opened this issue for defining how to pass information (name of the part, port opened, joint controlled) to the controlboard plugin.
@EnricoMingo I was unable to answer in Yammer that is not working for me.
Returning in topic:
What is the way implemented in ros_control? As far I can tell adding child elements to the tag is the standard way of passing information to the gazebo plugin, also for the ros plugins ( http://gazebosim.org/wiki/Tutorials/1.9/ROS_Motor_and_Sensor_Plugins ).
The text was updated successfully, but these errors were encountered: