Quote:
Originally Posted by ayeckley
Can anyone recommend a good tactic (that doesn't involve modifying the navX source code) to convert the yaw output from a range of -180 to 180 (i.e. modulo 360) to an accumulated total rotation? All of the approaches we can think of require an assumption of what a maximum realistic turn rate is, and we'd like to avoid that if possible. I'm confident that we're not the only team encountering this challenge.
|
We had this issue. However, as we were already reading the angle at 50hz, finding a reasonable assumption of turn rate wasn't hard, we used a threshold of 180 degrees, which means we'd have to be spinning at faster then 9000 degrees/sec to have a problem.
I GET that FIRST is about more than winning on the field. BUT... ...it is my experience that the great programs of the FIRST world almost always build on a foundation of competitive robots. Success on the field begets success in other realms. - Joe Johnson [more] 
Threaded Mode