Quote:
|
No matter how many corrections I tried, I could not maintain a reasonable value for position for more than about 10 seconds. Any small error in acceleration measurement is compounded when you integrate to get velocity, and any small error in velocity is further compounded when you integrate to get position. All of these errors sum up very quickly. As far as I can tell, the kit accelerometer simply does not have enough precision to be used in this way (although I would really like to be proven wrong). The sample times could also be an issue if a higher-precision accelerometer were used, but I am convinced that the limiting factor when using the kit accelerometer is its precision, not the sample times.
|
This is why I lean more towards the encoder/gyro method. Too many variables and errors in the accelerometer. But I may find that the encoder method has them too, only one way to find out. I'm gonna convince a few members of my team to help me work on an encoder/omni-wheel/gyro project with a kit chassis and give you guys an update in a few weeks.
Any suggestions before I start?
EDIT: The next thing after a mechanical solution has been found would be how to plot all this data on a 2D x&y plane on your dashboard in real time. I'm guessing the DB would do all the calculations and just get a couple SD Variables for encoders and gyro from the bot?