Finish Drivetrain subsystem

[jcorcoran]

This subsystem is already started, but it needs the encoders added to each side of the drivetrain, and methods to allow their values to be used. It also needs some methods to allow each side of the drivetrain to be driven independently.

See last years robot code for example: https://github.com/Team2168/FRC2013_Main_Robot/blob/master/FRC2013_Main_Robot/src/frc2168_2013/subsystems/Drivetrain.java

Be sure to follow the git workflow guide for creating a branch and submitting your code to the repository for review: http://forum.team2168.org/viewtopic.php?f=9&t=6

[jcorcoran]

@shilohfeldman @Benmw99 @inkinc Where are you guys at with completing this subsystem?

We're going to need this code early next week for testing the drivetrain.

[Benmw99]

@jcorcoran What exactly still needs to be done to complete the drive train so it is functional?

[jcorcoran]

I think the subsystem itself is good. It needs to be pulled into master. Unfortunately you guys started working on commands in the same branch, and those commands are not done/working as far as I know.

There are separate issues for those commands. I would suggest:

• making sure the commands in the drivetrain branch compile.
• create a pull request, to merge the drivetrain branch into master
• create new branches to work on the different drivetrain commands. These commands should include one to rotate to a specific angle, one to drive a specific distance (Straight), and a command for driving the drivetrain with joysticks.
• once thedrivetrain branch is merged into master, this issue can be closed.

There should be issues for each of these created already.