@circuits24x7 One useful distinction for this overview: the README lists Apache-2.0 for code, but says the hardware-design license is still to be chosen. It separates them in the License section: makerspet/oomwoo
6 views
DIY vacuum cleaner robot update - Drive wheel suspension bring-up
Video - drive wheel housing, suspension assembled and working! I test the suspension by pressing the wheel. The suspension bounces the wheel back out nicely once released. The wheel-dropped-detection micro switch clicks when the wheel drops out fully and the wheel itself spins smoothly.
Highlights - drive wheel housing printed, suspension brought up (see video)
3D design makerspet/oomwoo-cad
- printed, brought a piece of the chassis: drive wheel box with cover
Electronics I/O board makerspet/oomwoo-pcb
- v1 board schematic cleaned up for review
Firmware makerspet/oomwoo-firmware
- oomwoo_pins.h regenerated from the cleaned-up schematic
Community contributions
- Thank-you to Valdi320 - Nav2 keepout (virtual walls) for the simulator, PR in review; tool-free fastener ideas
176 points · 10 comments
Open-Source vacuum robot progress - drive wheels suspension designed
Video - drive wheels spin, dip (into imaginary "potholes") and return back thanks to wheel suspension. A spring pushes wheels down for better traction getting out of "potholes". The side brush, main brushes spin as well.
Next up - 3D print base for wheels testing.
Highlights - drive wheel suspension designed; schematics done; firmware C GPIO pinout include available
Decision: v1 I/O board - use Android phone as the compute (USB-C to the STM32); push the Raspberry Pi out to v2 to shorten schedule
3D design makerspet/oomwoo-cad
- drive wheels designed: each wheel has its own suspension spring, dips into a "pothole" and presses down for traction
Electronics I/O board makerspet/oomwoo-pcb
- new v1 board (main-phone): STM32 runs all motors and sensors, including LiDAR and ToF, and forwards data to the phone
- charging dock rev 2: CH32V003, checks the robot is there before the contacts go live, IR beacon
- new small boards: 2x front ToF, side sensor (VL53L0X + IR receiver), 6x cliff sensors, rear docking IR, 2x Hall sensors
Firmware makerspet/oomwoo-firmware
- C include file available with GPIO assignments
- SPEC updated for the v1 board; MCU pinout include file
Software makerspet/oomwoo-install
- lighter Nav2: only the servers OOMWOO uses, no voxel layers (release notes 10/19)
Build-in-public Blog Posts
- PCBs: first board, a phone as the compute makerspet.com
- 3D design: main brush gearbox - why two gears were not enough makerspet.com
- 3D design: how drive wheel suspension works
Community contributions
- Thank-you to Valdi320 - cleaning-jobs experiments (spot cleaning, virtual walls) in Gazebo, PR #78 merged
- Thank-you to xbattlax for pushing the watchdog firmware PR toward a bench test
- Thank-you to aarondyck, medicinous and mathwest for corner-cleaning ideas in issue #74
250 points · 7 comments
every "smart" vacuum uploads a map of your house to someone's server. this one runs fully local and you build it yourself. this is tanta roba makerspet/oomwoo
3 views
Oh putain, enfin !!!! Un robot aspirateur qui sait travailler sans cloud chinois, comme quoi c'est possible ! makerspet/oomwoo
16 likes · 9 reposts
好像有开源项目 makerspet/oomwoo
1 like · 4 views
OOMWOO open-source DIY vacuum - project update
Video - step-by-step instructions how to 3D print a gear in POM (aka Delrin, acetal) easily at home. Why? POM is self-lubricating, has low friction, commonly used in gears that move. POM filament is cheap, readily available. POM is notoriously hard to 3D print because it doesn't stick to print bed and shrinks as it cools. Deal with that (relatively) easily - print first 2 layers in PETG, add a "color change", print the rest in POM. Why this works? POM sticks to PETG very well. Results are subject to limitations because POM still warps, gear tips can tent up. Close off the enclosure when printing the POM layers (not PETG) to lessen the effect.
Highlights - main brush gears 3D printed in POM/Delrin (see video). Main brushes are now removable (for cleaning, replacement).
Decision: main brush gears - 3D printed in POM; cutting them from Delrin sheet is now the backup
3D design makerspet/oomwoo-cad
- main brush gears printed in POM: two sacrificial PETG layers first, then POM
- main brush assembly redesigned to fix issues found after printing and assembling the first prototype
- both main brushes now removable, for cleaning or replacement
Build-in-public Blog Posts
- new: How I 3D print gears using POM (Delrin) makerspet.com
- 3D design: updated main brush drive section makerspet.com
Community contributions
- Thank-you to xbattlax for the Nucleo G474RE bench-test guide for the watchdog firmware
61 points · 1 comment
I'm building an open-source vacuum cleaner robot in public
Official goals: Clean well · Hackable · Raspberry Pi · 3D printed · Local / No cloud required · Home Assistant · Arduino · ROS2 · ESP32 Currently 11K GitHub stars, 1K Discord, 1.6K weekly subreddit, 890 X followers, 1K+ mailing list, build-in-public technical blog posts.
- Development process: solo, Claude Code for software, firmware, schematic reviews. 3D design manual. Upwork freelancers for layout, manual 3D design aspects.
- Challenges: a massive amount of technical work, but doable
- Why? Frustrated with consumer vacuum robots cleaning quality; seriously uncomfortable privacy-wise (mics, cams). I own 9 vacuum cleaner robots, including $1K tier. All have hangups. Many rearrange dirt instead of cleaning. I'm also a retired, bored workaholic - nice to meet you all.
- Milestones/progress: I post progress in r/oomwoo twice a week. Available right now - software dev environment, simulation. First 3D prints - end of this month (October 2026). First public alpha - Christmas 2026, I think.
- Long term strategy: a trusted worldwide home brand faithful to open source, privacy.
Please feel free to ask questions, I will try to answer in comments.
61 points · 8 comments
OOMWOO open-source vacuum - progress update
Video - I've added the side brush, placed the (optional) smartphone, pointed the camera at the floor (instead of forward).
The side brush is Dreame off-the-shelf 3-arm angled (cheap on Amazon/eBay/AliExpress), tangle-resistant thanks to its arms being angled, not straight.
The (optional) smartphone - the idea is to reuse an old Android USB-C phone instead of buying Raspberry Pi CM4/CM5. The phone will run the compute, WiFi - plus act as touchscreen. Pi will be supported as main option.
Point camera at the floor (instead of forward) - why? a) to check each floor spot if it's still dirty or not. If dirty, mop it until clean (I'll add a mop in 2nd vacuum version). b) for privacy (can't see up) and c) still perform obstacle recognition, but just above floor level.
=========================
Highlights - designed side brush, camera now watches floor; placed smartphone. Roborock S5 Max supported as real placeholder robot.
Decision: side brush - angled, tangle-resistant brush driven directly by a geared motor (no printed gearbox) Decision: camera - one RGB camera pitched down to see the floor and obstacles, replacing stereo NIR Decision: smartphone rough placement - top center
3D design makerspet/oomwoo-cad
- side brush: JGA25-310 geared motor turns a Dreame angled brush through a custom coupler
- main brush: 608 bearing + M3 threaded rod with custom coupler and latch tip
- Dreame hex-mount side brush, brush box undercover, dust bin inlet fix
Electronics I/O board makerspet/oomwoo-pcb
- camera moves to the STM32 so an old smartphone can be the compute
- 2x VL53L7 time-of-flight sensors, ~126° ahead, for obstacle detection
Build-in-public Blog Posts
- 3D design: brushes from parts you can buy makerspet.com
- PCBs: why one RGB camera instead of stereo NIR makerspet.com
Community contributions
- Thank-you to yugeeklab
- A special shoutout to gkfabs for bringing up a Roborock S5 Max with ROS 2 and creating PRs for remakeai/vacuum_ros2_bridge and kaiaai/VacuumTiger
152 points · 5 comments
Mentions
@circuits24x7 One useful distinction for this overview: the README lists Apache-2.0 for code, but says the hardware-design license is still to be chosen. It separates them in the License section: makerspet/oomwoo
DIY vacuum cleaner robot update - Drive wheel suspension bring-up Video - drive wheel housing, suspension assembled and working! I test the suspension by pressing the wheel. The suspension bounces the wheel back out nicely once released. The wheel-dropped-detection micro switch clicks when the wheel drops out fully and the wheel itself spins smoothly. Highlights - drive wheel housing printed, suspension brought up (see video) 3D design makerspet/oomwoo-cad - printed, brought a piece of the chassis: drive wheel box with cover Electronics I/O board makerspet/oomwoo-pcb - v1 board schematic cleaned up for review Firmware makerspet/oomwoo-firmware - oomwoo_pins.h regenerated from the cleaned-up schematic Community contributions - Thank-you to Valdi320 - Nav2 keepout (virtual walls) for the simulator, PR in review; tool-free fastener ideas
Open-Source vacuum robot progress - drive wheels suspension designed Video - drive wheels spin, dip (into imaginary "potholes") and return back thanks to wheel suspension. A spring pushes wheels down for better traction getting out of "potholes". The side brush, main brushes spin as well. Next up - 3D print base for wheels testing. Highlights - drive wheel suspension designed; schematics done; firmware C GPIO pinout include available Decision: v1 I/O board - use Android phone as the compute (USB-C to the STM32); push the Raspberry Pi out to v2 to shorten schedule 3D design makerspet/oomwoo-cad - drive wheels designed: each wheel has its own suspension spring, dips into a "pothole" and presses down for traction Electronics I/O board makerspet/oomwoo-pcb - new v1 board (main-phone): STM32 runs all motors and sensors, including LiDAR and ToF, and forwards data to the phone - charging dock rev 2: CH32V003, checks the robot is there before the contacts go live, IR beacon - new small boards: 2x front ToF, side sensor (VL53L0X + IR receiver), 6x cliff sensors, rear docking IR, 2x Hall sensors Firmware makerspet/oomwoo-firmware - C include file available with GPIO assignments - SPEC updated for the v1 board; MCU pinout include file Software makerspet/oomwoo-install - lighter Nav2: only the servers OOMWOO uses, no voxel layers (release notes 10/19) Build-in-public Blog Posts - PCBs: first board, a phone as the compute makerspet.com - 3D design: main brush gearbox - why two gears were not enough makerspet.com - 3D design: how drive wheel suspension works Community contributions - Thank-you to Valdi320 - cleaning-jobs experiments (spot cleaning, virtual walls) in Gazebo, PR #78 merged - Thank-you to xbattlax for pushing the watchdog firmware PR toward a bench test - Thank-you to aarondyck, medicinous and mathwest for corner-cleaning ideas in issue #74
every "smart" vacuum uploads a map of your house to someone's server. this one runs fully local and you build it yourself. this is tanta roba makerspet/oomwoo
Oh putain, enfin !!!! Un robot aspirateur qui sait travailler sans cloud chinois, comme quoi c'est possible ! makerspet/oomwoo
好像有开源项目 makerspet/oomwoo
OOMWOO open-source DIY vacuum - project update Video - step-by-step instructions how to 3D print a gear in POM (aka Delrin, acetal) easily at home. Why? POM is self-lubricating, has low friction, commonly used in gears that move. POM filament is cheap, readily available. POM is notoriously hard to 3D print because it doesn't stick to print bed and shrinks as it cools. Deal with that (relatively) easily - print first 2 layers in PETG, add a "color change", print the rest in POM. Why this works? POM sticks to PETG very well. Results are subject to limitations because POM still warps, gear tips can tent up. Close off the enclosure when printing the POM layers (not PETG) to lessen the effect. Highlights - main brush gears 3D printed in POM/Delrin (see video). Main brushes are now removable (for cleaning, replacement). Decision: main brush gears - 3D printed in POM; cutting them from Delrin sheet is now the backup 3D design makerspet/oomwoo-cad - main brush gears printed in POM: two sacrificial PETG layers first, then POM - main brush assembly redesigned to fix issues found after printing and assembling the first prototype - both main brushes now removable, for cleaning or replacement Build-in-public Blog Posts - new: How I 3D print gears using POM (Delrin) makerspet.com - 3D design: updated main brush drive section makerspet.com Community contributions - Thank-you to xbattlax for the Nucleo G474RE bench-test guide for the watchdog firmware
I'm building an open-source vacuum cleaner robot in public Official goals: Clean well · Hackable · Raspberry Pi · 3D printed · Local / No cloud required · Home Assistant · Arduino · ROS2 · ESP32 Currently 11K GitHub stars, 1K Discord, 1.6K weekly subreddit, 890 X followers, 1K+ mailing list, build-in-public technical blog posts. - Development process: solo, Claude Code for software, firmware, schematic reviews. 3D design manual. Upwork freelancers for layout, manual 3D design aspects. - Challenges: a massive amount of technical work, but doable - Why? Frustrated with consumer vacuum robots cleaning quality; seriously uncomfortable privacy-wise (mics, cams). I own 9 vacuum cleaner robots, including $1K tier. All have hangups. Many rearrange dirt instead of cleaning. I'm also a retired, bored workaholic - nice to meet you all. - Milestones/progress: I post progress in r/oomwoo twice a week. Available right now - software dev environment, simulation. First 3D prints - end of this month (October 2026). First public alpha - Christmas 2026, I think. - Long term strategy: a trusted worldwide home brand faithful to open source, privacy. Please feel free to ask questions, I will try to answer in comments.
OOMWOO open-source vacuum - progress update Video - I've added the side brush, placed the (optional) smartphone, pointed the camera at the floor (instead of forward). The side brush is Dreame off-the-shelf 3-arm angled (cheap on Amazon/eBay/AliExpress), tangle-resistant thanks to its arms being angled, not straight. The (optional) smartphone - the idea is to reuse an old Android USB-C phone instead of buying Raspberry Pi CM4/CM5. The phone will run the compute, WiFi - plus act as touchscreen. Pi will be supported as main option. Point camera at the floor (instead of forward) - why? a) to check each floor spot if it's still dirty or not. If dirty, mop it until clean (I'll add a mop in 2nd vacuum version). b) for privacy (can't see up) and c) still perform obstacle recognition, but just above floor level. ========================= Highlights - designed side brush, camera now watches floor; placed smartphone. Roborock S5 Max supported as real placeholder robot. Decision: side brush - angled, tangle-resistant brush driven directly by a geared motor (no printed gearbox) Decision: camera - one RGB camera pitched down to see the floor and obstacles, replacing stereo NIR Decision: smartphone rough placement - top center 3D design makerspet/oomwoo-cad - side brush: JGA25-310 geared motor turns a Dreame angled brush through a custom coupler - main brush: 608 bearing + M3 threaded rod with custom coupler and latch tip - Dreame hex-mount side brush, brush box undercover, dust bin inlet fix Electronics I/O board makerspet/oomwoo-pcb - camera moves to the STM32 so an old smartphone can be the compute - 2x VL53L7 time-of-flight sensors, ~126° ahead, for obstacle detection Build-in-public Blog Posts - 3D design: brushes from parts you can buy makerspet.com - PCBs: why one RGB camera instead of stereo NIR makerspet.com Community contributions - Thank-you to yugeeklab - A special shoutout to gkfabs for bringing up a Roborock S5 Max with ROS 2 and creating PRs for remakeai/vacuum_ros2_bridge and kaiaai/VacuumTiger