Quote:
Originally Posted by ayeckley
I guess my frustration is over the loss of a feature that we weren't expecting to lose. Was it common knowledge?
|
The loss of support for the Cypress I/O was mentioned in pretty much every presentation I saw from Beta Test teams.
Quote:
|
...I think we'd need to use an interrupt-driven input for an encoder application. Our tick rates will be on the order of 10-100 Hz. We'd also want to represent the tick count in an equivalent way to the Enhanced I/O processed it (signed 32-bit integer, IIRC). Time to start reading, I guess...
|
I believe a Teensy's (or Arduino's) main loop would be plenty fast enough to read a quadrature-encoded knob. You can easily represent its count as a joystick axis with 16 bits of precision, and while I doubt you'd need more than that for a few minutes of a competition match, it isn't hard at all to handle over/underflow on the robot and track its rotations indefinitely.