[BradAMiller]

The camera waits a few seconds after the robot controller is started before initializing. The idea was to make sure that the camera had finished its own initialization before sending commands. The debug output you saw was the camera code in EasyC trying to initialize the camera and it not responding. You should see a bunch of commands followed by ACK messages (acknowledgment). If you only see commands being sent to the camera and no ACKs then it isn't getting your commands or it is in some strange state. I've occasionally seen a similar problem, and recycling the power seems to always fix it. I think the camera gets into some state where it doesn't accept commands.

There is no code in the EasyC runtime that does anything with the drive motors while the camera is initializing. I might suggest doing all the initialization in the Initialize() function if you're not already doing that. The IFI master code will prevent any PWM outputs from happening until the match actually starts (either autonomous or operator control). That way all the initialization (camera, gyros, etc.) is completed while the robot is sitting on the field waiting for autonomous period to start.