[Tanner]

Sunny's right - it could be sensors. Specific sensors like the gyro, need time to initialize, whilst others do not. I can't exactly remember how much time is recommended for the gyro to initialize, but I don't think three seconds would be it - sounds too long.

Also, the mass amount of stuff to initialize could be it. If you are using a lot of motors, sensors, servos, or anything else - it could take a long time for the cRIO to create them all and initialize them all. I haven't seen this in experience with teleoperated, though I'm not sure about autonomous - we haven't exactly thought about that yet.

Another thing it could be if a student has placed a wait sub-vi in the autonomous initialize block (assuming they use LabView). If one is there, it literally pauses the entire program, while waiting for the time to pass. Its not exactly a possibility that it could happen, but it is a cause.

Hope this helps.

-Tanner