[gnunes]

I will bet a cup of coffee that your problem was caused by the fact that your Autonomous VI ended on its own. When your Auton code has finished doing everything it has to do, put it into an infinite loop (containing a 10 or 20 millisecond delay) so that the VI never stops.

I saw this exact problem at a Mid-Atlantic regional event (on somebody else's robot). The problem went away when they added that infinite loop as I outlined above.

The problem comes when the robot code tries to stop an Autonomous VI that is already stopped. Looking at the Framework code, I can find no reason why this should be a problem, but nevertheless it appears to be one that only appears when connected to the FMS.