It does sound like a fried switcher, causing a low impedance path between
5V and ground. This is likely causing your 5V rail to sag, so it might
explain why your Android won't connect. One way to hack around this problem
is to desolder the switcher or the inductor. I would first verify this
guess
What is your goal? Do you want to use Processing or Java going forward?
If Processing: your best bet is to try to follow the tutorial verbatim
(i.e. use the SparkFun provided libraries, do everything from within the
Processing IDE, etc.). If you have any problems, SparkFun tech support are
the
Thanks!
As for the ADON thing: I'm reluctant to do something that's specifically
called out to NOT do. Indeed it sucks that the electrical specs don't
mention the stabilization time, although given their sample code and
empirical results, I see no reason to assume that what the current code
does
This has nothing to do with UART. It must likely has more to do with the
basic app structure. I recommend that you start with HelloIOIOService and
evolve it to your own use case. You probably forgot something in the app
event handlers or manifest etc.
On Nov 8, 2015 7:05 PM, "Eric Solomon"
You need a port that's both marked with "P" for being able to use the Pulse
Input module and also surrounded by a circle, which means 5V-tolerant.
On Nov 7, 2015 02:11, "Olli Pyynönen" wrote:
> Hello folks! I've been using IOIO ports for commanding (as output signal)
>
At a minimum (if you only care about running the motor in a single
direction), you'd need a single transistor (typically, a FET). If you want
bidirectional, you'd need an H-bridge driver.
On Fri, Nov 6, 2015 at 1:21 PM, Zvonimir Udovičić
wrote:
> is there a way to control
In the IOIO codebase, there's an app called IOIOTortureTest which uses the
IOIO in a multi-threaded environment. It is a little complicated, though,
so I'm not sure if that's what you're asking for.
What is the actual problem you're having? Can you send some small piece of
code that you're having
The IOIO0021, IOIO0022, IOIO0023, IOIO0030 IDs that you see are platform
versions and not bootloader implementation versions. Below, where it says
Bootloader V4.X, is where there's correspondence to the message you're
reading from the log (IOIO0400 being device bootloader V4.00 in this case).
On
1. This typically happens when something is wrong with your firmware
bundle. Either it is corrupt, or non-existent or whatever.
2. Just power-cycle the IOIO.
On Tue, Oct 27, 2015 at 4:00 AM, Byungha Choi wrote:
> I connect IOIO OTG board to PC and bootloader detected as
Pins 39, 40 are not 5V tolerant. You really shouldn't connect a 5V signal
to them. They may already be damaged at this point.
See this wiki page for information on how to interface the IOIO with 5V
logic:
https://github.com/ytai/ioio/wiki/Digital-IO
Make sure to use 5V tolerant pins for both. You
OK, I got around to reading the datasheet. The 0x3C/0x3D that you're
sending is part of the address. You shouldn't send it. Also, make sure you
check the return value of writeRead() or else you'd be reading garbage.
On Sun, Oct 18, 2015 at 7:34 AM, wrote:
> Yes, I have
Did you remember pull up resistors on the bus?
On Oct 16, 2015 8:50 AM, "Tyler Trombetta" wrote:
> I went back and re-read the data sheet more thoroughly, and it appears I
> was wrong. I just found the example on page 18 that details how to take a
> single measurement.
You need to disable USB debugging for the IOIO to work with Android >= 4.2.2
On Oct 12, 2015 4:54 AM, "Fried panseller" wrote:
> Same thing happens with my Note 2, but that's running 4.0.4 android, so i
> had to lower the SDK to 4.0.3API15
>
> On Monday, 12 October 2015
The alternative would be to use a PIC programmer (or a second IOIO/OTG
acting as one) and reflash a new bootloader+app image on the target IOIO.
Those images are available as "hex bundles" on the Downloads page. This is
essentially the same process they're following during production.
On Tue, Oct
How many pins do you need and what functions?
If you just need GPIO and your timing requirements are not very tight, an
I2C expander is indeed a good solution.
There exist expanders for other functions too, just a matter of what your
requirements are.
On Oct 1, 2015 7:52 AM, "Ailgor Bot"
Thanks for putting it together and for sharing!
I've noticed that you're referring readers to the v5.04 software with your
custom built jars. That is no longer required, since starting at v5.05
everything is already Gradle based and archives are available on Maven
Central. This would also
In the open source community, people very often share their source code
rather than the final artifacts so that people who use it can easily make
any changes they desire, build it to whatever platform they desire using
whatever told they desire.
Building should be very straightforward (it took me
I don't think "cannot be powered" is the right description of the problem
you're having. It is more like they don't charge fast enough to keep up
with the power draw of your specific application (e.g. it might require the
screen to be constantly lit, etc).
There are some tablets that have a
Can you move this out of this thread, preferably to ioio-dev?
On Sep 27, 2015 8:54 PM, "Vic Wintriss" wrote:
> I'm trying to reflash a ioio board with the Pickit 3. How do I determine
> which hardware version ioio board that I have? It seems that PGC and PGD
> goes to
The pot circuit has been introduced to allow limiting the charging current
to the Android, mostly in battery-powered applications, where you don't
want the Android to drain the main battery. Some Androids take is less well
than others, in terms of compromising the connection reliability.
On Tue,
Did your build succeed? What was the output?
On Sep 21, 2015 6:02 AM, "משה חדד" wrote:
> I could not find this file app-debug.apk
>
> --
> You received this message because you are subscribed to the Google Groups
> "ioio-users" group.
> To unsubscribe from this group and
This forum and other IOIO resources generally assume users are familiar
with how to write Android/Java applications, compile them and install them.
You can find more information on those topics online if you need help
(outside the IOIO context).
If you want to quickly download and build the app
In the front page of the link I sent there's a wiring diagram showing you
how to connect the IOIO to the vehicle's motors. Is that what you're asking
about?
On Sat, Sep 19, 2015 at 5:12 AM, משה חדד wrote:
> Yeah that's what I've seen, with this I build the project. But I
Does this help?
https://github.com/akexorcist/IOIO-CameraRobot
On Mon, Sep 14, 2015 at 8:34 AM, משה חדד wrote:
> Hey, I've got to build electronics project. I think the car is powered by
> a smartphone and the car will be a camera (smartphone) and a smartphone
>
Sorry for responding late. In case it matters, the IOIO is potentially
capable of up to 9 single-precision PulseInput, where every pair of single
precision can form a double precision.
For simplicity, I chose to expose this as 3 single + 3 double, but that's
strictly an arbitrary software
A minor firmware release including:
1. A small bug fix for better handling of corruption on UART RX
(handling *valid* input worked OK before the fix).
2. Better handling of oscillator calibration (matters almost exclusively
for manufacturers).
3. Improved reliability of detecting
Have your GUI code expose a setAnalogReading(float value) method, and have
the IOIO code call that method. If there's any requirement in Swing like in
Android) that all GUI operations are done from the same thread, use some
kind of a a communication mechanism (such as a synchronized queue) to send
This forum is not necessarily the best place for general swing questions.
Have you seen this?
https://docs.oracle.com/javase/tutorial/uiswing/components/label.html
Or is your question about how to read the value from the AnalogInput rather
than how to display it?
On Sep 11, 2015 11:24,
Eclipse is deprecated for IOIO. Android studio is now the recommended IDE.
Not quite a step be step guide, but this should get you going:
https://github.com/ytai/ioio/wiki/Building-IOIO-Applications-With-Gradle
On Sep 7, 2015 8:36 AM, "Fried panseller" wrote:
> Hi, I
Not sure what you mean by re-initialized, this sensor doesn't seem to have
any initialization associated with it.
Anyway, if you want the readings to take place in parallel, just create a
separate thread for each sensor and have those threads report their
readings (possibly with timestamps) to a
You're welcome to edit the wiki, I'll appreciate you doing so.
If you're not ready to move, you can use v5.04 of the software bundle,
which is intended for Eclipse. Note, however, that over time bug fixes and
new features will not be backported. Also note that with some effort it is
possible to
Friends, this has been a long journey...
I'm pleased to announce the availability of an easier, better way to build
Android and PC applications using the IOIO. This has been a long overdue on
my side, having been left behind the evolving technology. Starting at the
v5.05 release, which I have
Thanks! This is indeed the correct issue. As a tip to the OP, whenever
things fail, look at the logs which often explain what had happened.
The wiki is not intended to be a rigorous reference documenting every
little feature. The wiki is intended to give the user some general
orientation about how
This has been discussed many times recently.
I've made some fixes in this area which have not yet been released.
However, they are on GitHub master. People have reported these fixes to
work well for them. Make sure you're carefully reviewing how
HelloIOIOService is structured and have your app
Yes. This has been fixed, but not yet released. You can check out the
latest code from the master branch on GitHub for the time being.
On Aug 6, 2015 2:39 AM, Ole Tetzschner ole.tetzsch...@gmail.com wrote:
Hey Ytai
Any progress on this AOA Service-problem? Do you by chance have an updated
-06 16:19 GMT+02:00 Ytai Ben-Tsvi yta...@gmail.com:
Yes. This has been fixed, but not yet released. You can check out the
latest code from the master branch on GitHub for the time being.
On Aug 6, 2015 2:39 AM, Ole Tetzschner ole.tetzsch...@gmail.com
wrote:
Hey Ytai
Any progress on this AOA
Does it have to be Android? Otherwise, you can use a raspberry pi or
similar.
On Aug 4, 2015 3:30 AM, heikki.wa...@kolumbus.fi wrote:
Hello !
I have an IOIO project, where IOIO and an android phone are place in the
mobile vessel, moving on the water. On the land I have an android tablet,
that
If you're anxious to get started and can't wait for an official release,
check out the gradle branch on github. If you run gradle build it will
produce the jars/aars for you and the example applications demonstrate how
you should author your apps as far as integrating with the IOIO libraries.
.
Lo.
Le 22 juil. 2015 à 01:27, Laurent Turnauer laurent.turna...@gmail.com a
écrit :
Ok I’ll try it.
Thanks for advice.
Lo ; )
Le 22 juil. 2015 à 01:25, Ytai Ben-Tsvi yta...@gmail.com a écrit :
Are you able to test with a beefier supply or at least higher voltage? I'm
concerned
I'm not familiar enough with the Arduino library to be sure, but the fact
that you're writing from both handlers is probably wrong. Apparently,
you're receive handler should Wire.read() as many bytes as the argument
specifies, and you should do writes only from the request handler. Also,
how are
There is no such functionality implemented. What are you trying to
accomplish?
On Fri, Jul 31, 2015 at 6:09 AM, Bedri Bahtiyar bilu...@gmail.com wrote:
Hi every one. I'm new in android and ioio ogt board. Is there any way to
reach to internal registers of PIC 24F. For example, if i want to
Thanks!
Can you please send a pull request, explaining clearly what is the observed
problem and what this fix does? I'll be happy to merge it.
On Jul 25, 2015 6:46 AM, Emre gule...@gmail.com wrote:
I forgot to mention that it is for v5.00
--
You received this message because you are
Something like:
IOIOLooper createIOIOLooper(String type, Object extra) {
if (type.equals(ioio.lib.android.bluetooth.BluetoothIOIOConnection)) {
return new MyBluetoothLooper();
} else {
return new MyUsbLooper();
}
}
Where MyBluetoothLooper and MyUsbLooper are two classes you
Yeah, I did develop almost all of this myself. When you're excited about
something time can be found, especially if you're willing to put up with
not sleeping for a while :) In any case, I've been working on the IOIO on
and off for almost 5 years now.
Enjoy!
On Wed, Jul 22, 2015 at 10:30 AM,
This is impossible, at least with the current state of things.
Why do you care that the phone is the host? If the IOIO is the host, it
will charge the Android and communicate with it just as well.
On Tue, Jul 21, 2015 at 6:56 AM, Geerapa Wareerad geevir...@gmail.com
wrote:
Hello Ytai, I'm quite
Could it be that you overloaded one of the lifecycle events on your
activity (e.g. onStop()) and forgot to call the super's method (e.g.
super.onStop())?
There's no reason why what you're describing shouldn't work. I'm doing it
all the time.
On Tue, Jul 21, 2015 at 10:44 AM, Lo
Ben-Tsvi yta...@gmail.com a écrit :
AND is the CHG pot on the IOIO all the way clockwise?
On Tue, Jul 21, 2015 at 4:12 PM, Ytai Ben-Tsvi yta...@gmail.com wrote:
I'm curious to see what you find with the new library. Also, what power
supply are you using? Could we be seeing a dropout resulting
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
AND is the CHG pot on the IOIO all the way clockwise?
On Tue, Jul 21, 2015 at 4:12 PM, Ytai Ben-Tsvi yta...@gmail.com wrote:
I'm curious to see what you find with the new library. Also, what power
supply are you using? Could we be seeing a dropout resulting from a power
dip?
On Tue, Jul 21
Pretty simple, you're using a v5.x software with a v3.x firmware. Upgrade
your firmware as per:
https://github.com/ytai/ioio/wiki/IOIO-OTG-Bootloader-and-IOIODude
On Mon, Jul 20, 2015 at 1:31 AM, R.S. Agwan rsagw...@gmail.com wrote:
Hi all,
I've got a slightly older IOIO-OTG from SparkFun
I don't see how sampling faster is going to improve your accuracy. The
+/-100mA that you're seeing is about you might expect of your current
signal properties and a 10-bit ADC, regardless of sampling rate. In other
words, if the problem you're trying to solve is that of increasing
precision,
That won't do it in our case, as the different buffer slots are used for
different channels rather than consecutive samples of a single channel.
In this point in the code:
https://github.com/ytai/ioio/blob/master/firmware/app_layer_v1/adc.c#L192
the sample value for the i'th channel is obtained.
I think I understand now. So:
1. If you're really intending to measure a signal as high as 30A, the
output voltage will be around 4.5V, which exceeds the range the ADC is
willing to accept (0-3.3V).
2. Unless the sensor has a built-in amplifier, it is likely that it has
a fairly
Before we begin, can you please specify the signal you're trying to measure
better?
Specifically, its min and max (instantaneous) voltage, and its bandwidth
would be important.
Based on that I can recommend a way of measuring it.
On Tue, Jul 14, 2015 at 3:06 PM, Julio Castellanos
I don't understand your setup well enough. Are you connecting over BT or
USB? What's this HDMI you're referring to?
Does pairing work with the phone? With a PC?
The IOIO Hardware Tester app is not my own. I cannot vouch for its
reliability. You can use HelloIOIO.apk if you want to have a reference
I didn't read all the way through. Seems to me like you have at least a
problem with how reading/writing of registers work. I think what you need
is something along the lines of:
byte readRegister(byte index) throws ... {
byte[] request = new byte[] { index };
byte[] response = new byte[1];
There's a page on the wiki listing supported dongles.
On Jul 10, 2015 3:32 PM, shai frenkel zsfren...@gmail.com wrote:
Hi,
I am looking for a recommended Bluetooth dongle for an LG-G3 smartphone. I
bought a broadcom based dongle which shows up at the Bluetooth scanning
phase in the phone as
Two things to look at:
1. Do you see this behavior occurring with the precompiled example
applications? If not, what is different about you app that causes the
problem?
2. There were a bunch of fixes to OpenAccessory mode recently that are not
yet included in the release package, but have been
Thanks for sharing that here. I previously saw the youtube video, but not
the blog post.
Great project! Definitely keep us posted whenever you're adding new
features to it.
On Thu, Jul 2, 2015 at 5:51 PM, Karim Virani pondersom...@gmail.com wrote:
Just wanted to share the chromovore bot project
The IOIO v1 that you have can only be updated using IOIOManager on Android.
IOIO-OTG uses ioiodude and a PC.
Unfortunately, the IOIOManager way only works with Android 4.1. So you'd
need to get one of those if you want to be able to upgrade. An alternative
is to use a second IOIO or a PIC
Your question has actually little to do with the IOIO. The IOIO can
interface mostly any circuit that other microcontrollers can. What you're
really asking is about current sensing.
There are two primary ways to measure current:
- Putting a (shunt) resistor on your current path and measuring
It's fine. What I normally do is pull the control line down to ground and
use the pins in push-pull (normal) mode. Your setup is useful if you want
to operate in open drain mode to generate a 5V signal. In practice, I've
never seen a servo that minds feeding off of a 3.3V control signal. Pulling
UART can operate at any rate that is 4MHz/N, with N being [1..65536].
On Jun 24, 2015 8:53 AM, Glenn gal...@gmail.com wrote:
Hi,
Does the IOIO support non-standard baud rates for UART? I would like to
use the board to connect to my car's serial interface, which is 8192 baud.
Thanks,
Glenn
The next logical step is to try building HelloIOIO from source. Then figure
out what's different in your app. The main things required for IOIO in
device mode support are including the IOIOLibAndroidDevice library and some
manifest declarations.
On Wed, Jun 17, 2015 at 12:23 PM, James Warner
Either run it on a separate thread or interrupt the current thread after
some timeout. Search this forum for TimerTask. Your question has been asked
and answered several times.
On Wed, Jun 17, 2015 at 4:25 PM, James Warner jameswarn...@gmail.com
wrote:
My mistake, It was working, an
Frequencies (Sound Pins) on the IOIO for smoother operation of the Steppers?
On Sat, Jun 13, 2015 at 6:43 PM, Ytai Ben-Tsvi yta...@gmail.com wrote:
How does IOIO Inventor work? Does it have APIs for the motor control
libraries? Is it specifically designed for interacting with AppInventor
I'm not going to answer the AS questions, since as I said this is not yet
completed. You asked for AARs and you got them. If you want more help, use
Eclipse for now.
Regarding debugging, you have several options. The easiest one is using
Bluetooth for the Android : IOIO connection and then USB for
Your question is not very clear. Are you trying to prevent the Android from
drawing power from an external battery? If so, using device mode is indeed
a good solution, if your Android has support for it. If you don't want the
IOIO to use the phone battery, power it externally.
On Thu, Jun 11,
How does IOIO Inventor work? Does it have APIs for the motor control
libraries? Is it specifically designed for interacting with AppInventor?
On Fri, Jun 12, 2015 at 5:50 AM, tommazur...@gmail.com wrote:
Hi all, I am new to this discussion , but saw the post thought I could
contribute my
You need to use a device called relay, which is essentially a (low)
voltage controlled switch.
You're question indicates that you don't have a lot of experience with
electricity, so I would strongly advise against trying to mess with high
voltage yourself. I would imagine there should be relays
up to 80 cm or so, after that I get negative values. Any
suggestions?
Best regards,
Gabor
On Sat, 6 Jun 2015 07:52 Ytai Ben-Tsvi yta...@gmail.com wrote:
I2C is easy. Once you have implemented two near trivial methods, namely:
byte readRegister(byte regnum)
and
void writeRegister(byte
I2C is easy. Once you have implemented two near trivial methods, namely:
byte readRegister(byte regnum)
and
void writeRegister(byte regnum, byte value)
You can forget about I2C and start talking to the chip according to the
information provided in
What is the problem you're facing? And why do you need to program it with a
programmer as opposed to using the pre installed bootloader and programming
over USB?
On Jun 4, 2015 7:24 AM, Dinesh Kumar dineshkumar.smd...@gmail.com wrote:
Hello.,
I am trying to program IOIO-OTG(PIC24FJ256GB206)
mode alone.
while programming IOIO-OTG to PICKIT3 (in programmer to go mode),PICKIT3
shows some error.
Error message:status led blinks red in a pattern like 12 12 12 12..
can u pls explain source for the problem and solution to rectify it?
On 5 June 2015 at 00:35, Ytai Ben-Tsvi yta
How so?
The major version of the firmware always needs to be = major version of
IOIOLib. In your case you're using a v5.x IOIOLib with a v4.x firmware.
On May 29, 2015 3:30 AM, Egbert Boer egbertthe...@gmail.com wrote:
This is pretty self-explaining. Upgrade your firmware... :
ioiolib:
Thanks for sharing that.
I'm actually in the middle of converting everything to Gradle, then adding
AS support and upload packages to Maven, so hopefully your tutorial will
not be needed for much longer.
As for your questions:
- *android app future.usb.usbmanager not found*: you need to use
Can you part a link to said Arduino shield?
On May 27, 2015 8:01 AM, nourIroka nour.92im...@gmail.com wrote:
Hello everyone,
First of all thank you for the amazing board...
I just got the IOIO OTG and a part of my project consists of extracting
data from the vihicule's CAN-BUS and
Thanks for diagnosing this and thanks for making the wiki edit!
In the future, I recommend one of the official vendors (SparkFun or
SeeedStudio), as I can guarantee that their production practices are
excellent and that each individual board gets tested before being shipped.
They are also the only
There was talking about this before, but to the best of my knowledge,
nobody has yet implemented IOIO blocks for AI.
On Mon, May 25, 2015 at 5:26 AM, joe el khoury elkhou...@gmail.com wrote:
Dear Ytai,
Is it possible to use app inventor for IOIO? It may save a lot of time. If
yes, how?
First, there's a udev rule on the Downloads page, just in case you're not
sure about permissions etc.
If you cat or screen the device file, are you getting anything?
Also, have you tried a configuration wipe (see the ioiodude wiki page)?
Last, why would you buy from geeetech when you have a lot
Great! My guess would be that the resistors pull down on the address pins
and up on the alert pin.
On May 23, 2015 14:30, Chris beilbtpen...@gmail.com wrote:
Well yeh i just checked and the smd are not on SCL or SDA thanks ! Now i
see something on the screen ! I just thought that the smd were
Your request should be { 0x00 } and the response is 2 bytes. The actual
transaction will look exactly as in page 17.
Why do you think this module has pull-ups? I haven't found a schematic, but
it is generally a bad practice to include pull-ups with the slave. In other
words, it is likely that you
I'm aware that whether to destroy an activity is at the discretion of the
OS. From the examples you posted it seems like it might be what's making
the difference between being able to reconnect and not being able to
reconnect. If that's indeed the case, I'm wondering what effect the
destroy/create
The ADC (analog to digital converter) works by first briefly charging a
small internal capacitor to the pin voltage, then disconnecting it from the
pin and measuring its voltage. With high impedance on the input, the
internal cap might not fully charge and also any leakage current would
Your original question was slightly misleading. This motor is not a servo,
but a brushless motor. Heikki's answer above is correct. This mostly has
nothing to do with the IOIO. The IOIO-related piece is using a PwmOutput to
generate a 50Hz PWM signal, with the pulse width varying between 1-2ms for
The addresses for this module seem to be 0x78 until 0x7F (depending on the
address selection pins).
You need to always write 1 byte (the address of the register), then read
back two bytes for the register value. The datasheet goes into a lot of
detail on the specifics of I2C, which are all already
A couple of observations:
1. You're passing a 1-byte request to writeRead(), but specify a length
of 2. This should throw an exception, not sure where it gets lost.
2. I recommend checking the return value of writeRead(). When it is
false, it means your device NAK'ed and the response
The method that emits the main activity restarting: what's actually
happening there? Is it possible that some event that needs to propagate to
the IOIO framework doesn't make it through? Looks like the
destroy()/create() sequence is what makes things work. Can you debug a
little and figure out
As fast as possible is not very descriptive. Please specify which events
you want to limit the time between (for example, maximum time between
PWM.setPulseWidth() is called and until the servo arm starts moving) and
how much time you're allowing this to take. Based on that I can come up
with an
With earlier versions of Android, Java 6 want supported. This is no longer
the case.
On May 19, 2015 5:49 PM, webb.jonat...@gmail.com wrote:
I am considering using the IOIO-OTG for a project which will use a JavaFX
GUI on both PC and Android. I have seen on github.com/ytai/ioio/wiki
that
You seem to have omitted the logs generated by IOIOLib itself. Can you
include them? Which version of the library is this? What type of connection
are you using between the Android and IOIO?
On May 19, 2015 2:51 PM, hwut fit...@gmail.com wrote:
Sure, here is a log of the case that causes the
Seems like your voltage regulator is fried. Can you provide some details on
what power supply you're using and how it was connected to the IOIO (i.e.
length of wires, etc.)?
On Mon, May 18, 2015 at 3:28 AM, 'M. A.' via ioio-users
ioio-users@googlegroups.com wrote:
Hello IOIO fans,
I am using
Sorry, I just realized the the Processing stuff doesn't wrap the IOIO Java
API, but just allows direct access. In that case, you should have all the
information you need here:
https://github.com/ytai/ioio/wiki/TWI
On Mon, May 18, 2015 at 10:03 AM, Chris Do beilbtpen...@gmail.com wrote:
Here's
Can you add some logs and figure out the exact sequence of lifecycle calls
(e.g. onStart(), onStop(), etc.) in your scenario? Also include the
relevant IOIO logs so we can see whether a connection is closed properly
before switching.
On Mon, May 18, 2015 at 3:15 PM, Tiffany Hwu fit...@gmail.com
Make sure the A side of the cable is at the IOIO and the B side at the
phone. This will cause the IOIO to act as host. At this point, you should
at least see the phone charging. If it doesn't:
- Check the power supply - should be at least 5V and at least 1A to be
on the safe side.
-
What is the current bootloader / application firmware versions you have on
the board? Hint: if you look at the logs left by any IOIO app if will show
that.
Also: have you carefully read the IOIO Manager wiki page
https://github.com/ytai/ioio/wiki/The-IOIO-Manager-Application?
On Tue, May 12, 2015
Just upgrade the firmware to v5.x. There've been lots of fixes since v3.30,
as well as some cool new features.
On Wed, May 13, 2015 at 8:55 PM, Leonard inextricable...@gmail.com wrote:
Yes, that was it, I needed to downgrade to 3.30. I found a description in
the SparkFun website that said it
This parameter is unrelated to the physical setup. What it means is what is
the path's sampling rate, that is, the drawn curve is gets broken into many
small line segments, connecting the dots that are samples of the path in
regular time intervals. stepTime is those intervals.
On Fri, May 8, 2015
You can try SparkFun tech support. They are the one maintaining the
Processing libraries. I'm not familiar enough with the Processing stuff to
know how exactly it exposes the underlying Javaj-based IOIOLib.
On Mon, May 11, 2015 at 10:50 AM, Chris Do beilbtpen...@gmail.com wrote:
Hello
1. The analog input cannot measure and shouldn't be exposed to higher than
3.3V.
2. If you're using a resistor divider as recommended, I recommend a 1uF or
greater ceramic capacitor in parallel to the low side resistor. Otherwise,
use smaller resistors (like, a couple of kOhm), but that will come
201 - 300 of 941 matches
Mail list logo