[jwhite]

Yeah, the drivers were supposed to run with netconsole on, but it was among a variety of things that didn't get done :-/. That'll be something we hopefully remember tomorrow.

The vision code is all in it's own thread, and only executing 4 times / second; the FRC log viewer doesn't show extreme cpu usage (in fact, cpu usage looks quite reasonable right along).

Again, it's puzzling - this all works fine in the pit. And while we're arguably 'wrong' on the 0.1/0.04 thing, we have to work really hard to get it to trip just once in the pit, and from what you've said (and my reading of WPILib source code), that wouldn't explain what we're seeing.

What's tough is that at this point, the safe thing to do is just run without vision. Risking a 0 point match during quals is just too high risk. It's really a shame we have such limited access to the 'real' conditions - it really makes this hard.

Thanks for the suggestions; others gratefully taken. Puzzlers like this are frustrating!

Cheers,

Jeremy