CALCULATORS / CAMS AND INTERMITTENT MOTION

Cam cycle rate and throughput calculator

One product per active station per cam revolution.

cams-cycle-throughput.napkin / editable

SCENARIO COMPARISON

Compare the numbers.

This source describes an analytical model. Its quantities and checks are the view.

Scenario	cycleTimes	rates^-1
	1	1.9
	1.25	1.52

All calculated quantities are listed with the inputs. Switch to Source to inspect the equations.

SCENARIOS / CALCULATED VALUESSAME SOURCE

Change an input to see the consequences.

throughput target1.90 s^-1✓ passes

BASELINE INPUTS

speed60 rpmstations2 yieldFraction0.95

CALCULATED

cycleTime1 s

rate1.9 s^-1

Edits change the baseline source.

THE SOURCE

Edits below update the same model.

# Cam cycle rate and throughput
# Scope: One product per active station per cam revolution.
# Status: illustrative worked example; engineering review pending.
# Inputs are example values. Checks are editable example requirements, not standards.

speed = 60 rpm
stations = 2
yieldFraction = 0.95

cycleTime := 2*pi/speed [s]
rate := stations*yieldFraction/cycleTime [s^-1]

check throughput target: rate >= 1 s^-1

scenario alternative: speed = 48 rpm

Calculated from your source · not saved

Baseline · Baseline

throughput target1.90 s^-1 ✓ passes

alternative · alternative

throughput target1.52 s^-1 ✓ passes

Illustrative first-order example. Checks are editable requirements, not design standards. The broader topic may require additional equations, data, and validation.

Formula and units

This example uses the following equations. Input names and units match the editable source above.

cycle time: cycleTime = 2*pi/speed [s]
rate: rate = stations*yieldFraction/cycleTime [s^-1]

Original worked example

These are the baseline values in the downloadable source. Edits above let you test your own values.

Given

speed: 60 rpm
stations: 2
yield fraction: 0.95

Calculated

cycle time: 1 s
rate: 1.9 s^-1

Assumptions and limits

One product per active station per cam revolution.

The requirement checks use the limits written in this example. Passing a check does not establish that the model covers every load, material behavior, or operating condition in a real design.

Download this .napkin example ↓

Take it further with your agent

Napkin keeps the inputs, equations, checks and assumptions together in one study. Your agent sets it up; you change the numbers.

Try with Claude ↗

codex 'Use Napkin (https://napkin.engineering/mcp, or the local Napkin plugin) to build a study: Cam cycle rate and throughput. Inputs: parts per revolution; shaft speed; feed speed. Outputs: parts per minute; feed length per cycle. Model scope: Specified cam law, follower type and motion constraints. Read napkin_capabilities and the current snapshot. Ask me for the values that matter, label assumptions with units, author .napkin source, validate it and apply it with napkin_source using the current revision, then open the study. Add checks for the limits I supply. Keep unsupported analyses explicit.'

Claude needs the Napkin connector; Codex needs the Napkin plugin. Set up your agent ↗

The broader study

The topic brief below describes the broader scope. The worked example above states the particular calculation it implements.

Inputs: parts per revolution, shaft speed, feed speed
Outputs: parts per minute, feed length per cycle
Modes: calculate, compare, sweep
Drawing: Cam and follower animation

EXECUTABLE WORKED EXAMPLE · FIRST-ORDER MODEL · CHECK THE SCOPE & ASSUMPTIONS