I've just ordered a PCB that I'm hopeful will be a 'Version 1' https://rosmo-robot.github.io that I'll offer for sale on Lectronz.
This will support Microblocks Teleop from an Android app and also ROS2 Teleop from a browser.
There's a bunch of further software stuff that I'd like to get done 'at some point' I thought it would be good to write down some of these ideas to help potential collaborators jump into a bit of the project that's interesting to them.
ROS2 tasks
Create a URDF file for simulation
Confirm the Lidar to be working
Confirm IMU working
Confirm Mecanum drive working
Configure Foxlglove studio
Create up to date Virtualbox image of ROS2 install
Two I2C for the all important silly eyes OLED (haven't yet decided between the 1.3" or 1.5" pinout)
The MikroBus header compliments the on-board Qwiic and I2C breakout garden header as an attempt to navigate the I2C Zoo maybe I should stick a Grove on the breakout board to complete the menagerie..
This variant adds a Grove & Xiao camera for on board image processing
Having a bunch of encoder cabling is quite messy, It is functional but also fiddly to connect. I've almost finished a version that includes pluggable motor sockets to make the cable connection easier and less error prone
So thanks to Microblocks I have a remote control bot that can pick stuff up now. Still having problems with the ROS2 build, but nice to have some progress.
Arguably the Pi Pico format is becoming a 'default' footprint for microcontroller work. It at least has the benefit of having plenty of pins. It's a very narrow board though, not much room to play with.
So how does it look if we stick with the pico pinout (and maybe get a bit opinionated about how it's used, but break out the width to 28mm spacing?
The 'pico' one
Would be used as the compatibility layer between the narrow and wide spacing.