[Greg McKaskle]

If you have no errors on the diagnostics tab, the next item I'd look at is the Charts tab of the DS. You should see CPU, memory, and other useful robot elements charted and logged there. Can you run the robot through different modes to see if it is just tele, or just auto, or always pegging the CPU?

The step after this would be for me to profile it using the CPU profiler built into LV. It is important to open and start the profiler before you begin running your code, then run the code for say 10 seconds, then stop the code, and only then stop the profiler. The profiler will only record functions that started and stopped in a profile session, so opening it too late or stopping it too soon can confuse you if you aren't very aware of how the code is being invoked.

Greg McKaskle