Skip to content
CrocoDocs
Starter GuideProgrammingEngineeringDesignPortfolio
Documentation
EngineeringYour first engineering build

Design

Game strategyDesign processCAD and robot integration

Mechanical fundamentals

Structure and fastenersShafts and bearingsMotors and gearingServosGearsBelts and chain

Mechanisms

DrivetrainsLinear slides and riggingArms and linkagesIntakes and grippersTransfersTurretsFlywheels and launchers

Manufacturing

MaterialsFits and tolerances3D printingMachining and fabrication

Electrical and wiring

Electrical and wiringWiring and powerConnectors and cablesPower faults and ESDSensor integrationMulti-turn position

Build and compete

Assembly and serviceabilityMechanics and controlTesting and reliabilityEngineering notebook

Reference

Engineering glossaryEngineering resources
Appearance

Design process

Set requirements, compare designs, build prototypes, and test the decisions you make.

The engineering design process uses requirements, alternative designs, , and tests to decide what to build. Each revision should answer a question about the design.

Design requirements

"Build an " already assumes a solution. "Acquire the object while the approaches with imperfect alignment" identifies a problem several might solve.

Separate , which the design must meet, from targets, where you can accept a compromise. Size limits, workshop tools, and a fixed deadline are constraints. Pickup time, mass, and miss rate are targets until the team decides on a firm limit.

RequirementVerification
Object stays captured during the intended turnDrive the same turn with a retained object
Intake tolerates the chosen approach offsetTest marked lateral and angular offsets
Module can be replaced between practice runsTime a replacement with the actual tools

The specific target values should come from your strategy and measurements.

Concept comparison

concepts that differ in how they constrain or move the object. Three cosmetic versions of one claw do not investigate whether a roller intake would be better.

Set aside designs that cannot meet a constraint. Compare the others on pickup , size, build time, and access for repairs. If a score is the team’s judgment rather than a test result, say so.

Keep the reason for rejecting an option. That record prevents the same unworkable idea returning when a new student joins.

Prototyping

A prototype is a tool for answering a question. Use a cardboard envelope to check packaging, an adjustable roller mount to find compression, or a simple fixture to test load. It need not resemble the final robot if it preserves the physics under investigation.

For example, an intake experiment might vary roller gap while keeping roller material, speed, object, approach path, and fixture constant. Test several object orientations at each gap. Record capture, rejection, damage, and recovery; do not record only successful attempts.

is valuable for geometry and interference. Physical tests reveal friction, , wear, and manufacturing variation. Neither alone establishes full robot performance.

Design decisions

Before a test, write down what you expect, what you will change, what you will measure, and when to stop. Afterward, compare the result with your target. Keep what you saw separate from why you think it happened: “the object rotated out of the gap” is an observation; “the contact force was too high” is a possible explanation.

If the explanation is uncertain, design the next experiment to distinguish causes. Reducing speed, changing compression, and replacing the roller simultaneously may improve pickup without revealing which change helped.

Use this compact record:

Question: Which roller gap captures the chosen range of object orientations?
Revision: intake fixture A, roller material and dimensions recorded
Variable: gap at the contact region
Controlled conditions: speed command, approach fixture, object set
Measurements: attempts, captures, acquisition time, damage, recovery
Decision: selected geometry and reason, or further test needed
Evidence: dated photos, video, and raw trial table

Integration testing

A mechanism that passes on a bench can fail when flex changes its alignment or another mechanism consumes the same space. Repeat the relevant test on the assembled robot, with the intended payload and simultaneous motion.

For each connection between mechanisms, record the mounting references, allowed flex, space for movement, power demand, readings, and which code controls it. If one changes, repeat the tests that rely on it.

Sources

  • GM0: Engineering design process
  • FTC Wiki: Design philosophy

Game strategy

Translate game tasks into a robot scope, cycle model, resource budget, and development plan.

CAD and robot integration

Model parts and assemblies around datums, motion envelopes, manufacturing, and service access.

On this page

Design requirementsConcept comparisonPrototypingDesign decisionsIntegration testingSources