Student code can't tell if connected to FMS #1
Description
The Gizmo interface doesn't tell the student processor if the FMS is connected or not. One side effect of this is that when the robot's booting up and hasn't received gamepad states yet, all of the axes report zero and any motors that are simply mapped to those axes spin at full speed until the FMS connects and starts sending complete gamepad states.
Perhaps we could add a function that indicates whether the FMS is connected or more broadly whether motion should be allowed or not.
Students could then write something like this:
void loop() {
if(!gizmo.connected()) {
stopAllMotors();
return;
}
// do actual robot things...
}