Last night at about 1:40am after a 172 minute marathon runtime, the D10 completed its mission to vacuum and mop an absurdly large shared office space. This was not what the D10 is intended for, it’s designed for home use, however this is the use case I have that’s real for it at the moment.
The idea was to supplement our cleaning staff’s efforts because the vacuum they’re using, the amount of time they have, etc lead to a heavily trafficked area being somewhat… not as clean as one would like. Not horrible, but something that could be aided by the addition of a tireless little robot.
From the previous reviews you know I had my issues with overly aggressive D10 behavior when it came to anything it thought it could climb. It took a couple of days to properly map out everywhere I needed to block off, mostly because I had to accompany the puck and make sure nobody tripped on it.
The first complete run without interference was completed last night and I think we’ve got a verdict, at least on the corporate / large scale side, and that is – great little vacuum, firmware / logic problems that need to be stomped out in an update, lack of non-Amazon voice integration seems like a losing proposition that could be remedied easily.
Problems encountered (in a large corp environment)
Preface this with the D10 is *not* being used in these tests in the environment is is designed for. The space I consider easy mode, the largeness of the space is at the top range of difficulty judging by the battery and amount of dirt removed.
Let’s start with the logic problems. An overly aggressive profile means it will fight to get into an area. This leads the D10 to climb and suspend itself on chairs that have a horizontal component (think rocking chair rockers.) There needs to be a setting of “don’t climb” and I don’t know why this is now something that needs to happen in puck vacuum world. the D10 is not alone. Vacuums are wilder these days it seems, more extreme.
It also will squeeze into areas by pushing that it can’t escape. This is one of those things that in a household you’d probably recognize pretty quickly and move something slightly, but it happened enough times that I had to block off around several plants that are in the atrium.
Watching how this progressed over the 170+ minutes of cleaning last night and how it zipped from place to place occasionally, I have some thoughts on the cleaning logic, but you know what, it did the job and I don’t think it did it badly… just maybe not as efficiently as it should have.
The cleaning completed with I’m guessing one line not properly cleaned. At least according to the map. I’m not entirely sure it wasn’t but I’m going by what the map shows which is a tiny sliver not hit. At 207 square meters (2228 sq feet,) cleaned on one charge, I’m fine with that. The battery hit some threshold, I’m guessing 15-16% and I got a warning that it was “Returning Charge” and a low battery popup.
I watched from home as the D10 drove itself to the dock, took an inordinate amount of time to empty, tossed me a note to clean the mop pad, popped up an error asking me to deal with errors that had popped up (rrr?,) said it was charging and then went offline. It stayed offline for the remainder of the night only coming back online when I walked in today and pressed a button.
So, after nearly 3 hours of cleaning this will become inoperable it appears. I’m not sure if this is time related, or that it was finishing up right as we hit the battery threshold. Whatever the case, it went offline and would not come back online without physically touching a button. More firmware issues.
What’s great about the D10?
While it took nearly 3 hours to do a daily routine, it got just about everywhere. We weren’t in a rush, and if this can go nightly without intervention then we’ve got a markedly cleaner building every day. That nearly 3 hour runtime is impressive. That’s on normal vacuum and increased mopping.
I’ll be moving this to a household test later, but it did good… I’m a bit surprised I found so little to be annoyed about.[Amazon]