Do you have a way to measure voltage? If so, I'd like to see what is the
voltage on the 5V rail while the phone is connected.
I'm pretty much out of ideas. There might be something special about this
phone's OS version or settings which make it misbehave. As I said, this
phone model is a
Inline
On Thu, Mar 27, 2014 at 1:25 PM, Rémy Grandin remy.gran...@gmail.comwrote:
For all my previous test i used the Vin and ground pin and i recently
brought a JST male connector (which by the way was a bit to large for the
jst connector of the IOIO OTG)
I meant what power supply are you
It is possible that this device does not support the USB device API.
I think that even if you have no IOIO application installed, you should see
the USB dialog popping up, but I'm not 100% sure (this is for sure the
behavior in IOIO as host mode).
In either case, try using the pre-compiled
You're in good shape. Try upgrading the firmware to v5.00 and my guess is
that everything will work fine.
On Mar 27, 2014 10:02 PM, Lagz Moncs lagz...@gmail.com wrote:
I tried using the pre-compiled HelloIOIO.apk from v5.03 as you suggested.
It did show a Hello IOIO dialog box. Allow the app
And again:
What do you actually mean by turning the IOIO on and off?
On Wed, Mar 26, 2014 at 6:59 PM, francismusic1984
francismusic1...@gmail.com wrote:
I mean, turn on and off the IOIO by code (if possible of course)
El miércoles, 26 de marzo de 2014 20:48:57 UTC-4, Ytai escribió:
To get Celsius, get rid of the +273.15.
You can connect as many devices as you want on the same I2C bus, as long as
they have distinct addresses. With the SparkFun TMP102, there's a slight
problem that the breakout board has pull-ups on it, so if you connect too
many of those in parallel you'd
Very welcome. Good luck!
On Mar 25, 2014 10:28 AM, Santiago Alfaro titoalf...@gmail.com wrote:
YES!!!
not only that works but it got me much closer to answering some of my long
lingering questions about I2C. I can't keep working on this project until
next week so I might bug you again. but
When the connection between the IOIO and the client (Android / PC) is lost,
all the pins float. You can thus use a pull-up / pull-down resistor on any
pin to give it a default high / low state. There's no need to modify the
firmware I believe.
When you say this would have fried... what do you mean
Can you change ioiodude on the command line to ioiodude.bat?
On Mar 24, 2014 2:39 AM, Shahfiq Nashrah shahfiqnash...@gmail.com wrote:
Hello Ytai, I've updated the latest IOIODude. I also have tested with jre6
and jre7 with same set of commands and the output is still the same.
Other than your weird choice of naming, everything sounds fine.
On Mon, Mar 24, 2014 at 6:23 AM, Marius Vosylius
marius.vosyl...@gmail.comwrote:
Dear Ytai,
Here's what I have so far:
1. My *A0* pin Connected to GND, in this case it means my address is
*0x48* (Please correct me if
It is possible to fry the board with incompatible firmware, for example, if
your firmware is trying to pull a pin low while something else on the
circuit is trying to pull it high, etc.
However, odds are that something else fried your board. There's a notorious
voltage regulator bug that might fry
That seems OK. If I were you I would probably leave the INA226 as a class
and use it from the Looper, but that's mostly a stylistic matter.
On Mon, Mar 24, 2014 at 10:26 AM, Marius Vosylius marius.vosyl...@gmail.com
wrote:
Main Class:
private TwiMaster twi;
private static final byte
Is the battery powering the IOIO also a 2-cell? Is the servo powered by the
5V rail? Can you send a wiring diagram of some sort?
On Mon, Mar 24, 2014 at 10:40 AM, Marius Vosylius marius.vosyl...@gmail.com
wrote:
Im Using 7.4 LiPo Battery for 4WD Motor Module Only.
And Another LiPo Battery
You need to:
1. Power off the IOIO.
2. Bridge boot to GND.
3. Connect the IOIO to the PC. The yellow LED should be on.
4. Remove the bridge. The LED should blink a few times, then turn off.
5. Now the IOIO should be correctly identified.
Is that what you did?
On Mar 24, 2014 11:56 AM, Juan David
What's the current rating on this adapter? Are you seeing similar issues
when using a battery too?
On Mon, Mar 24, 2014 at 12:33 PM, Marius Vosylius marius.vosyl...@gmail.com
wrote:
Sorry it was IR Range module making this noise. For testing Im using 12 V
Adaptor to power mo IOIO.
On
Great work on that, Jordan and all who helped!
From my experience, there are *many many* users that would benefit from
this smoother learning curve into the world of IOIO and Android.
Definitely a milestone for this project. Keep up the good work!
On Mon, Mar 24, 2014 at 1:26 PM, Jordan
Can you send a wiring diagram? A hand-drawn scan would do.
On Mon, Mar 24, 2014 at 1:34 PM, Marius Vosylius
marius.vosyl...@gmail.comwrote:
Using Battery or adapter is the same.
On Monday, March 24, 2014 8:28:20 PM UTC, Ytai wrote:
What's the current rating on this adapter? Are you seeing
Works for me... Things to try:
- Use a different computer.
- Oscillator calibration (configuration wipe, as described on the
IOIODude wiki).
On Mon, Mar 24, 2014 at 1:00 PM, Juan David Bolanos Aguilar
juda901...@gmail.com wrote:
Yes my friend thats what I did!
El lunes, 24 de
It should be periodically called from loop() and the result sent to the UI
widget (TextView).
On Mar 24, 2014 1:45 PM, Marius Vosylius marius.vosyl...@gmail.com
wrote:
getTemperature should be outside Looper class?
On Monday, March 24, 2014 8:35:57 PM UTC, Ytai wrote:
Read my previous post
The code seems OK. What are you seeing in the logs?
Also, did you intentionally change the TWI number back to 0?
On Mar 24, 2014 3:15 PM, Marius Vosylius marius.vosyl...@gmail.com
wrote:
Ytai, Could you have a look what is wrong as Im still cant get output:
class Looper extends BaseIOIOLooper
can't instantiate class com.example.timobot.MainActivity
Seems like you changed the class name in the manifest file, but have not
actually renamed the class (or put it in the correct package)?
On Mon, Mar 24, 2014 at 3:30 PM, Francesco Cembrola f.cembr...@ntlworld.com
wrote:
Hi Ytai.
thank
You need to first enable debugging in your android and connect it to the
PC. Verify by running 'adb devices' and make sure the Android appears in
the output.
On Mar 23, 2014 1:34 PM, Chris Seto chris12...@gmail.com wrote:
Hi,
I have my IOIO connected to my computer as COM46, I am trying to run
There are many separate issues here, let's start with this:
For Nexus 7 over USB you *have* to use OpenAccessory (i.e. turn USB
debugging off). Since you got to the point where you're getting the
accessory dialog, this means that you haven't installed an app that was
compiled to work in accessory
One thing that pops immediately is that twiNum should be either 0, 1 or 2,
not 26.
Another thing is that the address probably doesn't need to be inside the
request buffer.
Yet another thing is that you probably want to only read back 2 bytes and
not 4.
In the future, it would help a lot if you
Let's remove variables here. Fork your code so that it only has minimal
support for the 4WD and servo.
Do you have a datasheet for this 4WD driver?
Can you send an electrical diagram of how those components are connected to
the IOIO and power supply?
Regarding resistors, 1/4W or 1/8W through-hole
See https://github.com/ytai/ioio/wiki/Getting-To-Know-The-IOIO-OTG-Board,
or the legend on the back of your board. Pins 25, 26 are associated with
TWI 2.
On Fri, Mar 21, 2014 at 2:13 PM, Marius Vosylius
marius.vosyl...@gmail.comwrote:
Thanks Ytai, Im using Pin 25, 26 on board, so can i use
Do you have USB debugging on at this point? Can you verify that it works
against a PC (and make sure it is* not* configured for wireless mode)?
I've seen the Galaxy Y working with the IOIO with my own eyes, so whatever
issues you're seeing should be fixable.
Also, look at logcat for any clues
Nothing is not very informative...
TWI 1 that you're using indeed uses pins 1, 2 (assuming IOIO-OTG).
Please add a check for the return value of writeRead(): true means success
and false means failure (which typically means that the device is
improperly connected, improperly powered or using a
.pulseWidth = 0;
stepper2StepCue_.period = 5000;
sequencer_.push(cue_, 62500/20);
}
On Mon, Mar 10, 2014 at 3:00 PM, Ytai Ben-Tsvi yta...@gmail.com wrote:
The JavaDocs are the comments that are inside the Sequencer.java code.
They get converted into HTML, which can be found under
signals simultaneously. I only
allow to send single pulse to either clockwise pin or anticlocwise at one
time. Is there other way to achieve it ?
On Thu, Mar 20, 2014 at 11:40 PM, Ytai Ben-Tsvi yta...@gmail.com wrote:
Setting the pulse width to 0, as you did, is the correct way to stop.
On Mar
Yes, you should be able to use all 16 at 1KHz concurrently.
There was a bug that might explain this that got fixed long ago. Are you
running ancient firmware by any chance?
Also, just verifying that you're using USB as opposed to Bluetooth, because
Bluetooth might not be able to keep up with the
The writeRead() function returns a boolean that will be false in case
anything goes wrong (for example, failing to get an ACK from the device).
The contents of the response array do not matter, only its size.
Do you have pull-ups on SDA and SCL?
On Thu, Mar 20, 2014 at 2:29 PM, Santiago Alfaro
the another pin has to be off.
Because the motor driver cannot receive two input pulse signals even one of
the pulse signal is with 0 pulse width.
On 21 Mar 2014 00:51, Ytai Ben-Tsvi yta...@gmail.com wrote:
You got me confused. How many motors are there, 1 or 2? How are you
trying to get each
Hmmm... You *might* be able to get it working at very low speeds (I would
guess 100Hz would be good). It will require quite some effort to do that I
believe.
You might be able to find a bit-bang I2C code for the PIC and swap the
existing driver with it (or add it) on the firmware side.
On Wed,
Has this IOIO *ever *worked with this phone for you or is this the first
time you're trying?
What firmware versions are on the IOIO (ioiodude --port=xxx versions)?
Make sure ADB is enabled over USB for the IOIO to work.
Are you getting a charging icon on the phone when connecting the IOIO?
Are you
In order to blink you probably want to use System.currentTimeMillis().
Something like:
if (i_should_be_blinking) {
final boolean led_on = System.currentTimeMillis() % BLINK_INTERVAL_MILLIS
BLINK_PULSE_WIDTH);
led1.write(led_on);
led2.write(led_on);
}
On Sun, Mar 16, 2014 at 4:41 AM,
You cannot debug and use the IOIO over USB at the same time.
Your options are either:
- Connect to the IOIO over Bluetooth (for development time) and do
debugging over USB / WiFi.
- Connect the IOIO to your development PC (over Bluetooth or USB), your
phone to the PC over USB / Wifi
This seems the right place to change. Are you sure you are actually running
the firmware that you've modified? How did you install it on the IOIO?
On Wed, Mar 12, 2014 at 8:06 PM, Rich richardgmar...@gmail.com wrote:
Hello,
I was wondering, has anyone (users and/or the IOIO inventor)
Agreed.
On Tue, Mar 11, 2014 at 5:09 PM, Al B cagiva...@gmail.com wrote:
Hey Ytai,,
Your description below says that you used two(2) A4988 Stepper Motor
Driver http://www.pololu.com/product/1182. You also indicate that you
are using a 2-cell Lipo battery. However, the stepper driver
Have you tried Googling for resistor ladder?
On Tue, Mar 11, 2014 at 6:53 PM, francismusic1984
francismusic1...@gmail.com wrote:
Hello people !
So, last time I posted this Ytai said you can easily read the voltage
from the battery connected to the IOIO, but now I'm about to finish the
BTW, since English is not my native tongue too, I probably have used the
wrong term. This is what you're looking for:
http://en.wikipedia.org/wiki/Voltage_divider
On Wed, Mar 12, 2014 at 8:39 AM, Ytai Ben-Tsvi yta...@gmail.com wrote:
Have you tried Googling for resistor ladder?
On Tue, Mar
I powered by connecting IOIO Vin - Driver Vmot.
Despite the specs, I can verify that 2-cell works OK even when the battery
is low. In hindsight, since you've pointed out the out-of-spec usage, I
would probably do things differently.
If I were you, I'd probably just use the drivers as is, and if
Press edit
On Thu, Mar 6, 2014 at 8:51 AM, Tim Frisch tjfri...@gmail.com wrote:
Also; how would I go about updating that page if I found several more
devices that work?
On Thursday, March 6, 2014 10:47:23 AM UTC-6, Tim Frisch wrote:
Sorry didn't consider that a double post; they were two
Before going down the firmware route:
1. While BT is not a good option for the app, it may sometimes still be
used for development time. This is what I normally do. If I have some
bandwidth intensive / latency sensitive piece of code, I would scale it
down for development, then
I'm not sure I understand the question.
The output rate is governed by the Thread.sleep() call inside your loop()
method and the input rate is governed by the way you configure the sensor
manager.
I don't have an encoder in my app, so I'm not sure I understand your
encoder comment.
On Thu, Mar
Hey,
I'm not using anything special. I'm using some dirt-cheap dongles I could
find on Amazon. Make sure the trim-pot is all the way clockwise (common
problem causing intermittent connection). Otherwise try the oscillator
recalibration process (described on the IOIODude wiki page) and/or a
Yes, should be possible.
You might have forgotten to include the IOIOLibAndroidDevice or one of the
manifest requirements OR your Android doesn't support host.
The best way to check is to see whether the prebuilt HelloIOIO.apk works in
this mode for you.
On Wed, Mar 5, 2014 at 6:04 AM, Arjen
Probably has to do with the way you build the app (which libraries /
manifest differences). Just diff the two apps.
On Wed, Mar 5, 2014 at 8:36 AM, Tim Frisch tjfri...@gmail.com wrote:
I have two applications that are nearly identical to one another; when I
run the two only the example
When you said the HelloIOIO works, was it the prebuilt version or one you
built yourself? If the former, try first building HelloIOIO as-is and see
if it works. Otherwise, there has to be *some* difference that makes it not
work, so diff more carefully...
On Wed, Mar 5, 2014 at 9:59 AM, Tim
You are not allowed to call setText() from the IOIO thread. See how
IOIOSimpleApp handles this.
On Mar 5, 2014 11:04 PM, ZackD zackdanie...@gmail.com wrote:
Hello all,
HelloIOIO was working on a Verizon Galaxy S, using the App-IOIO0324
library (I'm on a V1 board marked 4-6-11 on the
By overloading the connection I meant trying to push data at a higher rate
than the channel can handle. If all you have is I2C transactions this
should never happen. Opening a lot of analog inputs or digital inputs that
change very rapidly etc. are examples for things that can generate high
data
What's the question? What would happen is what what you've coded...
If this method gets called periodically, the pin will get closed and open
all the time, and would not produce a stable output when in output mode.
On Mon, Mar 3, 2014 at 1:35 PM, Tim Frisch tjfri...@gmail.com wrote:
Or this
It shouldn't.
On Fri, Feb 28, 2014 at 12:34 PM, Tim Frisch tjfri...@gmail.com wrote:
Title says it all, does it recall setup();?
--
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,
This might very well be a problem that got fixed on a later version of
IOIOLib.
Start with trying the pre-built HelloIOIOConsole from the latest software
bundle (V5.03 as of now).
If all is good, you're supposed to get an error message saying the your
firmware is not compatible. Once you get
What you want to do falls outside the scope of IOIOActivity. So what you
basically want to do is look at how IOIOActivity is implemented (calling
methods of IOIOAndroidApplicationHelper at different times) and modify it
to suit your needs.
On Fri, Feb 28, 2014 at 11:19 PM, Chiong Ching Lai
The pins don't open themselves, so you can simply store every pin you open
in an array / map / etc.
They also don't set their own output, so once again, you can store this
state yourself.
For input pins, read() will tell you the value.
This behavior is one purpose - when designing the API I've
That's unfortunate... If you have any ideas on how to make it better I'd
like to know.
Thanks for reporting.
On Thu, Feb 27, 2014 at 12:53 PM, kolbe brdanko...@gmail.com wrote:
Thanks but I don't think I'll need to roll back the changes. If already
paired it does work fine. If I use an older
IIUC, you're not talking about an oscilloscope, but rather about a logic
analyzer.
You basically have two possible routes:
1. Periodic sampling of digital inputs. Send either raw data of some
kind of compressed data over USB to the host, where the decoding of the
protocol will take
Bonsoir,
Nope. It is currently set to 1KHz.Can probably be speeded up somewhat with
a single number change it firmware, but only up to a certain point (which I
don't know exactly, but would guess at least 10x if you only use one
channel).
On Thu, Feb 27, 2014 at 7:38 AM,
Datasheet says typical 35mA maximum 40mA.
I'd use a transistor.
On Feb 26, 2014 12:02 AM, Al B cagiva...@gmail.com wrote:
Can this module be connected directly to the IOIO or do I need to use a
MOSFET? Although according to the comments, it seems to consume only 15mA.
Marius, how is this question different than the one I answered on my
previous post?
On Wed, Feb 26, 2014 at 7:26 AM, Marius Vosylius
marius.vosyl...@gmail.comwrote:
Dear Ytai, Does Grove TempHumi Sensor SEN11301P or AOSONG OHT11 TempHumi
Sensor works with IOIO-OTG?
On Thursday, February
Have you been able to upgrade the firmware (hint: ioiodude versions will
tell you your current version)?
If so, I would try a different dongle.
USB debugging is irrelevant for Bluetooth.
On Thu, Feb 20, 2014 at 8:25 AM, lakersgang...@gmail.com wrote:
Thank you for the quick response
I still
That sounds interesting and challenging for various reasons:
- If you use, say 16x muxes, you'd need 4000 of them. Lots of $$ and a
complicated assembly.
- At this fan-out, the depth is going to be at least 4 (i.e. 4 muxes to
go through before getting to the ADC) - meaning that it may
A picture is worth more than a 1000 words :)
You have no more libraries to add, as all are already added. Remove them,
then re-add. I'm assuming all the library project have been imported into
your workspace and build correctly.
On Mon, Feb 17, 2014 at 12:18 AM, Chris Seto chris12...@gmail.com
Can you send a picture of your project explorer view?
On Mon, Feb 17, 2014 at 1:31 PM, Chris Seto chris12...@gmail.com wrote:
No matter what, it is a blank window. See attached.
On Monday, February 17, 2014 2:55:39 PM UTC-6, Ytai wrote:
A picture is worth more than a 1000 words :)
You
This sounds like some kind of an Eclipse installation problem.
I recommend trying the Android ADT bundle, which includes everything
(Eclipse, Java, ADT, SDK) in one package of verified versions.
On Sat, Feb 15, 2014 at 8:50 PM, Chris Seto chris12...@gmail.com wrote:
Thanks for the suggestion.
I think the main problem might be integrating with the camera app - I'm not
sure if it actually send notifications for other app when a picture gets
taken. You may want to look for an Open Source camera app that you can
modify.
The IOIO side of things should be straightforward. You'll probably
I don't think getting a blank window in Eclipse may be in any way related
to IOIO or to a certain tutorial, unless I'm misunderstanding the problem
you're describing. Maybe screen-shots of video captures can help.
The tutorial may be slightly out-dated, I'm not sure, but not so much that
it will
What do you mean by high resolution timer API exactly?
On Sun, Feb 16, 2014 at 7:57 PM, Mehrdad N mnav...@gmail.com wrote:
+1 for *Parallel synchronous I/O. *I would also like to see high
resolution timer API for IOIO if possible. Much appreciated!!!
On Tuesday, August 2, 2011 8:08:35 AM
See the eclipse troubleshooting guide on the ioio wiki.
On Feb 15, 2014 4:45 PM, Chris Seto chris12...@gmail.com wrote:
Hi,
I am trying to get a development environment setup to begin developing on
the IOIO. I installed the latest ADK, downloaded the latest 5.03 release,
and downloaded JDK
InputStream.read() which you are calling reads a single byte from the
input. This is probably not what you want. I do not know the format of your
stream, but in case it is text, take a look at
http://docs.oracle.com/javase/7/docs/api/java/util/Scanner.html, which
provides an easy way to parse
Oh, this should obviously not work too well...
You should be calling this from setup(), not loop(). You're opening SPI
over and over (which would start failing after exactly 1 attempt), as well
as setting the button listener over and over.
You should have tons of error messages in your log, which
Why do you think it's faulty?
On Feb 13, 2014 7:50 AM, fabrio pellegrinetti oir...@gmail.com wrote:
I checked with the voltmeter the ioio, as shown in the figure below.
I think the FET Q1 is faulty.
Tips?
it is possible to replace the FET Q1, and what is its part number?
And the code of
(in
the hardware it cuts off only when full charge automatically) then I would
suggest controlling the power going to the android controlled using a
power
mosfet switched programmatically when you sense the system has gone to
battery backup
On Fri, Feb 7, 2014 at 10:28 PM, Ytai Ben-Tsvi yta
The net labeled HOST is controlled in software to enable or disable VBUS
based on whether the IOIO needs to act as host or device. It'll switch to
host mode and apply VBUS whenever you plug in a compliant A plug to the
USB jack OR if the host selection switch is in the H position.
On Feb 13, 2014
The way in which a component might fail when exceeding its absolute maximum
ratings depends on a lot of variables, including the internal design of the
part, manufacturing variance and environmental conditions. We don't know
any of those, so we have to settle for undefined. Nobody guarantees that
I never said that there's no damage in supplying *5V* on the 3.3V pins. I
was assuming when you were talking about supplying power on the 3.3V pins
you meant supplying *3.3V* on the 3.3V pins...
On Mon, Feb 10, 2014 at 11:59 PM, ioioROOKIE gule...@gmail.com wrote:
So, I'm confused. You're
using a power
mosfet switched programmatically when you sense the system has gone to
battery backup
On Fri, Feb 7, 2014 at 10:28 PM, Ytai Ben-Tsvi yta...@gmail.com wrote:
I don't know if there's a programmatic way to disable charging on the
Android.
What you *can* do, however, is detect
It looks like you were supplying 5V on the 3.3V rail... Is be very
surprised if this didn't damage your PIC.
On Feb 10, 2014 2:19 AM, ioioROOKIE gule...@gmail.com wrote:
Also, If I feed the line 3.3v(which is intended to be output) does this
affect the chip in long-term? In other words, does
It's a first order IIR filter (lowpass):
y[n] = 0.999*y[n-1] + 0.001*x[n]
On Sun, Feb 9, 2014 at 8:56 PM, Al B cagiva...@gmail.com wrote:
That makes more sense now.
What about that 0.999 factor? Why do you need that?
errorInt_ = (float) ((error_ * dt * 1e-9) + 0.999 * errorInt_);
--
I can't think of anything that would cause that, except maybe a corrupt
ioioapp file.
To check that, change the suffix of ioioapp to zip and see whether it opens
correctly with a zip tool.
On Sun, Feb 9, 2014 at 10:34 PM, איציק גילי itzik.g...@gmail.com wrote:
Sure,
ioiodude --port=COM6
It is very unlikely that you'd be able to actually get samples at this rate
to the Android.
The processing power on the PIC as well as the USB bandwidth will limit you.
However, you should be able to increase the sample rate from its current
1kHz. I would start by building the firmware as-is and
I meant the 3.3V output rails.
On Mon, Feb 10, 2014 at 8:09 AM, ioioROOKIE gule...@gmail.com wrote:
YTAI,
You said You're not supposed to be supplying power on either the 3.3V or
the 5V pins (although, there's no damage in doing so).
By saying 3.3V, did you mean the 3.3v outputs near of
Try using the Android development bundle from the Android developer site.
It includes known-working versions of everything.
On Feb 9, 2014 10:00 AM, M.A.K makp...@gmail.com wrote:
Good day dears ,
I'm new with IOIO , my problem when I try to import the libs inside the
eclipse it will shutdown
This means that the problem is almost certainly on the Android side. Either
in the IOIO code or in Android itself (more likely in this case). Do you
have a different Android to try with?
On Sun, Feb 9, 2014 at 1:11 PM, Thomas Hermansson
thomas.hermans...@gmail.com wrote:
Hi!
Ok!
No
As of writing this, the N5 is known to not work over OpenAccessory with the
IOIO acting as host.
It *does* work with the IOIO acting as a device (will not charge the
Android in this case). Remember to add IOIOLibAndroidDevice to your app and
make the necessary manifest changes (look at the sample
You're not supposed to be supplying power on either the 3.3V or the 5V pins
(although, there's no damage in doing so).
Power should be supplied between Vin and GND through the pins or the JST
connector. If everything is valid, you should be able to measure 5V and
3.3V on the respective pins
programmatically (in the
hardware it cuts off only when full charge automatically) then I would
suggest controlling the power going to the android controlled using a power
mosfet switched programmatically when you sense the system has gone to
battery backup
On Fri, Feb 7, 2014 at 10:28 PM, Ytai Ben-Tsvi yta
Try upgrading both the firmware and IOIOLib to version 5.
On Feb 5, 2014 6:46 AM, tyimofej admiralissi...@gmail.com wrote:
Hello
I have 2 boards, that is why you can read about different firmwares.
Indeed, one of my problems was, that my Lib version did not match the
Firmware version.
For starters, IOIOLib v4.x or v5.x won't work with firmware v3.x. Either
upgrade your firmware or downgrade your software.
However, the logs you sent suggest that it hasn't even gotten to that stage.
Let's separate some variables here. Can you pick up the pre-compiled
HelloIOIO.apk from the
How are you running the app? The message you're getting is from Eclipse and
not from the Android. Also, it seems to be running the app, is it not being
installed / launched?
On Tue, Feb 4, 2014 at 3:20 AM, Christian Henkel ctietg...@gmail.comwrote:
Yes, it is checked. Clean Rebuild works.
You can call ioio_.disconnect(), but I find it hard to imagine cases where
you'd want to do this explicitly. It is normally handled for you by the
IOIO application framework.
On Tue, Feb 4, 2014 at 11:34 AM, Greg Gradwell roto...@gmail.com wrote:
Ytai,
What's a good way to force a
Other than the message - does it work OK?
On Tue, Feb 4, 2014 at 9:16 PM, Christian Henkel ctietg...@gmail.comwrote:
I tried to run the app using the run button in eclipse. As you can see in
the logs, it is uploaded first and then started. I have tried already a
directly connected phone, a
This type of errors are usually a result of overloading the connection
bandwidth. I don't know whether there's anything better to do about it - I
at least made it so your app doesn't crash when that happens, but rather
the connection gets dropped. At the end of the day, I don't know what would
be
I would start with a simple code that just prints out whatever's read from
the UART. Consider using BufferedReader.readLine() and regular expressions
for parsing instead of your existing code that is error prone. There also
might be open-source NMEA libraries in Java out there that you can
My self-balancing
ShoeBothttps://github.com/ytai/ioio/tree/pwm-improvements/software/applications/ShoeBot
is
an example. It is not directly compatible with the stock IOIO firmware, but
should give you a rough idea.
Here's a video:
http://www.youtube.com/watch?v=DMEYUsGte9o
On Mon, Feb 3, 2014 at
Is the IsLibrary checkbox checked in the Android properties page of
IOIOLibAndroid?
Otherwise, try a clean-build.
On Mon, Feb 3, 2014 at 11:05 AM, Christian Henkel ctietg...@gmail.comwrote:
I have been trying to get the HelloIOIO example running for ages now. It
really looks good now. All
Here's where you download MPLAB-X (free):
https://www.microchip.com/pagehandler/en-us/family/mplabx/
C30 seems to no longer be available. You can get XC16 and convert the
projects from here:
http://www.microchip.com/pagehandler/en_us/devtools/mplabxc/
I have no idea why they did that... Pretty
The root cause is corruption in the data coming in. IIRC, you're using
Bluetooth, with a number of analog inputs, and it might be that the
connection is not keeping up until eventually dropping data.
I recently changed the behavior of this failure mode to not crash the app,
and IOIOLib seems to
It is recommended to use potentiometers of up to 2.5K ohm.
Number of analog inputs is 16 (unrelated to PWM).
On Thu, Jan 30, 2014 at 4:29 AM, doron atuar doronat...@gmail.com wrote:
Hi,
i need to connect 5 potentiometers to IOIO in order to create a close-loop
feedback for a robotic arm
is
801 - 900 of 941 matches
Mail list logo
