View Single Post
  #2   Spotlight this post!  
Unread 03-04-2005, 18:54
Ben Margolis Ben Margolis is offline
Programmer Boy
no team
 
Join Date: Mar 2005
Rookie Year: 2005
Location: San Bruno, CA
Posts: 9
Ben Margolis is a glorious beacon of lightBen Margolis is a glorious beacon of lightBen Margolis is a glorious beacon of lightBen Margolis is a glorious beacon of lightBen Margolis is a glorious beacon of lightBen Margolis is a glorious beacon of light
Re: What to do next?

As long as your samples are occuring consistently, you should be able to have a consistent error, which you seem to have, although I'm just eye-balling the numbers. I would try tweaking the gyro calculation constant (I believe thats what Kevin calls it).

The gyro gives whatever rate of rotation it has at the time of the call. Rate wise, it will always be accurate. If you don't call it quickly enough (your question), you may miss subtle changes. This is important because you are integrating the rate. Not having the smoothest slope (or as many samples of gyro rate) means you MAY be losing accuracy due to that. However, the processor works so darn fast, and our robots move so relatively slow, that I doubt that sample rate is the cause of your problem.

I hope I've made sense....