Thread: cRIO Program Delay
View Single Post
  #1   Spotlight this post!  
Unread 28-01-2009, 21:49
bomber7 bomber7 is offline
Humanoid
FRC #0585
Team Role: Programmer
  
Join Date: Feb 2007
Rookie Year: 2007
Location: CA - Tehachapi
Posts: 20
bomber7 is an unknown quantity at this point
cRIO Program Delay
I couldn't find it, but a thread probably already exists about this problem.

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? (Its not just our code, we've loaded several different templates/samples provided with windriver)