View Single Post
  #3   Spotlight this post!  
Unread 27-12-2012, 22:51
Ether's Avatar
Ether Ether is offline
systems engineer (retired)
no team
 
Join Date: Nov 2009
Rookie Year: 1969
Location: US
Posts: 8,084
Ether has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond repute
Re: Dealing with low resolution data for speed PID

Quote:
Originally Posted by Jared341 View Post
The first thing I would explore is ways to get a higher resolution speed signal. I am not all that familiar with the Vex controller so I can't speak to the ease of the following approach, but one way to solve this problem in general would be to measure the time between successive encoder pulses rather than counting pulses and dividing by unit time. Most timers have resolutions that far exceed the resolution that you are showing here.
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.