Finish updating Octa's PIDController stuff to 2020 [Adam]
Following recently arrived in shop. Put them in appripriate electrical place, and maybe test them out on a robot, make sure we know how to code them. Line break sensors, Potentiometers for shooter, servos for shooter
Further discuss the placement of the encoder. Currently, we're thinking about integrating it with the motor (under the turret contraption). However, backlash is a possible concern. We should ask Adam, Chris, and other mentors for their opinions.
Continue testing vision stuff
- Maybe move limelight from Frisbee to Octa?
- Create DT command to align the robot with the port target, using the limelight's "tx" value from NetworkTables
- See if we can get the limelight to tell us distance-to-target for setting shooter range/speed
- Until we have a working turret shooter to play with, we can continue working towards making the robot rotate to align to a target using shortest path, but also handle cable bundling we'll have on the turret. Meaning the turret won't be able to spin > 360 degrees, it will need to rotate the other (long) way sometimes to keep slack on the cables. We haven't written PID code like that before, so something to explore.
- Get drivetrain sensors working again on Octa, start working towards autonomous stuff
- Create a drive command that moves robot straight X feet. Drive correction can use either gyro or DT sensors, we've done both in the past codebases.