[LukeS]

We experienced what were usually short blips where we could not control the robot, and it simply sat there. The FTAs would comment that they usually saw the comm blip, but we never saw comm drop on our driver station. One of the FTAs (Jerry) inspected the logs from our driver station, During the time that we lost control, the battery reported constant voltage, confirming that nothing was running on our robot. Nothing in the log looked "wrong." When we regained control, the ping time would spike.

We suspected that it was a bad USB cable connecting our OI, and that we really did stop giving the robot commands. However, we replaced the USB cable, and the issue persisted.

- Team 1024
- Which event? Boilermaker
- Wireless bridge radio HW revision? (A1, A2, or B1) A, can't verify A1 or A2 until I can get into it at Cincinnati.
- Radio firmware rev? I'll check at Cincinnati
- Programming language? Java
- Using a dashboard app? SmartDashboard
- Using vision with Axis Camera and cRIO processing? No
- Using vision with driver station processing? No We would, but left the camera power unplugged for fear of it causing more comm issues.
- Did you have the radio mounted near motors/large metal structure? Mounted on a metal panel near metal tubes and near 2 Jaguars
- Using classmate as driver station? No, an HP 6530b
- 4 or 8 slot cRIO? (FRC-CRIO2 or Old version) 4 slot
- CAN Jaguars? What FW version? All version 101