Skip to content
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.

Sign up for GitHub

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

Jump to bottom

ROS2 Humble with Ubuntu 22.04 can't communicate with the demos robots #893

Closed
ruca03 opened this issue Feb 5, 2024 · 18 comments · Fixed by #896
Closed

ROS2 Humble with Ubuntu 22.04 can't communicate with the demos robots #893

ruca03 opened this issue Feb 5, 2024 · 18 comments · Fixed by #896
Labels
bug Something isn't working

Comments

@ruca03
Copy link

ruca03 commented Feb 5, 2024 •
edited
Loading

Describe the Bug
I installed the webots from the source files and when i run: ros2 pkg xml webots_ros2 | grep version
It returns:
<version>2023.1.1</version>

I start the demo with ros2 launch webots_ros2_universal_robot multirobot_launch.py.
While both arms spawn and the conveyor starts to move with the soda can on top, both arms remain frozen.

The only warnings the webots console gives is when the soda can touches the arm:
WARNING: Contact joints between materials 'default' and 'default' will only be created for the 10 deepest contact points instead of all the 12 contact points.

For what i could understand the controllers and the robots arent communicating with each other. Do you guys know what is happening or can you guys tell me what I'm doing wrong?

The terminal used to launch the demo gives the following response:

[INFO] [launch]: All log files can be found below /home/rui/.ros/log/2024-02-05-16-59-59-481893-rui-REPLANT-5596
[INFO] [launch]: Default logging verbosity is set to INFO
WARNING: No valid Webots directory specified in `ROS2_WEBOTS_HOME` and `WEBOTS_HOME`, fallback to default installation folder /home/rui/.ros/webotsR2023b/webots.
[INFO] [webots-1]: process started with pid [5597]
[INFO] [ros2_supervisor.py-2]: process started with pid [5599]
[INFO] [webots_controller_UR5e-3]: process started with pid [5602]
[INFO] [webots_controller_abbirb4600-4]: process started with pid [5605]
[INFO] [ros2-5]: process started with pid [5607]
[webots_controller_abbirb4600-4] Cannot connect to Webots instance, retrying for another 50 seconds...
[webots_controller_UR5e-3] The specified robot is not in the list of robots with <extern> controllers, retrying for another 50 seconds...
[ros2_supervisor.py-2] The specified robot is not in the list of robots with <extern> controllers, retrying for another 50 seconds...
[webots_controller_abbirb4600-4] The Webots simulation world is not yet ready, pending until loading is done...
[webots_controller_UR5e-3] The Webots simulation world is not yet ready, pending until loading is done...
[ros2_supervisor.py-2] The Webots simulation world is not yet ready, pending until loading is done...
[webots_controller_abbirb4600-4] [INFO] [1707152406.792231304] [resource_manager]: Initialize hardware 'WebotsControl' 
[webots_controller_abbirb4600-4] [INFO] [1707152406.792328131] [resource_manager]: Successful initialization of hardware 'WebotsControl'
[webots_controller_abbirb4600-4] [INFO] [1707152406.792438849] [resource_manager]: 'configure' hardware 'WebotsControl' 
[webots_controller_abbirb4600-4] [INFO] [1707152406.792444473] [resource_manager]: Successful 'configure' of hardware 'WebotsControl'
[webots_controller_abbirb4600-4] [INFO] [1707152406.792453572] [resource_manager]: 'activate' hardware 'WebotsControl' 
[webots_controller_abbirb4600-4] [INFO] [1707152406.792456950] [resource_manager]: Successful 'activate' of hardware 'WebotsControl'
[webots_controller_abbirb4600-4] [INFO] [1707152406.795363743] [abb.controller_manager]: Subscribing to '~/robot_description' topic for robot description file.
[webots_controller_abbirb4600-4] [INFO] [1707152406.795778526] [abb.abbirb4600]: Controller successfully connected to robot in Webots simulation.
[ros2_supervisor.py-2] [WARN] [1707152406.842193865] [Ros2Supervisor.Ros2Supervisor]: The URDF Spawner is deprecated. It will be replaced by a new PROTOSpawner in the future. See https://github.com/cyberbotics/webots_ros2/issues/818 for more information.
[ros2_supervisor.py-2] [INFO] [1707152407.077071230] [Ros2Supervisor.Ros2Supervisor]: Ros2Supervisor has imported the URDF robot named "UR5e".
[INFO] [ur5e_controller-6]: process started with pid [5670]
[INFO] [abb_controller-7]: process started with pid [5672]
[INFO] [spawner-8]: process started with pid [5674]
[INFO] [spawner-9]: process started with pid [5676]
[INFO] [spawner-10]: process started with pid [5678]
[INFO] [spawner-11]: process started with pid [5680]
[INFO] [ros2-5]: process has finished cleanly [pid 5607]
[abb_controller-7] [INFO] [1707152407.388614352] [abb.abb_controller]: Waiting for action server to be ready...
[ur5e_controller-6] [INFO] [1707152407.459413697] [ur5e.ur5e_controller]: Waiting for action server to be ready...
[webots_controller_UR5e-3] [INFO] [1707152408.380589273] [resource_manager]: Initialize hardware 'WebotsControl' 
[webots_controller_UR5e-3] [INFO] [1707152408.380711450] [resource_manager]: Successful initialization of hardware 'WebotsControl'
[webots_controller_UR5e-3] [INFO] [1707152408.380846431] [resource_manager]: 'configure' hardware 'WebotsControl' 
[webots_controller_UR5e-3] [INFO] [1707152408.380852592] [resource_manager]: Successful 'configure' of hardware 'WebotsControl'
[webots_controller_UR5e-3] [INFO] [1707152408.380863707] [resource_manager]: 'activate' hardware 'WebotsControl' 
[webots_controller_UR5e-3] [INFO] [1707152408.380868009] [resource_manager]: Successful 'activate' of hardware 'WebotsControl'
[webots_controller_UR5e-3] [INFO] [1707152408.385146517] [ur5e.controller_manager]: Subscribing to '~/robot_description' topic for robot description file.
[webots_controller_UR5e-3] [INFO] [1707152408.385616855] [ur5e.UR5e]: Controller successfully connected to robot in Webots simulation.
[spawner-9] [INFO] [1707152409.311290442] [spawner_ur_joint_state_broadcaster]: Waiting for '/ur5e/controller_manager' services to be available
[spawner-8] [INFO] [1707152409.312604206] [spawner_ur_joint_trajectory_controller]: Waiting for '/ur5e/controller_manager' services to be available
[spawner-10] [INFO] [1707152409.329472709] [spawner_abb_joint_trajectory_controller]: Waiting for '/abb/controller_manager' services to be available
[spawner-11] [INFO] [1707152409.409835686] [spawner_abb_joint_state_broadcaster]: Waiting for '/abb/controller_manager' services to be available
[spawner-9] [INFO] [1707152411.321595095] [spawner_ur_joint_state_broadcaster]: Waiting for '/ur5e/controller_manager' services to be available
[spawner-8] [INFO] [1707152411.322464644] [spawner_ur_joint_trajectory_controller]: Waiting for '/ur5e/controller_manager' services to be available
[spawner-10] [INFO] [1707152411.340501070] [spawner_abb_joint_trajectory_controller]: Waiting for '/abb/controller_manager' services to be available
[spawner-11] [INFO] [1707152411.420263965] [spawner_abb_joint_state_broadcaster]: Waiting for '/abb/controller_manager' services to be available
[spawner-9] [INFO] [1707152413.332441699] [spawner_ur_joint_state_broadcaster]: Waiting for '/ur5e/controller_manager' services to be available
[spawner-8] [INFO] [1707152413.332775907] [spawner_ur_joint_trajectory_controller]: Waiting for '/ur5e/controller_manager' services to be available
[spawner-10] [INFO] [1707152413.352002663] [spawner_abb_joint_trajectory_controller]: Waiting for '/abb/controller_manager' services to be available
[spawner-11] [INFO] [1707152413.432669351] [spawner_abb_joint_state_broadcaster]: Waiting for '/abb/controller_manager' services to be available
[spawner-8] [INFO] [1707152415.344530215] [spawner_ur_joint_trajectory_controller]: Waiting for '/ur5e/controller_manager' services to be available
[spawner-9] [INFO] [1707152415.344841939] [spawner_ur_joint_state_broadcaster]: Waiting for '/ur5e/controller_manager' services to be available
[spawner-10] [INFO] [1707152415.362234324] [spawner_abb_joint_trajectory_controller]: Waiting for '/abb/controller_manager' services to be available
[spawner-11] [INFO] [1707152415.445284734] [spawner_abb_joint_state_broadcaster]: Waiting for '/abb/controller_manager' services to be available
[spawner-8] [INFO] [1707152417.356326900] [spawner_ur_joint_trajectory_controller]: Waiting for '/ur5e/controller_manager' services to be available
[spawner-9] [INFO] [1707152417.356560010] [spawner_ur_joint_state_broadcaster]: Waiting for '/ur5e/controller_manager' services to be available
[spawner-10] [INFO] [1707152417.373139189] [spawner_abb_joint_trajectory_controller]: Waiting for '/abb/controller_manager' services to be available
[spawner-11] [INFO] [1707152417.456198134] [spawner_abb_joint_state_broadcaster]: Waiting for '/abb/controller_manager' services to be available
[spawner-8] [INFO] [1707152419.363920567] [spawner_ur_joint_trajectory_controller]: Waiting for '/ur5e/controller_manager' services to be available
[spawner-9] [INFO] [1707152419.363944083] [spawner_ur_joint_state_broadcaster]: Waiting for '/ur5e/controller_manager' services to be available
[spawner-10] [INFO] [1707152419.380367555] [spawner_abb_joint_trajectory_controller]: Waiting for '/abb/controller_manager' services to be available
[spawner-11] [INFO] [1707152419.465535209] [spawner_abb_joint_state_broadcaster]: Waiting for '/abb/controller_manager' services to be available
[spawner-8] [INFO] [1707152421.371208868] [spawner_ur_joint_trajectory_controller]: Waiting for '/ur5e/controller_manager' services to be available
[spawner-9] [INFO] [1707152421.371261015] [spawner_ur_joint_state_broadcaster]: Waiting for '/ur5e/controller_manager' services to be available
[spawner-10] [INFO] [1707152421.387558883] [spawner_abb_joint_trajectory_controller]: Waiting for '/abb/controller_manager' services to be available
[spawner-11] [INFO] [1707152421.475366892] [spawner_abb_joint_state_broadcaster]: Waiting for '/abb/controller_manager' services to be available
[spawner-8] [INFO] [1707152423.378185437] [spawner_ur_joint_trajectory_controller]: Waiting for '/ur5e/controller_manager' services to be available
[spawner-9] [INFO] [1707152423.378209722] [spawner_ur_joint_state_broadcaster]: Waiting for '/ur5e/controller_manager' services to be available
[spawner-10] [INFO] [1707152423.395142927] [spawner_abb_joint_trajectory_controller]: Waiting for '/abb/controller_manager' services to be available
[spawner-11] [INFO] [1707152423.483449723] [spawner_abb_joint_state_broadcaster]: Waiting for '/abb/controller_manager' services to be available
[spawner-8] [INFO] [1707152425.387458958] [spawner_ur_joint_trajectory_controller]: Waiting for '/ur5e/controller_manager' services to be available
[spawner-9] [INFO] [1707152425.387516360] [spawner_ur_joint_state_broadcaster]: Waiting for '/ur5e/controller_manager' services to be available
[spawner-10] [INFO] [1707152425.404244898] [spawner_abb_joint_trajectory_controller]: Waiting for '/abb/controller_manager' services to be available
[spawner-11] [INFO] [1707152425.493461555] [spawner_abb_joint_state_broadcaster]: Waiting for '/abb/controller_manager' services to be available
[spawner-9] [INFO] [1707152427.396123316] [spawner_ur_joint_state_broadcaster]: Waiting for '/ur5e/controller_manager' services to be available
[spawner-8] [INFO] [1707152427.396577043] [spawner_ur_joint_trajectory_controller]: Waiting for '/ur5e/controller_manager' services to be available
[spawner-10] [INFO] [1707152427.412796989] [spawner_abb_joint_trajectory_controller]: Waiting for '/abb/controller_manager' services to be available
[spawner-11] [INFO] [1707152427.505147375] [spawner_abb_joint_state_broadcaster]: Waiting for '/abb/controller_manager' services to be available
[spawner-8] [INFO] [1707152429.407198357] [spawner_ur_joint_trajectory_controller]: Waiting for '/ur5e/controller_manager' services to be available
[spawner-9] [INFO] [1707152429.407502654] [spawner_ur_joint_state_broadcaster]: Waiting for '/ur5e/controller_manager' services to be available
[spawner-10] [INFO] [1707152429.423951411] [spawner_abb_joint_trajectory_controller]: Waiting for '/abb/controller_manager' services to be available
[spawner-11] [INFO] [1707152429.516499232] [spawner_abb_joint_state_broadcaster]: Waiting for '/abb/controller_manager' services to be available

And these are the ros2 services that are available with ros2 service list:

/Ros2Supervisor/Ros2Supervisor/describe_parameters
/Ros2Supervisor/Ros2Supervisor/get_parameter_types
/Ros2Supervisor/Ros2Supervisor/get_parameters
/Ros2Supervisor/Ros2Supervisor/list_parameters
/Ros2Supervisor/Ros2Supervisor/set_parameters
/Ros2Supervisor/Ros2Supervisor/set_parameters_atomically
/Ros2Supervisor/animation_start_recording
/Ros2Supervisor/animation_stop_recording
/Ros2Supervisor/spawn_node_from_string
/Ros2Supervisor/spawn_urdf_robot
/abb/abb_controller/describe_parameters
/abb/abb_controller/get_parameter_types
/abb/abb_controller/get_parameters
/abb/abb_controller/list_parameters
/abb/abb_controller/set_parameters
/abb/abb_controller/set_parameters_atomically
/abb/abbirb4600/describe_parameters
/abb/abbirb4600/get_parameter_types
/abb/abbirb4600/get_parameters
/abb/abbirb4600/list_parameters
/abb/abbirb4600/set_parameters
/abb/abbirb4600/set_parameters_atomically
/abb/controller_manager/describe_parameters
/abb/controller_manager/get_parameter_types
/abb/controller_manager/get_parameters
/abb/controller_manager/list_parameters
/abb/controller_manager/set_parameters
/abb/controller_manager/set_parameters_atomically
/spawner_abb_joint_state_broadcaster/describe_parameters
/spawner_abb_joint_state_broadcaster/get_parameter_types
/spawner_abb_joint_state_broadcaster/get_parameters
/spawner_abb_joint_state_broadcaster/list_parameters
/spawner_abb_joint_state_broadcaster/set_parameters
/spawner_abb_joint_state_broadcaster/set_parameters_atomically
/spawner_abb_joint_trajectory_controller/describe_parameters
/spawner_abb_joint_trajectory_controller/get_parameter_types
/spawner_abb_joint_trajectory_controller/get_parameters
/spawner_abb_joint_trajectory_controller/list_parameters
/spawner_abb_joint_trajectory_controller/set_parameters
/spawner_abb_joint_trajectory_controller/set_parameters_atomically
/spawner_ur_joint_state_broadcaster/describe_parameters
/spawner_ur_joint_state_broadcaster/get_parameter_types
/spawner_ur_joint_state_broadcaster/get_parameters
/spawner_ur_joint_state_broadcaster/list_parameters
/spawner_ur_joint_state_broadcaster/set_parameters
/spawner_ur_joint_state_broadcaster/set_parameters_atomically
/spawner_ur_joint_trajectory_controller/describe_parameters
/spawner_ur_joint_trajectory_controller/get_parameter_types
/spawner_ur_joint_trajectory_controller/get_parameters
/spawner_ur_joint_trajectory_controller/list_parameters
/spawner_ur_joint_trajectory_controller/set_parameters
/spawner_ur_joint_trajectory_controller/set_parameters_atomically
/ur5e/UR5e/describe_parameters
/ur5e/UR5e/get_parameter_types
/ur5e/UR5e/get_parameters
/ur5e/UR5e/list_parameters
/ur5e/UR5e/set_parameters
/ur5e/UR5e/set_parameters_atomically
/ur5e/controller_manager/describe_parameters
/ur5e/controller_manager/get_parameter_types
/ur5e/controller_manager/get_parameters
/ur5e/controller_manager/list_parameters
/ur5e/controller_manager/set_parameters
/ur5e/controller_manager/set_parameters_atomically
/ur5e/ur5e_controller/describe_parameters
/ur5e/ur5e_controller/get_parameter_types
/ur5e/ur5e_controller/get_parameters
/ur5e/ur5e_controller/list_parameters
/ur5e/ur5e_controller/set_parameters
/ur5e/ur5e_controller/set_parameters_atomically
@ralphieraccoon
Copy link
Contributor

I've had the same problem with iron. I think ros2_control has made a breaking change recently.

@Acwok
Copy link

Acwok commented Feb 7, 2024 •
edited
Loading

Same problem with the e_puck demo and ROS humble:

[spawner-7] [INFO] [1707298270.095655670] [spawner_diffdrive_controller]: Waiting for '/controller_manager' services to be available
[spawner-8] [INFO] [1707298270.106261863] [spawner_joint_state_broadcaster]: Waiting for '/controller_manager' services to be available

@ralphieraccoon ralphieraccoon added the bug Something isn't working label Feb 7, 2024
@wilhem
Copy link

wilhem commented Feb 8, 2024

Same problem here:

  • Humble
  • Ubuntu 22.04

@omichel omichel mentioned this issue Feb 8, 2024
Closed
@omichel
Copy link
Member

omichel commented Feb 8, 2024

Can you try the patch proposed in #894 and let me know if that helps?

@ruca03
Copy link
Author

ruca03 commented Feb 8, 2024

Hi, @omichel.

I did your sugegstion. While it stops the error message "Waiting for ... to be available" the robots dont move.

The Webots log shows:
INFO: 'abbirb4600' extern controller: Waiting for local or remote connection on port 1234 targeting robot named 'abbirb4600'. INFO: conveyor_belt: Starting controller: /home/rui/.ros/webotsR2023b/webots/projects/objects/factory/conveyors/controllers/conveyor_belt/conveyor_belt -0.17 0 INFO: 'Ros2Supervisor' extern controller: Waiting for local or remote connection on port 1234 targeting robot named 'Ros2Supervisor'. INFO: 'abbirb4600' extern controller: connected. INFO: 'Ros2Supervisor' extern controller: connected. INFO: 'UR5e' extern controller: Waiting for local or remote connection on port 1234 targeting robot named 'UR5e'. INFO: 'UR5e' extern controller: connected. WARNING: Contact joints between materials 'default' and 'default' will only be created for the 10 deepest contact points instead of all the 90 contact points. WARNING: Contact joints between materials 'default' and 'default' will only be created for the 10 deepest contact points instead of all the 21 contact points.

And the terminal when i run ros2 launch webots_ros2_universal_robot multirobot_launch.py shows:


[INFO] [launch]: All log files can be found below /home/rui/.ros/log/2024-02-08-15-43-50-895216-rui-REPLANT-18004
[INFO] [launch]: Default logging verbosity is set to INFO
WARNING: No valid Webots directory specified in `ROS2_WEBOTS_HOME` and `WEBOTS_HOME`, fallback to default installation folder /home/rui/.ros/webotsR2023b/webots.
[INFO] [webots-1]: process started with pid [18005]
[INFO] [ros2_supervisor.py-2]: process started with pid [18007]
[INFO] [webots_controller_UR5e-3]: process started with pid [18010]
[INFO] [webots_controller_abbirb4600-4]: process started with pid [18013]
[INFO] [ros2-5]: process started with pid [18015]
[webots_controller_UR5e-3] The specified robot is not in the list of robots with <extern> controllers, retrying for another 50 seconds...
[webots_controller_abbirb4600-4] The specified robot is not in the list of robots with <extern> controllers, retrying for another 50 seconds...
[ros2_supervisor.py-2] The specified robot is not in the list of robots with <extern> controllers, retrying for another 50 seconds...
[webots_controller_UR5e-3] The Webots simulation world is not yet ready, pending until loading is done...
[webots_controller_abbirb4600-4] The Webots simulation world is not yet ready, pending until loading is done...
[ros2_supervisor.py-2] The Webots simulation world is not yet ready, pending until loading is done...
[webots_controller_abbirb4600-4] [INFO] [1707407038.230590805] [resource_manager]: Initialize hardware 'WebotsControl' 
[webots_controller_abbirb4600-4] [INFO] [1707407038.230821465] [resource_manager]: Successful initialization of hardware 'WebotsControl'
[webots_controller_abbirb4600-4] [INFO] [1707407038.231043607] [resource_manager]: 'configure' hardware 'WebotsControl' 
[webots_controller_abbirb4600-4] [INFO] [1707407038.231060032] [resource_manager]: Successful 'configure' of hardware 'WebotsControl'
[webots_controller_abbirb4600-4] [INFO] [1707407038.231074364] [resource_manager]: 'activate' hardware 'WebotsControl' 
[webots_controller_abbirb4600-4] [INFO] [1707407038.231079585] [resource_manager]: Successful 'activate' of hardware 'WebotsControl'
[webots_controller_abbirb4600-4] [INFO] [1707407038.235500788] [abb.controller_manager]: Subscribing to '~/robot_description' topic for robot description file.
[webots_controller_abbirb4600-4] [INFO] [1707407038.236073859] [abb.abbirb4600]: Controller successfully connected to robot in Webots simulation.
[ros2_supervisor.py-2] [WARN] [1707407038.415912712] [Ros2Supervisor.Ros2Supervisor]: The URDF Spawner is deprecated. It will be replaced by a new PROTOSpawner in the future. See https://github.com/cyberbotics/webots_ros2/issues/818 for more information.
[ros2_supervisor.py-2] [INFO] [1707407038.694156319] [Ros2Supervisor.Ros2Supervisor]: Ros2Supervisor has imported the URDF robot named "UR5e".
[INFO] [ur5e_controller-6]: process started with pid [18086]
[INFO] [abb_controller-7]: process started with pid [18088]
[INFO] [ros2_control_node-8]: process started with pid [18090]
[INFO] [ros2_control_node-9]: process started with pid [18092]
[INFO] [ros2_control_node-10]: process started with pid [18094]
[INFO] [ros2_control_node-11]: process started with pid [18096]
[ros2_control_node-9] [WARN] [1707407038.727792944] [controller_manager]: 'update_rate' parameter not set, using default value.
[ros2_control_node-9] [INFO] [1707407038.727924904] [controller_manager]: Subscribing to '~/robot_description' topic for robot description file.
[ros2_control_node-9] [INFO] [1707407038.728784460] [controller_manager]: update rate is 100 Hz
[ros2_control_node-9] [INFO] [1707407038.728917604] [controller_manager]: RT kernel is recommended for better performance
[ros2_control_node-11] [WARN] [1707407038.733139987] [controller_manager]: 'update_rate' parameter not set, using default value.
[ros2_control_node-11] [INFO] [1707407038.733226851] [controller_manager]: Subscribing to '~/robot_description' topic for robot description file.
[ros2_control_node-8] [WARN] [1707407038.733706203] [controller_manager]: 'update_rate' parameter not set, using default value.
[ros2_control_node-8] [INFO] [1707407038.733786422] [controller_manager]: Subscribing to '~/robot_description' topic for robot description file.
[ros2_control_node-11] [INFO] [1707407038.733912854] [controller_manager]: update rate is 100 Hz
[ros2_control_node-11] [INFO] [1707407038.734054210] [controller_manager]: RT kernel is recommended for better performance
[ros2_control_node-8] [INFO] [1707407038.734532091] [controller_manager]: update rate is 100 Hz
[ros2_control_node-8] [INFO] [1707407038.734626828] [controller_manager]: RT kernel is recommended for better performance
[ros2_control_node-10] [WARN] [1707407038.735623685] [controller_manager]: 'update_rate' parameter not set, using default value.
[ros2_control_node-10] [INFO] [1707407038.735772225] [controller_manager]: Subscribing to '~/robot_description' topic for robot description file.
[ros2_control_node-10] [INFO] [1707407038.744208227] [controller_manager]: update rate is 100 Hz
[ros2_control_node-10] [INFO] [1707407038.744383942] [controller_manager]: RT kernel is recommended for better performance
[INFO] [ros2-5]: process has finished cleanly [pid 18015]
[ur5e_controller-6] [INFO] [1707407039.047889641] [ur5e.ur5e_controller]: Waiting for action server to be ready...
[abb_controller-7] [INFO] [1707407039.047921095] [abb.abb_controller]: Waiting for action server to be ready...
[webots_controller_UR5e-3] [INFO] [1707407039.703054183] [resource_manager]: Initialize hardware 'WebotsControl' 
[webots_controller_UR5e-3] [INFO] [1707407039.703248802] [resource_manager]: Successful initialization of hardware 'WebotsControl'
[webots_controller_UR5e-3] [INFO] [1707407039.703420684] [resource_manager]: 'configure' hardware 'WebotsControl' 
[webots_controller_UR5e-3] [INFO] [1707407039.703430431] [resource_manager]: Successful 'configure' of hardware 'WebotsControl'
[webots_controller_UR5e-3] [INFO] [1707407039.703442747] [resource_manager]: 'activate' hardware 'WebotsControl' 
[webots_controller_UR5e-3] [INFO] [1707407039.703447273] [resource_manager]: Successful 'activate' of hardware 'WebotsControl'
[webots_controller_UR5e-3] [INFO] [1707407039.708499371] [ur5e.controller_manager]: Subscribing to '~/robot_description' topic for robot description file.
[webots_controller_UR5e-3] [INFO] [1707407039.709177077] [ur5e.UR5e]: Controller successfully connected to robot in Webots simulation.

@ralphieraccoon
Copy link
Contributor

I'm wondering if ros-controls/ros2_control#1169 might be the culprit. It says it is API breaking.

@elad-eyal
Copy link

elad-eyal commented Feb 9, 2024 •
edited
Loading

Fails for me too, on Ubuntu 22.04 , WSL2, humble.

I installed using apt the packages ros-humble-ros2-control and ros-humble-ros2-controllers so I get ros2_control v2.37.0 (That's what I get when trying ros2 pkg xml ros2_control

@elad-eyal
Copy link

I wish there was a fix or workaround @omichel .. Webots is so nice but I need to use ros2_control

@ralphieraccoon
Copy link
Contributor

ralphieraccoon commented Feb 14, 2024 •
edited
Loading

Based on my analysis, the problem is the robot_description topic has no publishers. The controller_manager services that are being polled for are not made available until a message is published on this topic. So I think something is failing which prevents the robot_description publisher from being created.

I've also tried loading the URDF directly into the resource manager, which I believe bypasses the need to subscribe to robot_description and makes the services available immediately, but I've not got it to work without error.

@skpawar1305
Copy link
Contributor

skpawar1305 commented Feb 14, 2024 •
edited
Loading

I wish there was a fix or workaround @omichel .. Webots is so nice but I need to use ros2_control

you may build n use ros2_control 2.36.1 for now

@skpawar1305 skpawar1305 mentioned this issue Feb 14, 2024
Merged
1 task
omichel added a commit that referenced this issue Feb 15, 2024
@skpawar1305 @omichel
set is_urdf_loaded__ of the resource manager to true (#896)
b56cc41 
it's probably needed after ros-controls/ros2_control@385293e

fixes #893

Co-authored-by: Olivier Michel <[email protected]>
@wilhem
Copy link

wilhem commented Feb 15, 2024 •
edited
Loading

How to update our systems with the new changes?
Doing a:

$sudo apt update 
$sudo apt upgrade

does show that the repository to webots_ros2 is checked but no update is downloaded.

@ralphieraccoon
Copy link
Contributor

How to update our systems with the new changes? Doing a:

$sudo apt update 
$sudo apt upgrade

does show that the repository to webots_ros2 is checked but no update is downloaded.

You won't see an update until the next version release. If you want to use this fix now, you need to either clone webots_ros2 or include it as a submodule in your ros2 workspace and compile it yourself. You'll also want to remove the version of webots_ros2 installed with apt.

@wilhem
Copy link

wilhem commented Mar 2, 2024

And there is any estimated time for the next release?

@omichel
Copy link
Member

omichel commented Mar 2, 2024

Now that all the tests are passing on all ROS2 distributions, @Yadunund may be able to bump a release. A PR for this was prepared a long time ago in #839 and @Yadunund also prepared one in #892. Not sure from which we should re-start.

@Yadunund
Copy link
Member

Yadunund commented Mar 4, 2024

If CI is working on all distro we should continue with #839 imo

@omichel
Copy link
Member

omichel commented Mar 4, 2024

If CI is working on all distro we should continue with #839 imo

I agree. Can you take the lead on this since @ygoumaz is not working on the project any more?

@Yadunund
Copy link
Member

Yadunund commented Mar 4, 2024

If CI is working on all distro we should continue with #839 imo

I agree. Can you take the lead on this since @ygoumaz is not working on the project any more?

Sure. But I'm likely to have time only next week or so.

@wilhem wilhem mentioned this issue Mar 18, 2024
Closed
@wilhem
Copy link

wilhem commented Apr 7, 2024

This issue is still continuing here: link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Milestone
No milestone
8 participants
@wilhem @omichel @Acwok @Yadunund @elad-eyal @ralphieraccoon @ruca03 @skpawar1305