Thread: Unexpected results from Encoder::GetRate()
View Single Post
  #27   Spotlight this post!  
Unread 10-04-2010, 11:07
Bigcheese Bigcheese is offline
C++0x FTW!
AKA: Michael Spencer
FRC #1771
Team Role: Mentor
  
Join Date: Feb 2008
Rookie Year: 2008
Location: GA
Posts: 36
Bigcheese is a jewel in the roughBigcheese is a jewel in the roughBigcheese is a jewel in the roughBigcheese is a jewel in the rough
Re: Unexpected results from Encoder::GetRate()
Quote:
Originally Posted by vamfun View Post
Only thing clear is a factor of 2 difference in your data so far.
The factor of two difference between the encoders is because one is about twice the pulses per rev as the other.

Quote:
Originally Posted by vamfun View Post
What are the units?
How did you acquire data?
Can you also print GetDistance or GetRaw?
Was SetDistancePerPulse checked for each encoder?
Can you run a 1x case if you have time?
  • The units are in feet per second.
  • Using a notifier that printed GetFPGATime(),GetJagOutput(),GetLeftRate(),GetRigh tRate() at 200Hz
  • Hopefully today.
  • The same value was used for both and was correct for one of them.
  • I think I have one, but I'm not sure which it was (we were rushing to see the data, didn't mark any of it). The data was almost identical except for a little less noise. I'll run it again though.

I will do this today if I can get into the school.
Reply With Quote