I have developed ROS2 packages for the BrickPi3. It has been tested on a Raspberry Pi 3 Model B+ running Ubuntu 22.04
There is a package for sensors and includes all the standard EV3 sensors plus a battery node, a HiTechnic Compass sensor and Gyro sensor.
There is a package that provides a ROS2 control hardware plugin (motors) for the BrickPi3.
There is also a demo package with an example launch file to launch ROS2 control and configure the plugin to use the ROS2 control differential driver controller (so you can drive the motors). The ROS2 control differential driver controller (part of ROS2) accepts Twist messages, and in this example configuration drives the EV3 motors.
I hope this may be of interest to the community and I welcome feedback.
The code is hosted on github and is available here: ROS2_BrickPi3
Regarding the forum I do plan on keeping in contact. I am not a BrickPi3 expert, for writing those ROS2 brickpi3 packages, they basically rely on the BrickPi3 github libraries (both their Python and C interfaces) to control the BrickPi3 board. The ROS2 brickpi3 packages that I wrote are just glue logic to tie ROS2 to the BrickPi3 library code. But I am happy to chip in with what I know.
I’ll be adding a YouTube link from my git hub repo (ROS2_BrickPi3 over the next day or so, if you are interested. (I have already made several versions of the video I am just deciding which one is best).
This is just a comment intended for those who are thinking about ROS2 but are not that familiar with it.
This is just my personal opinion, but my thoughts are that ROS2 is quite a complicated system, and for those who just want to get a robot up and running, reading some sensors and driving around; ROS2 is probably overkill. However for those who are feeling super ambitious, ie wanting navigation (SLAM), sophisticated object detectors, needing more compute than the Raspberry Pi can provide, therefore needing a distributed compute system…etc etc, ROS2 is the way to go.
Exactly agree. Unless trying to get hired by one of the 900 companies actually using ROS, or wanting to get a head start for a masters level degree in robotics, choosing to use ROS will complicate progress. (Or in my case really want to access visual SLAM with dynamic navigation to make my home robot “aware” and safe when exploring its surroundings.)
Yes, That multi-color LED (turning off the WiFi indication) makes a great color ID that can be seen by a PiCamera. (and I built a GoPiGo3 recognize color “sensor” that should be much easier to use than ROS!)
I don’t think anyone here is an “expert”, (with the exception of @cleoqc, who’s the relevant engineer at Modular Robotics!)
We’re all just people who find robotics interesting and stimulating, and find that the GoPiGo provides the best bang for the buck.
I also have a GrovePi+ to experiment with, (though I haven’t even unpacked it yet! )
@cyclicalobsessive and @KeithW are the local “experts” on ROS, alternative operating systems and getting things to work. You would do well to go back and read anything they’ve posted, as well as cloning their GitHub repos.
My own expertise is primarily hardware, multi-booting the Raspberry Pi, and the various flavors of Dexter OS, Raspbian for Robots, and the newer GoPiGo OS.
@cleoqc is the resident engineer for everything that is related to Dexter Industries’ products before they were subsumed by Modular Robotics. She’s forgotten more than we’ll ever know. She also maintains the distributions of GoPiGo OS and the Master Dexter Industries GitHub repos.
We need “resident experts” in the Brick Pi and GrovePi.
Anything you can provide would be gratefully appreciated!
Thanks for the tips. I didn’t see any reference to cyclicals or Keiths github repo’s. Would definitely be interested in checking them out. I thought it might be on their profile’s, maybe I am looking in the wrong place.