Note Viewer

• Split "gear" subsystem into two subsystems: "gear_funnel" and "gear_claw".  Renamed a few misc things for consistency
• Climber turns either direction but will not stop.  Need to limit when it can go in reverse, since the ratchet will stop it and motor might burn out.
• Changed a few controls mappings.
• Climber works but will not stop once started.  The commands need some tweaks to support whileHeld.  It's also possible the new 2017 robotpy controller code has an issue
• Fixed PCM CAN ID issues on comp bot, after several reboots
• Tested on practice bot: Feeder, funnel, lexan and gear claw, eject, paddles, climber, basic tank drivetrain
• Tested on comp bot (very briefly): Feeder, funnel, lexan, climber, basic tank drivetrain
• Fixed a few motor wiring issues on comp bot before bag
• Blew fuse on PDP on comp bot, not sure why.  Replace it hastily and seemed to work until we bagged.  Like a whole 3 minutes.
• Removed RPi from comp bot before bag
• Reported bug in pyfrc simulator where it doesn't know how to deal with > 1 PCM.  Response from dev said he's thinking about how to address it.
• Stole radio power cable from Nona.  Need to order more

• Very little testing done on comp bot.  Like literally 5 minutes.
• Assigning CAN IDs to mulitple PCMs is a pain.  Fortunately one-time thing.  Also unsupported by pyfrc sim, which limits usefulness of sim for us.  Hopefully they will fix.

• Order more radio power cables, plus a few USB-to-MicroUSB cables for Rpi and Switch
• Make (more) sure the code works
  • In simulator, everything works except for the gear pneumatics which I could not test
    • The simulator cannot handle 2 Pneumatic Control Modules (Maybe)????
  • Make sure all pneumatic constants are correct
• WIRE WIRE WIRE
  • Practice bot needs solenoid and TalonSRX and PI and Radio
• Try and connect to the frisbee bot
• 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

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