2018:Programming

General programming stuff relevant to all subsystems should be documented here.

Outstanding Tasks

Split up by subsystem - responsible veteran student in (), student(s) doing actual code, if different, in []. These are not in any particular order!

• Review questions for mechanism teams and get answers (Kate, Ethan)
• Document on Wiki (or link to gdocs) autonomous modes. Include Names/Number assignments for Dashboard/Controls to use (Kate, Josh)
• Controls: document which specific model of gamepads we will use this year (Kyle)
• Controls: Start deciding and documenting, with controls team and potential drive team input, what buttons/axis/whatever control all mechanisms. Document on IO Map page on wiki (Kyle)
• Drive: Test/Evaluate new gyro (SPI-based interface instead of analoggyro - already installed on test board) (Josh)
• Drive: Examine auto modes and decide what range(s) of auto driving actions need to work the best, then make them happen (Josh)
• Auto/Vision: Where on robot do(es) camera(s) need to go? Document on Robot Design page on Wiki and talk to relevant design teams so they carve out that place!  (Kate)
• Old robots: Bring 2015, 2016, 2017 all up to 2018 image and ported code. Test. (anyone, but this is super low priority)

 

 

Programmers:

Controls: Kyle & Adrian & Cameron

DriveMeyer: Josh

Arm/Intake: Kate & Ethan

Ramp: Kate & Josh

Auto: Josh & Kate

Lights: Zack E

 

 

Autonomous

Do nothing

Cross auto line

Sense switch and place cube in switch and cross auto line

Programming Sub-pages and Links

• Documentation
  • WPILib_Screensteps
  • WPILib documentation
• SVN
  • SVN Setup
  • Online browsing of our SVN Tree
• 2018:Robot_IO_Map

Programming Archives

• 2017:Programming
• 2016:Programming
• 2015:Programming
• 2014:Programming
• 2013:Programming
• 2012:Programming
• 2011:Programming
• 2010:Programming
• 2009:Programming