[Electrosync] is the creator and driver of the world’s fastest robotic vaccum cleaner, the Vroomba. It’s a heavily modified roomba capable of speeds of around 60 kph, well beyond the pedaling speed of most bicyclists. Despite being rejected by Guinness for a world record, we’re fairly confident that no other vacuum cleaners have gotten up to these speeds since the Vroomba first hit the streets. That’s not going to stop [electrosync] from trying to top his own record, though, and he’s brought the Vroomba some much needed upgrades.
The first, and perhaps most important, upgrades are to some of the structural components and wheels. The robot is much heavier than comparable RC vehicles and is under much greater strain than typical parts are meant to endure, so he’s 3D printed some parts of the chassis and some new wheels using a nylon-carbon fiber filament for improved strength. The wheels get a custom polyurethane coating similar to last time.
To our way of thinking, the whole purpose behind robotic vacuum cleaners is their autonomy. They’re not particularly good at vacuuming, but they are persistent about it, and eventually get the job done with as little human intervention as possible. So why in the world would you want to convert a robotic vacuum to radio control?
For [Lucas], the answer was simple: it was a $20 yard sale find, so why not? Plus, he’s got some secret evil plan to repurpose the suckbot for autonomous room mapping, which sounds like a cool project that would benefit from a thorough knowledge of this little fellow’s anatomy and physiology. The bot in question is a Hoover Quest. Like [Lucas] we didn’t know that Hoover made robotic vacuums (Narrator: they probably don’t) but despite generally negative online reviews by users, he found it to be a sturdily built and very modular and repairable unit.
After an initial valiant attempt at reverse engineering the bot’s main board — a project we encourage [Lucas] to return to eventually — he settled for just characterizing the bot’s motors and sensors and building his own controller. The Raspberry Pi Zero he chose may seem like overkill, but he already had it set up to talk to a PS4 game controller, so it made sense — right up until he released the Magic Smoke within it. A backup Pi took the sting out of that, and as the brief video below shows, he was finally able to get the bot under his command.
[Lucas] has more plans for his new little buddy, including integrating the original sensors and adding new ones. Given its intended mission, we’d say a lidar sensor would be a good addition, but that’s just a guess. Whatever he’s got in store for this, we’re keen to hear what happens.
The original Roomba robotic vacuum cleaner led to loads of clones and lookalikes over the years, and one of them is the ALEE mopping “robot”. [Raymond] tears it down and reveals what’s inside. Turns out it contains mostly regret! Although it does host some design cleverness in its own way.
Technically the ALEE, which cost [Raymond] a cool $85 USD, is not a robot since it has no sensors. And unless a dragging a wet cloth pad kept moist by a crude drip reservoir counts as “mopping”, it’s not much of a mop, either.
This one-motor unit (and tiny battery) is responsible for both motion and direction control. There are no sensors.
There is one interesting aspect to this thing, and it’s to do with the drive system and direction control. The whole thing is driven by a single motor, and not a very powerful one. The center of the robot has a pair of wheels that are both driven at the same rate and speed, and the wheel assembly can pivot around its axis. That’s about it. There are not even any bump sensors of any kind.
So how does this thing move, let alone change direction to (poorly) emulate an original Roomba-like crisscross pattern? The control board appears to have one job: if the motor stalls, reverse direction. That, combined with the fact that the drive unit can pivot and the enclosure is dragging a wet rag, appears to be all the chaos that’s needed to turn bonking into a wall into an undefined direction change.
It’s not great performance, but it sure is some impressive cost-cutting. You can see it bonk around unimpressively in a short video, embedded below the page break.
Just to be clear, [Raymond] knows perfectly well what he’s in for when he obtains cheap tech items from overseas retailers for teardowns. The ALEE does have some mildly interesting secrets to share, but overall, it really wasn’t worth it. Sometimes cheap tech has hacker potential, but there’s no such potential here. Seriously, don’t buy this thing.
A lot of people complain that Roombas are unreliable, poor at their job, or just plain annoying. Few people complain they’re not fast enough in a straight line. Regardless, [electrosync] set about building the world’s fastest Roomba for his own personal satisfaction.
For this challenge, [electrosync] set his own rules. The build must look like a Roomba, use two drive wheels, and one motor per wheel. It also has to maintain its vacuum functionality. After stripping down a used Roomba, he set about carving out space in the chassis for upgraded hardware. Brushed DC 775 motors were selected for the drivetrain, and these run through a 3:1 planetary reduction gearbox. 3D-printed mounts were then used to install the new motors in the existing chassis. New 3D-printed wheels completed the drivetrain. The original Ni-MH cells were replaced with a pair of 3-cell lithium polymer batteries for more power.
Measured with a Bluetooth GPS device, the upgraded Roomba achieved an impressive 36 km/h (22 MPH). With new wheel designs clad in urethane rubber and an improved anti-wheelie device, it hit a mighty 49 km/h (30 MPH). Adding 4-cell batteries pushed things further to 57 km/h (35 MPH), but the Roomba became difficult to control.
The gauntlet has been thrown down. Do you think you can build a faster Roomba? Time to get hacking! Video after the break.
If you’ve ever thought that your floor cleaning robot eating the fringe on your rug wasn’t destructive enough, [Kyle Brinkerhoff] is working on a solution — Doomba.
This blazingly fast RC vehicle has a tank of butane/propane gas nestled snugly amid its electronics and drive system to fuel a (not yet implemented) flamethrower. Watching how quickly this little bot can move in the video below certainly made our hearts race with anticipation for the inevitable fireworks glory of completed build. Dual motors and a tank-style drive ensure that this firebug will be able to maneuver around any obstacle.
As of writing, the flamethrower and an updated carriage for the drivetrain are underway. Apparently, spinning very quickly in circles can be just as disorienting for robots as it is for us biological beings. During the test shown below, the robot kicked out one of its drive motors. [Kyle] says the final touch will be putting the whole assembly inside an actual Roomba shell for that authentic look.
With spooky season upon us, it’s always good to have the cleansing power of fire at hand in case you find more than you bargained for with your Ghost-Hunting PKE Meter. While there’s no indication whether Doomba can actually run DOOM, you might be interested in this other Doomba Project that uses Roomba’s maps of your house to generate levels for the iconic shooter.
After all the fuss and bother along the way, it seems a bit anticlimactic now that the James Webb Space Telescope has arrived at its forever home orbiting around L2. The observatory finished its trip on schedule, arriving on January 24 in its fully deployed state, after a one-month journey and a couple of hundred single-point failure deployments. The next phase of the mission is commissioning, and is a somewhat more sedate and far less perilous process of tweaking and trimming the optical systems, and getting the telescope and its sensors down to operating temperature. The commissioning phase will take five or six months, so don’t count on any new desktop photos until summer at the earliest. Until then, enjoy the video below which answers some of the questions we had about what Webb can actually see — here’s hoping there’s not much interesting to see approximately in the plane of the ecliptic.
The modern home is filled with plenty of “smart” devices, but unfortunately, they don’t always speak the same language. The coffee maker and the TV might both be able to talk to your phone through their respective apps, but that doesn’t necessarily mean the two appliances can work together to better coordinate your morning routine. Which is a shame, since if more of these devices could communicate with each other, we’d be a lot closer to living that Jetsons life we were promised.
Luckily, as hardware hackers we can help get our devices better acquainted with one another. A recent post by [MyHomeThings] shows how the ESP8266 can bridge the gap between a Roomba and Amazon’s Alexa assistant. This not only allows you to cheaply and easily add voice control to the robotic vacuum, but makes it compatible with the Amazon’s popular home automation framework. This makes it possible to chain devices together into complex conditional routines, such as turning off the lights and activating the vacuum at a certain time each night.
The hack depends on the so-called Roomba Open Interface, a seven pin Mini-DIN connector that can be accessed by partially disassembling the bot. This connector provides power from the Roomba’s onboard batteries as well as a two-way serial communications bus to the controller.
By connecting a MP1584EN DC-DC converter and ESP8266 to this connector, it’s possible to send commands directly to the hardware. Add a little glue code to combine this capability with a library that emulates a Belkin Wemo device, and now Alexa is able to stop and start the robot at will.
