Originally Posted by apalrd (Post 931993)

Lots of field problems at Kettering. We notices the same GIANT delay on the field, blamed it on the camera, removed the camera, and were fine. We have had several instances where BOOT TIMES and CODE DOWNLOAD TIMES have caused us giant problems, but those existed last year. Our biggest issue by far is that if you power on the Classmate with the FMS and Cypress board connected, it will go into FMS Lock before detecting the Cypress board and not detect the Cypress board at all. The fix is even worse. You must reboot your Classmate two times without FMS connection to get the IO board back. We are no longer shutting down our laptop ever again. We played two matches out of 7 (and won them both, btw) with only our driver, since our operators box was completely dead. What is also annoying is there is no way to detect this loss, as the Classmate sends the last good data packet to the cRio even if the Cypress board is unplugged, so we can't pull an input high and wait for it to go low. We had so many FMS problems today that matches went 1/2 hour late, and they're still around 10 matches behind.

Originally Posted by whytheheckme (Post 933307)

...Also, with regard to the First Problem, what type of compression/frame size are you using? It could be a bandwidth issue on the field, or just simply a different throughput of field equipment vs your kit router? (simply un-based thoughts, btw)

Jacob

Originally Posted by sparrowkc (Post 933352)

320x240 compression=30 fps=10

We used these settings because they were a reasonable margin below the settings that caused >1sec lag on the classmate. I doubt bandwidth was the problem. Chrisisme's answer makes the most sense to me right now, we need to look into that some more. We ended up scrapping all of our camera code and physically unplugging the camera. The lag never came back, but who knows if it was the camera's fault or not...

Originally Posted by sparrowkc (Post 931869)

Second problem
During some matches, our joystick simply did not work. Inputs on the IO board did work, and the joystick was listed in the setup tab of the DS. I know of at least one other team that had this problem. I remember it happening on and off the field. It seemed to persist across power cycles and then fix itself. Ours was a logitech 3-axis joystick. It was going through the hub, and I couldn't reproduce it after I connected it straight to the classmate.

Originally Posted by Joe Ross (Post 932096)

I believe there is another RSL flash pattern (possibly undocumented) when it's attached to the FMS that indicates that there is a SW version mismatch. It may be a fast flash, I don't remember. Someone found it during the beta when they tried to use this year's controller with last year's FMS.