Problem launching Gazebo from docker about rosbot_ros HOT 12 CLOSED

Hi @julietcookies!
If you have ROS 2 Humble installed natively you can follow this instruction https://github.com/husarion/rosbot_ros#build-and-run-gazebo-simulation.

If you want to use docker look at this demo: https://github.com/husarion/rosbot-docker/blob/ros2/demo/compose.simulation.yaml

Please tell me if this solved your issues!

Best regards,
JD

from rosbot_ros.

Thank you for the quick response. Unfortunately when following the instructions given in the GitHub, we encounter the same issue - "Waiting for '/simulation_controller_manager' node to exist". The same issue happens when running the docker demo (i.e., running the compose file given and launching gazebo through it).

Is there another solution to combat this (specifically the simulation_controller_manager node missing)?

from rosbot_ros.

Please send me whole logs.

from rosbot_ros.

I'm closing due to inactivity. If the issue is still valid, please reopen it.

from rosbot_ros.

I would like to reopen this issue as I have the same problem.
Currently I am trying to get the ROSbot 2 in the simulation and in a Singularity container to work

I get the following log in the console:
2023_08_16_simulation_control_manager_node_not_existing.txt

Maybe this is a little bit off-topic, but would you recommend Gazebo-Classic or Gazebo-Sim (Fortress or Garden) to use with the ROSbot? I am currently setting things up for a lab at out university.

from rosbot_ros.

Hi @Heenne,
we are using the Fortress version of Gazebo-Sim.
Please send the output of:

ign gazebo --versions

Best regards,
JD

from rosbot_ros.

Hi @delihus
thanks for the quick reply. This is the output:
Singularity> ign gazebo --version Ignition Gazebo, version 6.11.0 Copyright (C) 2018 Open Source Robotics Foundation. Released under the Apache 2.0 License.

Best regards
Heenne

from rosbot_ros.

I have just added the requirements before running the simulation. Please see https://github.com/husarion/rosbot_ros#build-and-run-gazebo-simulation.
Try export this global variable:

export GZ_VERSION=fortress

from rosbot_ros.

I executed the command and launched the simulation.launch.py again, but nothing changed.
In the log there is shown that the GZ_VERSION contains "fortress" and the error remains.

2023_08_17_simulation_control_manager_node_not_existing.txt

from rosbot_ros.

I can reproduce your issue.
After source the workspace source install/setup.bash, check the path to the ign_ros2_control package:

ros2 pkg prefix ign_ros2_control

The path should be the workspace path not the /opt/ros/humble/.
Also the version of the package ign_ros2_control should be 0.5.0. You can check this in the xml file in the tag <version>

ros2 pkg xml ign_ros2_control

If your path is /opt/ros/humble/ make sure that you correctly followed the building instructions.
I think you missed this line:

vcs import src < src/rosbot/rosbot_simulation.repos

from rosbot_ros.

The path to ign_ros2_control is /opt/ros/humble/
The version of the ign_ros2_control is 0.7.0.
First I used the "vcs"-command in the container itself. Now I inserted it into the definition-file of the container that is used for the building process. That worked.
So now the simulation works in Gazebo Fortress.

Just a heads up: The path to the .repos-file is incorrect. It should be src/rosbot_ros/rosbot/rosbot_simulation.repos
Also it might be a good idea to include an information that one must cd into the workspace folder.

Thank you very much for the help and the well documented repository. Very looking forward to the real robot (will be ordered soon).

from rosbot_ros.

It's great that you solved the issue.

First I used the "vcs"-command in the container itself. Now I inserted it into the definition-file of the container that is used for the building process. That worked.

You can check our docker images with the simulation in the rosbot-docker repository.

Just a heads up: The path to the .repos-file is incorrect. It should be src/rosbot_ros/rosbot/rosbot_simulation.repos
Also it might be a good idea to include an information that one must cd into the workspace folder.

In the instruction you have to clone repository into the src folder.

git clone https://github.com/husarion/rosbot_ros src/

Best regards,
JD

from rosbot_ros.