ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

Revision history [back]

This sounds like you try it on fuerte (and used it on electric the last time you tried). The Gazebo server (simulation) and client (visualization) have been split into two independent processes starting with fuerte, which means that old launch files might start up without a Gazebo GUI. Start the launch file and type

rosrun gazebo gui

afterwards. The Gazebo GUI should come up then.

This sounds like you try it on fuerte (and used it on electric the last time you tried). The Gazebo server (simulation) and client (visualization) have been split into two independent processes starting with fuerte, which means that old launch files might start up without a Gazebo GUI. Start the launch file and type

rosrun gazebo gui

afterwards. The Gazebo GUI should come up then.

/edit: As mentioned below in the comments, the above wasn't the solution. Just tried it myself, and the robot indeed doesn't spawn with the spawner waiting for the spawn model service to appear. It works with the laser equipped erratic, however:

roslaunch erratic_description erratic_laser_wg_world.launch

or:

roslaunch erratic_description erratic_laser_empty_world.launch

For the latter, you have to start the gui manually as it appears it was forgotten in the launch file.

Not sure why it doesn't work with the launch file in the original question, I suspect either a) a subtle difference in launch files that I didn't catch or b) a timing problem during gazebo startup which leads to the spawn model service not getting called.

This sounds like you try it on fuerte (and used it on electric the last time you tried). The Gazebo server (simulation) and client (visualization) have been split into two independent processes starting with fuerte, which means that old launch files might start up without a Gazebo GUI. Start the launch file and type

rosrun gazebo gui

afterwards. The Gazebo GUI should come up then.

/edit: As mentioned below in the comments, the above wasn't the solution. Just tried it myself, and the robot indeed doesn't spawn with the spawner waiting for the spawn model service to appear. It works with the laser equipped erratic, however:

roslaunch erratic_description erratic_laser_wg_world.launch

or:

roslaunch erratic_description erratic_laser_empty_world.launch

For the latter, you have to start the gui manually as it appears it was forgotten in the launch file.

Not sure why it doesn't work with the launch file in the original question, I suspect either a) a subtle difference in launch files that I didn't catch or b) a timing problem during gazebo startup which leads to the spawn model service not getting called.

/edit: As apparent from answer by arebgun, it was a) ;)