Skip to main content

Prototypes (Template)

Logs must contain:

  1. The requirement being validated.
  2. The data collected.
  3. Outcome and action taken.

Linked Subsystem/Requirement​

Subsystem:
Requirement ID:
Design intent:

Prototype entry​

  • Date:
  • People:
  • What we tried:
  • Expected:
  • Actual:
  • Decision: continue / modify / kill
  • Evidence: photos/videos/data

Checklist

  • Expected vs. actual captured
  • Decision made with rationale
  • Evidence linked

Instructions (numbered)​

  1. Describe the prototype, what was tried, and the intended outcome.
  2. State the expectation (quantitative if possible) and the actual result.
  3. Decide to continue/modify/kill; note rationale and next steps.
  4. Attach evidence (photos, videos, data, CAD version, code branch).

Best practices

  • Change one variable at a time; log settings.
  • Test with realistic game pieces/conditions.
  • Capture dimensions/settings to carry into CAD or code.

Common mistakes

  • No measurements; no evidence; unclear decision.
  • Ignoring wear/variance in game pieces.

Recommended tools

  • Camera/phone, simple data sheet, scale/tape, tach/temp if applicable.

Data to Collect​

  • Voltage and current
  • Setpoint vs measured value
  • Pose/heading if applicable
  • Battery voltage
  • Temperature of motors/controllers
  • Errors/faults/warnings
  • Any relevant sensor streams