Startup Delay, Effects Everyone?

[bomber7]

Originally Posted by bomber7

The cRIO works great, our code works, however even with default program code the cRIO seems to follow this time table. (Approximitly)

000s cRIO turned on.
040s Labview dashboard begins receiving data.** (As well as Driver station)
080s User-created code begins to run.

I am using the windriver development enviroment.

If I'm not mistaken an 80 second delay between the turn on of a robot and the start of its usefulness will prove too long for the way we normally do competitions. It also makes testing a real pain.

Is this problem widespread or are we just having some kind of funny bug?

Yes I quoted myself >.>

I want to know if everyone is having this problem or just me? Its pretty ridiculous to have to wait 80 seconds before the robot becomes responsive.

I'm using windriver, but if the problem's part of the cRIO it could affect lab view too.

If your having this problem please, please say so. If not, I would like to know that too.

**Clarification, at 40 seconds, by the dashboard begening to recieve data, I mean the mode displays disabled, and the status says "connected"
I know that the dashboard is always recieving data as long as the cRIO is turned on.