Note Viewer

"Quote, quote, quote, quote"-Isaac

• Helped fixed drivetrain
• Isaac successfully compiled and installed numpy on the raspberry pi
• Wired gyro
• Copied over PID code from the old robot code to the new robot code
• Talked to Mike about ideas for autonomous code
  • Use area of each strip of tape relative to the other to decide which direction to strafe
  • Rotate robot so that the camera's center is between both strips of retroreflective tape
  • Simultaniously and Continuously do the 2 above until both criteria are met
    • Areas are equal, center of camera's view is between the two strips of tape
• Organized the pwm cables

• Testing of robot was made difficult because the strafe motor got really hot
• Drivetrain not 100% working yet
• TIme for numpy to compile
  • Internet slow but better than yesterday
• Realized we need to compile OpenCV from source

• Get Michael or someone from mech to fix nona drivetrain problems. (if that wasn't completed Thurs)
• Finish configuring RPi
  • goal: run these test files https://github.com/WPIRoboticsProjects/GRIP-code-generation
  • then real files we generate
• Get RPi installed on nona
• Make a cylinder-like boiler target including reflective tape, close to specs in the game manual.  We'll need this for vision targeting, in addition to the gear peg target we already have.
• Get exposure control on driverstations (Needs Work)
• Get auto-aim code from last year integrated into 2017 robot code
• 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
  • ​

prob no