Skip to main content

Cleaning the Roomba: RTFSWS

Early last year, I purchased a Roomba (one of those robotic vacuum cleaners that whip around on the floor). Great device! I had some problems with one unit and their customer service sent me a new one out without any hesitation.

Last week, Trish was noting that it didn't seem to be charging properly. I reverified the cord and it worked fine.

Then yesterday, she said "it doesn't work. he starts and then just stops." There was nothing in the user guide (gasp!) on it except "clean the brushes" so after cleaning it out (yes, we do this after EVERY use), I went into Self-test mode to see if that would solve it. Nope - everything seemed to check out. After searching some posts from other users (some positive and some negative), I decided when all else fails, RTFWS - Read the Freaking Support Web Site.

Sure enough - there it was. The Roomba's sensors are all really well placed except for the left one, which is right above one of the brushes - (it uses the sensors for movement and there are left open presumably for more accurate checks). With three dogs and a cat, you can only imagine how dirty it would get. Sure enough, cleaned it out with a little air and a damp cloth, and Rover (the Roomba) was off on his merry way, spinning and turning as he cleaned the floor.

Over the years, I've had a number of vacuum cleaners from expensive ($1500) to dirt cheap ($50), for $200US, the Roomba is well worth the value but be aware: it has to be cleaned just like a computer. If Roomba could do one little thing to improve this device, it would be to provide better tools or technologies for cleaning the Roomba (granted I haven't seen the latest Discovery model).

Include a little screwdriver for undoing the brushes, provide a little brush for cleaning those hard to reach areas, maybe include (or suggest) a can of compressed air - but perhaps most importantly, have the Roomba itself tell you when those sensors are dirty. Most people wouldn't think to look there and its not mentioned clearly in the user guide.

Comments

Popular posts from this blog

Elevating Project Specifications with Three Insightful ChatGPT Prompts

For developers and testers, ChatGPT, the freely accessible tool from OpenAI, is game-changing. If you want to learn a new programming language, ask for samples or have it convert your existing code. This can be done in Visual Studio Code (using GitHub CoPilot) or directly in the ChatGPT app or web site.  If you’re a tester, ChatGPT can write a test spec or actual test code (if you use Jest or Cypress) based on existing code, copied and pasted into the input area. But ChatGPT can be of huge value for analysts (whether system or business) who need to validate their needs. There’s often a disconnect between developers and analysts. Analysts complain that developers don’t build what they asked for or ask too many questions. Developers complain that analysts haven’t thought of obvious things. In these situations, ChatGPT can be a great intermediary. At its worst, it forces you to think about and then discount obvious issues. At best, it clarifies the needs into documented requirements. ...

Blogs and RSS come to Microsoft.com

MS has just introduced their portal and it's pretty comprehensive. Nothing quite like learning that some people use AIM instead of MSN messenger, or that there really may be a need for supporting 4 monitors ( Cyrus Complains ) However, it's really a great sign that MS is serious about supporting the blogging community which seems to have um, exploded in size in the past year. Blogs and RSS come to Microsoft.com

I’m Supposed to Know

https://programmingzen.com/im-supposed-to-know/ Great post for developers who are struggling with unrealistic expectations of what they should know and what they shouldn't. Thirty-forty years ago, it was possible to know a lot about a certain environment - that environment was MS-DOS (for non Mac/UNIX systems). . There was pretty much only a handful of ways to get things going. Enter networking. That added a new wrinkle to how systems worked. Networks back then were finicky. One of my first jobs was working on a 3COM + LAN and it then migrated to LAN Manager. Enter Windows or the graphical user interface. The best depiction of the complexity Windows (OS/2, Windows NT, etc) introduced that I recall was by Charles Petzold (if memory serves) at a local user group meeting. He invited a bunch of people on the stage and then acted as the Windows "Colonel", a nice play on kernel. Each person had a role but to complete their job they always had to pass things back to h...