Edit

Note Viewer


Electrical 2017

Attendance

Note Info

Students
Mentors
Date & Time
Location & Author
  • Adam P.

  • 2/28/2017

  • 3 hours

  • Shapland Shop

  • Adam P.

Guests

Sam Knight


Work Completed

  • Updated pyfrc on DS, so simulator works again without gagging on our 2 PCM modules
  • Enabled shooter wheel PID.  Started tuning values, but needs more testing/tuning.  
  • Added logfile dump of shooter wheel velocity, so we can graph it.
  • Isaac started working on script to turn dumped CSV values into graphs
  • Learned SmartDashboard can graph any value over time, so will check that out
  • Re-enabled gyro-based drive correction for forward/back and strafe.  Tuned the values, but might need more tweaks
  • Named the RPi units, with only about 30 minutes of debate among the whole electrical team

Challenges

names are hard

Work for Next Meeting

  • Continue tuning shooter PID
  • Continue work on moving to the peg
    • 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
    • ​

On Schedule?

no