Thanks. Let me know if there's any change with v5. Also, if someone can give me a simple test case that I can reproduce the problem with, I will be grateful. Hint, the new motor control library can generate pulses very similar to the wind sensor. I'm currently working on detailed documentation for this library, but in the meantime the Javadocs should provide a good starting point.
On Sun, Jan 12, 2014 at 1:45 PM, kolbe <[email protected]> wrote: > Just to add my experience to what seems to be the same problem. I've got > an weather app running 24/7 that uses just about all the different I/Os > available. I too get a hung PulseIn.frequency. It used to work but now > pretty much it will hang every few days. I use 3 PulseIn at a time calling > them successively and it is always the third call that blocks. The signal > is good on the scope and if I reconnect to the IOIO all works fine again. I > can't be sure but it seems this started to happen with version 4. This is > over BT but when the protocol gets corrupted the app usually just dies and > the logs reflect it, so I don't think this is BT related. When it hangs > everything else keeps on working, UART, TWI, PulseOut, digital I/O, and > AnalogIn. > > Let see what v5 does. > > -- > You received this message because you are subscribed to the Google Groups > "ioio-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/ioio-users. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "ioio-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/ioio-users. For more options, visit https://groups.google.com/groups/opt_out.
