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

gazebo-yarp-plugins use with roslaunch #123

Closed
traversaro opened this issue Jul 26, 2014 · 4 comments
Closed

gazebo-yarp-plugins use with roslaunch #123

traversaro opened this issue Jul 26, 2014 · 4 comments

Comments

@traversaro
Copy link
Member

Hi ROS and gazebo-yarp-plugins users @EnricoMingo @arocchi @MirkoFerrati, we have a question for you.
Here at the iCub summer school @miaragao is working in integration the gazebo_yarp_controlboard plugin in its Vizzy robot simulation.
He is launching the simulation using roslaunch as described in the gazebo ros documentation, and apparently the GAZEBO_PLUGIN_PATH does not contains the directory in which the gazebo-yarp-plugins are found, even if the

export GAZEBO_PLUGIN_PATH=${GAZEBO_PLUGIN_PATH}:/path/to/gazebo-yarp-plugins/build

iine in .bashrc is correctly set. Apparently roslaunch is overwriting at some point the GAZEBO_PLUGIN_PATH environment variable.
Have you every experienced something similar, and you know a clean solution to this problem?
Thanks

@MirkoFerrati
Copy link
Contributor

Have a look at this http://wiki.ros.org/roslaunch/XML section 2

@traversaro
Copy link
Member Author

This should be fixed for GAZEBO_MODEL_PATH by Gazebo PR https://bitbucket.org/osrf/gazebo/pull-request/1430/preserve-previous-gazebo_model_path-values/diff , as explained in https://bitbucket.org/osrf/gazebo_tutorials/issue/27/roslaunch-not-working-properly-when-using .
A similar fix for GAZEBO_PLUGIN_PATH should solve this bug.

@traversaro
Copy link
Member Author

This bug should be solved by https://bitbucket.org/osrf/gazebo/pull-request/1430/preserve-previous-gazebo_model_path-values/diff (thanks @scpeters!) in Gazebo 4.1 , and I guess it will be propagated to following versions.

@mikearagao feel free to re-open if the problem persists , or if we need to solve this even for Gazebo versions older then 4.1 .

@scpeters
Copy link

I merged it forward to gazebo5 and the default branch, though it hasn't been released in any debian packages yet.

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

3 participants