Loop Timing on Robot Drive

[Wendy Holladay]

We have been doing some experimenting with an issue we have put off for a while. We read our joysticks in teleop and then set global variables. We actuate the motors, including drive in periodic.

This works well and our robots drives just fine. However when we set our loop time to 100ms, setting our Drive vi, we get the following error/message at the diagnostic tab of the driver's console.

Robot drive is running too fast or being starved due to too much code.

When we set that loop for 10ms, no diagnostics error/message.

The performance of the robot does not change. The setting of the drive is the only action in the loop. This error does not seem to hurt us, but I have wondered for a while why we get it and was hoping for some help from the community.