[Greg McKaskle]

I was talking about pulling the USB cable and reinserting it. I'm not suggesting this is happening on the robot when you aren't looking or anything. I'm suggesting it as a debugging tool. Anytime the USB camera code errors out, it closes, opens, and sets the properties such as exposure to the requested values. If this works, it means that the LV session saw the property be set, but the camera either rejected it or perhaps another property interfered.

I agree that the different ways of running your code should work the same, and except for some uninitialized shift registers in our code, our robot generally does that. At least I think it does.

What about the navX is different?

Greg McKaskle