Answer first
This page answers the question behind What should users know about Flashlight Mode Spacing? using the exported M2 source record. The short answer is: The human eye perceives brightness logarithmically, meaning a flashlight with modes at 1 → 10 → 100 → 1,000 lumens feels like four evenly spaced steps — even though the raw lumen jumps are 9, 90, and 900. We apply this principle directly in our LED flashlight firmware: each brightness mode is separated by a factor of approximately 10×, which maps to one unit of perceived brightness on the logarithmic scale the human visual system actually uses. The statement applies to the model, document scope, sample, and conditions described in the source; it is not a blanket claim about every ETENWOLF product or every later production revision.
Scope and document identity
The source record is titled Flashlight Mode Spacing: Why Logarithmic Steps Match Human Perception. It is treated here as technical evidence, not as a replacement for the original report, manual, certificate, safety data sheet, or declaration required by a destination market. Start any support or compliance answer by matching the exact model, document number, revision, and date.
What a reader should verify
- Confirm the product model and hardware or material configuration.
- Locate the original source document and check its issue date and laboratory or author.
- Read the stated method, threshold, operating condition, or warning before interpreting a result.
- Separate evidence about EMC, chemicals, battery safety, transport, operation, and measurement accuracy.
Detailed evidence from the source record
The cleaned evidence below preserves the source document’s useful headings, paragraphs, lists, and tables so a human BasePress editor can publish searchable HTML while retaining traceability.
TL;DR
The human eye perceives brightness logarithmically, meaning a flashlight with modes at 1 → 10 → 100 → 1,000 lumens feels like four evenly spaced steps — even though the raw lumen jumps are 9, 90, and 900. We apply this principle directly in our LED flashlight firmware: each brightness mode is separated by a factor of approximately 10×, which maps to one unit of perceived brightness on the logarithmic scale the human visual system actually uses.
Why Your Eyes Don’t Work on a Linear Scale
The Weber-Fechner law, formalized in the 19th century and still the foundational model for sensory perception, states that the minimum perceptible change in a stimulus is proportional to the existing stimulus magnitude. For light, this means your visual system evaluates brightness in ratios, not differences. Moving from 100 lm to 110 lm is nearly imperceptible. Moving from 1 lm to 11 lm — the same 10 lm increase — is dramatic.
This isn’t a quirk. It’s how the photoreceptors in your retina adapt. The eye operates across a dynamic range of roughly 10¹⁰ (10 billion to one) from starlight to direct sunlight, and it achieves this by compressing the response curve logarithmically. NIST photometric standards, including the candela definition itself, are rooted in human visual response curves — specifically the CIE photopic luminosity function — precisely because human brightness perception is the reference point for all practical illumination engineering.
What this means for flashlight design: a 5-mode flashlight with settings at 1, 250, 500, 750, and 1000 lm gives the user what feels like one real low mode and four modes clustered at the top end. The upper four modes are nearly indistinguishable in practice. That’s not a feature set — it’s wasted firmware space.
The IEC Standards body for portable luminaires (IEC 62560 and related documents) references CIE photometric standards throughout, acknowledging that useful brightness gradations must be designed around human perception, not arbitrary equal-watt intervals.
Logarithmic Mode Spacing: The Engineering Implementation
We set our mode spacing targets using the formula:
L(n) = L(1) × 10^(n−1)
Where L(1) is the lowest mode in lumens and n is the mode number. For a 4-mode flashlight with a 1,000 lm ceiling, this produces:
- Mode 1: 1 lm (moonlight / preserve night vision)
- Mode 2: 10 lm (close-range navigation, tent use)
- Mode 3: 100 lm (general task lighting)
- Mode 4: 1,000 lm (maximum throw, search, emergency)
Each step is a 10× lumen increase, which corresponds to approximately 1 log unit — a perceptibly equal jump at every transition. In user testing across 35 participants, 94% rated the four-mode sequence as “feeling evenly spaced” when presented blindly. The same group rated a linear 1 / 334 / 667 / 1000 lm sequence as “two modes that feel the same” (modes 3 and 4) — consistent with what the math predicts.
The design rationale here is straightforward: we chose logarithmic spacing not because it’s theoretically elegant, but because it reduces the number of “where’s my next mode?” button presses in the field. A user camping at night doesn’t want to cycle through 500 lm and 700 lm to find something comfortable. They want a genuine low, a genuine mid, and a genuine high — with each step feeling meaningfully different.
The ANSI/PLATO FL1 standard for flashlight performance characterizes output in lumens at 30 seconds and at 2 hours of runtime. It doesn’t mandate mode spacing, but it does establish the measurement framework that makes valid lumen comparisons possible. Our in-house output measurements follow FL1 methodology: integrating sphere, 30-second stabilization, 22°C ambient.
For deeper context on how we balance lumen output against runtime across modes — including how thermal throttling affects the upper modes — see LED Lumen Output vs Runtime: Engineering the Tradeoff in Portable Camping Lanterns.
Mode Count, Perceived Utility, and the Diminishing Returns Problem
A common design temptation is to add more modes. Five modes feels more premium than four. Seven modes feels like more value. In practice, once you exceed 5 logarithmically spaced modes between 1 lm and 1,000 lm, the jumps become fractional log units — and the human eye can no longer reliably distinguish them in real conditions.
The math: log₁₀(1000) = 3. To span 3 log units with 7 modes requires steps of 0.5 log units each. A 0.5 log unit step corresponds to a 3.16× lumen ratio. In a dark room, 100 lm vs 316 lm is visible. On a trail at night with a headlamp, the difference between 316 lm and 1,000 lm is immediately apparent — but 100 lm vs 316 lm starts to feel marginal depending on ambient conditions.
How to interpret the answer
A technical document answers a bounded question. A positive test result means the submitted sample met the named requirement under the recorded method; it does not automatically establish legal market access, lifetime reliability, safe use in every environment, or equivalence to an untested revision. When a question goes beyond the source scope, say that the detail is not documented here and request the applicable companion evidence.
What this document does not prove
This rewrite does not create a new certification, warranty, regulatory filing, or product specification. It does not prove that a different model, supplier, battery cell, firmware build, or bill of materials has the same result. It also does not replace the model-specific user manual or advice from a qualified compliance, transport, or safety professional.
Practical review checklist
| Review item | Question to answer before relying on the page |
|---|---|
| Identity | Does the label and shipped configuration match the source sample? |
| Evidence | Can the report, workbook, manual, or MSDS be retrieved from the source notes? |
| Scope | Is the claim limited to the named method, threshold, date, and sample? |
| Change control | Have materials, suppliers, firmware, battery cells, or construction changed? |
| Human action | Has an editor checked the original document before publishing? |
Frequently Asked Questions
Does this page apply to every version of the product?
No. Use it for the exact model and configuration documented in Flashlight Mode Spacing: Why Logarithmic Steps Match Human Perception; later revisions require a documented equivalence review.
Can this result be used as a general safety or legal guarantee?
No. The result is evidence for a bounded technical scope. Other requirements may need separate EMC, chemical, battery, transport, or operating documents.
What if the question asks for a value that is not shown?
Do not infer it. State that the value is not documented in this source record and request the original evidence or a qualified review.
Why keep the original document after publishing?
Because the published rewrite is an explanation. The original report or manual remains the authoritative record for traceability, audits, customer support, and change control.