Closed HazemAshraf11 closed 3 months ago
You said that the problem was when you use the voxel layer right? I only see the config with the obstacle layer. Can you add the problematic config?
Additionally, you're using Foxy? Foxy is end of life and not supported anymore. Can you try to reproduce it on humble or more recent?
The local costmap doesn't even work when I use a voxel layer, and it gives me this warning "Sensor origin out of map bounds. The costmap can't raytrace for it." When I use an obstacle layer, the obstacles don't appear in the local costmap until it's too late as you can see in the two pictures.
I am going to use a jetson nano later and it doesn't support Ubuntu 22.04 so I can't use humble.
I am pretty sure the problem is related to the ( obstacle layer.data source.obstacle_max_range ) parameter. It's default value is 2.5 and indeed the obstacles don't appear in the local costmap if they are more than 2.5 m far from the sensor. After they appear, they stay in this map untill the robot moves and they become out of the 15*15 m^2 square. But when I change this parameter, it doesn't do any thing. it's like it only works with the defined default value.
I found the problem. It's "obstacle_range" not "obstacle_max_range". In the documentation, it's "obstacle_max_range" but maybe that's for humble
Yepp, you are right @HazemAshraf11
You can see the PR here: https://github.com/open-navigation/navigation2/pull/2126/files
It can be also found in foxy to galactic migration guide: https://navigation.ros.org/migration/Foxy.html
can we close the issue now @HazemAshraf11 ?
Required Info:
Steps to reproduce issue
The navigation works with the static map but when I introduce a new obstacle, the LaserScan sees it but the local costmap doesn't react until the robot is too close and it hits the obstacle. the width = 15 and height = 15 so the obstacle should be visible in the local costmap. Here are the parameters I am using. I used an obstacle layer instead of a voxel layer because for some reason I get an error saying (Sensor origin out of map bounds. The costmap can't raytrace for it.) and the local planner doesn't work. The only solution I found was to replace the voxel layer with an obstacle layer.
Params File
Expected behavior
The obstacles within the 15*15 m^2 square around the robot should be visible in the local costmap
Actual behavior
They are not visible untill the robot is too close. If they appear and the robot leaves, they become visible in the costmap within that square until the robot get far away.