Thread: Encoders on Drive Train DON'T WORK.
View Single Post
  #13   Spotlight this post!  
Unread 14-04-2012, 21:10
JamesTerm's Avatar
JamesTerm JamesTerm is offline
Terminator
AKA: James Killian
FRC #3481 (Bronc Botz)
Team Role: Engineer
  
Join Date: May 2011
Rookie Year: 2010
Location: San Antonio, Texas
Posts: 298
JamesTerm is a splendid one to beholdJamesTerm is a splendid one to beholdJamesTerm is a splendid one to beholdJamesTerm is a splendid one to beholdJamesTerm is a splendid one to beholdJamesTerm is a splendid one to beholdJamesTerm is a splendid one to behold
Re: Encoders on Drive Train DON'T WORK.
Quote:
Originally Posted by slijin View Post
Were they the ones received in the KoP this year or from AM FIRST choice? If the answer is yes to either, then you're using the E4P encoder with a 360 CPR wheel.


There has been a wealth of discussion on this topic and how to filter encoder data to return a more stable rate. I would suggest doing a forum search and comparing your results with those that others have documented. I doubt it's related to the problem that this thread was created to discuss, as this is a widely documented issue that is commonly expected of encoders, whereas the one that you're experiencing hints of a connection problem.

I believe they are from the KoP... I know that the power wheel encoder is indeed the 360 CPR... as I use (1/360) when I set the pulse distance to get RPS units.

Thanks for the tip on the other discussions... I'll definately want to check them out... but I should reiterate something... I do the same identical test with last years robot and this years with the same exact code. I simply turn the wheel by hand, and last years robot was very smooth numbers. There has got to be some explanation. I'll try to find what you are talking about as well.