Best Hardware Interfaces for Max

I've been studying for a few days now. I think I've narrowed my search down to using the Arduino Mega or the Make Controller v2.0 Application Kit.

For anyone else looking for hardware information these are somewhat helpful:
http://www.uchobby.com/index.php/2008/12/07/where-to-start-with-microcontrollers
http://forums.makezine.com/comments.php?DiscussionID=2621
http://ask.metafilter.com/91772/Aurduino-or-Make-Controller
http://www.makingthings.com/arduino-comparison
http://blog.makezine.com/archive/2009/09/review_make_controller_kit_v2.html

At this point I'm leaning towards the Arduino Mega.
Reasons:
1) It has more available connections.
2) It seems there are many current books published with examples.
3) It seems the support documentation and user community are up-to-date and lively.

I really want to get a Make Controller however because the board is faster, has more memory, etc. After reading tutorials it seems really easy to use USB/Ethernet to get values from sensors into Max/Flash... The main reason I'd love to go with the Make is the built in ethernet.

However, it seems like make isn't supported very well (documents on site are buried and hard to find), there are no books published about it that I could find, and the forums are lack-luster. The latest forum entry is from two users begging for an update on new firmware development and consequently complaining that it's been like 3 months and still no answer. Not very reassuring. Being a new user this scares me... hahaha.

So my question now is this. Does anyone know if it is possible to add an ethernet shield onto the mega (like this one: http://www.nkcelectronics.com/nkc-ethernet-shield-for-arduino-mega--duemilanove--diecimila-diy-kit.html ) and interface with it over UDP or TCP via OSC from MaxMSP or Flash AS3? This seemed very straightforward with the Make Controller but potentially more difficult with the Mega.

You are probably correct in choosing Arduino. It's a great learning platform and there is a huge community. Look to Lady Ada for some excellent tutorial material:

http://www.ladyada.net/make/eshield/

I have a Make Controller Kit and I like it. I've found it it very easy to use with Max, and I like ethernet as a hardware interface. Also, it has good built in control for motors. However, it's been a long time since I looked for support. Your questions:

Which are best supported in documentation/tutorial and customer support?
Doubtless, this will be arduino.

Which work best using a Mac?
Both support Mac fully. I don't know what "best" means, but you won't be limited in either case.

Which are easiest to use?
I found MCK to be easier to get started. YMMV.

Which have the best sensors?
The ones you learn to build yourself are the best. The same sensors work with either.

Are certain systems better for certain things?
Because of cost, I'd prefer Arduino for something embedded. Especially if I needed many of them. For example, a sculpture that I left in a gallery for months. Probably anything that doesn't use a multimedia computer in it's normal running is a good Arduino application.

MCK is good with motors. It's faster. If I were building an instrument that I performed with, I think I'd go this way.

mz

Arduino is definitely the place to start due to the massive user-base. Probably people in your program will have experience with it. Since your'e just starting, I would recommend buying the cheapest Arduino board you can find and upgrading later according to the requirements of your project.

Arduino Pro Mini from SparkFun or the Teensy (google it) are good places to start, and they're more convenient than the bigger boards because they fit right into a breadboard. They're also not so much less capable. The Teensy has 12 analog inputs, for instance.

I use both, arduino and Make controller.
I use the arduino for standalone installations, i.e. without a computer. And I use the Make Controller when I need to interface Max with actuators (like servos, valves, motors) because it's much faster to develop (no need to build or buy shields to drive higher current, get ethernet, etc.), and has built-in ethernet.

I never tried to change the Make Controller firmware, but it is quite easy to program the arduino (as long has you have some experience in programming), although I max out the RAM very easily.

So far I never had any problem with both hardwares.

It's true Make's documentation is not optimal (especially because it's only online) but it's OK. The forum is indeed not always fresh, but aren't forums generally mostly filled with complains.

p

There is also a materiel fantasy of interfaceZ that I use for my machines http://www.interface-z.com/produits/index.htm

Hello all,

Thanks for the excellent input! After reading books and scouring the web until my eyes were ready to bleed... I decided to get a Make Controller. I'll probably end up getting an Arduino at some point anyway. :-) I just really like the built in Ethernet and use of OSC to pass data... Seems super slick and easy to me. I usually end up pushing hardware to the limits so I thought I'd get something a little more powerful to start with as well. Thanks again for the input!!!

David

I've found the difference between the way engineers make purchases and the way artists make purchases quite interesting.

The Engineering Way:
Determine your exact needs in advance and buy parts that meet or exceed your needs only by a calculated margin (~25%).

The Artist Way:
Minimize shopping time by making the most versatile purchase possible initially.

The problem with the Artist Way is that you almost always end up overspending or buying something that is overkill (e.g. too large or too expensive to experiment with). The problem with the Engineering Way is that it does not facilitate experimentation.

The artist experimenting with physical computing should strike a balance between the two Ways.

@morgan,

Yeah, it may be overkill, and it wasn't the cheapest choice... But I studied hard before choosing. Indeed finding the balance was key, and very hard!

I chose the Make b/c:
1) I liked OSC control that's the core of the Make system so I can bypass programming the board as much as possible. I'm an experienced programmer, but I'd rather deal with things in languages I already know like Flash AS3, Perl, Python, Max than learning a new language to program a board directly. And the OSC commands make the use of so many different languages so easy!
2) I really didn't want to have a computer tethered to a controller via USB. I know I could add an ethernet board to an Arduino but it seemed more involved with programming again whereas the Make has it built in with tools for Mac/Win, AS3, Max, etc. Plus it seems even more complicated adding Ethernet to an Arduino Mega. I'll also want to interface with everything via the web. And the cost seemed to be somewhat comparable once you add Ethernet to an Arduino.
3) I based my choices on the current project I'm working on, but I did certainly double the capacity of what I'll need to leave room for future projects with more complexity. I'm a total nerd and as this may not be appropriate for a typical student that's just taking a semester class or something, I'm in it for the long haul. I've been a technologist for 10+ years so I just know I'll outgrow current needs very quickly once I have my head around the basics.

I'd love to continue to hear input on this subject. As a technologist/artist, the hardest part so far in getting involved has been choosing the controller b/c so much depends upon it as the brain/bridge to the computer. If I feel a bit overwhelmed in choosing as an experienced programmer, I'm sure many artists with no technical background find it to be an almost insurmountable wall!

Thx to everyone again! :-)

just bumping this very interesting Topic, thanks guys

should be a Sticky