View Single Post
  #20   Spotlight this post!  
Unread 25-03-2011, 07:54
Jared Russell's Avatar
Jared Russell Jared Russell is offline
Taking a year (mostly) off
FRC #0254 (The Cheesy Poofs), FRC #0341 (Miss Daisy)
Team Role: Engineer
 
Join Date: Nov 2002
Rookie Year: 2001
Location: San Francisco, CA
Posts: 3,082
Jared Russell has a reputation beyond reputeJared Russell has a reputation beyond reputeJared Russell has a reputation beyond reputeJared Russell has a reputation beyond reputeJared Russell has a reputation beyond reputeJared Russell has a reputation beyond reputeJared Russell has a reputation beyond reputeJared Russell has a reputation beyond reputeJared Russell has a reputation beyond reputeJared Russell has a reputation beyond reputeJared Russell has a reputation beyond repute
Re: Walking Encoder Values

My suspects would be, in order:

1. Mechanical slippage between the encoder and the shaft whose rotation it is measuring (you seem fairly sure that this isn't the issue, and I believe you, but in general it is the first/easiest thing to check)

2. Improper spacing between the optical disc and the encoder circuitry. Use a spacer tool when installing the disc.

3. A "smudge" (fingerprint or scratch) on the disc that causes one of the photoreflectors to miss a count or two per revolution. Easiest solution: try another encoder disc.

4. EMI/wiring problem.

5. Code issue. Your code doesn't ever reset the encoder, does it?

6. An absurd pulse frequency (too high of a CPR on the encoder given the speed of the shaft it is measuring). However, in the cRIO era, you need to be well into the tens-of-thousands of pulses per second before this would be an issue, so it is unlikely.

Last edited by Jared Russell : 25-03-2011 at 10:54.