Closed warp1337 closed 7 years ago
It seems I have somehow messed up my Gazebo installation. Closing.
Hi warp, do you know what was wrong with your gazebo installation ?
Hello @warp1337 I'm happy you solved your problem. What was our version of Gazebo ? What went wrong in the installation process ? Thanks
I installed all packages (for kinetic) as mentioned in the ReadMe. However, I get the following error that indicates (IMHO) that the corresponding controller cannot be loaded.
PARAMETERS
NODES / gazebo (gazebo_ros/gzserver) gazebo_gui (gazebo_ros/gzclient) pepper_trajectory_controller (controller_manager/spawner) spawn_urdf (gazebo_ros/spawn_model)
auto-starting new master process[master]: started with pid [16343] ROS_MASTER_URI=http://localhost:11311
setting /run_id to ba0db4f2-f521-11e6-af70-9890969b8671 process[rosout-1]: started with pid [16356] started core service [/rosout] process[gazebo-2]: started with pid [16369] process[gazebo_gui-3]: started with pid [16376] process[pepper_trajectory_controller-4]: started with pid [16385] process[spawn_urdf-5]: started with pid [16387] [ INFO] [1487343589.687508533]: Finished loading Gazebo ROS API Plugin. [ INFO] [1487343589.689367997]: waitForService: Service [/gazebo/set_physics_properties] has not been advertised, waiting... [INFO] [1487343589.921023, 0.000000]: Controller Spawner: Waiting for service controller_manager/load_controller [spawn_urdf-5] process has finished cleanly log file: /home/fl/.ros/log/ba0db4f2-f521-11e6-af70-9890969b8671/spawn_urdf-5*.log [WARN] [1487343620.146810, 0.000000]: Controller Spawner couldn't find the expected controller_manager ROS interface. [pepper_trajectory_controller-4] process has finished cleanly