2012 Field Comm. Issue Logs

[Tristan Lall]

Originally Posted by Greg McKaskle

Does the robot connect but not stay connected, or does never connect to or through the field? Are the cabled tests in the pits practice matches? what rev radio and what FW version?

Cabled tests were in the pits. It never worked with field FMS.

Radio was initially hardware A1 with 1.4; swapped with a loaner with hardware A1 and 1.21. (When I said "reflashed", I should have specified that the WPA key was updated using the kiosk; neither radio had new firmware installed.)

We verified the WPA key in the FMS and on the robot radio, and manually re-entered it. It was correct initially, and re-saving it had no new effect.

As for the build/deploy, we independently confirmed what was mentioned above: these symptoms don't match that fault. (And we made sure the code was deployed when reloading it.)

Further attempts were made: a third laptop (known good) as the DS had no effect, except under one very specific condition. The initial DS laptop (some sort of ordinary Windows PC) was connected to the field at the driver station via Ethernet, and the DS VI was started. (It indicated FMS was found.) The known good laptop was connected directly to the robot radio via Ethernet, and various software was loaded (potentially including another instance of the DS VI). At this point, the communications and robot code lights on the driver station DS VI flashed on and off intermittently, for a couple seconds at a time. Nobody had any firm idea what was going on there.