Edit

Note Viewer

Electrical 2017

Attendance

Note Info

Students
Mentors
Date & Time
Location & Author

  • David S.

  • Adam P.

  • 1/12/2017

  • 3 hours

  • Shapland Shop

  • Alexandre G.

Notes

*Russian words we don't understand* -Mikhail

Work Completed

  • Talked to Mike about preventative measure with regards to the electronics on the robot.
  • Worked on the nonadrive code
    • Copied over the commands and controls folders from the old robot
  • Stripped 6-awg wire with an X-acto knife
    • Adjectives to describe this project: mildly dangerous, unnecessary, for the team
  • Isaac brought the raspberry pi in to the shop
    • Descriptors: surprising, great, fantastic, timely
    • Exclamations often accompanying this event: "WOW!", "Finally", "You had that?", and "What? I can't hear you a saw is running! You brought pie for us? Nice!"
  • Successfully tuned out 75% of the loud noises surrounding the table
  • Used the pulsinator

Challenges

  • Not yet sure exactly how the Tank Drive code works
  • Unable to stop the command line from spewing errors when deploying code making it very difficult to read the errors.
  • Tried to access the internet while still connected to the robot
  • Helped mechanical connect a battery to a motor for the climber and there were issues
    • Issues included that the problem was already solved and Isaac wasted his time

Work for Next Meeting

  •  
  • Write the code for nonadrivE
    • First step is to simply get the wheels turning
    • Try and find a way to make the robot turn
  • fix da pi
  •  
  • Put sensors (gyro/accelerometer?) on nonadrive

 

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?

Sure