Did anyone figure out a solution to this, having the same issue currently...
On Saturday, December 31, 2011 at 5:29:02 PM UTC-5, Bob wrote: > > I'm not yet an IOIO user - only discovered it on friday. > > I posted a couple of questions in the comments section of Ytai's pages and > Yati suggested that I post here. > > I've done some play with Arduino and optical Rotary encoders, primarily > with an interest in tracking the position of telescopes (although I have > an ArgoNavis which does that very well). Interesting learning and hoping > one day that I get enough bit's of learning together to make some useful > real world application with this (using a phone or tablet as a telescope > control handpiece with fairly simple electronics at the telescope). Ability > to read encoders and control steppers has a raft of potential uses for DIY > projects. > > The encoders I'm using are the predecessors to these > http://www.usdigital.com/assets/general/82_s6_datasheet_3.pdf > Detecting all state changes on the two channels of a 2.5k encoder can give > a 10k resolution. > > I put some notes on what I was doing with the Arduino onto a Sparkfun > forum http://forum.sparkfun.com/viewtopic.php?f=8&t=20137&view=print for > those who want to see how I did that. > I'm trying to work out if it would be viable to add encoder interfacing > into the IOIO firmware so that the IOIO kept track of the position and the > phone polled position as needed. In practice it would also need to be able > to set current position, notify the phone when it got to a specified > position etc. Great to be able to deal with multiple encoders as well > although that potentially makes the speed issue much worse). > > I've not been able to determine what sort of real clock speeds the IOIO > runs at, the Arduino missed some state changes when I upped the rotation > speed (trying to mimic a fast hand slew of a telescope). From memory I was > working with a 16MHz 328 board. I've not yet worked with PIC's so I don't > have any idea if they might handle some of that stuff differently to the > Arduino. > > Any thoughts on what would be involved on adding in encoder functionality > to the firmware? > > What's the speed of the board and does the way the firmware is implemented > alter performance compared to tools such as the Arduino and Picaxe? > Please excuse the vagueness of that question, not an issue I understand > well but I'm hoping that there are some ballpark figures that would help me > understand what sort of performance to expect compared to what I'm already > used to (eg 16MHz Arduino). > > Bob > -- 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.
