About this project
Did you miss the Arduberry Kickstarter? You can pre-order the Arduberry from our website at http://www.dexterindustries.com/Arduberry.html !
The Arduberry is a simple and inexpensive way to bring Arduino shields to the Raspberry Pi. The device is a shield that slides over the Raspberry Pi and allows you to stack and use Arduino shields. The Arduberry requires no physical configuration to work with most shields. You can write Arduino sketches (programs) right on your Raspberry Pi.
The Arduberry will bring the Raspberry Pi and Arduino together, uniting the two greatest hacking systems ever.
The Arduberry is the simplest way to bring the physical world to your Raspberry Pi.
So What Exactly Is It?
The Arduberry is a shield for the Raspberry Pi that connects Arduino Shields. You can think of it almost as an Arduino, built for the Raspberry Pi. The Arduberry connects to the Raspberry Pi with the standard 26 pin header. The shield has an Arduino UNO-compatible microcontroller on it, as well as standard pins for an Arduino shield.
The Arduberry requires virtually no hardware setup: slip it onto the Raspberry Pi and go. It ships ready to work. The Arduberry comes fully assembled, and you won't need to make any changes to the hardware (no pinning, no batteries, no nothing!).
The Arduberry microcontroller can be programmed to run on it's own and access Arduino shields. Shields that use digital communications can be accessed directly by the Raspberry Pi, while shields that use digital or analog pins can be controlled by the Arduino. The Arduino chip on the Arduberry can communicate directly with the Raspberry Pi with no extra setup required.
How Does it Work?
While most shields can work directly with the Raspberry Pi, some sketches, like those that use analog signals, will need slight modification to the sketch to be able to relay information on to the Raspberry Pi. We will create a tutorial that walks you through how to adapt those sketches.
The Arduberry Board.
The Arduberry Image.
Who are you?
A corollary to your question might be: why are we capable of delivering the hardware? We've been working with contract manufacturers for the past few years. That's not to say that we know everything about manufacturing, but it is to say that we know who we're going to use on this project. We have worked with the manufacturers on projects more complex than this, and we have faith they can deliver only because they do it for us on a monthly basis already.
Why Are You Doing a Kickstarter?
Like our previous project, we want to build a community around Arduberry, and get feedback on our project. We believe that the best projects are responsive and the work of many, not just two nerds working alone. For that reason, we wanted to get this project out of our heads, and in the open. We think Kickstarter is the best way to do this.
Why is the design open? Aren't you afraid someone's going to steal it?
The design is open because we genuinely want to contribute to learning, and the best way to do that is to show your work. We want to honor those that made this project possible, in particular the brave folks that open-sourced the Arduino and the Raspberry Pi. Like all things in the Arduino and Raspberry Pi community, we hope that people will use this, and make it better: it raises our game.
Even more importantly, we hope that whoever uses the Arduberry, moves the open source community forward, and helps folks make their hacking dreams come true.
What Have You Done and What Is Left To do?
We have hand-made prototypes, and a growing library of examples with the Arduberry. We have had the design reviewed by manufacturing engineers for mass production. If this product is successfully funded, our focus will be on three things:
- Developing software examples. We have found that the best way to learn with software is to follow examples. We want to produce a solid library of examples with different shields to make sure Arduberry users have an easy start. Doing this takes developer time and effort.
- Developing tutorials for getting started. Furthering goal number 1, we want to make sure we develop tutorials for a few of the most popular Arduino shields to ensure that its easy for most folks to get started with the Arduberry.
- Developing a custom image for the Arduberry. The Arduberry needs a few changes made to the Raspbian image to operate. We found in our previous project that some folks prefer to have the changes to the image already made. In order to make the Arduberry as easy to use as possible, we will develop a custom image for download that will allow users to get started right out of the box, with minimal setup.
Hardware Delivery Timeline
We plan for the campaign to end on approximately 2/14/2014. We will immediately formalize the order with our manufacturer and begin material procurement. We need a little under 30 days to secure the PCBs and components. We allow a 7-day prototyping window in which a sample is delivered by the manufacturer and approved by our team. Production afterwards should take 10 days, with an extra 2 days of testing and QA/QC. Finally, we allow for 14 days of shipping from Asia to the US, where our team will ship the rewards.
Software Delivery Timeline
We will prioritize the development of the Arduberry Image. We have developed an initial install script (found on our Github site) and will finish testing this mid-campaign. We should have final changes to the image done by the end of the campaign.
We plan to finish the software examples and tutorials by the time the Arduberry is shipping so that it will be ready for backers receiving their rewards.
Risks and challenges
There are risks to every hardware project. Having successfully completed a previous Kickstarter Project, we would like to think we're wiser and more capable than ever before. Furthermore, having a long term relationship with our manufacturer, and having some experience in manufacturing major projects, we think we're well prepared to deliver.
Risks to manufacturing include material delivery delays, QA/QC delays, and customs delays (just to name a few). In our first Kickstarter Project, we received a lot of great feedback on our design and because of it, we delayed delivery by a month so we could properly integrate the feedback. There is the risk that feedback from the community during the campaign could result in changes in the timeline, due to us improving the product.
There are risks to fulfillment: once we have the parts manufactured and tested, we have to ship them to our backers. Fortunately, we've been shipping products to people all over the world for a few years, and we've got loads of experience with that. We have priced all of our products for standard delivery via USPS.
There are risks to delivery. For simplicity, we are pricing our rewards with standard United States Postal Service Parcel shipping built in. USPS has been a reliable partner for years, but from time to time they can lose an order in the system.Learn about accountability on Kickstarter
Have a question? If the info above doesn't help, you can ask the project creator directly.
Support this project
- (30 days)