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

Graco Swing By Me - Battery to AC wall adapter modification

If you have one of these Graco battery powered swings you are probably familiar with the cost of C batteries! The swing takes four of them and they only last a handful of days. I'm not sure if the newer models support being plugged into the wall but ours didn't. If you are a little familiar with electronics and soldering, here is a rough guide on how you can modify yours to plug in! I wasn't sure how exactly to disassemble the swing side where the batteries were. I was able to open up the clamshell a bit but throughout this mod I was unable to determine how to fully separate the pieces. I suspect that there is some kind of a slip plate on the moving arm portion. The two parts of the plastic are assembled and the moving arm portion with the slip plate is slid onto the shaft. Because of the tension in that slip plate it doesn't want to back away, and because of the mechanicals that portion of the assembly doesn't appear accessible in order to free it. I was

Memory efficient queuing of variable length elements

In embedded environments memory can be a critical driver of the design of data structures and containers. Computing resources have been expanding steadily each year but there are still a wide range of systems with far less than a megabyte of memory. On systems with tens of kilobytes of memory, structures are often designed to be compact to maximize data density. Rather than splurging on memory aligned elements that would be faster for the processor to access, a developer will typically use types with minimal sizes based on the known range of values that the element is intending to hold. Fixed sized buffers At my day job a fixed size pool of messages was implemented to hold message data. While this achieved one design goal of using statically allocated buffers, avoiding dynamic allocations that might fail at runtime, it isn't efficient if there is a wide range of message sizes. It isn't efficient because each message uses a message buffer. With small message sizes the buff