[Chris_Elston]

I think I read somewhere that it takes 3 seconds for the CMUcam to either initialize or send packets. Does anyone know for sure which one is taking the 3 seconds?

We noticed today that from the time you power up the robot until about 3 seconds later, we would finally get some sort of life out of the robot, like responding to the joysticks.....

It seems very evident that during this 3 second camera power up the CPU is still holding up the scan (program pointer) and nothing else will work.

Is there any work around for this? I see this a problem in autonomous mode mostly, unless the camera is initialize on power up, we walk off the field, and it's ready before the master computer throws the big switch to go fully auto...

So we need to Start the camera as well, BEFORE autonomous mode?

I guess it would help to know where the 3 second delay is happening. In the initialize function? In the start function? In the capture data function?

Maybe we are too paranoid... ;-)