I'm currently using a normal breadbord 'n' solid-core-wires for prototyping, but it gets messy when I need to connect a large number of pins on the arduino, as when using an LCD display + another sensor. What are my other options for prototyping?
3
-
The real strength of an Arduino is shields. Ironically, that's also its biggest weakness.Ignacio Vazquez-Abrams– Ignacio Vazquez-Abrams2014-06-09 13:39:53 +00:00Commented Jun 9, 2014 at 13:39
-
After seeing pictures of shields and shields on top of each other, I really wanted to stay away from stacking things as possible i canDélisson Junio– Délisson Junio2014-06-09 13:41:30 +00:00Commented Jun 9, 2014 at 13:41
-
Use a protoshield like: arduino.cc/en/Main/ArduinoProtoShield or make your own out of protoboardimjosh– imjosh2014-06-11 14:59:53 +00:00Commented Jun 11, 2014 at 14:59
Add a comment
|
1 Answer
One of the Arduino's greatest strengths are shields, and shields upon shields. (Another is it's ease of programming via USB amongst a whole host of others).
They are perfect for prototyping. There's nothing wrong with breadboarding it as well, but it's pretty much one or the other (excluding making your own circuit board).
I am working on a garage controller and it has three shields on top of the arduino itself.
XBee/wireless coms
a relay shield, and
a prototying shield where I have created custom circuitry (buttons, connectors, optocouplers etc).
Especially with the top shield, I have made several changes to get it to perform as I'd like. If I'd committed to making a custom board, then I would have had to change it (and re-change it). What I've done would be virtually impossible on a breadboard.
The idea is, you use the shields to get your idea up and running, as a proof of concept. Then, you could/can leave it as is, or you could take the next step, break it down to the required components and make a custom PCB for your project. If it wasn't for shields and stacking shields, you would either breadboard it (which as you've indicated can get ugly, cumbersome and problematic), or make a PCB which (depending on the project) might not be a small task. So shield it up, test it out, then build your own based on what you've put together.
That's not to say, you have to make your own PCB in the end, many projects can remain a shield on an arduino. So if you can find a shield to do specifically what you're after, then why wouldn't you use it?
