Why hasn't Brandon been blogging recently?May 11, 2011 | categories: rascal | View Comments
This blog has tended toward dormancy over the last year because I've been pouring all my energy into a new project, the Rascal. It's a small computer aimed at artists and scientists who want to add web interfaces to their projects. It similar to the Arduino, but much more powerful.
Recently, I've been alternating between working on the Rascal and various renewable energy engineering projects with Matt Dorson at Mystic River Engineering. In April, the first batch of Rascal beta units arrived from an assembler in China; I've sold 4 of them to various adventurous friends of mine for hardware testing. In the immediate future (May, June), I'm working on a project at MIT with Matt, but on the side, I'm selling more Rascals and gathering results from hardware testing. Depending on the results of the tests, I'll either commit to a larger batch of 100 Rascals, or run another small batch with improved hardware. If you're interested in the Rascal, you should follow the Rascal on Twitter here, or add your email address to the announcement list on the main page of the Rascal website. There's also a quick video interview of me explaining how the Rascal works. It was shot by Chris Connors at the 2011 mini-Maker Faire in Cambridge, MA, USA.
Thoughts on the 2010 Open Hardware SummitSeptember 28, 2010 | categories: rascal, openhardware, embedded | View Comments
Last Thursday, I went to the Open Hardware Summit in Queens, NY. The Summit had a lot going for it-- people from all of the major open hardware players were there (Arduino, Adafruit, Sparkfun, Bug Labs, and Beagleboard, to name a few), and it took place at the New York Hall of Science, a cool science museum right next to Flushing Meadows with its enormous, awesome Unisphere.
For the past few months, I have been working solo on a device that I intend to be open hardware. In my circumstances as not just a "small business," but the smallest possible business, the crucial question is whether opening my hardware designs to the world will result in someone taking a design and replicating it more cheaply than I can, thereby stealing all my customers. Against that fear, I have the hope that opening my designs will result in people improving them in ways that I can't predict.
This issue came up repeatedly at the summit. Many of the speakers were actually building and selling open hardware. Very few came from VC-funded companies (Bug Labs is the notable exception). Most of them were engineers who had bootstrapped their way from a few small designs they made themselves. They are evidence that my fears are unfounded, particularly in my current state of obscurity.
The explanations varied. Limor Fried of Adafruit said something like, "People say they will copy you, but it's hard to actually do. . . . Being obscure is worse than being ubiquitous." (A video of her talk is now available.)
In a later talk, Chris Anderson, who runs DIY Drones, mentioned the power of the community. They design small, autonomous aircraft and release all the plans on the internet. Their customers buy the electronics from DIY Drones and then tweak them. Anderson isn't worried about closed competitors: "We think the customers will go with the community." He also pointed out that the community of drone zealots was innovating faster than most private companies; even if you were to copy the hardware today, you'd be obsolete in short order.
After one of the panels, I talked to Nathan Seidle of Sparkfun for a few minutes. Sparkfun is the internet version of what Radio Shack was in the 70's, when they sold lots of electronic components. They have over 80 employees and around $10M in annual revenue. I asked Nathan why Sparkfun, if run by an evil version of him, wouldn't just collect open hardware designs and start replicating them. His answer was that breaking the trust of the community like that would devastate his sales.
Later in the day, I talked with Chris Gammell of the Amp Hour for a few minutes. He said that he was worried about what was going to happen when larger distributors enter the open hardware market. This is an interesting point viewed in the light of Nathan Seidle's and Chris Anderson's comments about the trust of the community. When the open hardware community is a small subgroup of a 10-100 thousand people forming a somewhat cohesive culture, losing the support of the community might be catastrophic. But if the electronic hobbyist world grows so that most of Sparkfun's customers don't even know that the hardware they're buying is open, it might be worth it for a giant like Digikey to risk alienating the hardcore open hardware folks. The situation might be like the libertarian anti-Obamacare editorial published by the CEO of Whole Foods in the Wall Street Journal last year-- hardcore liberals started boycotting Whole Foods, but the majority of their customers didn't care, because have you tried their almond cookies?
For me, as a new entrant to the market, I have no worries about a large corporation stealing my ideas-- risking the $100,000 it would take to beat me on volume on the hope that this solitary engineer has come up with a winning product would be colossal folly. I do think that the Rascal will be a great product, but it's definitely not there yet, and it will take a community of users to get it there.
One other interesting note-- during lunch, I met Simon Ford and Dan Ros of mbed.org, a small group within ARM that is making development tools for ARM processors. The Mbed is not fully open hardware, though they do distribute schematics of the system. Simon said it was because he wanted to be sure they were built right.
The Mbed is an interesting board. It actually has two microcontrollers on it. The main processor, on top, is an LPC1768 running at 96 MHz. There is a second processor running at 12 MHz on the underside of the board that acts as the programmer for the first processor. You compile your code on their website and then transmit your programs to this supervisory processor via USB. It puts the code on the second processor via JTAG. The advantage of this is that the main processor behaves exactly as it will in a final design. You can design a device using the mbed, and when you're done, you can buy the same LPC1768 processor and replicate what you've got, minus the second processor, which is no longer necessary. It's an elegant architecture.