Semantic difference between endless rotation and limited throw

What it is

An oven thermostat hits a metal stop; the pointer sits on off or on full, and position is the value. A mouse-wheel-style encoder can turn forever; where the knob points does not mean current volume—it only reports how much more it turned. End-stop versus endless rotation are two semantics: absolute position versus relative increment. Using one shell for the other vocabulary makes the hand read the wrong dictionary.

Why it happens

An end-stopped potentiometer writes the parameter into the shaft’s absolute angle: mechanical zero, full scale, and mid ticks line up with the housing. After power loss the pointer still sits there; a glance or a felt stop is enough. An endless encoder has no mechanical origin; the live value lives in software, the knob’s clock-facing is arbitrary, and the shell does not store the parameter on release. “Turned all the way” then means opposite things: with a stop it is arrival at a bound; with endless travel it never happens, and the bound can only be hinted by software clamping or by the sound suddenly not changing. A pointer on a limited knob also lets state be read at a glance; an unmarked endless knob banishes state to a nearby display. The grasp can look identical; the semantic channel is not.

Studying it

Give the same parameter an end-stopped pointer knob, an end-stopped unmarked knob, and an endless unmarked encoder, then watch how people judge current value and treat bounds.

Independent variables: throw type (stopped / endless), pointer or scale present, whether hardware holds value across power loss, presence of a separate numeric display. Dependent measures: estimate error for current value with the display hidden, behavior at the bound (keep turning, stop, hunt for a stop), whether shaft heading misleads after power-up.

The informative moments are power-up and taking over after someone else: endless heading is independent of the parameter, yet people read it as absolute. Include a hand-off segment or the wrong dictionary never shows.

Where it stops holding

A ten-turn pot is limited travel that feels endless; the stop arrives late and is easy to misfile as infinite. Mapping an endless encoder onto a soft-limited parameter (turning past max adds nothing) leaves the hand moving while the value has stopped—the “it’s broken” illusion. Settings that must survive power loss (mechanical thermostats, analog consoles) almost require stopped or otherwise absolute hardware; browsing a huge range without slamming a pointer (long lists, multi-turn focus) prefers endless. Under vibration, an under-damped endless knob accumulates increments with no one touching it; a stopped knob only rattles between its stops.

Applying it

• For parameters that must be readable from the shell and that have a physical min/max, use an end-stopped knob, preferably with a pointer.
• For values that live in software, whose range changes, or that need multi-turn browsing, use endless rotation and put current value on a nearby display; do not paint a fake pointer.
• Do not drop an endless encoder into a calibrated dial housing that pretends to point at an absolute value.
• Verify: after power loss or after someone else changed the parameter, ask “about how much is it now” with the display hidden. An end-stopped pointer should hit the right order of magnitude; if an endless knob’s heading misleads, the shell is speaking one semantics and the system another. Then have people drive past the bound: a stop should go hard; endless should become “turning but the value holds,” with a non-visual cue.

Related

• Same group: C10.02.1 A knob maps a continuous quantity onto controllable hand rotation · C10.02.2 Damping and detents supply eyes-free quantized feedback
• Adjacent: C10.10 Knob Detents and Damping · C1.02 Absolute and relative positioning
• Search: endless encoder · end-stop knob · absolute versus relative