Robot code delay on startup

[flippy147852]

When we first enable the robot after startup, there is a five to ten second delay before we can operate the robot. We have no errors or extra code that would cause this, so if anyone knows whether this should happen or how to fix it, please let us know. Thanks!

[DominickC]

I'm experiencing this as well with a brand new 4-Slot cRIO.

[Greg McKaskle]

I've seen this happen when Begin was allocating a number of things that fail out --serial and camera can both contribute.

One thing I often do is to put a small wire from the i terminal to the edge of the loop. For teleop, that turns into a feedback with a +1. Then I can probe some of these spots and see which loops are running, which are not, and get a sense of performance. A step up from this in terms of info is to use the Elapsed Times VI in the Support folder. You place this wherever you like and open the Elapsed Times to see the rate info.

This should help narrow down which code is responsible.

Greg Mckaskle