1. This format is not easy to read. Consider posting a schematic.
2. Connect pin 8 of the driver to Vin rather than 5V.
3. Use a smaller breadboard or a perf board. Alternatively, there are motor
driver breakout boards from various vendors (e.g. pololou, sparkfun) that
you can wire to the IOIO
Don't worry about those projects. Only the projects that get packaged in
the software release bundle are actively maintained in good shape.
On Feb 18, 2015 6:11 PM, clay_shooter jfree...@freemansoft.com wrote:
I just pulled down a fresh copy latest from GitHub to a clean workspace.
It looks
Thanos, Tux is right, PWMing the motors at 50Hz is not a good idea.
Measuring the voltage across the motors can be done using a voltmeter.
Since the IOIO doesn't work now, I would advise you as a first step to
disconnect as much as you can from it, plug it into a PC and see if the
power LED turns
On Fri, Feb 13, 2015 at 1:56 PM, Artur K kvach...@gmail.com wrote:
Thx for ur help. Are there any more options to upgrade firmware?
The other option is a second IOIO or a PIC programmer (e.g. PICKit3).
I don`t have any android 4.1 :(. I tried to install android 4.0.3 in
virtual box, but I
Would you post your code? Also, why do your IOIOs fail? And in what way?
How are you powering them? What are you connecting to them?
On Wed, Feb 11, 2015 at 8:24 AM, ryan mcaloney rmcalo...@gmail.com wrote:
im trying to make an app with at least 2 radio groups with 3 radio
buttons each to
1. The 12V cigarette lighter outlet of cars is often unregulated and can
jump to 100V or so during ignition. You really don't want to connect your
IOIO directly there... Use a regulator that is designed to be plugged in to
a lighter jack.
2. MicroUSB connector coming off is often a
IOIO Android apps are just normal Android apps, so you can do from them
anything that you can do with Android, such as GUI, internal sensors,
Internet, etc. Of it wasn't for that, there wouldn't be a big difference
between using a IOIO and using an Arduino in terms of what you can do.
For anything
Welcome!
Have you seen any of the existing tutorials?
https://www.sparkfun.com/tutorials/280
http://www.jayconsystems.com/tutorial/ioiobeg/
They are both slightly outdated, but for the most part have the procedure.
On Mon, Feb 9, 2015 at 3:23 AM, Rahtak Channel قناة راحتك
Show me what you're doing step by step. Start only with IOIOLibAndroid.
On Feb 8, 2015 5:14 AM, joe el khoury elkhou...@gmail.com wrote:
Ytai!! Dude, Is it that much hard to import ioio libraries and projects!!
I am a mechanical engineering student and I want to use ioio!! I spent days
just
!! I tried to
download a different ioio projects but they are all the same !!!
without IOIOLibAndroid
On Sun, Feb 8, 2015 at 10:33 PM, Ytai Ben-Tsvi yta...@gmail.com wrote:
Not IOIOLibAndroid*Device*, but IOIOLibAndroid. Point your Browse...
box to the root directory where you extracted
Can you please read my questions more carefully? I requested that you
import only IOIOLibAndroid and send a screenshot of the project import
screen.
On Feb 8, 2015 11:25 AM, joe el khoury elkhou...@gmail.com wrote:
I tried IOIOLibAndroidDevice , I got the same errors!!! :( I don't know a
lot in
Not IOIOLibAndroid*Device*, but IOIOLibAndroid. Point your Browse... box
to the root directory where you extracted the software bundle.
Please close (or delete) all the other projects from Eclipse while you're
resolving that, or otherwise they'll just add too much noise.
On Sun, Feb 8, 2015 at
Can you send a screenshot of what the import project dialog looked like
when you imported?
On Feb 8, 2015 11:09 AM, joe el khoury elkhou...@gmail.com wrote:
Dear!! First, I clicked file-import-general-existing projects into
workspace-next-select root directory browse ioio file
Joe, when you import into eclipse you get a dialog window asking you to
severely the project. Fill in what you normally do and before clicking OK
send me a screenshot.
On Feb 8, 2015 11:38 AM, joe el khoury elkhou...@gmail.com wrote:
Unzipped and zipped files
--
You received this message
On Sat, Feb 7, 2015 at 3:41 PM, Artur K kvach...@gmail.com wrote:
Hello. I`m very newbie of this device, I have tried to get some info on
github wiki of IOIO, but so many topics crosses with newer version of
board, so it`s difficult enough to do.
Firstly, I`m not sure which version I have. I
You happen to be one of the select few that have the most ancient version
of the bootloader, the one that has been later found to be broken:
http://ytai-mer.blogspot.com/2011/07/ioio-manager-unleashes-power-of.html
In short, you'd (temporarily) need a second IOIO or a PIC programmer to
upgrade
Some links, courtesy of Google Search:
http://www.dash.co.il/index.php?route=product/productproduct_id=2511
https://www.4project.co.il/product/ioio-otg
http://www.or-e.co.il/ioio-otg.html
Ordering from Seeed might save you some $$$, on expense of some longer
shipping time.
On Wed, Feb 4, 2015 at
Most adapters work. Here's a partial list:
https://github.com/ytai/ioio/wiki/Supported-Bluetooth-Dongles
On Wed, Feb 4, 2015 at 10:22 AM, Frank Li frank...@machinetelemetry.com
wrote:
Thanks a lot!! Now it is working !! I spent one and half day trying to fix
this. I guess the upgrade did not
Did the upgrade (write) succeed? If so, disable USB debugging and connect
the IOIO to your phone. Let it launch the HelloIOIO app. If it does work,
connect the phone to your PC, enable USB debugging and examine the app's
logcat output. Let me know what the IOIO-related messages are there.
BTW, are
Yes
On Feb 4, 2015 2:28 PM, Frank Li frank...@machinetelemetry.com wrote:
Sorry I am still a little bit confused. If the adapter works, does it mean
that all we need to do is to plug it in ioio, and then we can find and
pair it by phone or lapto?
--
You received this message because you
You cannot (easily). Either they work or they don't. Most do.
On Feb 4, 2015 2:08 PM, Frank Li frank...@machinetelemetry.com wrote:
I am just wondering for some adapters, we need to install drivers to make
it work. How can I install drivers on ioio?
Thanks
--
You received this message
Did you upgrade to the latest?
On Feb 4, 2015 7:45 AM, Frank Li frank...@machinetelemetry.com wrote:
I finally get the ioio working on another phone( Samsung s3 android 4.4 2)
but it still does not work for Motorola XT 1064 (Android 4.4.4). Any
suggestions?
--
You received this message
Make sure the little trim pot for current limiting on the IOIO is fully
clockwise.
On Feb 4, 2015 2:29 PM, Ytai Ben-Tsvi yta...@gmail.com wrote:
Yes
On Feb 4, 2015 2:28 PM, Frank Li frank...@machinetelemetry.com wrote:
Sorry I am still a little bit confused. If the adapter works, does
I recommend that you upgrade both the firmware and IOIOLib to the latest
and try again.
On Feb 4, 2015 7:27 AM, Frank Li frank...@machinetelemetry.com wrote:
Thanks for the reply. After I disabled the USB debugging and connected the
phone to ioio, the hello ioio app pumped out, but the yellow
Thanks for doing this work and sharing your results.
I really prefer not to push workarounds for problems that are not fully
understood. Specifically I would prefer workarounds only once it is decided
that a problem is out of our control to fix proper.
What might be helpful is to open a bug (on
Lower frequency means bigger and more expensive passives. The high
frequency *should* work if done properly. I would like to understand what
I've done wrong. Your catch of the missing capacitor is a promising
candidate.
I haven't tried to analyze failed parts - it is a good idea and I'll do it.
I
Using the IOIO as a barebone PIC24+USB dev board is very plausible (I'm
doing it all the time).
Programming in Java is not trivial. There was an attempt by someone to port
uJava on to it with some rudimentary bootstrapping of some of the I/O
functionality to be accessible. In general this doesn't
Disable USB debugging when running your app. IOIO over ADB only works with
Android 4.2.2. Above that you have to use OpenAccessory.
On Tue, Feb 3, 2015 at 2:54 PM, Frank Li frank...@machinetelemetry.com
wrote:
I just bought a new ioio-OTG. I can not run hello ioio. I updated the
firmware to
PICs are typically programmed in C (assembly is another option). MPLABX is
the name of the (free) development environment offered by Microchip for
this purpose.
The standard firmware that you are used to using is merely one such
application. The IOIO bootloader can be used for installing such
Alternatively, you can use a v3.x version of IOIOLib.
On Feb 2, 2015 8:14 AM, Ytai Ben-Tsvi yta...@gmail.com wrote:
It's all on GitHub. I thought it's been agreed that you can do everything
you need with the stock firmware, but up to you...
On Feb 2, 2015 8:12 AM, Vincent Nadon vincent.nadon
It's all on GitHub. I thought it's been agreed that you can do everything
you need with the stock firmware, but up to you...
On Feb 2, 2015 8:12 AM, Vincent Nadon vincent.nadon@gmail.com wrote:
I think I have to consider myself more of a IOIO developer than a IOIO
user ;)
I have an
If you want my honest opinion, I have a good guess that converting your
code to Java would be way easier than the way you're approaching it. It
will also have the benefit of being able to upgrade the firmware and
IOIOLib very easily in the future without having to port the code.
If you're
Just a wild guess: people often forget to click the raw link when
downloading files from Github, resulting in your .jar file actually
containing HTML or something.
On Sat, Jan 31, 2015 at 9:58 AM, Marouane M marouan...@gmail.com wrote:
I downlaoded App-IOIO05045 but I do not have a .jar file
), but it doesn't
trigger any AOA activity, so I can't debug that.
I'd be interested in having some polling of state, rather than be event
driven, so that's the type of change I'd like to pursue.
- Paul
On Wed, Jan 21, 2015 at 12:11 AM, Ytai Ben-Tsvi yta...@gmail.com wrote:
I don't think Tim's
Are you aware of the fact that you're using the IOIO in a way that is very
different from its intended usage? If this is unintentional, better read
the wiki. Otherwise, in order to help you I need some context and
specifically, what you're trying to do, how you were thinking about doing
it and why
This is still under investigation. The problem has now been narrowed down
to be related to switching high loads when the input voltage is high. A
solution has not yet been found.
If you're curious about the progress, you can track my post on the TI forum
here:
Many apps offer some interface for programmatic control, such as Intents. I
don't think there's a generic way to control an app programmatically.
On Jan 25, 2015 6:56 AM, joe el khoury elkhou...@gmail.com wrote:
Hi dear!! Can I control any android app (let's say google translator) from
google
Look at the preprocessor definitions for each configuration to see what the
differences are. Essentially, what you're seeing is that some
configurations have reduced functionality in order to decease the code size
of the bootloader, which doesn't need everything. The app always uses the
fully
What I'm mostly interested is the library refactoring (making the shared
code a separate library), followed by Gradle files and AS project files for
each, followed by Maven packages (or equivalent).
It is important to keep code compatibility with existing apps, so a package
name change in this
OK, great! Let me know if there's anything else I can help with.
On Jan 21, 2015 11:07 AM, bourdonn...@gmail.com wrote:
Thanks for your prompt reply;
So I'm going to pretend i did NOT swap ADD0 and ALT pins on the sensor.
After much, pain - (I broke my whole dev environment updating sdk and
Ben-Tsvi yta...@gmail.com
wrote:
I do see this. I don't know if this is fixable. To the best of my
knowledge this is a bug with Android, where the disconnect event doesn't
get generated in this case. There may or may not be a workaround. Maybe
just polling periodically instead of relying
So what you're experiencing is proper enumeration and then losing of the
connection as soon as you're actually trying to talk to it, or does the
connection drop on its own regardless?
On Tue, Jan 20, 2015 at 8:47 PM, Denis Torres denis.tor...@gmail.com
wrote:
Same issue here. Ubuntu 14.04.
Your intuition is correct, this is how it is done indeed.
In practice you'd typically have a loop running at some fixed rate,
comparable to the PWM frequency, which would repeatedly tell the servo arm
where to be. If you want it to move slowly, the value will only change a
little between two
There's no reason why it shouldn't be possible. I don't currently have any
plans of doing so, though.
On Thu, Jan 15, 2015 at 11:15 PM, Al B cagiva...@gmail.com wrote:
Will it be possible to incorporate an on-board Bluetooth LE chip (BLE 4.0)
like the Bluno Nano so an external dongle or
I'm likely not attending this year :(
Will make a comeback on 2016 with an additional toddler in my family :)
On Jan 16, 2015 10:27 AM, Al B cagiva...@gmail.com wrote:
Is there anyone from this group participating at MakerFaire Bay Area this
year?
15, 2015 at 9:21 PM, Ytai Ben-Tsvi yta...@gmail.com wrote:
Paul, you are probably using a linear regulator, which is inefficient by
design (it reduces the voltage by burning the difference as heat.
Andries, sounds to me like your external 5V regulator is unstable.
On Thu, Jan 15, 2015 at 6:03
Paul, you are probably using a linear regulator, which is inefficient by
design (it reduces the voltage by burning the difference as heat.
Andries, sounds to me like your external 5V regulator is unstable.
On Thu, Jan 15, 2015 at 6:03 AM, Paul McMahon paul.mcmaho...@gmail.com
wrote:
Yes, I was
The easiest way to get a click event from the button is by registering an
OnClick listener:
http://developer.android.com/reference/android/view/View.html#setOnClickListener(android.view.View.OnClickListener)
Then, your handler should probably send the motor command. Unless you
specify how your
If this is an Android = 4.2.2:
- Make sure USB debugging is *off*. Does the Open Accessory dialog
pop-up when the IOIO is connected?
Otherwise:
- Make sure USB debugging is *on*. Does the USB debugging icon pop-up
when the IOIO is connected?
Keep in mind that this is independent of
I do see this. I don't know if this is fixable. To the best of my knowledge
this is a bug with Android, where the disconnect event doesn't get
generated in this case. There may or may not be a workaround. Maybe just
polling periodically instead of relying on the event system.
On Thu, Jan 15, 2015
It doesn't seem from your description that you're talking about an unstable
connection, but rather a failure to connect.
It is most likely something with your app. Start with the pre-compiled
HelloIOIO.apk, taken from the correct version of the software bundle
(ideally, v5). If that works, try
Is been working for months now
On Jan 14, 2015 5:17 PM, Tim Frisch tjfri...@gmail.com wrote:
Our of curiosity; was anything ever implemented to enable support as IOIO
as a device for AOA?
On Friday, June 7, 2013 at 10:00:39 PM UTC-5, Ytai wrote:
To be accurate, the host is responsible for
The role is determined by the cable. Whomever has the B side is the
device, and whomever the A side is the host. So make sure your B side
is on the IOIO. Otherwise, you'd have to compile your app with the
IOIOLibAndroidDevice library and add a bunch of manifest boilerplate. See
HelloIOIO as an
Yes, it is.
On Wed, Jan 14, 2015 at 8:38 AM, Thanos Fisherman psari...@gmail.com
wrote:
Hey,
Is this possible nowadays using the current software?
--
You received this message because you are subscribed to the Google Groups
ioio-users group.
To unsubscribe from this group and stop
I've never encountered this problem. When this happens, what happens if you
don't power-cycle, but rather disconnect and reconnect USB?
On Mon, Jan 12, 2015 at 9:12 PM, Andries Kruger andriesk...@gmail.com
wrote:
Thanks for the reply, I'll make use of an external regulator then for the
time
The issue is still under investigation. If you're curious, here's the
thread I've been keeping with TI engineers to try to resolve it:
http://e2e.ti.com/support/power_management/non-isolated_dcdc/f/196/p/390774/1379558#1379558.
The issue is now believe to be more associated with load (output)
I don't have it. You could look into generating it based on the eagle
files. I think there are tools that can do it, at least partially.
On Jan 9, 2015 3:11 PM, Sarp Akal sarpa...@gmail.com wrote:
Hi Ytai,
Could you supply IOIO-OTG 3D model (as .step, .iges)?
Thanks,
--
You received this
Awesome project! Thanks for sharing. If you ever document it somehow please
share the links.
On Jan 10, 2015 6:31 AM, JP jp.surfe...@gmail.com wrote:
Dear Ytai and all other IOIO developers,
Just thought that I would give a brief status update on this.
A couple of years ago I developed an
Glad to hear! Enjoy.
On Jan 9, 2015 11:26 AM, Cesar Quiroz cesar...@gmail.com wrote:
Hi, Ytai, thank you for you assistence!
I got it to update the code and I'm using 3 ultrasonic sensor coupled on
the wheelchair.
The problem was the CLASS used and I needed to update class Looper
extends
There aren't any debug steps as this is currently the intended behavior. It
is indeed inconvenient in some cases, but I couldn't find a better way to
make the same firmware automatically detect the right mode and use it.
Anyway, this isn't really a catch 22. You have several options for online
Is this question related to the visual basic library? If so, they have a
separate making list where there are more likely to be people who can help.
On Jan 10, 2015 8:39 AM, Paulo Gomes psapg2...@gmail.com wrote:
Am I right to say that pulsewidth_done is only triggered if exception
occurs?
--
This probably has to do with the way your project is set up. Make sure to
depend on the IOIOLibAccessory library project and carefully compare your
AndroidManifest.xml and your project.properties file to those of HelloIOIO.
On Sat, Jan 10, 2015 at 10:08 AM, Paul McMahon paul.mcmaho...@gmail.com
On Fri, Jan 9, 2015 at 1:02 AM, heikki.wa...@kolumbus.fi wrote:
Hi !
I have IOIO board where the VREG is damaged, so it cannot be powered
normally (5-15V through VREG). As Ytai suggested it can be powered directly
through 5V pin. If I have 7.4V Lipo battery, is it ok to connect it to this
5V
1. AFAIK, popping the accessory dialog when an accessory connects is an
Android thing that cannot be disabled. The only way to avoid that is that
the user defined an app to be the default app for this accessory, in which
case the app will get automatically launched whenever the
The simplest way to achieve that would be along the lines of the code you
sent originally.
On Thu, Jan 8, 2015 at 12:25 PM, Cesar Quiroz cesar...@gmail.com wrote:
Thanks for Help!
I bought more three sensors model SRF05 and i can trying to program.
But i don't know that's happening with the
I think this is an inherent problem with Android, where it is apparently
impossible to register the connection event (Intent) with a Service through
the manifest file. If you find a solution to that problem, I would happily
include it. Otherwise, perhaps it would be possible to
modify
We're talking about connecting to a PC right? Can you describe what's not
working? Is the IOIO enumerated as a USB device?
Is the power LED on when connecting? Does it work in bootloader mode?
Otherwise have you tried a configuration wipe?
On Jan 8, 2015 12:59 AM, Abdou airs...@gmail.com wrote:
Sounds like you did the wiping correctly. The calibration procedure is very
short, so it is probably indeed happening. If you want to verify, replace
your Connect IOIO stage with Power IOIO (not over USB) and observe the
LED blinking rapidly to indicate un-calibrated state until connected to a
USB
So, if I understand correctly, what you're asking is not how to use more
than one sensor, but rather how to use the URM37. Is that right? If so, I
first recommend that you start with the simplest setup, containing ONLY ONE
URM37 and nothing more.
According to this page
Hey Chard, is this still relevant to you?
On Sun, Dec 21, 2014 at 10:32 AM, Ytai Ben-Tsvi yta...@gmail.com wrote:
I haven't forgotten about you, just letting you know that the diagnosis
will have to wait until after the holidays (New Year's).
However, with two IOIOs you should be able
In response to the original question: I'm actively in pursuit of a *pretty
rare* failure mode causing the 5V voltage regulator on the IOIO to fail
permanently. Hopefully I will be able to get down to the root cause of this
and find a fix that will make it to the next revision. In the meantime, I'm
Indeed, Android 4.2.2 introduced a change in the ADB protocol for security
purposes which broke compatibility with the IOIO. Since Android 4 and up
all support AOA, I've never bothered changing the ADB implementation on the
IOIO to support the new protocol. So what you're seeing is the normal
Have you tried mounting the phone in the intended place and using the
mirror trick to change the point of view? Might be mechanically simpler
than pivoting the entire phone.
On Fri, Jan 2, 2015 at 5:08 PM, Bill Carter a11yra...@gmail.com wrote:
Yes that is the app, thanks. I have a version of
I don't know of a better way to define this setting in the project. What
you did is how I would do it. And soon we'd need to learn the AS-way of
doing it :) But you got a little taste of why the JAR way discussed on
the other thread wouldn't cut it.
I don't know anything specific about the new
Added a paragraph on the page. Thanks for the feedback!
On Fri, Jan 2, 2015 at 1:22 AM, Ben b.marcha...@gmail.com wrote:
Beginner mistake :-)
But since IOIO is for beginners like me, why not adding a little comment
on that in the documentation (https://github.com/ytai/ioio/wiki/UART)?
You'd surely need custom firmware for the IOIO to do that.
Also, since POV devices have such harsh mechanical constraints, I would
probably use a board that is smaller for that purpose, most likely a board
custom-designed for that purpose. I actually made one at one point (which I
never completed,
Only semi-relevant to the original question, but I have an Android watch
that I've been wanting to check the IOIO with. It does not have a camera
nor USB but otherwise seems to have a bona-fide Android running on it (can
work completely standalone from a phone) that *should* be able to run the
Yes, hooking up the transmit line (tx) from the IOIO to the receive line
(rx) of the device is the common way to connect. Luckily, you haven't
caused any damage while doing it wrong initially.
On Dec 30, 2014 2:37 PM, Ben b.marcha...@gmail.com wrote:
Hello,
Back from holiday break. Well I have
The initial pulse width is also set in ticks, so multiply the value by 2 in
your case.
Channels in your case are the 4 different ESC.
The rest of what you wrote is correct.
Just had a thought:
Why are you even bothering with the sequencer as opposed to using 4
PwmOutput? The latter has a much
Inline
On Dec 25, 2014 1:27 AM, cont...@claudiumurariu.net wrote:
Hi Ytai,
Well, will try to go your approach. Most of the program you see there is
from open source projects we tried to patch together, but by now we should
be able to do a simple program that does as you suggest.
A few
First and most important, I think the way you're approaching debugging is
inefficient. You're using a long program where a lot of things can go wrong
to bring up some very low level functionality. A more effective approach
would be to write a very simple program to exercise one ESC and make sure
Could you have swapped Tx and Rx?
Also, the adding of all digits seems wrong (I know this is the same as the
app note too, but it looks wrong there as well). Anyway, this isn't your
problem right now since you don't even get there.
I would temporarily replace the entire loop() with a simple
I used wire wrap a couple of decades ago. Nowadays my usual choices are one
of:
- Solderless breadboard for initial experimentation of temporary one-offs.
- Home etched PCB for simple circuits in small quantities.
- OSHPark for more complicated circuits or larger quantities.
The main cons of wire
A simple starting point would be to use a matched IR transmitter/receiver
pair of the kind that modulates/demodulates its signal using a 38KHz or so
carrier, such as the ones used for IR remote control. Those provide pretty
good nose immunity. Then, modulate a low rate UART over this carrier and
Looking forward to videos!
Too bad Santa doesn't visit my kind :) I'm making up for this with friends
in the silicon valley...
On Dec 24, 2014 11:32 PM, noros nicolasyo...@gmail.com wrote:
Thanks Ytai.
It is a fun robot to drive around...really nimble.
And controlling it is really easy using
I'm not familiar with such a tutorial except the information on the IOIO
wiki. How about you share your circuit, which sensor you're using and the
relevant piece of your code and I'll try to help.
On Dec 23, 2014 3:14 PM, Ben b.marcha...@gmail.com wrote:
Hello,
Since 2 days I am struggling
The multiplication by 2 is only valid for the 2MHz case, where each tick is
half a microsecond or each 2 ticks are one microsecond.
The ESC is likely not arming as result of sending the wrong pulse width.
Your example doesn't show how you set the pulse width. Also, you seem to be
setting the
Is it possible that you're confusing the motor (output) PWM rate with the
control (input) PWM?
Hobby ESC are almost universally 50Hz (20ms) input.
You also used the wrong type of PWM channel and fed the pulse width in
microseconds instead of ticks.
So I imagine you should need something like:
That is one hell of a build you got there! Love the details you go into in
the documentation too.
Congratulations on your great work and please share some videos and/or
details about the competition when the time comes.
Don't know whether or not Tango support AOA. I see no reason why it
wouldn't.
I haven't forgotten about you, just letting you know that the diagnosis
will have to wait until after the holidays (New Year's).
However, with two IOIOs you should be able to upgrade your firmware
irrespective of the bootloader as per
https://github.com/ytai/ioio/wiki/The-IOIO-Manager-Application.
Google for botiful and you'll see an example for one way to connect IOIO
with Skype.
There is nothing specific here about the combination of Skype and IOIO.
Supposedly, Skype has some API allowing developers to write extensions,
where such an extension on the Android side may interact with a IOIO.
.
I can try to debug this further and get back to the group.
Mark.
On Tue, Dec 16, 2014 at 11:48 PM, Ytai Ben-Tsvi yta...@gmail.com wrote:
The protocol limits the write size to 256 and read size to 255. The
hardware buffers are 256 for writing (4 byte overhead for each transaction)
and 128
Hey IOIOers,
Finally, Android Studio is the officially recommended IDE for Android
projects and Gradle is the recommended build system.
From the reading I've done, it seems like there is potentially a lot of
improvement in the user experience and simplicity of getting started.
Personally, I'm new
!!
On 11 Dec 2014 20:38, joe el khoury elkhou...@gmail.com wrote:
Man!! Nothing works!!! I appreciate your help!!! I removed the broken
files and I readded the libraries but nothing works!!
On 11 Dec 2014 19:07, Ytai Ben-Tsvi yta...@gmail.com wrote:
You don't need any of these projects
It seems to me like the process is still running. How are you launching
from Eclipse? What is the console output you're seeing? How are you
quitting the program?
On Mon, Dec 8, 2014 at 10:50 AM, Vic Wintriss g...@san.rr.com wrote:
Based on your comment, I find that…after restarting the
Sorry for the late reply.
Multi-device support is advertised as being possibly flaky. To the best of
my knowledge from experimenting with this shortly after developing BT
support, the problems are inherent in the Android's BT stack, which is out
of our control. What I've seen is that on some
Absolutely! See the wiki page about using the IOIO with a PC. This works
both over USB or Bluetooth. The old IOIO version will do just Bluetooth.
Raspberry Pis and Beaglebones running Linux are also supported.
On Dec 4, 2014 10:50 AM, Vic Wintriss g...@san.rr.com wrote:
I would like to set up a
With the standard firmware you need *either* and Android *or* a PC to be
connected at all time you want the IOIO to work.
With custom firmware you can do whatever you want, but that would not
typically be in Java. There was some work done in the past by someone to
port uJava (a minimal JVM) to the
/Devices-With-USB-OTG-Host-Mode-Support
Feel free to add to it!
Thanks,
Mark.
On Mon, Nov 24, 2014 at 11:54 PM, Ytai Ben-Tsvi yta...@gmail.com wrote:
The important thing is that on the side of the cable that goes into the
Android, the USBID pin is shorted to the GND pin, which is what tells
It is not possible for it to blink when the Android (or PC) is disconnected
using the standard firmware.
On Tue, Nov 25, 2014, 02:30 Javier Soriano javi4...@gmail.com wrote:
So, it's not possible that the yellow led of the IOIO OTG can blink with
the standard firmware?
Thanks!
El martes,
401 - 500 of 941 matches
Mail list logo
