Skip to content
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

Closed
traversaro opened this issue Oct 25, 2013 · 3 comments
Closed

ControlBoard configuration #6

traversaro opened this issue Oct 25, 2013 · 3 comments

Comments

@traversaro
Copy link
Member

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 ).

@EnricoMingo
Copy link
Member

ros_control basically implement what is implemented in the .ini files of iCub.

@traversaro
Copy link
Member Author

Perfect, my idea is doing something like:

<plugin name="coman_yarp_gazebo_plugin" filename="libyarp_gazebo.so">
        <yarpConfigurationFile>file.ini</yarpConfigurationFile>
</plugin> 

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:

  • Using a different .ini yarp file
  • Adding the parameters in the SDF as child of plugin tag. I would prefer this solution for compactness, but apparently the only way to include a list of names would be: <jointNames>name1 name2 name3 ..</jointNames> that doesn't seem too clean to me.

@traversaro
Copy link
Member Author

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 .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants