If instead of overriding createIOIOLooper() you override createIOIOLooper(...) you'll get two arguments that allow you to distinguish the IOIOs by their connection. The multiple IOIO scenario should work fine. If you're using more than one IOIO over Bluetooth you may run into some flakiness, which I suspect has to do with Android and might have been resolved on recent versions of it.
On Tue, Jul 21, 2015 at 12:43 PM, Eric Rule <[email protected]> wrote: > Hey everyone, I'm trying to control two IOIO boards (latest, > models/firmware) simultaneously, but individually; so I may toggle pins > separately. One board is connected through USB OTG to my phone and the > other through Bluetooth (same phone). > > My question: how can I differentiate between the two IOIO's in my > application? I've read into the IOIO interface and creating an instance for > each board, but I'm a little confused. > > Have any of you successfully controlled two or more IOIO's from one phone? > > Any help is appreciated. > > -- > You received this message because you are subscribed to the Google Groups > "ioio-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/ioio-users. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "ioio-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/ioio-users. For more options, visit https://groups.google.com/d/optout.
