Why 26ms update rate?

[mluckham]

Using Easy/C the necessity to think about the 26 msec from the Master is removed, the compiler lets your code run in a tight loop and simply updates the Master processor at appropriate intervals. So if next year, the Master updates every 28 msec or 22 msec instead - who cares?

With the provision of the Easy/C (WPILIB)Timer() functions, it unnecessary (IMHO) for code to base any calculations on the 26 msec interval, or programmers to be concerned about same.

Kevin's explanation of 'why' is clear enough, and it is clear enough that the robots work just fine at this rate.