[Nav2] 3D obstacle avoidance with Realsense D435(i)
Hey!
i'm working on a mobile robot platform and tuning the navigation right now. After a few hours on the real hardware and in gazebo simulations i encountered a problem with the voxel layer. Everytime one of the Realsense D435 on my robot (4 in total - one for each site) detects an obstacle it is marked correctly in the voxel layer but if i remove the obstacle some of the voxels still stay in the costmap (mostly the lower and upper part). This will block the area and result in replanning or aborted navigation.
I read multiple github issus / questions here on answers.ros.org and it seems that this is a common problem with the raytracing algorythm. I tried almost all "solutions" that i have found but nothing seems to work.
Is it really the only answer to use the non-persistent voxel layer or STVL for Realsense 3D pointclouds? And if so, why is almost every example in the internet using the normal voxel layer?
Thanks in advance!
p0rys