Week one regional control system showstoppers

[DtD]

Originally Posted by apalrd

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.

^^This. Our team (Which uses C++) could never get the camera to work, we also found out after our first match that the camera randomly decided to either cause huge robot reaction delays or constant robot resetting (Which causes even larger delays - about 5 seconds)

As for joysticks and the io board not working, it might be a power draw issue. We never had the issue but we are not using the io board.

~David