Skip to main content

An open letter to Neato Robotics

I recently purchased a Neato Robotics Neato XV Signature Pro. We went with the Neato over the iRobot Roomba because the Neato actively maps the room. I've been impressed with how well the Neato works.


Originally I thought it might be marginally useful, would pick up some dust and dirt but we would have to vacuum by hand every so often. This doesn't appear to the case. Its room mapping and edge following work pretty well, it can climb up onto rugs without trouble and generally the floors (all hard floors on the first floor, except for a few rugs) are the cleanest they've ever been, and consistently so. We schedule the Neato to run almost every day, usually when we are home in case we need to pull a dog toy out of its brush or get it out from under the dining room table where it got in between all of the pushed in chairs but then couldn't find its way out. Which brings me to the topic of this post.




Dear Neato Robotics,

You should consider leveraging the interest and expertise of the community of robot hackers to build an even better product. A considerable amount of time has gone into figuring out how the Neato Lidar system works, organizing information about hacking the product, or trying to add useful new features like a side brush for better edge cleaning.

Why not attempt to take advantage of this community? Providing a standard hardware and software interface might accelerate improvements in the floor mapping system. Individuals may build systems to add wireless connectivity so you might get a helpful reminder from your Neato about it being stuck or needing its dust bin cleaned. Better hardware details could open up improvements to the battery system that might enable the use of Li-Ion batteries for longer battery life. Companies can't build or test all of the odd ideas that are developed internally. It costs too much, in terms of time and dollars, to develop these ideas and present them to your customers. By letting the hobbyist try some of these ideas out it would be possible to watch to see the level of interest from each one and to use that as an input into product development.

Being open with the community is likely to yield some useful product ideas, improvements and engineering concepts that can be folded back into the next versions of the product, but it can also be a marketing and public relations tool. 

The hobbyist groups most likely to work on these technical areas of the robots can represent a new set of product champions and they may not overlap with the current set of customers.

I'd encourage you to take advantage of the interest people have and to use it to differentiate your business from your competitors. I believe that you could do so in a way that would both protect your IP and leverage the work of others.

Regards,
Chris Morgan

Comments

  1. Hi Thomas.

    I haven't. I looked at the Neato website and they've made some big improvements since I checked last several months ago. Their new vacuums have lithium ion batteries and wifi.

    It would still be cool to see if the hacker/maker community could make their product even better wig some amount of openness or cooperation. Feels like there is free engineering and product development out there if they were willing to share a bit.

    What is your interest in Neato btw?

    Chris

    ReplyDelete
  2. I just got the wifi version of the bot and from what I've seen so far, this open letter still very much applies to Neato; they refuse to provide API access over the IP interface (no fun!), and have even removed a lot of the online documentation of the existing serial API. There's a huge interest in this type of stuff from the Home Automation community, and it seems they've been stonewalled, though many of them have found varying, but limited ways around that.

    ReplyDelete

Post a Comment

Popular posts from this blog

Debugging an imprecise bus access fault on a Cortex-M3

This information may apply to other cortex series processors but is written from practical experience with the Cortex-M3. Imprecise bus access faults are ambiguous, as noted by the term "imprecise". Compared to precise bus errors, imprecise errors are much trickier to debug and especially so without a deep understanding of arm processors and assembly language. Imprecise and precise flags are found in the BusFault status register, a byte in the CFSR (Configurable Fault Status Register). BusFault status register bits The definition for imprecise and precise bits is: [2] IMPRECISERR Imprecise data bus error: 0 = no imprecise data bus error 1 = a data bus error has occurred, but the return address in the stack frame is not related to the instruction that caused the error. When the processor sets this bit to 1, it does not write a fault address to the BFAR. This is an asynchronous fault. Therefore, if it is detected when the priority of the current pr...

Travelling on Spirit airlines out of Boston Logan airport? Here are some tips.

I attended CES 2017 in Las Vegas. Booking the trip late I ended up on Spirit airlines. It was both non-stop, making it six hours to Las Vegas from Boston, and affordable, less than $300 for a one way trip compared to around $700 with JetBlue. Here are some tips that might help you when travelling on Spirit from Boston Logan airport. Eat Spirit is located in the B-terminal, gates B-37 and 38, with its own TSA security checkpoint. While it does have restrooms and places to sit the food selection is limited to a single food stand. I'd recommend eating at the Legal C Bar (number 77 in the image below) prior to going through the terminal security checkpoint. The food and service there were great. Drink The water and other drinks are cheaper if you buy them at the food cart rather than on the flight. Seats The seats on Spirit don't recline. They do this to reduce weight, seat cost, seat maintenance costs, and so seats don't impact the free space of other passengers,...

Yocto recipe SRC_URI for a BitBucket / GitHub ssh git repository

This is a particularly geeky post but because Google searches didn't turn up any information I thought it would be helpful to document the issue and solution for others. I was writing  Yocto recipes that pulled from BitBucket git repositories in ssh form and ran into several issues getting a SRC_URI that worked. GitHub uses the same syntax for their ssh repositories. A BitBucket / GitHub git url, in ssh form, looks like: < username >@bitbucket.org:< account name >/< repository name >.git a more concrete example for a git repository in one of my BitBucket accounts looks like: git@bitbucket.org:cmorgan/somerepository.git Yocto recipes can pull from git repositories by setting the SRC_URI variable appropriately. Unfortunately you can't just do: SRC_URI = "git@bitbucket.org:cmorgan/somerepository.git You'll get errors because the Yocto won't know what kind of url this is. You need to specify the protocol for Yocto to k...