Note Viewer

• Adam showed Erika and Sam P. how to configure & use data from Limelight
• Billy showed Malia some wiring stuff with the drivetrain encoders on Octa
• Tried to work out what's wrong with the left drivetrain encoder in Octa's code. Didn't find a solution yet.
• Imaged Saba's roborio for 2020.  Vasista installed robotpy 2020 stuff on it

• left DT encoder isn't posting values

1. Figure out what's wrong with Octa's left DT encoder
2. Continue testing vision stuff with Frisbee (until Octa is available again)
   1. Add drivetrain "turn to angle" command to Frisbee code, for testing.
   2. Create DT command to align the robot with the port target, using the limelight's "tx" value from NetworkTables
   3. See if we can get the limelight to tell us distance-to-target for setting shooter range/speed
   4. 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.
3. Get drivetrain sensors working again on Octa, start working towards autonomous stuff
   1. 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.

yeah