View Single Post
  #10   Spotlight this post!  
Unread 24-03-2011, 21:15
apalrd's Avatar
apalrd apalrd is offline
More Torque!
AKA: Andrew Palardy (Most people call me Palardy)
VRC #3333
Team Role: College Student
 
Join Date: Mar 2009
Rookie Year: 2009
Location: Auburn Hills, MI
Posts: 1,347
apalrd has a reputation beyond reputeapalrd has a reputation beyond reputeapalrd has a reputation beyond reputeapalrd has a reputation beyond reputeapalrd has a reputation beyond reputeapalrd has a reputation beyond reputeapalrd has a reputation beyond reputeapalrd has a reputation beyond reputeapalrd has a reputation beyond reputeapalrd has a reputation beyond reputeapalrd has a reputation beyond repute
Re: Walking Encoder Values

Quote:
Originally Posted by DonRotolo View Post
Computational: Your input circuit is missing some of the encoder's output pulses. If you are using a hardware interrupt, then your encoder resolution (pulses per revolution) may be higher than the hardware can manage. If you are not using a hardware interrupt, that could be your problem.

If you are using the cRio's Encoder or Counter modules, they are handled with dedicated hardware in the FPGA, and should never drop counts in any reasonable encoder.
__________________
Kettering University - Computer Engineering
Kettering Motorsports
Williams International - Commercial Engines - Controls and Accessories
FRC 33 - The Killer Bees - 2009-2012 Student, 2013-2014 Advisor
VEX IQ 3333 - The Bumble Bees - 2014+ Mentor

"Sometimes, the elegant implementation is a function. Not a method. Not a class. Not a framework. Just a function." ~ John Carmack