Skip to content

Changing voxel_layer of local_costmap to Lidar pointcloud2 doesn't work #28

@Bli9sta

Description

@Bli9sta

Please provide the following information:

  • OS: (e.g. Ubuntu 24.04)
  • ROS 2 Distro: (e.g. Jazzy)
  • Built from source or installed: source (clearpath_nav2_demos), installed (nav2)
  • Package version: commit 42d9fa6
  • Real hardware or simulation: Real Hardware. We are using the Clearpath Husky A200

Expected behaviour
When changing topic of observation_sources from sensors/lidar3d_0/scan to sensors/lidar3d_0/points, the voxel layer in RVIZ should be present (RVIZ: Add->By topic -> /local_costmap -> /voxel_layer -> Map) and update itself on new Pointcloud data

Actual behaviour
The topic itself is present and can be selected in RVIZ. When selecting it to be displayed, the voxel_layer map stays blank. It can be noticed that the local_costmap itself is also not updating, i.e. when walking in front of the Lidar, the local costmap does not update. A screenshot of the situation in RVIZ is appended:

  1. "Controller" checkbox checked:
    Image
  2. "Controller" checkbox not checked:
    Image

For comparison, this is what it looks like with the default configuration (local_costmap using lidar3d_0/scan):

Image

Now there are voxels within the boundaries of the local_costmap square. The costmap is also constantly updating. We already checked that the topic (sensors/lidar3d_0/points) actually sends data, which it does

To Reproduce
Provide the steps to reproduce:

  1. Edit Nav2.yaml file
  2. Build using colcon build
  3. launch nav2.launch.pyros2 launch clearpath_nav2_demos nav2.launch.py use_sim_time:=false setup_path:=/path/to/setup
  4. launch localization
    ros2 launch clearpath_nav2_demos localization.launch.py use_sim_time:=false setup_path:=/path/to/setup map:=/path/to/map
  5. launch RVIZ
    ros2 launch clearpath_viz view_navigation.launch.py namespace:=a200_0000

Other notes
This is our Nav2.yaml file, where the local_costmap is defined (as txt because git doesnt support .yaml):

nav2.txt

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions