Difference between revisions of "FRC 1640 Punchlist"

From DEW Robotics
Jump to: navigation, search
(Programming / Control)
 
(13 intermediate revisions by 3 users not shown)
Line 1: Line 1:
==Mechanical Prototyping==
+
We are making the transition from prototyping to fabrication.  It's time to (finish designing and) build a robot.
* Prototype slingshot to determine accuracy of shot positions, including by pipe (pullback) adjustment
 
* Prototype roller frame for required rise (without or with forks)
 
* Prototype JVN catapult to determine accuracy of shot positions and how to load
 
  
 
==Mechanical Fabrication==
 
==Mechanical Fabrication==
 
* Pivots
 
* Pivots
* Field pieces
+
** Complete cutting and key the 7075 Al transfer axles
* Shop organization tools
+
** Key and cut retaining clip groove into 4140 steel co-axial drive shafts
 +
** Fabricate angle sensor mounts
 +
** Key 32T Al pulleys (1" diam)
 +
 
 +
* Chassis
 +
** Complete gussets
 +
** Finish welding Deux
 +
** Start welding Prime
 +
 
 +
*Slingshot
 +
** Complete rough cutting 1 x 1 square tubing
 +
** Finish square tubes with non-square ends
 +
** Cut gussets
  
 
==Design==
 
==Design==
* Stack-style chassis CAD for early plywood cut (Molly)
 
* Stack-style chassis tradeoffs (Ben, Gary, Siri, Clem, Molly, Kira)
 
 
* Layout basic state logic with programmers (Siri, Julie - draft done)
 
* Layout basic state logic with programmers (Siri, Julie - draft done)
 
* System-level ball routing, ball auto-ejection, manipulator tensioning
 
* System-level ball routing, ball auto-ejection, manipulator tensioning
  
 
==Programming / Control==
 
==Programming / Control==
# All programming team members need to install LabVIEW and FRC software on a personal computer (see [[DEWBOT_X_Programming]] for details)
+
* All programming team members need to install LabVIEW and FRC software on a personal computer (see [[DEWBOT_X_Programming]] for details) -- '''Make sure ''FRC 2014'' appears when starting LabVIEW'''
# LabVIEW and FRC software needs to be installed on the team's computers: the driver station laptop and the IBM ThinkPad
+
* All programming team members need to complete the certification test  
# All programming team members need to complete the certification test during the meeting on Wednesday, 1/8, if they have not already completed it
 
# Preliminary list of programming products needs to be created
 
# The programming team needs to organize into product sub-teams
 
 
 
 
* Position and angular error spread for autonomous movement (by revolution counts) via testing procedure (Pat, Julie, Siri - procedure documented)
 
* Position and angular error spread for autonomous movement (by revolution counts) via testing procedure (Pat, Julie, Siri - procedure documented)
* Demonstrate move to/wait for Hot Goal
+
** Tweaks to keep in mind for tach-based autonomous driving (kept here as reminders for any new code):
 +
*** Wheel initialization -- e.g. rotate 360 degrees (no shortest distance), then back 180 degrees
 +
*** Ramp up drive power based on revolutions reported by encoders
 +
** Gather tach-based autonomous driving trial data -- '''FOR EACH COMPETING ALGORITHM'''
 +
*** ''Should still compare two versions: tach-vs-tach and tach-vs-expected'' ?
 +
* ''Demonstrate move to/wait for Hot Goal'' -- N/A?
 +
* '''Demonstrate dashboard-to-robot-code communication -- HIGH PRIORITY'''
 +
* '''Design dashboard layout with drive team -- HIGH PRIORITY'''
 +
* '''Finish translation of automated tasks strings into motor/solenoid commands -- HIGH PRIORITY'''
 +
* '''Autonomous sequence needs to be implemented'''
 +
** Typical "primitives" approach is not going to work
 +
* '''CODE REVIEW on Wednesday''' -- All available programming team members should participate
  
 
==Scouting==
 
==Scouting==
Line 35: Line 49:
  
 
==Welding==
 
==Welding==
* Complete machinist's shelf unit  
+
* Build a shelf storage unit for the welding area giving welding team much needed practice.
 +
* We've been using alloy 4043 for all our robot welding. However, alloy 5356 may be a better choice.  It is more ductile and stronger especially in
 +
shear, which it what many of our chassis joints are subject to.  We need to devise a simple test to evaluate.
 +
* Weld pivot tubes to pivot tops
 +
 
 
----
 
----
 
[[Category:DEWBOT X]][[Category:DEWBOT X Build]][[Category:Organization]]
 
[[Category:DEWBOT X]][[Category:DEWBOT X Build]][[Category:Organization]]

Latest revision as of 03:12, 24 February 2014

We are making the transition from prototyping to fabrication. It's time to (finish designing and) build a robot.

Mechanical Fabrication

  • Pivots
    • Complete cutting and key the 7075 Al transfer axles
    • Key and cut retaining clip groove into 4140 steel co-axial drive shafts
    • Fabricate angle sensor mounts
    • Key 32T Al pulleys (1" diam)
  • Chassis
    • Complete gussets
    • Finish welding Deux
    • Start welding Prime
  • Slingshot
    • Complete rough cutting 1 x 1 square tubing
    • Finish square tubes with non-square ends
    • Cut gussets

Design

  • Layout basic state logic with programmers (Siri, Julie - draft done)
  • System-level ball routing, ball auto-ejection, manipulator tensioning

Programming / Control

  • All programming team members need to install LabVIEW and FRC software on a personal computer (see DEWBOT_X_Programming for details) -- Make sure FRC 2014 appears when starting LabVIEW
  • All programming team members need to complete the certification test
  • Position and angular error spread for autonomous movement (by revolution counts) via testing procedure (Pat, Julie, Siri - procedure documented)
    • Tweaks to keep in mind for tach-based autonomous driving (kept here as reminders for any new code):
      • Wheel initialization -- e.g. rotate 360 degrees (no shortest distance), then back 180 degrees
      • Ramp up drive power based on revolutions reported by encoders
    • Gather tach-based autonomous driving trial data -- FOR EACH COMPETING ALGORITHM
      • Should still compare two versions: tach-vs-tach and tach-vs-expected ?
  • Demonstrate move to/wait for Hot Goal -- N/A?
  • Demonstrate dashboard-to-robot-code communication -- HIGH PRIORITY
  • Design dashboard layout with drive team -- HIGH PRIORITY
  • Finish translation of automated tasks strings into motor/solenoid commands -- HIGH PRIORITY
  • Autonomous sequence needs to be implemented
    • Typical "primitives" approach is not going to work
  • CODE REVIEW on Wednesday -- All available programming team members should participate

Scouting

  • Layout preliminary match and pit UI sheets and Excel/Tableau files
  • Lock down prioritize (first generation) metrics

PR

  • Paint more hats
  • Plan/start videos (at least release video)
  • Vests and sweatshirts

Welding

  • Build a shelf storage unit for the welding area giving welding team much needed practice.
  • We've been using alloy 4043 for all our robot welding. However, alloy 5356 may be a better choice. It is more ductile and stronger especially in

shear, which it what many of our chassis joints are subject to. We need to devise a simple test to evaluate.

  • Weld pivot tubes to pivot tops