Why Google Choosing Arduino Matters
ptorrone writes "Earlier this week at Google I/O, Google announced the Android Open Accessory kit which uses the open source hardware platform, Arduino. MAKE magazine has an in-depth article about why Google choosing the Arduino matters, why Google picked Arduino and some predictions about what's next for Apple's 'Made for iPod' as well and what Microsoft/Nokia/Skype should do to keep up."
It already existed (an android-arduino "interface"). It only matters because google is behind it now (with an official API), but whoever wanted to do stuff before already could.
A friend recently made a "magnetic core memory" extension board for an Arduino:
http://www.corememoryshield.com/report.html
Just an example (with pictures) of what can be done with these things. (Magnetic core memory was the main form of non-volatile memory for computers from the 50s through to the 70s.)
Expert in software patents or patent law? Contribute to the ESP wiki!
Why are they charging nearly $400 for something that you can buy separately for $200?
Arduino is great, I've got my own, but it seems like the choice you'd make if you were pursuing hobbyists instead of commercial device manufacturers. Am I wrong?
I am seeing the same thing. It started as of today, possibly since mid-afternoon ET, though I couldn't be positive it wasn't happening earlier.
Whoever's maintaining the website is making things worse, not better.
Better would involve loading all comments on a single page, or at least making it an option. Having to click the "get more comments" button a dozen times to make sure I've got all the comments in a subthread is bogus.
Better would be limiting the thread-expand-o-matic to the title bars of articles, instead of anywhere in the body of any article in the thread.
Better would be making edit-boxes expandable, or at least telling them the right way to wrap text.
I see I did not get in before the Arduino haters. Yes, I know, it's a simple board, I understand that it's not a PIC or whatever embedded thing you prefer. I accept that. But it's a nice, easy to use board. It's fun. You can do stuff quickly with it. It's good for quick little things. I'm sorry that us Arduino users don't measure up to your expectations. I'm not going to tell you that you are wrong for your embedded choices. Can I get the same courtesy?
When It Counts.
1. This is also designed for anyone who wants to make money. People/companies who have never touched Arduino in their life may become interested and start developing interesting things. A giant market share can attract a lot of attention.
2. Steve Jobs is currently busy hoping someone will develop an Android/Arduino based liver/pancreas/spleen/who knows what other internal organ replacement and not giving nearly as much time to his dictatorship.
You are lucky, Ed Gruberman. Few novices experience so much of Ti Kwan Leep so soon.
The AtMega (the actual CPU) is too weak to use enough data to load down the cellular network. You couldn't, for example, decompress video with it. So people aren't going to build accessories which let you watch TV over your Android connection.
There's nothing wrong with those parts, but they're for tiny programs.
Don't forget, you can always pull the chip off after you're done testing (replacing any board-specific code with target specific) and burn it into production devices.
There's no reason it needs to stay on the Arduino dev board. It's just so handy that way that few feel the need.
For large sets, this will be our guide even unto death, for the LORD will work for each type of data it is applied to...
Keep in mind that the *any* device that supports USB Host mode can be an Accessory. There's a full open source reference implementation for Arduino, but the protocols are documented and open and you can implement it on any hardware you like.
Docs and Specs: http://accessories.android.com/
Google IO Talk: http://www.youtube.com/watch?v=s7szcpXf2rE
For blog cred
that they say: from android 3.0 on devices are expected to have usb host functionality to get access to the app store and must mandatory implement usb standard protocols to talk to hardware.
advantages:
-standards hubs exist
-Mass storage could be attached
-HID devices could be uses AND the specialized HID devices designed for the use with Android devices could be used with other devices
-Testing of the device could happen easily on your personal computer
-Availability of hundreds of ultra-cheap reference implementations including small microprocessors.
Until they do this: Thanks, i will stay with some arduino bluetooth module. Costs a little extra, but can be attached to anything.
1. This is obviously designed for those who make hardware as a hobby. It's a cool hobby, and every once in a while something that would be useful generally comes out of it, but makers aren't making stuff that the average person wants.
You know what caused the last couple of tech bubbles? The fact that it's really easy to write some software as a hobby, then commercialise it later. Google wants to do the same sort of thing with Android accessories. If 1,000 people make an accessory as a hobby, then one of them may have a really great design. They can then probably get funding to turn it into a shipping product (I imagine that Google has primed some VC funds to do exactly that). Going from working prototype to shipping product is largely a question of having sufficient money to invest.
I am TheRaven on Soylent News
It's a nice idea, but only supporting a usb connection? I've already used an Arduino with a bluetooth module to communicate with my android phone over a BT serial connection, worked rather well.
Just posted here: http://groups.google.com/group/openmanufacturing/browse_thread/thread/8d32987e3767c868#
So, is this going to make an Android phone an important part of a lot of open source hardware projects (including RepRap perhaps)?
Note also: ..."
http://faircompanies.com/diy/view/make-your-own-open-source-android-smartphone/
"Flow DIY is an open source hardware platform so anyone can make a smartphone with the Android operating system and the exact capabilities one is looking for. Its components as well as the final creation by the user are open source, a first step toward the generalization of DIY devices. Interest is growing in personalizing not only software and web applications, but in everyday devices. A legion of DIYers are demanding tools to create increasingly more sophisticated devices.
As I've said elsewhere, with the turnover rate of Smartphones, in two or three years, today's generation of smartphones will be free-as-in-discarded. :-) So, it can make sense to build stuff for them, especially since if they are free-as-in-discarded-beer then they can be free for kids to use for educational things (like instead of the OLPC XO-1). Reference:
http://listcultures.org/pipermail/p2presearch_listcultures.org/2009-November/006250.html
That's one reason I started working on Android software (and under a three-years-and-its-free-under-the-GPL model that I am still conflicted
about).
http://www.artificialscarcity.com/
Still, sadly my Google Developer Smartphone died several after I got it and I never got around to sending it in for replacement, so I guess there is an amount of old phones that will not be usable for similar reasons (but I doubt that will be the majority). Also, as people have pointed out, the Smartphone batteries tend to go, making them less useful as they age (although I guess you could hack in some alternative power if you were motivated).
Still, I'd suggest that if one is making an open manufacturing project that requires computing, integrating an Android Smartphone might be an interesting idea.
A 21st century issue: the irony of technologies of abundance in the hands of those still thinking in terms of scarcity.
The coolest thing about this presentation came right after the stuff about accessories (Video). Google claims that they have "designed an open, wireless protocol" for devices that don't speak WiFi or Bluetooth. This is supposed to enable "very low cost connectivity with anything that's electrical in your home".
A little more detail: link. Seems that it's low speed, which is okay, and that they're using the 900 MHz band which means that sadly it's not going to be for Europe.
The situation with Apple requiring a special chip be purchased and then paying them a fee for each product sold vs the Android open access and anyone can build an accessory to sell reminds me of the early Apple vz IBM days. Apple made all the hardware and software while there were many IBM clones. Due to the more open nature of the connectors and operating systems that run on each PC, the IBM version won out in the end. Apple products have always been praised for being well build and easy to use. I stayed away from them because I wanted to get into guts of whatever I was doing. I felt too restricted on Apple. It's just interesting that this new competiton looks very similar.
-- ssoorrrryy,, dduupplleexx sswwiittcchh oonn.. -Quote found on actual fortune cookie.
Greed?
The tyrant will always find a pretext for his tyranny - Aesop
From TFA:
Oh, please let the answer be "yes". Why should those of us who don't want to be coddled by the Evil Empire be forced to pay an extra $90 for garbage we won't need or use? (Just try and find the non-iPod version for sale - I've looked and I can't find it).
Nathan's blog
More importantly, Apple doesn't have to change their program. If a competitor finds a way to so something cheaper, it makes Apple look like the "premium" product, without having to change anything. Apple has always been able to stay at least a step behind everyone else in terms of features, pricing and flexibility, and instead of hurting them, it's made their brand extremely valuable.
Also, they already have a huge ecosystem of existing accessories... Nobody else even comes recognizably close. With that ecosystem comes recognition in the minds of all consumers.
A common (old) argument against VB was that it was all so abstracted away programmers using it typically really didn't know what on earth they were doing (but it was still useful to those without knowledge of other programming languages). Likewise with the arduino, the comment that it was like vb was not insinuating that it is worthless, only that it is for people who care less about knowing how it really works and simply wish for it to do what it tells it without caring about the details.
Arduino is really the visual basic of the embedded world. But that is not as insulting as it seems on it's face, it is simply a comment on it's level of abstraction.
OK, that's fair. I'll admit to defensiveness after seeing many posts bashing the Arduino.
When It Counts.