Take an exit with dignity

[Tom Line]

Originally Posted by Don Rotolo

Quoted for truth. I have no doubts that the 134 alliance would give us a run for our money.

I went over to offer any help at all after the first failure, watched as they tethered, and saw the motors run with my own eyes. Something similar happened to us in NJ (no joystick response coming out of Auton) that was "fixed"* by plugging both USB Hub connectors into the robot (I started a thread about this just after NJ), but 134 was using only 2 joysticks, so USB power consumption was ruled out. I also advised them to consult with the FTA, which they did.

My heart sank to the ground when it happened a second time.

Sure, we like to win, but only in a fair fight. What happened just stinks.

Somehow, the actual cause needs to be identified, we can't just chalk it up to some random event.

Don, we had the /exact/ same issues during a match at Western Michigan. We have never had communications problems. Nor have we had on-the-field code problems.

When the match started, our robot went through autonomous. When it shifted to teleop, our drivers had NO control. Pushing F1 to refresh the USB devices did not work. Our quick thinking driver unplugged all the USB and plugged it back in, and voila, we had joysticks.

Our classmate is at 100% battery all the time. We charge it with an inverter on the cart when it isn't plugged into an outlet. Our human player (who is also a programmer) is methodical and incredibly competent. We KNOW we did nothing wrong that match.