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.


Popular posts from this blog

FoxInCloud Stats

FoxInCloud sent this link a while back about their statistics regarding visits to their site:

What's interesting here is the breakdown of people. Yes, I think it's understandable that the Fox community is getting older.

Another factor is the growth of the mobile and web environments taking over development. These environments really do push people towards the newer non-SQL or free SQL/hosted environments but more towards hosted storage options like Amazon and Google. A tool like FoxInCloud that helps MOVE existing applications to the cloud inherently competes with those environments.

But FoxInCloud also allows developers to extend their application further by giving them a starting point using Javascript and the basic CSS (such as Bootstrap). If you're not rebuilding your application from scratch, it's certainly a great step forward.

Well, that explains CodePlex...

In a move that will be sure to anger open source (or rather anti-paid software, anti-Microsoft open source)  zealots, Microsoft is planning to buy GitHub.

A year ago, I mused about why Microsoft would shut down CodePlex and how the world needs competing source code repositories to be strong. I'm not the only one per this Slashdot article :
"...people have warned about GitHub becoming as large as it did as problematic because it concentrates too much of the power to make or break the open source world in a single entity, moreso because there were valid questions about GitHubs financial viability...." - Jacques Mattheij

I will be interested in seeing this play out - whether developers jump ship or not. Have all the efforts Microsoft has made in pushing towards open source be seen as genuine or will all the zealots jump ship or maybe even attack?

Microsoft's comment about why they shut down CodePlex referred to how spammers were using CodePlex. Well, GitHub has its own …

The World of Updates Today

I just received an update for Office 365. It certainly includes some cool features - including starting in one environment and picking it up in another environment. In recent years, I've certainly enjoined the use of Continuity on a Mac and in fact, I feel spoiled being able to start a message in one environment (even Google) and then finish it off on another.  This has become some pervasive when we were reviewing our most recent backlog at a client site, a similar feature was added to the current workload.

But with web applications, the trend is to reduce the amount of software on a client machine. I used to have automatic backup for all of my machines (thanks Carbonite!) but these days, many of my machines don't need anything beyond the core OS and some basic applications. Certainly that's the feeling with Chromebooks and even the lightweight aspect of many iOS apps. The functionality is mostly in the cloud.

When you upgrade your system, you expect it to a big update. So…