[Kevin Sevcik]

Originally Posted by willson.thomas

I think the best implementation would be to simply disable the robot if a joystick is disconnected, and to also require a power cycle to re-enable the robot. This would make sure that no bad data/timing error caused by the disable would make the robot behave erratically.

Problematic and probably overkill. How do you implement default code that doesn't need to be changed to run a robot if missing a joystick means the robot won't run? Plus, disabling the whole robot when a joystick read fails probably takes more work.