Gear Trains

§1Why chain gears together

A single pair is limited: push the ratio much past about 6 : 1 and the gears become wildly mismatched in size, the large one dominating the housing. A train shares the total reduction across several modest stages.

Two questions define any train: what is the overall ratio, and which way does the output turn? Both are answered by tracking tooth counts through the mesh. Beyond the plain ratio, trains let a designer place input and output shafts where the machine needs them, split power down several paths, and — in the planetary form — pack a large ratio into a concentric, in-line package or switch ratios while running. This page works from the simple train to the planetary, the arrangement inside every automatic gearbox and most compact reducers.

Contents

§2Simple trains and idlers

In a simple train each gear sits on its own shaft and meshes with the next. Only the first and last gears set the ratio; everything between is an idler.

simple train: i = z_lastz_first (idlers cancel from the magnitude)

An idler earns its place not by changing the ratio — its teeth appear once on top and once on the bottom of the chain of fractions and cancel — but by two other services: it spans a gap when the input and output shafts must sit far apart without a huge single gear, and it reverses the direction of rotation. Each mesh flips the sense of turn, so counting meshes (or idlers) tells you whether output turns with or against input: an even number of gears means opposite senses, an odd number the same.

Contents

§3Compound trains

To make the ratio actually multiply, two gears are fixed on a shared intermediate shaft so they turn together — a compound train.

i = product of driven (output-side) teethproduct of driver (input-side) teeth

Example 1 — a two-stage compound reduction

Stage one: a 20-tooth driver meshes a 60-tooth gear. On that gear’s shaft sits a 15-tooth gear driving a 45-tooth output. Overall i = (60 × 45)/(20 × 15) = 2700/300 = 9 : 1. A 1500 rev/min input therefore leaves at 1500/9 = 166.7 rev/min. The same 9 : 1 as two 3 : 1 stages keeps every individual gear pair sensibly matched, where a single 9 : 1 pair would pair a small pinion with a gear nine times its diameter.

Contents

§4Planetary trains

A planetary (epicyclic) train has three concentric members — a central sun, an outer internally-toothed ring (annulus), and planet gears that mesh both and ride on a rotating carrier.

What sets it apart is that the planet axes themselves move, orbiting the sun on the carrier, so the gears both spin and revolve. That gives it three shafts on one axis — sun, ring and carrier — any one of which can be input, output or held fixed, and each choice yields a different ratio from the same hardware. The load is shared among several planets, so a planetary carries more torque for its size than an ordinary train, in a package that is concentric and in-line. The cost is complexity: the members interact, so the ratio can no longer be read off by tracking one path — it needs the equation of §5.

Contents

§5The epicyclic equation

Because the carrier moves, ratios are found by working relative to the carrier — imagining you ride on it, so the train looks momentarily like a simple one.

n_sun − n_carriern_ring − n_carrier = − z_ringz_sun and z_ring = z_sun + 2 z_planet

The minus sign records that, seen from the carrier, sun and ring turn in opposite directions (the ring is internally toothed). Fix any one member by setting its speed to zero and the equation gives the ratio between the other two. The tooth-count identity on the right — the ring equals the sun plus twice the planet — is the geometric constraint that the planets fit the annular space; it also fixes the planet size once sun and ring are chosen.

Contents

§6Worked planetary

The commonest case — ring held fixed, sun driven, carrier out — gives a compact reduction.

Example 2 — fixed ring, sun in, carrier out

Sun z = 24, ring z = 72; the planets are therefore (72 − 24)/2 = 24 teeth each. With the ring fixed (n_ring = 0), the equation reduces to n_sun = n_carrier(1 + z_ring/z_sun), so the reduction is 1 + 72/24 = 4 : 1. A sun turning at 2000 rev/min drives the carrier at 2000/4 = 500 rev/min, both turning the same way. Swap which member is fixed and the same gears give a different ratio — hold the sun instead and drive the ring, and the reduction changes, which is exactly how an automatic gearbox selects gears by clamping different members.

Contents

§7Quick reference

The working core of the page on one card rack.

Simple

i = z_last/z_first

idlers reverse only

Compound

i = Π driven / Π driver

Direction

even gears → opposite

odd gears → same

Planetary

(n_s−n_c)/(n_r−n_c) = −z_r/z_s

z_r = z_s + 2 z_p

Fixed ring

i = 1 + z_r/z_s

sun in, carrier out

Contents

Handbook application: from concept to controlled practice

Purpose. This expanded section turns the original page into a practical handbook. It preserves the supplied material and adds a repeatable way to apply, check and review Gear Trains. It does not replace a contract, legislation, a controlled standard, competent engineering judgement or specialist advice.

The operating aim is to carry the subject from function and assumptions through design evidence, verification and controlled release. Read the original explanation first, then use the workflow and checks below to convert knowledge into evidence.

Apply Gear Trains by beginning with the duty, not the component or software command. Convert the key ideas—trains, simple, planetary, gear, compound—into measurable requirements and interfaces. Record operating and non-operating environments, duty cycle, expected life, loads, energy sources, human interaction and reasonably foreseeable abnormal conditions. When a value is not a project requirement or verified supplier datum, identify it as an assumption or illustrative value.

Create a calculation and evidence trail that another competent person can audit. Every input should carry a source, unit, revision and uncertainty or tolerance where relevant. Every model should state its boundary conditions and limitations. Keep nominal capacity separate from design capacity, and keep verification margin separate from an arbitrary safety factor. If a code or standard governs the work, confirm the applicable edition and contractual status rather than copying a number from a secondary summary.

Design for manufacture, assembly, inspection, operation and maintenance at the same time. A technically valid geometry can still fail because it cannot be fixtured, measured, cleaned, guarded, reached or replaced. Review process capability, datum or reference strategy, tolerance accumulation, access, error-proofing and changeover. Where people interact with plant, apply the hierarchy of controls and consult those who will operate, clean, maintain and recover the equipment.

Plan verification before release. Define the characteristic, method, equipment, sample or test condition, acceptance criterion, record and responsible person. Validation then asks a different question: whether the resulting system is effective and suitable in the intended use context. A passed drawing check or analysis does not by itself validate usability, maintainability or production performance.

Step-by-step operating method

Define the duty. Capture the required function, interfaces, operating environment, life, loads and unacceptable outcomes.
Establish the model. Identify governing principles, units, material or process data, assumptions and uncertainty.
Develop alternatives. Compare feasible concepts against performance, manufacturability, safety, maintainability and cost.
Verify the design. Use analysis, test, inspection or demonstration with acceptance criteria defined before execution.
Release and learn. Baseline the design, control changes, retain evidence and feed operating results into the next revision.

Illustrative design review record

Illustrative values only. Build a one-page record with the required function, input sources, assumptions, governing load or process condition, failure consequences, selected concept, verification method and acceptance criterion. Mark every numerical input as project requirement, verified supplier data, measured value, calculation output or assumption. Review the weakest evidence first. If an assumption can change safety, compliance, interchangeability or capacity, it must be resolved before release rather than buried in a calculation note.

Evidence class	Question	Release expectation
Requirement	What must the design do and under which conditions?	Approved and traceable
Input	Where did the load, property, tolerance or process limit come from?	Source, unit and revision recorded
Analysis	Which model and assumptions connect input to result?	Checkable calculation or simulation
Verification	How will conformity be demonstrated?	Method and acceptance criterion agreed
Validation	Will the solution work for intended users and conditions?	Representative use evidence

Common failure modes and recovery actions

1. Watch for

Starting detailed design before interfaces and operating limits are agreed.

Recovery: Return to the governing definition or requirement and restate the decision in one sentence.

2. Watch for

Using catalogue or typical values as though they were certified project inputs.

Recovery: Separate evidence from assumption, assign an owner and set a date for validation.

3. Watch for

Checking nominal performance while ignoring tolerances, degradation and foreseeable misuse.

Recovery: Run a small counterexample, boundary test, pilot or independent check before proceeding.

4. Watch for

Confusing verification of requirements with validation of user need.

Recovery: Record the consequence, decision and rationale, then update the controlled baseline.

5. Watch for

Releasing drawings or procedures without configuration, inspection and change controls.

Recovery: Escalate when the issue affects safety, compliance, acceptance, material value or an agreed tolerance.