View Single Post
  #4   Spotlight this post!  
Unread 26-12-2011, 21:47
plnyyanks's Avatar
plnyyanks plnyyanks is offline
Data wins arguments.
AKA: Phil Lopreiato
FRC #1124 (The ÜberBots), FRC #2900 (The Mighty Penguins)
Team Role: College Student
 
Join Date: Apr 2010
Rookie Year: 2010
Location: NYC/Washington, DC
Posts: 1,113
plnyyanks has a reputation beyond reputeplnyyanks has a reputation beyond reputeplnyyanks has a reputation beyond reputeplnyyanks has a reputation beyond reputeplnyyanks has a reputation beyond reputeplnyyanks has a reputation beyond reputeplnyyanks has a reputation beyond reputeplnyyanks has a reputation beyond reputeplnyyanks has a reputation beyond reputeplnyyanks has a reputation beyond reputeplnyyanks has a reputation beyond repute
Re: Getting Encoder Position Value

Quote:
Originally Posted by kws4000 View Post
So distance is what I'll want if I want to know where I am in relation to startup?

So if I'm reading this right, rate will be used for, say, traction control?
That is correct. I forgot to mention, that when you open the encoder, one of the inputs to the Encoder Open VI is "Distance Per Count", which is the tangible distance per encoder tick (and I think it also factors into the rate calculation). Make good use of that parameter, and look into the VI documentation for some more information.
__________________
Phil Lopreiato - "It's a hardware problem"
Team 1124 (2010 - 2013), Team 1418 (2014), Team 2900 (2016)
FRC Notebook The Blue Alliance for Android
Reply With Quote