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

[aleksandergabriel]

Hello

I am trying to use your code as a base for a project vith Ev3. I am running ros kinetic on ubuntu 16.04 and ros jade on debian Jessie (raspbery pi). The upper error appears on both machines when I try to run roslaunch h4r_ev3_launch ultrasonic.launch ev3_hostname:=ev3brick1 (hostname was changed and correct one)
The connection between machines is fine. I can ping all machines and can see messages with rostopic echo / when I run rostopic pub -r 1 /krneki std_msgs/String test_msg. roscore is runing on computer/rpi, ev3_manager is running on ev3 and then roslaunch command is being executed.

My first idea was that ev3 is too slow, so I set respawn to true in launch file, but that did not solve the problem. Could this error arise due to different ros versions on ev3 and compiter/rpi?

Whole output:
... logging to /home/ales/.ros/log/7504273a-a398-11e7-bdd8-aced5c9f81a2/roslaunch-wendigo-4584.log
Checking log directory for disk usage. This may take awhile.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.

started roslaunch server http://192.168.8.105:34833/

SUMMARY

PARAMETERS

• /ev3brick1/Ev3UltraSonic/frame_id: ultrasonic_link
• /ev3brick1/Ev3UltraSonic/max_range: 1.5
• /ev3brick1/Ev3UltraSonic/min_range: 0.01
• /ev3brick1/Ev3UltraSonic/mode: distance
• /ev3brick1/Ev3UltraSonic/port: in2
• /ev3brick1/Ev3UltraSonic/publish_rate: 10
• /ev3brick1/Ev3UltraSonic/topic_name: /ultrasonic
• /ev3brick1/Ev3UltraSonic/type: h4r_ev3_control/E...
• /rosdistro: kinetic
• /rosversion: 1.12.7

NODES
/ev3brick1/
ev3_sensor_spawner (controller_manager/spawner)

ROS_MASTER_URI=http://localhost:11311

core service [/rosout] found
process[ev3brick1/ev3_sensor_spawner-1]: started with pid [4602]
[INFO] [1506526195.200964]: Controller Spawner: Waiting for service controller_manager/load_controller
[WARN] [1506526225.224220]: Controller Spawner couldn't find the expected controller_manager ROS interface.
[ev3brick1/ev3_sensor_spawner-1] process has finished cleanly
log file: /home/ales/.ros/log/7504273a-a398-11e7-bdd8-aced5c9f81a2/ev3brick1-ev3_sensor_spawner-1*.log
all processes on machine have died, roslaunch will exit
shutting down processing monitor...
... shutting down processing monitor complete
done
``

[OTHMAN007]

Hi ! I have the same problem for a school project , did u solve this problem ?

[dhruvil122]

did you fix the problem? I have the same problem. How did you fix the controller_manager ros interface problem?