View Single Post
  #3   Spotlight this post!  
Unread 25-01-2008, 20:59
lukevanoort lukevanoort is offline
in between teams
AKA: Luke Van Oort
no team
 
Join Date: Oct 2005
Rookie Year: 2005
Location: Waterloo, ON, Canada
Posts: 1,873
lukevanoort has a reputation beyond reputelukevanoort has a reputation beyond reputelukevanoort has a reputation beyond reputelukevanoort has a reputation beyond reputelukevanoort has a reputation beyond reputelukevanoort has a reputation beyond reputelukevanoort has a reputation beyond reputelukevanoort has a reputation beyond reputelukevanoort has a reputation beyond reputelukevanoort has a reputation beyond reputelukevanoort has a reputation beyond repute
Send a message via AIM to lukevanoort
Re: Gyro vs Dead Reckoning

Sensor feedback in autonomous is almost always better than dead-reckoning; in fact, the only situation I can think of where dead-reckoning would be preferred is if your sensor was really buggy and gave false reading often (in which case you probably should be using a different sensor). The question is like asking "Is it better to drive by looking at a map the whole time or by remembering where you want to go and watching the road instead?"

I have written both sensor-driven and dead-reckoning autonomous modes, but the dead-reckoning ones were always rush jobs that weren't expected to do much (like just deploy our arm). We use a hardware timer and interrupts for timing a dead-reckoning autonomous modes. If you do use dead-reckoning (many autonomous modes will have at least some time-dependent stuff, so the advice will probably apply with gyros too), I would definitely suggest using timers. Loop-counting seems like a bit of an unreliable and undesirable solution to me.
__________________
Team 1219: 2009 - Mentor
Team 587: 2005 - Animator, 2006-2008 - Team Captain

Last edited by lukevanoort : 25-01-2008 at 21:05.