Note Viewer

• Determined massive packet loss was the cause of the stuttering motors
• Spent most of the time trying to narrow this down.  Rebooting DS laptop solved it, until we opened Wing.  While Wing is open it loses most packets every 15 seconds, for several seconds each time.  Adam will contact Wingware guys about this.
• Tweaked RPMs on shooter wheel, got to the point where it makes all but a few balls out of a full bin, at a height 1 tote lower than real goal (lowered it so it wouldn't hit ceiling)

packet loss

• Continue testing/iteration on gear mechanism
• Get Rpi running vision code again, start auto behavior
  • See how well it works if we have to drive then turn 30 degrees in the case that we do not get the middle starting position.
• 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
• Auto strafing based on position values from camera and network tables
• 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
• Try and connect to the frisbee bot

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
    • Resistors!
• 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
  • ​

nope nope nope