Mechanisms without motors
Some models have no motors and no sensors at all. They are not lesser lessons — they are where the physics lives. A build that stores energy, changes a force, or turns one kind of motion into another explains why the powered models later need the gearing and the speeds they do.
The one bargain behind all of it
Gears, pulleys and levers look like three different topics and are three shapes of the same deal: whatever you gain in force, you pay for in distance. Halve the effort and you move twice as far; move half as far and you need twice the effort. No arrangement of anything gives you both, and recognising that saves a great deal of time hunting for one.
What a mechanism actually does is let you spend the same effort in a form you can manage — a little at a time instead of all at once, or all at once instead of a little at a time.
The nine ideas, and where each one lives
| Tutorial | The question it answers |
|---|---|
| Gearing up and gearing down | How do I trade turns for force? |
| Changing the direction of a turn | Why is it going backwards, and how do I drive an axle at 90°? |
| Pulley systems | How does a rope let a small motor lift a big load? |
| Levers — effort, load and pivot | Where should the pivot go? |
| Elastic and stored energy | How much further does pulling back twice as far actually get me? |
| Scissor mechanisms | How do I make something extend a long way — and why won’t it start? |
| Oscillatory motion | How do I turn going round into going back and forth? |
| Centre of gravity | Why does it keep falling over? |
| Biomimetic mechanisms | How does a machine walk without ever being told to? |
Friction — the one that is in all of them
Friction is what makes wheels grip and also what wastes effort. Every mesh, pin and rope turn loses a little to it, so a mechanism with more parts delivers less than the arithmetic promises. A build that binds — that is stiff to move by hand — is losing far more than that, and no amount of extra motor power fixes a mechanism that is rubbing.
Before measuring anything, turn the mechanism by hand. It should move smoothly and coast a little. If it does not, fix the build first; numbers taken off a binding mechanism describe the binding, not the idea you were trying to test.
How to investigate a mechanism
Since there is nothing to program, the work is measuring. Change one thing, keep everything else the same, and record what happened — pull the car back 5 cm, then 10, then 15, and measure how far each one travels. Three readings at each setting, not one, because a single run is not evidence.
That is genuinely how engineers test, and it is the same discipline that makes debugging a program work: change one thing at a time.
More mechanics tutorials
- Gearing up and gearing down — Trade turns for force, or force for turns — you cannot have both.
- Changing the direction of a turn — Reverse a turn, restore it with an idler, or send it round a 90° corner.
- Pulley systems — Fixed, movable and combined — how rope pulled trades against force needed.
- Levers — effort, load and pivot — Where the pivot sits decides the force you need and the distance you get.
- Elastic and stored energy — Stretch a band, store energy, let it go — and find where more stops helping.
- Scissor mechanisms — Crossed links that extend and retract, and why the last bit is the hardest.
- Oscillatory motion — Turning a rotation into a back-and-forth, and what sets the rhythm.
- Centre of gravity — Why a robot tips, and how to build one that does not.
- Biomimetic mechanisms — Linkages that copy how animals move — turning a rotation into a step.