Skip to main content

Week 2: Prototyping and Validation

Schedule constraint: Mon/Wed/Thu 2:30–6:00 pm (~10.5 hrs).

Goals​

  • Fuel prototype scores in active hub; measure cycle times per 25 s shift.
  • L2 climb rig built and tested within endgame window.
  • Hub-state timer running in code; dashboard shows hub state.
  • Data logged (video + temps/currents) for 10-run sets.
  • Test log template used (date/config/RPM/angle/success %/notes).
  • Jam scenarios matrix for intake/indexer drafted.

Plan & time budget (ETA ~10.5 hrs, Thu as buffer)​

  • 2.0h: Build/tune fuel prototype; log 10 shots, adjust RPM/angle.
  • 2.0h: Build L2 climb rig; test lifts with timer and current limits.
  • 1.0h: Hub-state timer integrated to dashboard; confirm shift cues.
  • 1.0h: Run 10-cycle test in a 25 s shift window; record times/temps.
  • 1.0h: Debrief, adjust parameters, update docs.

Checklist​

  • Fuel prototype 80% on 10 shots in active hub
  • L2 rig lifts to legal height within endgame window
  • Cycle time measured for one 25 s shift (documented)
  • Hub-state timer visible on dashboard
  • Video + data logs stored in testing folder
  • Test log template filled for runs (config + success %)
  • Jam scenarios matrix drafted
  • Risks/dependencies updated

Owners​

  • Mech/Proto Lead: fuel prototype, climb rig
  • Software Lead: hub-state timer/dashboard
  • Drive Coach: run timed shift cycles, video

Risks and mitigations​

  • Risk: Prototype misses accuracy. Mitigation: adjust wheel/speed/angle; document fails; keep scope tight.
  • Risk: Climb motor overcurrent. Mitigation: enforce current limits; timeouts on lift.

Priorities (P0 must, P1 should, P2 stretch)​

  • P0: Fuel proto 80%/10 shots; L2 rig within endgame window; hub-state timer live; timed 25 s shift test logged.
  • P1: Test log filled with RPM/angle; jam scenarios matrix.
  • P2: Explore alternate intake tweak if time allows.

Time tracking tips​

  • Use a stopwatch for each test set; log setup time vs. run time.
  • If a test fails twice, log the issue, adjust once, and re-run—don’t burn all session.

Tips for students​

  • Film every run; write the RPM/angle on tape near the proto for quick reference.
  • Change one variable at a time (speed OR angle) when tuning.

Tips for mentors​

  • Keep test blocks short and structured; assign a scribe for logs.
  • Watch current draw during climbs; stop if limits exceed plan.