POST No. 2408021
Which ROS 2 release is the most stable and reliable for a TB3 Burger install
2021-02-18 07:17:39 edcepp

I installed ROS 2 Dashing on my new TB3 Burger for the following reasons

  • I suspected that Dashing would have been more thoroughly tested on the Burger because it has been around longer than Foxy.
  • I also suspected that Dashing would be more stable than Foxy because developers have had more time to fix issues.
  • I also suspected that Dashing would be more featured because developers had a longer time to port packages to it.

For example, I used ROS 1 Indigo for a long time because it did what I wanted and was rock solid.

I've been having some issues with my Dashing install. See 

Which ROS 2 release is the best ROS 2 version for Burger?

In which ROS2 release are you putting most of your development and testing energy for TB3? Is Dashing getting less completely supported and getting substantially less focus now that Foxy is released?

How often are binary releases (Kinetic, Melodic, ....., Dashing, Foxy) updated with known fixes? Is there a release schedule? Are a releases actively supported?

2021-02-18 07:17:39
2021-02-18 18:32:03 Will Son


In ROS2 community, most developers recommend ROS2 Foxy.

Dashing has been around for a while, but it was not as popular as stable ROS1 which was running based on Kinetic.

As you may know ROS2 Eloquent had already reached to its EOL and soon Dashing will be in this May.

I think ROS community is going to put more effort on porting various packages to Foxy and upcoming Galactic.

We're also trying to update and support Foxy as much as possible, and setting up a development plan for ROS2.

In a few weeks, we're going to distribute SBC recovery images for TurtleBot3 RPi3B+, which will minimize the agony of SBC setup :)

I usually release binaries at the end of every month if there's a significant issue in current release.

In case you need a most up to date code, you may download the source with "git clone -b .git"

Thank you.

2021-02-18 18:32:03
2021-02-24 07:07:01 Edward Epp

Thanks Wilson,

I upgraded from Dashing to Foxy. Nav2 has healthy signs of life. 

Putting the first paragraph in your above response into the emanual would be welcome. I want to put my energy where you are putting yours. Is this already part of Discourse and I missed it? In general, a note about the capabilities of each release would be great. 

Upgrading from 18.04 to 20.04 was the biggest headache. Removing incompatible packages that result in recalculating error messages during the upgrade were the biggest headache. Ubuntu doesn't like ROS packages in the upgrade formula and there where a few that hid themselves. Other than that things went well on the Remote PC side. I look forward to the day when ROS versions work across Ubuntu releases. A lot of my other software does.

ssh didn't come up on the SBC the first time I installed 20.04. So, I reinstalled using this this image


instead of this one


which I got by following your link in section 3.2.1 (Prepare microSD Card) of the eManual.  The eManual indicates that you are picking up 20.04.01. I noticed that ssh was already installed in the 20.04.02 image so I skipped the install step this time. I'm not sure if skipping the ssh install step, using a more recent image or something else fixed the ssh issue I had.

The Foxy install does not have some of the annoying directory issues during the colcon build that I encountered in the Dashing install several weeks back (section 3.2.6 Install ROS Packages). It looks like you have fixed these issues in the Dashing install as well. I also see the dynamixel-sdk install steps. Thanks. I hope to live on Foxy for a while.

I like the idea of distributing SBC recovery images. Building the SBC images takes a lot of time and is easy to mess up. I ended up creating three recovery images at different stages of the install so I could recover easily if I made install mistakes.


2021-02-24 07:07:01
웹에디터 시작 웹 에디터 끝