Controller Spawner couldn't find the expected controller_manager ROS interface.

[yuan0623]

Dave
Hi, my name is Yuan and I'm following the tutorial Gazebo ROS demo, I have a smooth experience on following the tutorial except for the rrbot_control package. When I type 'roslaunch rrbot_control rrbot_control.launch' , I didn't get expected behaviour. Instead I get a warning message: [WARN] [WallTime: 1529028805.545238] [835.983000] Controller Spawner couldn't find the expected controller_manager ROS interface.
When I type rosservise list, I didn't see control/manager at all.
I download the ROS demo pkg directly from github into my workspace and 'catkin build' the package. I'm using ROS-indigo on Ubuntu 14.04. I also have Gazebo 7 installed. What can be wrong? Do you have similar experience?
Looking forward your respond!
Best

[davetcoleman]

Off the top of my head I do not know what is wrong, sorry.

[kiranpallacom]

@yuan0623 This problem occurs when you launch the rrbot_control demo while a gazebo server process is already running (in the background). Check for stray gserver processes, kill them & re-launch rrbot_control to make it work.

[ipa-msa]

make sure you have gazebo_ros_pkgs installed http://gazebosim.org/tutorials?tut=ros_installing

[yuan0623]

Thank you, guys :)

[cpuwanan]

This could be helpful
$ sudo apt-get install ros-kinetic-joint-state-controller
$ sudo apt-get install ros-kinetic-effort-controllers
$ sudo apt-get install ros-kinetic-position-controllers

[Ekanshh]

Check if the ros package has all the dependencies and install the necessary dependencies:
rosdep check *package name*
install the necessary dependencies using:
rosdep install -i <package name>
or else, try to run roslaunch directly, without going into the catkin_ws:
roslaunch *package_name* *launch_file*

[dk008652]

I have installed gazebo_ros_pkgs and even it does show that controller_manager is present in rosservice list but still having this problem

[pringithub]

I don't see the /rrbot/controller_manager either, just the controller_spawner ... any help?

[KingCoCos]

sudo apt-get install ros-kinetic-gazebo-ros-pkgs ros-kinetic-gazebo-ros-control
make sure you have installed “ros-kinetic-gazebo-ros-control”
after installation, restart the terminal

[saadi-tech]

I also have the same problem on Melodic, I have tried literally everything.. :( SOmeone please help me out.....
First I get this error for all joints, even though I have defined the PID controllers in .yaml file.

[ERROR] [1587451335.148328678, 0.195000000]: No p gain specified for pid. Namespace: /robot/gazebo_ros_control/pid_gains/j1

then after like 20 secs, it shows the warning:
[WARN] [1587451349.966721, 14.843000]: Controller Spawner couldn't find the expected controller_manager ROS interface.

Please help me out. Im using ROS melodic, and I have installed all the needed packages.

[DroppedOut]

I have same problem on Melodic

[norn93]

To fix the PID gains issue, you need to load those params in. Something like a file called gazebo_pid.yaml:

  gazebo_ros_control:
    pid_gains:
      front_right_wheel_joint:
        p: 0.1
        i: 1
        d: 0
      back_right_wheel_joint:
        p: 0.1
        i: 1
        d: 0
      front_left_wheel_joint:
        p: 0.1
        i: 1
        d: 0
      back_left_wheel_joint:
        p: 0.1
        i: 1
        d: 0

And then load it into your launch file using:

  <!-- Load the gazebo params -->
  <rosparam command="load"
          file="$(find bb1_bringup)/config/gazebo_pid.yaml"
  />

I still have the error you guys describe though:

[WARN] [1587451349.966721, 14.843000]: Controller Spawner couldn't find the expected controller_manager ROS interface.

I'm not sure how to fix this either.

[imeshsps]

Controller Spawner couldn't find the expected controller_manager ROS interface.

Hey.. for me it was package version mismatching. An package update might fix it.

[KingCoCos]

Maybe this answer will be helpful: https://answers.ros.org/question/214712/gazebo-controller-spawner-warning/

[brschettini]

It happened to me right now and I realized that a gzclient process was stuck in background.

ps -ef | grep gzclient

If that's the case, just kill it or restart you computer.