-
Notifications
You must be signed in to change notification settings - Fork 310
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
[spawner_joint_trajectory_controller]: Could not contact service /controller_manager/list_controllers (UR robot) #1761
Comments
I just tried this locally and cannot really reproduce that. It sounds a bit like the problem, we tried to solve in #1680. Which version of ros2_control do you currently have installed? The fix should be available from version 2.43 on. |
This comment was marked as resolved.
This comment was marked as resolved.
No, that should already be included in 2.43.0. Looking at your output in more detail (Please use a code section in future posts, that is much easier to parse than images) I am missing any output of I would expect some kind of error output, though, if you did not have that installed. Specifically, I am missing something like this:
Did you run
as suggested in https://github.com/UniversalRobots/Universal_Robots_ROS2_Gazebo_Simulation?tab=readme-ov-file#setup-ros-workspace? |
Here is my output with codesection (Didn't know about this thx):
Seems like gazebo-ros2-control is well installed:
Just did again the installation as explained here UR_Gazebo_installation_for_humble:
Still got same message error. Could maybe come from my .bashrc. I tried to use a different dds, but don't changed anything. Also have both humble and gazebo_ros2_control from source, but don't seems to change anything too, so I m using debian packages installed with command:
|
Just find the culprit ! When going on this link Ur_Gazebo_HUMBLE and git clone it, it was git cloning the rolling branch ! The correct command line is Thanks sir to have taken bit of your time to help me. |
Ah, that totally explains it. For rolling we refactored things so that the ros2_control tag gets added in the ur_simulation_gazebo package. So, you never had a ros2_control tag and hence never had any gazebo_ros2_control started. I'm glad that things are working for you now! |
Describe the bug
I am trying to launch the simulation for a UR10e robot using Universal_Robots_ROS2_Gazebo_Simulation. When launching
ros2 launch ur_simulation_gazebo ur_sim_moveit.launch.py
, I get the following error:[spawner-2] [INFO] [1727077744.034227709] [spawner_joint_state_broadcaster]: waiting for service /controller_manager/list_controllers to become available...
[spawner-3] [WARN] [1727077744.081321269] [spawner_joint_trajectory_controller]: Could not contact service /controller_manager/list_controllers
(Cf screenshots below for the full message error)
To Reproduce
Steps to reproduce the behavior:
ros2 launch ur_simulation_gazebo ur_sim_moveit.launch.py
Behavior
Screenshots
Environment:
Additional context
I have install humble through deb packages, but got similar error with source. I have correctly install ros2-control and ros2-controllers through
sudo apt install ros-humble-ros2-control
andsudo apt install ros-humble-ros2-controllers
.Finally, I've tried to launch following example: ros2_control_demo_example_9_Gazebo and controller_manager load well ! But when doing
ros2 launch ros2_control_demo_example_9 test_forward_position_controller.launch.py
or simplyros2 topic pub /forward_position_controller/commands std_msgs/msg/Float64MultiArray "data:- 0.5 - 0.5"
, robot start to teleport directly to the desired position, so here (0.5, 0.5).Thanks !
The text was updated successfully, but these errors were encountered: