TB3 isn't rendered correctly in Gazebo

asked 2021-12-01 02:54:57 -0500

ljaniec gravatar image

updated 2021-12-01 06:04:30 -0500

My system

  • Ubuntu 20.04
  • ROS2 Galactic (binaries)

Steps to reproduce problem:

  • install aws-robomaker-small-warehouse-world and nav2-simple-commander ROS2 Galactic packages (binaries)
  • ros2 launch nav2_simple_commander inspection_demo_launch.py

Part of my .bashrc file: source ~/ros2_ws/install/setup.bash export TURTLEBOT3_MODEL=waffle export GAZEBO_MODEL_PATH=$GAZEBO_MODEL_PATH:/home/ljaniec/ros2_ws/install/aws_robomaker_small_warehouse_world/share/aws_robomaker_small_warehouse_world/worlds:/home/ljaniec/ros2_ws/install/aws_robomaker_small_warehouse_world/share/aws_robomaker_small_warehouse_world/models:/opt/ros/galactic/share/turtlebot3_gazebo/models:/home/ljaniec/.gazebo/models

Expected behavior

The simulation with one visible TB3 with Nav2 stack and basic autonomy script starts.

Actual behavior

The simulation doesn't have correctly rendered robot (screens below). Autonomy demo still works (robot moves, LiDAR can be seen etc).

Simulation 1

Simulation 2

Simulation 3

Simulation 4

Additional information

What I tried:

  • reinstall Gazebo and Nav2 packages

  • I have found a similar bug there

  • I checked URDF like there and it didn't show problems

  • this bug shows in this package too (nav2_rosdevday_2021, there ), one with MP 400 (the robot is invisible, in "Collisions" view in Gazebo too) - maybe it is something connected with these meshfile changes mentioned in the first link above?

Am I doing something wrong there? Standard simulation (1 TB3 in TurtleWorld) is working fine (edit: no longer after rebuilding latest galactic branch of ros-planning/navigation2 branch - robot is invisible there too) - robot model loads (edit: it's invisible too now) etc. The discrepancy between simulations with the same model (AFAIK) is surprising to me.

I prepared a small set of commands to show, what the problem is (with Turtlebot3 and MP400 from Neobotix).

  • TB3 case 1

Start Gazebo simulation with empty world

ros2 launch gazebo_ros gazebo.launch.py

Add TB3 SDF model to Gazebo (package turtlebot3_gazebo)

ros2 run gazebo_ros spawn_entity.py -file /opt/ros/galactic/share/turtlebot3_gazebo/models/turtlebot3_waffle/model.sdf -entity robot01

It spawns TB3 Waffle normally (visible model and LiDAR).

  • TB3 case 2-1

Start Gazebo simulation with empty world

ros2 launch gazebo_ros gazebo.launch.py

Add TB3 URDF model to Gazebo (package nav2_bringup)

ros2 run gazebo_ros spawn_entity.py -file /opt/ros/galactic/share/nav2_bringup/urdf/turtlebot3_waffle.urdf -entity robot01

Surprisingly, it spawns invisible TB3 Waffle. It is visible only in the 'Collision' view in Gazebo. No LiDAR too.

  • TB3 case 2-2

Start Gazebo simulation with empty world

ros2 launch gazebo_ros gazebo.launch.py

Generate TB3 SDF model from URDF

gz sdf -p turtlebot3_waffle.urdf > turtlebot3_waffle.sdf

Add TB3 SDF model to Gazebo (from package nav2_bringup)

ros2 run gazebo_ros spawn_entity.py -file ~/Desktop/turtlebot3_waffle.sdf -entity robot01

TB3 is invisible (but it's there, after launching 'Collision' view in Gazebo).

  • MP400 case

Start Gazebo simulation with empty world

ros2 launch gazebo_ros gazebo.launch.py

Add MP400 URDF model to Gazebo

ros2 run gazebo_ros spawn_entity.py -file ~/mp_400/mp_400.urdf -entity robot01

Robot is invisible, there are only blobs in the air and a LiDAR.

Generate SDF model from URDF

gz sdf -p mp_400.urdf > mp_400.sdf

Add MP400 SDF model to Gazebo

ros2 run gazebo_ros spawn_entity.py -file ~/mp_400/mp_400.sdf -entity robot01

Robot is again invisible, there are only blobs in the air ... (more)

edit retag flag offensive close merge delete

Comments

Great well structured question. Lots of details. I’ll follow up on it and hope you find an answer soon.

osilva gravatar image osilva  ( 2021-12-01 05:54:36 -0500 )edit