Reset subsystem states (at minimum kicker wheel) @ disabledInit

[binnur]

This issue was observed during Saturday (2/22) testing. When the robot is enabled, after a prior enabled/disabled state transition that included launcher, kicker wheel also immediately started running. This behavior can potentially cause jams if there is a ball in the slot, yet the fly wheel is not running when the robot is enabled. There is a potential for this to occur during a competition, if our robot looses communication with the radio.

robotDisabled() is a good place to reset any subsystem states -- recommend using that to turn off kicker motor and other motors (reset indexer?) that maintain states.

[pietroglyph]

I added a default command for the indexer that turns everything off. This fixes the issue, but I need to loop back and put a stop call in the end methods of the indexer commands.

…

On Sun, Feb 23, 2020 at 1:25 PM Binnur Al-Kazily ***@***.***> wrote: Assigned #152 <#152> to @pietroglyph <https://github.com/pietroglyph>. — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#152?email_source=notifications&email_token=ACTINQR5KTQCJTUQJ4WQA2DRELSUJA5CNFSM4KZ5645KYY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOW2OLPNI#event-3063723957>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACTINQWCC7E22ZQG7E6NSPDRELSUJANCNFSM4KZ5645A> .