- Continue work on moving to the peg
- At the moment, we are constantly checking distance values to see how far we are, but we need to do something like "rotate_to_gear" where it checks the value once and then moves to it
- This might mean using encoders to see how far we have moved
- confirm and order electrical bom for new robots
- Work on auto mode that follows path, similar to one we'd need to get to a peg, test and see how consistently it can be navigated
- Work on electrical organization for new robot.
- Auto strafing based on position values from camera and network tables
- Test out the NavX more, decide if it's a better gyro than our regular gyro, and what other features might be useful.
- If not using NavX, do some testing with the gyro to see how far off the values are, seeing if it is possible to fix the inaccuracies...
- Get streaming working well on raspi
- Probably use custom python http server in vision_helper script
- example http://answers.opencv.org/question/61070/streaming-http-server-from-inside-opencv2-python-script/
- Get exposure control on driverstations (Needs Work)
- works on linux, not windows
List from Mike (preventative measures):
- Batteries
- Battery Beak, logging and tracking internal resistance
- Make a google spreadsheet to track battery data
- Use computer to collect data/make a graph about voltage over time
- Put meaningful labels on the batteries
- Build load testing board
- Power Distribution Panel
- Can read voltage/current on every port
- Could be used for diagnostics
- Make a checklist
- Learn how to read LED indicators on all components
- Guidlines for checking wire integrity
- Unit tests in robot code
- Check to see if sensors are working?
- Motors running correctly
- Battery has enough voltage
- Check the pneumatic pressure as well as solenoids
- Useful for prematch/prebagging​
- Voltimeter between the various locations
- Sensors
- Range finders - analog IO -> RIO (code)
- Touch sensor - digital IO -> RIO (code)
- Checkout Code // Comptetion Code