Autonomous does not run during first enable

[Bmcdonnell]

We never found the problem, but we did just redo our autonomous code and got it working.

Thanks for the advice.

[404'd]

This happened to us every time starting at our first regional. We never figured out what the problem was, but we did fix it. The NI guy at the competition came over and used the NI Measurement & Automation explorer to completely reformat the cRIO. Once we re-imaged and re-deployed it worked perfectly

[j.cole]

ours does something similar to this. The problem is that the autonomous runs too many things at once which slows it down the first time. AKA do you have multiple while loops acting independently? Thats what our problem is we have a PID loop and a drive loop. The PID loop delays the drive loop a couple seconds then it runs. So everything works but it just takes a couple seconds extra.

NOW FOR YOUR ANSWER IF IT DOESNT WORK SORRY
Preface- If you have a working one DONT TOUCH THE OLD ONE TILL OFFSEASON
1 Run your robot in Autonomous mode (if your not already). And after about a minute or 2 it should execute something (if nothing happens go no further)
2 If something happens remove/combine some of your while loops.
3 Profit

[Greg McKaskle]

If your autonomous loops are taxing the CPU too much, it is likely because one or more of them is running full speed, with no sleep function in it. This is very easy to spot and very easy to fix. Come by the NI booth or ask the CSE folks if you need assistance.

Greg McKaskle