8565 TechnicBots Meeting #15 – 1/6/2018

Team members:

 

Engineering Notebook (due Thursday night midnight)

• Overall:
• Hardware: all builders
• Software:
• CAD:

Agenda:

• Action item check
• Team alliance courtesy gestures
• Rule updates check
• Assign team members for watching and participating in FTC online forums
  • There were some online discussions of the defense strategy by forcing the opponent robot to go over the balance stone. From FTC official answers, this has been confirmed as a legal play.
• wireless communication debug guide review
  • The FTC documents described some scenarios of non-allowed wireless communications or wireless interference, besides the suspicion from Yibing. The Head Referee Patrick should have some ideas about what was going on, as he answered some similar questions online before. But he would not take any action, if our team, as a victim, did not raise any concerns. The tournament host was responsible for a clean environment of wireless connection for the tournament and they was monitoring closely on the wireless traffic on the competition site(s). If we got the FTA, WTA, CSA, and the Head Referee involved to evaluate the situation, it should be easy for them to verify whether there were Wi-Fi interference, as they had the tool(s) and the data. On the other hand, the team members should be able to determine whether it resulted from the cable connection issues and/or the software issues as soon as possible.
• Tournament Operation Guide Binder:
  • Challenge rules
  • Trouble Shooting Common issues Guide
  • Logs for the tournament
    • Team brochure
    • Robot Flyer
    • pitcrew check list
    • Driver Coach Strategy sheet
    • Driver coach observation notes / programmer tuning notes
• Tournament preparation
  • Engineering notebook
  • Team brochure
  • Scouting interview form
    
  • Robot Flyer
  • Scouting match recording google form and excel file format
  • Pitcrew check list
  • Driver coach strategy reminder sheet
    • We should have a change of plan without getting stuck in one place. 
    • End game decision on what to proceed with the time left. 
  • Driver coach match observation recording form
  • CAD model improvement
  • Prezi presentation rehearsal
• Robot improvement wrapup and driver training starts
• Programmers to go through Control System Troubleshoot guide
  • Appendix A: Tech Tips on Using Log Files (15 pages)

Action Items: (Blue means completed, Black means ongoing and Red means uncompleted)

• General
  • Everyone- Finalize engineering notebook
  • Jerry- write driver coach sheet, look at Melody’s
  • Samuel- write engineering notebook entry for 12/31
  • Samuel – update brochure
  • Jerry- add teleop for flip bot in engineering notebook
  • Abhishek- document flip bot in appendix
  • Abhishek- make bom for flip bot
  • Amanda- update scouting sheet for rating
  • Amanda- update robot flyer
  • Brandon- add auto glyph key row in spreadsheet
  • Abhishek- make pit crew list
  • Abhisehk, Evan, and Samuel- practice script, review Prezi
• Hardware
  • Abhishek- Finalize flip bot
• Software
  • Samuel- Program flip bot auto
• CAD
  • Justin- finish CAD video of flip bot, send to Evan