Quote:
Originally Posted by EricVanWyk
Neat! Sounds like an interesting break inside the DSC then: Haven't seen this one before. You are listed as being in texas - If you are headed to an Austin kickoff I'd love to take a look at it.
|
We are going to the Dallas kickoff. Once we get a replacement I could mail it to you if you PM me your address.
Quote:
Originally Posted by Chris Hibner
Are you doing any encoder resets? (In LabVIEW, there is a Reset Encoder vi that resets the encoder counts to 0 and stops the encoder, you then need to do an Encoder Start. I'm assuming there are equivalent methods of doing this in C++ and Java.)
I found a bug with the Encoder Reset / Encoder Start / Encoder Stop functionality in the 2012 firmware. The bug caused it to act exactly as you're describing. We lost days trying to track that down.
|
I took the code from last year's shooter encoder and it called the start() method once and reset() each cycle. It seemed to work fine in Java but I will give it a try with start() after each reset(). For this current issue I had removed all the reset() calls to make it as simple as possible.