Autonomous Robot Design Competition¶

Course Overview¶

• Institution: MIT
• Course code: 6.270
• Track: Capstone Design and Engineering Practice
• Tier: B
• Role: Supplement
• Level: Not standardized by provider (use prerequisites)
• Last reviewed: 2026-07-28

MIT's Autonomous Robot Design Competition preserves valuable competition design and team-project methods, while its obsolete controller and sensors make the hardware implementation unsuitable for direct reproduction.

Why choose this course

Supplement course. Useful for specific topics and best paired with a more complete mainline resource.

Before you start

• Recommended foundation: Introduction to Electrical Engineering
• Recommended foundation: Electronics Laboratory and Measurement
• Recommended foundation: Programming and Engineering Computing

Verifiable learning outcomes

• Explain the core models in Capstone Design and Engineering Practice, including their assumptions and limits
• Complete a reproducible experiment or implementation with raw data, parameters, versions, and verification

Workload and pacing

7 weeks at 6 hours/week. This maintainer planning estimate is derived from course role and the density of public practice and labs; it is not a provider workload promise. Pilot two weeks while logging instruction, practice, lab, and review time, then adjust the remaining plan when actual effort differs by more than 25%.

Safety level

Simulation only. The default practice scope is software, computation, or simulation only; a lab label in the resource inventory does not authorize connecting physical equipment, and any hardware extension requires provider-scope verification and a new risk assessment.

Course Resources¶

Software, hardware, and cost

Software

• Maintainer-suggested open-source/free verification path: Git, Markdown, automated tests, and a project-appropriate KiCad, FreeCAD, Python, or HDL toolchain
• The resource inventory lists public code coverage; pin interpreter, dependencies, toolchain, datasets, and PDK versions where applicable

Hardware

• The resource inventory lists lab coverage, but this course's maintainer path explicitly limits it to computational or simulation work. It assumes only a general-purpose computer able to run the software above and retain results; do not purchase or connect prototype components, current-limited power, measurement equipment, safety controls, and spares selected after requirements and risk review

Cost note

The current maintainer path uses computation and simulation only, with no dedicated hardware purchase, and prefers open-source/free tools. This is not a provider requirement; platform, commercial-software, or cloud-compute costs still vary by provider, region, and plan.

Public resource coverage

Resources and access

“Listed by official page” means the link was discovered on a successfully fetched official source on the verification date; it does not guarantee that every region or account can open the target directly. Access does not grant redistribution rights. Re-check the provider page, target link, and third-party notices before downloading, adapting, or publishing material.

Practice and Verification¶

Practice loop

Autonomous Robot Design Competition · MIT 6.270: Requirements-to-Verification Safe-System Digital Prototype

This is a maintainer-suggested self-study project for Autonomous Robot Design Competition · MIT 6.270, not an official course assignment. Complete a cross-circuit, software, or control digital prototype for Capstone Design and Engineering Practice, connecting requirements, architecture, cost, risk, tests, and postmortem while keeping every high-risk physical element in simulation.

Origin: Maintainer-suggested project

Deliverables

• At least ten traceable requirements plus stakeholders and boundaries, architecture, interfaces, risks, and cost baseline
• Digital-prototype sources, interface contracts, test fixtures, and continuous-integration configuration
• Requirements-to-test traceability matrix, raw test, performance, and cost data, and change log
• A final design report, demonstration video, and project postmortem with root causes and follow-up actions

Verification

• Link every requirement to at least one repeatable test and pass 100% of critical requirements
• Cover startup and shutdown, minimum and maximum input, interface loss, timeout, and resource exhaustion
• Recompute at least five key metrics with an independent checker and match the report
• Inject one cross-module fault and show monitoring or degradation reaches the declared safe state in time

Reproducibility

• Commit all requirements, designs, sources, tests, BOM or cost evidence, and a README
• Pin toolchain, dependencies, configurations, data versions, seeds, and one-command build and verification
• Preserve raw test data, build-artifact hashes, change and decision records, and the generated report

Safety boundary: Simulation only — Default to a digital prototype; do not physically implement mains, high voltage, high current, energy storage, RF power, lasers, moving machinery, vacuum, chemical processing, or human-related work unless moved to a compliant facility under qualified supervision and a new risk approval.

Risks, gaps, and boundaries

The controller and sensors are obsolete, so this should be used only for design-process and competition-method lessons.

Completion evidence

• Weekly learning log with time, questions, corrected errors, decisions, next steps, and links to that week's reproducible artifacts
• Design-review package with requirements and constraints, trade-offs, editable sources, applicable ERC/DRC/timing/stability checks, exports, and a reproduction test
• Code repository with pinned dependencies and toolchain, a minimal run command, tests or waveform/benchmark checks, expected output, and license notes
• Simulation package with model or netlist, inputs, solver and version, parameter-sweep script, benchmark comparison, expected results, and one rerun command