Note Viewer

"We have a schedule and I made it!" -Nolan

• Ate pizza
• Attempted to measure FOV in degrees of the camera
  • put tape on the wall
• Checked to see if new gyro (navx) works
  • Acts a little weird and gives erros check tomorrow
  • Make sure it is navx that is broken in get_pid_value()
• Kyle drove frisbee bot

• Vex is bad
• Communism is bad
  • says mikhail
• The height value from grip (pixels) does not seem to be correct
  • The value ranges from 250-300, but we are not sure why. This means that the distance values are wrong..........
• The PID loop only works on omni wheels (CANT RUN ON TANKS)

• confirm and order electrical bom for new robots
• Possibly add something for PID loop to work when on tanks
  • need to find the smallest value to turn the robot while on tanks
• 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
• Start figuring out how we might manuver the robot during auto
  • Get access to network tables
  • Start by simply rotating towards the pin
  • Next attempt strafing so the robot is aligned with the pin
  • Calculate distance from retroreflective tape

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

"NO!"