Edit

Note Viewer


Electrical 2017

Attendance

Note Info

Students
Mentors
Date & Time
Location & Author
  • David S.

  • 2/2/2017

  • 3 hours

  • Shapland Shop

  • Alexandre G.


Work Completed

  • ELECTRICAL PASSED THE 40% MARK ON PERCENTAGE OF TOTAL NOTES!!!!
    • This actually isnt good, because it means the other groups are slacking...
  • Isaac worked on raspberry pi with David
  • Changed the contour code in grip which was giving bad values for height
    • It now gives the right values for height which range from about 30-100
  • Fixed equation for calculating  distance
    • Correct to withing about 2 inches (more testing needed)
  • Added a turinary operator in PID code which allows for us to turn when on tanks AND omnis

Challenges

  • We failed to write good code for the grip file which needed fixing
  • There seems to be an issue with the navx gyro, so I switched the PID loop back to the regular gyro.

Work for Next Meeting

  • Do extensive testing on the distance formula for the robot
    • Try and fine tune it
  • Figure out how we can move the distance we calculated
    • Make a command that drives to the peg the correct distance.
  • 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
      • 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?

I don't know