Quote:
|
Originally Posted by Matt Krass
If memory serves it loops as fast as possible, so it could run anywhere from about 12ms to 26.2 and it will change depending on your autonomous code, if its really time sensitive, you should use the hardware timer, and its just good to know how to use that anyway.
|
No, that's the entire point. It doesn't loop as quickly as possible. It does its calculations and idles for the remaining part of the loop time. While I'm not at all sure about your robot being disabled if you don't get data within 26.2 ms, it could be true. However, no reasonable code for your robot would go beyond the 26.2 ms loop. You're not calculating pi to the 500th decimal place, you're not using the cubic formula, and you certainly shouldn't be using an loop except an iteration loop. Therefore, 26.2 ms is a safe figure by design.
Hope this helps,
Paul