Perhaps ROS 2 Robotics is just too complicated a subject, too diversified domain for a hobbyist. After 40 years of building robots, the last two years have been dedicated to building a ROS 2 robot that would allow me to leverage ROS community developed software to achieve my robot dreams - primarily being a fully autonomous, 24/7 home robot aware of the objects and people in its environment.
I successfully built a ROS 2 Humble (first Foxy, Galactic) robot from the ground up, based on the GoPiGo3 platform, starting with the hardware interface/control node, and progressing to mapping, and localization with a LIDAR and SLAM-toolbox.
Doing this alone, I became blocked at developing an EKF node to fuse IMU and wheel encoder data to improve the odometry accuracy. This hurdle increased my desire to “follow” folks rather than be a “blind leader of a group of one”
During that project I actively participated in the Create3 Simulator beta, and the Oak-D-Lite kickstarter program, so when the TurtleBot 4 Lite was released I grabbed one of the first units available.
I was really excited by the TB4Lite design, but discovered:
- I was not a part of a flood of new owners as I had expected
- The TB4 software had not integrated the Oak-D-Lite sensor for mapping/localization/navigation
and as my particular TB4Lite was damaged in shipping, it was returned.
At the end of last year, I decided to purchase a Create3 to form the platform for my next robot. Having an Oak-D-Lite sensor already, my plan for this robot is to investigate what is possible with only the Create3 sensors and the Oak-D-Lite stereo depth sensor. Choosing not to include a LIDAR in my robot architecture has again set me on a slightly different path than most ROS hobby robots, but seeing that there is a depthai-ros package and a launch file to tie the Oak camera with RTABmapping, I thought I would not be totally alone on this path.
While the support teams for both the Create3 and the Oak-D-Lite are really superb, the diversity of sensors, user installations, languages, ROS versions, package versions, DDS types, data and power connections, underlying operating systems, user sophistication, and user goals seems to me just a chaotic mess. I am again feeling left to navigate alone with no one to follow.
Most of my questions on robotics.stackexchange.com have gone unanswered. My issue reports created on github sit for weeks or months without solution. The community seems too diverse to find another hobbyist that might have seen and solved my particular challenges. There is lots of great activity going on, but the hurdles are very frustrating at this point.