Unit 03 · lesson
Motors Turn Electrical Power into Motion
A motor does not create “speed.” It converts electrical power into rotational mechanical output, and the load decides what happens next.
That distinction matters because a mechanism can demand more torque than the motor can comfortably produce. The result can be slow motion, high current, heat, voltage sag, or a stall.
Speed and torque are connected
Speed describes how fast the shaft rotates.
Torque describes rotational turning force.
For a given motor and operating condition, asking for more torque usually means the motor slows down and draws more current.
At stall, the shaft is not rotating even though the motor is trying to produce maximum torque. Stall is not a normal operating target.
Read a motor problem as a load problem
Suppose an intake works with no game piece but stops when the piece contacts the rollers.
Possible explanations include:
- the required torque rises beyond what the current setup can deliver;
- gearing favors speed too aggressively;
- friction or compression is higher than expected;
- voltage is dropping;
- the mechanism is binding;
- software current limits or output limits are active.
“The motor is weak” is not enough.
Mechanical power has a price
A robot has a limited energy source and limited electrical distribution. Multiple mechanisms can demand current at the same time.
A drivetrain acceleration, elevator lift, and shooter spin-up can overlap. Each one may work alone and still create a system-level failure together.
That is why motor selection is not just a motor question. It is an architecture question.
Evidence table
For a mechanism you are studying, collect or estimate:
| Property | Value or observation |
|---|---|
| motor type | |
| number of motors | |
| motor controller | |
| gear reduction | |
| expected load | |
| no-load behavior | |
| loaded behavior | |
| current/temperature evidence available | |
| most likely failure mode |
If you do not have hardware, use a published motor data sheet and a hypothetical FRC mechanism such as an intake roller, elevator, arm, or drivetrain.
Worked reasoning: faster is not automatically better
A team wants to make an elevator twice as fast.
If they change gearing to increase output speed, the available output torque changes too. The motor may now operate closer to a high-current region while lifting the same mass.
The design question is not:
Can we make it faster?
It is:
Can we make it faster while still meeting torque, current, control, reliability, and safety constraints?
That longer sentence is what engineering looks like.
Failure mode: testing without load
Free-spinning a mechanism proves surprisingly little.
Loads expose problems. So do repeated cycles. A mechanism that succeeds once may still overheat, loosen, stretch, slip, or brown out after repeated operation.
Record not only whether it moved, but under what load, for how long, and with what evidence.
You will use that record in Lesson 3 when you defend a mechanism choice.
process flow
Mechanical Systems and Prototyping: FRC Evidence Flow
Plan
Name the role, rule, criterion, constraint, and safety condition.
Model
Trace the subsystem or match decision and its dependencies.
Test
Use a bounded approved test or simulation and record evidence.
Review
Document correction, limitation, and next team action.
Read this concept flow as plain text
- Plan. Name the role, rule, criterion, constraint, and safety condition.
- Model. Trace the subsystem or match decision and its dependencies.
- Test. Use a bounded approved test or simulation and record evidence.
- Review. Document correction, limitation, and next team action.