Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ROS2 Plans? #75

Open
mkhansenbot opened this issue Jun 29, 2018 · 11 comments
Open

ROS2 Plans? #75

mkhansenbot opened this issue Jun 29, 2018 · 11 comments

Comments

@mkhansenbot
Copy link

Are there any plans to port move_base_flex to ROS2? I'm driving an effort to create a ROS2 Navigation system, and many of the improvements in move_base_flex are similar to the ideas & concepts we've been discussing within our team. I'd like to make sure we're not working on a redundant effort.

@spuetz
Copy link
Collaborator

spuetz commented Jun 29, 2018

Yes! We though about Move Base Flex as a good base for the ROS2 Navigation system. Should we discuss a possible procedure? At the moment I put a lot of work into making MBF parallel. (#36) This will be released soon. After that I'll have a bit capacities for porting MBF to ROS2.

@reinzor
Copy link
Contributor

reinzor commented Jun 4, 2019

Any updates on this? Will move_base_flex be deprecated in favor of the ROS2 Navigation stack?

@spuetz
Copy link
Collaborator

spuetz commented Jun 4, 2019

We planned a MBF version for ROS2, It will be developed when all necessary parts in ROS2 are available.

@reinzor
Copy link
Contributor

reinzor commented Jun 4, 2019

Nice. I am not fully aware of the ROS2 navigation stack features but wouldn't be an idea to merge both efforts?

@adamkrawczyk
Copy link

Any news now?

@spuetz
Copy link
Collaborator

spuetz commented Apr 29, 2020

I'll start the MBF Development for ROS2 around September / October.

@mkhansenbot
Copy link
Author

I'm closing this issue as the Nav2 project has been released for over a year now, this question is outdated.

@StefanFabian
Copy link

The existence of Nav2 doesn't have anything to do with a possible ROS 2 release unless the maintainers here stopped their plans in favor of Nav2.
Nav2 is also not perfect and still heavily relies on costmap2d.
Could you or one of the maintainers please reopen this issue as it may still be of interest to other people?

@spuetz spuetz reopened this Apr 30, 2021
@Rayman
Copy link
Contributor

Rayman commented Apr 30, 2021

The good thing about nav2 is that they have added action interfaces for GetPath and ExePath, just like MBF did for ROS1. For us that was the biggest feature to use MBF.

For ROS2 I think we are going to first try out nav2 as that seems to fulfill all our requirements.

@spuetz
Copy link
Collaborator

spuetz commented Apr 30, 2021

We will work on ROS2 MBF versions, porting the mbf-costmap-nav (costmap_2d), mbf-gridmap-nav (gridmap library), and mbf-mesh-nav (mesh navigation stack), also with additional action interfaces. Just as a quick info.

@moooeeeep
Copy link

No pressure, but... any updates on this? :)

Related discussions regarding other map representations at navigation2:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants