2012 Field Comm. Issue Logs

[Tristan Lall]

Although probably a different issue than is being experienced by the others, 253 at SVR has been consistently unable to connect to the field. The robot works correctly on the tether, but will not communicate with the FMS.

So far, the cRIO-II has been imaged (v. 43, 2012-01-20 imaging tool) and replaced, code has been recompiled and reloaded, the radio has been reflashed and replaced, and all of the cRIO modules have been either checked or replaced (a sidecar and bad 37-pin cable were replaced). The robot is running C++ code and Jaguars over PWM.

The system has been tested with two driver station computers: a regular laptop and a loaner classmate. Neither works on the field.

I have a couple more wild theories: can anyone sanity-check them?

Firstly, what would happen if the WPA key given in the kiosk and the one from the FMS were inconsistent? Would we see red indications for code and communications on the dashboard?

Secondly, wasn't there something in the LV code (and maybe C++) where you could run code from the laptop, but it wouldn't be installed on the cRIO? I haven't seen that in a while, but maybe the team has an incorrect build option set? (I don't think this is it, though, because the robot flash codes seem to indicate it's running code.)