FTC: Using the Hitechnic SuperPro Prototype Board

[Andrew Lobos]

Originally Posted by TRWSHSHLX

One suggestion is don't draw too much power from the motor controllers at once (like putting full throttle on a six motor drivetrain instantaneously) since that does in fact mess up the encoder count.

This happens because the encoder counts are stored and read from the motor controllers - if they loose power (or brownout), the count will reset.

My FTC team used encoders to achieve infinite rotation on our swerve drive last year, and we had no issues with the encoders returning the wrong position.

A few more questions -
How old are the encoders you're using? Some of the older packages they made used adhesive backing, which I've seen come loose.

When deciding the encoders are returning incorrect values, are you looking at the value itself, or just seeing the results of an action using the encoders? If you are observing the robot driving different distances, but the encoder values are consistant, your issue may be rooted in how your code decides it is "there".