Shooter motor sometimes stops during competition matches

[GoogleCodeExporter]

The shooter motor sometimes stops during competition matches.  This can usually 
be fixed by manually starting the shooter using the joystick.  However, time 
and shots are lost in the process.

It's not clear why this happens, but may be due to the Jaguar simply stopping 
the motor because it thinks it's lost comm with the cRIO, or for some other 
reason.  A relatively simple fix would be for the code to repeatedly command 
the cRIO to start the motor when the code wants the motor running, rather than 
just commanding it once.

Currently, the RunShooter command just calls runTheShooter() once, then exits.  
Instead, it could call runTheShooter() repeatedly via Execute(), and never exit 
- until interrupted.  Since RunShooter requires the shooter subsystem, any 
commands which do anything else to the shooter should interrupt the RunShooter 
command.

Original issue reported on code.google.com by jtec...@gmail.com on 25 Mar 2013 at 12:16

• Blocked on: #28

[GoogleCodeExporter]

Original comment by jtec...@gmail.com on 25 Mar 2013 at 12:25

• Now blocked on: #28

[GoogleCodeExporter]

Original comment by jarr...@corr.org on 30 Mar 2013 at 10:52

• Changed state: Verified