Encoder Problem.

[Kevin Sevcik]

Originally Posted by slijin

I've ran into weird errors with Java when the leading character isn't a lowercase letter, hence my suggestion.

I'm skeptical. Mostly because I've seen programmers use all sorts of capitalization schemes and have them work. If they're consistent. If you're prone to typos and accidentally using different capitalization then that's obviously going to cause issues. Similarly if you accidentally name a variable identically to a function or class or something.

Originally Posted by slijin

I don't believe there's any problem with the order of the reset() and start() calls, as start() initializes the accumulator, and reset() just resets the count to 0 - one does not affect the other.

Technically it strobes a reset bit on the counter in the FPGA. I'll agree it probably doesn't matter since it does this during the setup of the Counter object before you can start the Counter. So the reset() call probably sn't even necessary.

Originally Posted by slijin

He did say that the encoder worked fine on an Arduino.

Which was before it was likely rewired or atleast moved to being hooked to the Sidecar. Which is not a 100% guaranteed benign operation. It should take no more than 10 minutes to test this and if it DOES turn out to be wired wrong or blown, it will save you days or weeks of debugging a program that's trying to read a bad encoder. I like to knock off low hanging fruit in my troubleshooting so I don't feel like an idiot later when I've spent hours on something I could've spent 10 minutes checking at the beginning. If you're really that desperately attached to not "wasting" 5-10 minutes, then do the check while you're downloading code or rebooting the robot and otherwise twiddling your thumbs. Or recruit a helper to check for you while you're plugging away at your code. Just check it to give us all some peace of mind.