Hello,
White Box Robotics is a great idea, and one that a number of people have been working on for some years. I wish Tom every success in his venture.
I spent many years making my living as a professional musician and composer. Some of the tenor of this discussion reminds me of the early years of electronic music, especially with the introduction of synthesizers (Moog, Arp, Putney, Buchla) in the late 60's and early 70's. That spawned an enormous amount of creativity in the same way that the microprocessor and advances in sensor technology have goosed the field of experimental robotics 30 years later.
Part of the excitement at that time centered around the idea that this new technology would take "music making to the masses." The concept was that now folks would be able to make music without all the messy contingencies of having to learn, you know, all those notes and chords and scales and arpeggios and theory and stuff. The synthesizer would do it all for you. (think "disco").
Turns out, of course, that if you ever wanted to do any more than just play the demos on your Casio keyboard, that you actually DO have to learn all that other stuff. And yes, there is quite a bit to learn.
Now I seem to hear an echo of that same thing with experimental robotics: "Can't I just do robotics without having to learn all that mechanical, electronics, and software stuff? Can't I just buy that part from somebody else?"
With robotics, as with music, I think the real answer here is no.
You can, of course, buy a trumpet or a piano built by someone else, just as you can buy a micro-controller or gear-head motor or IMU built by someone else. But you can't "buy" the ability to play that piano. You actually have to take the time to learn the skill; there are no shortcuts (as my music teachers used to tell me!!!)
If you want to write a symphony, you really do have to master the entire orchestra. No other way to do it.
(For the non-musicians among us, substitute the word "math" for the word "music" and the words "pocket calculator" for the word "synthesizer" and the words "calculus and algebra and geometry" for the words "scales and arpeggios and music theory." Then substitute "build a robot" for "write a symphony" and "master hardware AND software" for "master the entire orchestra" :>} )
Part of the problem with the "commodity" approach to robotics, as Gordon and others have pointed out, is that there is no good definition of what problems we are trying to solve, or even agreement on the problems themselves, much less their definitions. This makes it very hard to define a commodity level, hardware, software, API, whatever. Your API ("you" in the universal sense) will probably not provide the functions that I want my robot to have, and vice versa.
So the "innovative" robots tend to be innovative in both software AND hardware. The two are really inseparable. I believe it will be that way for a long time to come.
The good news is, with robotics as with music, learning a new skill set is still worth it! Indispensable, some might say.
regards, dpa
formatting link