View Single Post
  #4   Spotlight this post!  
Unread 27-12-2012, 23:41
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,078
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: Dealing with low resolution data for speed PID

Quote:
Originally Posted by Ether View Post
Problem with measuring elapsed time between consecutive encoder pulses is: manufacturing tolerances of the spacing of pulses on the encoder wheel can result in an excessively noisy signal if you measure only one pulse.


I have found that the most common source of this problem with encoders is that the A and B lines are not exactly 90 degrees out of phase and I am trying to measure the time between two consecutive transitions in "x4" mode (rising A -> falling B for example). I have had good luck with measuring successive transitions in "x1" mode (rising A -> rising A) because the disks themselves are usually pretty well made(at least in the case of US Digital S series and Grayhill 61/63 series optical encoders).

Worst case you can average the last N measurements and be able to trade off phase delay with smoothness.