[Greg McKaskle]

At the regionals I've attended, I've seen a number of teams throwing this when disabled because they are using a different name for their drive or for other reasons aren't updating the speed. Setting the speed there is useful to avoid jumps when the robot first enables, but otherwise isn't super important.

The most troubling issue with these issues is that they bog down the cRIO so that deploying new code is a bit more difficult, especially when other parallel loops like vision and Timed tasks are running at high CPU usage.

I also saw an error in built apps caused by the calibration code on the Vision diagram. That may not be common, but it makes sense if the panel is being removed during build.

I wish the error messages were a bit easier to understand, but if you are still having ones you can't find, post the Diagnostic messages, including the location info.

Greg McKaskle