View Single Post
  #9   Spotlight this post!  
Unread 09-11-2013, 19:50
MattRain MattRain is offline
AZ FTC AF, FTC #2844 and FTC #8640
FRC #1492 (Team Caution)
Team Role: RoboCoach
 
Join Date: Sep 2012
Rookie Year: 2008
Location: Chandler, Arizona
Posts: 317
MattRain has a brilliant futureMattRain has a brilliant futureMattRain has a brilliant futureMattRain has a brilliant futureMattRain has a brilliant futureMattRain has a brilliant futureMattRain has a brilliant futureMattRain has a brilliant futureMattRain has a brilliant futureMattRain has a brilliant futureMattRain has a brilliant future
Re: [FTC]: Motor encoders Love'em? or leave'em?

Quote:
Originally Posted by Ether View Post
I don't think that answered the question Madison was asking.

There's a difference between what the sensor on your robot says and how far the vehicle actually moved.


Ok, yes there is that fact of that robot could have gone a little under or over that number. Again, there really is no reason for programming that far, and hard to even get that measurement in real time, without looking at the computer. I was just stating the fact that the program could do it if it really wanted to. Right now in our programming, we do give a tolerance area for the code to decided if its in the right place without it getting stuck on a certain step. Its just stupid not to have your program run through all the steps because of a small.1 of an inch. I think right now, our programmer has it to a .1 or .15 of a tolerance, as there is really no need for huge precision this year, unlike last year with the pegs and such.
Reply With Quote