Program overloading the cRIO?

[edzenitis]

We had similar problems to team 2893. After Autonomous mode finished, Teleop mode would work only half the time. I don't know if these are related or separate problems, but we were getting error messages about Robot drive being too slow, when Teleop did work it was sometimes sluggish, and data rate on the field was taking twice as long as the other teams. There seemed to be a pattern where we would deploy the code, it would work in Auto and Teleop. Then the next round, Teleop wouldn't work. When the code was redeployed, the same thing happened. This was repeated ~6 times during the tournament. We raised the radio up higher for the last two rounds, but had similar issues. We never experienced this when tethered to the cRIO.

We don't have a spare cRIO or I would try running the software using the Elapsed Times.vi to see if Teleop is running too slowly and try to isolate the problem. I'm posting the code if anyone is willing to take a look at it or possibly run it to see if the timing is reasonable or not.

[Greg McKaskle]

I believe that deleting the compressor code will solve the problem.

The compressor code is a bit more complex than it needs to be, and it looks to me like the GetEnabledState was intended to be placed a periodic task. The timeout of 100ms means that this is slowing down your TeleOp and causing the safety VIs to kick in.

Greg McKaskle