Mechanical duty-cycle loads calculator

Two-state power budget; supplied on/off power.

dynamics-duty-cycle.napkin / editable

SCENARIO COMPARISON

Compare the numbers.

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

Scenario	duty	averageW
	0.166667	20.8333
	0.166667	17.5

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.

average power budget20.83 W✓ passes

BASELINE INPUTS

onPower100 WoffPower5 WonTime10 soffTime50 s

CALCULATED

duty0.16667

average20.833 W

Edits change the baseline source.

THE SOURCE

Edits below update the same model.

# Mechanical duty-cycle loads
# Scope: Two-state power budget; supplied on/off power.
# Status: illustrative worked example; engineering review pending.
# Inputs are example values. Checks are editable example requirements, not standards.

onPower = 100 W
offPower = 5 W
onTime = 10 s
offTime = 50 s

duty := onTime/(onTime+offTime)
average := duty*onPower+(1-duty)*offPower [W]

check average power budget: average <= 25 W

scenario alternative: onPower = 80 W

Calculated from your source · not saved

Baseline · Baseline

average power budget20.83 W ✓ passes

alternative · alternative

average power budget17.50 W ✓ 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.

duty: duty = onTime/(onTime+offTime)
average: average = duty*onPower+(1-duty)*offPower [W]

Original worked example

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

Given

on power: 100 W
off power: 5 W
on time: 10 s
off time: 50 s

Calculated

duty: 0.166667
average: 20.8333 W

Assumptions and limits

Two-state power budget; supplied on/off power.

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: Mechanical duty-cycle loads. Inputs: time-at-load profile; speed profile. Outputs: RMS torque; mean power; cycle energy. Model scope: Rigid-body dynamics with stated force and motion profiles. 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: time-at-load profile, speed profile
Outputs: RMS torque, mean power, cycle energy
Modes: calculate, compare, sweep
Drawing: Motion and load plots

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