Thanks a lot for the answer and suggestion!

I figured out that the reason for failure was custom made usb cable which 
probably got short-wired during the stress test. So I got new cable, 
connected it to new Sparkfun IOIO and now everything works perfectly :)

Btw, I would like to present my project to the wider audience, any ideas 
how can I share it on IOIO Pinterest group?


Dana četvrtak, 15. lipnja 2017. u 19:48:43 UTC+2, korisnik Ytai napisao je:
>
> It is hard to tell exactly what was the failure mode. If you indeed 
> correlate the failures with physical damage, consider making sure the 
> electronics are well protected against shorting or cutting off during 
> flipping. What I often do in my hacky projects is bury electrical 
> connections in hot glue once everything is working. This ensure nothing 
> shorts and nothing moves. But of course, there are more elegant ways to 
> achieve that :)
> The v2.2 fix is designed to survive many possible fault conditions, such 
> as (short) high voltage spikes on the input and overload / short conditions 
> on the output. So that would possibly give you another safety net for 
> reliability, although it is of course recommended to try to prevent these 
> conditions from occurring.
>
> I hope this helps!
> Ytai
>
> On Thu, Jun 8, 2017 at 11:34 PM, Ante Brkic <[email protected] 
> <javascript:>> wrote:
>
>> Hi,
>>
>> First of all, kudos to ioio and ytai, I really appreciate and love IOIO 
>> project.
>>
>> My issue is that the moment I connect IOIO to the Android device, the 
>> power led on IOIO turns off. IOIO is still functioning properly when I 
>> connect it to the PC but does not get power when I connect it to the 
>> external power source. I've been studying this issue on the net (this very 
>> group) to figure out that it must be IOIO voltage regulator burn-out 
>> syndrome.
>>
>> I had a working setup - basically it is a remotely controlled tank (which 
>> I plan to present as soon as I get it working again) and I was stress 
>> testing it driving it around my room. Everything worked fine but my tank 
>> flipped several times after which it first started to experience random but 
>> frequent IOIO reconnects (increasingly frequent), culminating with 
>> definitive failure.
>>
>> In the aftermath of this stress test I figured out that:
>>
>>    1. IOIO power cables (connected to power JST on IOIO) were 
>>    disconnected on the soldering point (due to physical damage when tank 
>>    flipped I suppose).
>>    2. IOIO couldn't be powered any more from the JST and neither VIN 
>>    line but only from the PC when running in the device mode.
>>
>>
>> After that I ordered another IOIO from the net, fixed my cables in the 
>> meantime, but as soon as I connected the new IOIO it's voltage regulator 
>> got burned - power led turned off and I couldn't get power any more unless 
>> I connected IOIO to the PC.
>>
>>
>> Both mentioned IOIO's were IOIO OTG but not v2.2 with voltage regulation 
>> fix although my power cables are short (20cm) so I can not identify the 
>> issue as the one that was addresses through v2.2 fix.
>>
>>
>> And this is what troubles me. I have now ordered two new IOIO's, one from 
>> Sparkfun and one from ebay but I am very afraid to connect them to my 
>> project before understanding what is causing the issue.
>>
>>
>> It is worth mentioning that the USB cable I was using was custom made 
>> cable which I made from two USB cables, one OTG and one common which I've 
>> done because I wanted to have micro-USB to micro-USB OTG cable (which I 
>> can't find anywhere to purchase btw). But this cable was working properly - 
>> issue happened only after the tank flipped. I am now returning to original 
>> OTG cable but I'm still afraid not to burn any more IOIO's.
>>
>>
>> I've tested the Andorid device USB port by connecting it to PC and it's 
>> both charging and enabling data transfer.
>>
>>
>> Could it be that my custom cable went shortwired for a while and that 
>> caused the voltage regulator to burn?
>>
>>
>> How would you proceed here?
>>
>>
>> My debug plan is as following:
>>
>>    1. Connect the new IOIO to PC.
>>    2. Connect IOIO to Android with original OTG cable + male USB to 
>>    micro USB.
>>    3. Connect JST power to IOIO.
>>    4. Attach electronic circuit to IOIO.
>>
>> Is there anything else I can do in the debug process to prevent 
>> additional damage?
>>
>> -- 
>> 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] <javascript:>.
>> To post to this group, send email to [email protected] 
>> <javascript:>.
>> Visit this group at https://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 https://groups.google.com/group/ioio-users.
For more options, visit https://groups.google.com/d/optout.

Reply via email to