The ioio is a controller board with USB host and a firmware designed to 
communication with android devices (the android devices work as usb devices 
in this case). I.e. the ioio is kind of a replacement for android accessory 
boards that works with android >= 1.6 (?) while android accessories need 
android >= 3.1(?).

Arduino boards typically have a usb device connector (this depends on the 
concrete arduino variant). As such, it can only communicate with USB host 
devices, i.e. not with all android devices. I'm also not aware of android 
software to communicate with arduino via USB. 

So for an arduino solution, you need either an USB host shield (in that 
case, you  <?fromgroups#%21forum/ioio-users>would have to write something 
like the firmware oand the android lib of the ioio yourself) or bluetooth 
(see e.g. http://www.amarino-toolkit.net). The latency via bluetooth will 
be significantly higher than via usb, which may be problem depending on 
your application.

Normally, I would recommend to use the ioio. However, I don't know if your 
project has requirements that would change this recommendation.

You may ask further questions on the ioio user list 
https://groups.google.com/forum/?fromgroups#!forum/ioio-users<?fromgroups#%21forum/ioio-users>.
 
It seems more appropriate than this list. Ytai, the developer behind the 
ioio, is very active on that list and provides great support.

The ioio docu lives at https://github.com/ytai/ioio/wiki


Am Samstag, 24. März 2012 03:45:08 UTC+1 schrieb James Cardona:
>
> how I can communicate two IO-IO card, controlled by Android. 
>
> And if android vs arduino communication is better than IO-IO vs 
> android 
>
> thanks

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Reply via email to