Delay for Isaac ROS Nvblox

Hello, I am trying to use Isaac ROS Nvblox for drone navigation with Nav2 for path planning. Since this package is designed for mobile robotics, when the .launch.py file is executed, the cost map is generated at the robot’s current position. This is not suitable for me because I need the drone to be at a level where it can fly.

Additionally, I understand that in version 3.0 of this package, the .launch.py file launches all the nodes simultaneously. Since the drone uses odometry to estimate its position, I need VSLAM to run before Nvblox. I was thinking about adding a timer, but I’m not entirely sure how to approach this. What would be the best way to handle it?

Thanks.

Hi @jim.fabian

Yes, you can change the nvblox layer using <mapper_name>.esdf_slice* ROS Parameters — isaac_ros_docs documentation

But like you wrote, it is mainly designed for mobile robots.

Hello @Raffaello, thanks for your response. I missed that parameter, my apologies. I tried it, and the layer does indeed change the height. However, this change seems to be only visual, correct? The obstacles still appear on the layer as if it were in their initial position. I thought it might be related to the esdf_slice_min_height and esdf_slice_max_height, but the layer is outside those limits.

Thanks!


1 Like

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.