Sensor state lux comparison notes
Sensor state lux comparison shows how several control states differ on the same plane.
Sensor state sequence
Enter the control states, then read the spread and target gap.
- 1Enter state 1
Use the first measured state.
- 2Enter state 2
Use the second measured state.
- 3Enter state 3
Add an optional third state.
- 4Enter the target
Use the planning target if needed.
- 5Read the spread
Keep the same plane and condition with the result.
Application measurement fit
Match the search phrase to the plane, reading condition and diagnostic output before using the calculator.
| Search phrasing | Calculator case | Carry forward |
|---|---|---|
| Sensor state lux comparison | A lighting group with two or three control states. | State spread and target gap. |
| Dimming-state note | A room where the dimming states need a quick comparison. | Lowest and highest state. |
| Control review | A sensor-controlled space with repeatable states. | Average state lux and spread. |
| Operational summary | A simple comparison across control modes. | Same plane and same condition. |
Reading the diagnostic output
Measurement calculators produce evidence notes, not compliance decisions or fixture approvals.
| Output | Technical meaning | Review item |
|---|---|---|
| State spread | Highest state reading minus lowest state reading. | Main spread note. |
| Average state lux | Average of the entered states. | Central control-state value. |
| Lowest state | Lowest entered control-state reading. | Weakest state. |
| Highest state | Highest entered control-state reading. | Brightest state. |
| Target gap | Average state lux minus target. | Comparison with the planning line. |
Assumptions that stay visible
The same number can mean different things when the plane, condition or target changes.
| Assumption | Why it matters | Where it belongs |
|---|---|---|
| Same plane | All state readings should use the same plane. | State the plane beside the result. |
| Same condition | The state comparison should use the same room and layout. | Keep the condition visible. |
| Target line | The target is a planning comparison line. | Use the project target if one exists. |
| State meaning | The spread is descriptive, not a compliance decision. | Treat it as a control note. |
control-state plane before the number
A useful sensor state lux comparison result starts with the exact control-state plane. A desk row, wall face, display surface, daylight zone or control state can produce a very different reading from the neighbouring surface, even when the fixtures look similar. Naming the plane keeps the result tied to a visible lighting task.
That boundary also makes the number repeatable. If another person checks the space later, they need the same plane, approximate point positions and operating condition. The measurement note is more reliable when it travels with those plain details rather than a bare lux value.
Measurement conditions change the result
Several readings from the same controlled space should be read with the same fittings, daylight condition, blinds, dimming state and sensor state recorded beside the result. A point measured under daylight-only conditions should not be mixed with a point measured under full electric light unless the calculator is specifically comparing those conditions.
Australian lighting notes often become confusing when readings from different days, weather states or control states are pooled together. Keep the operating state in the note so the number remains useful after the room changes. When a grid, average or variation result looks odd, check whether the conditions were actually consistent.
Point layout is part of the evidence
For grid and reading-set calculators, the point pattern is not just admin. It shapes the average, spread, variation and target gap. A sparse grid can miss local shadows; an uneven grid can overweight one side of a room. The point count or spacing should stay visible so the reading method can be reviewed.
Keep edge offsets, rows, columns and repeated point labels with the result. Even a simple three-point reading set becomes more trustworthy when it states which face, bench, wall, daylight patch or control state was being checked.
Comparisons need the same basis
The same room state should apply to every reading is useful only when both sides describe the same lighting plane. A calculated-lux estimate and a meter reading should use the same surface, height and condition. A baseline reading and current reading should use the same operating mode and approximate point location.
If the basis changes, the difference may be real but the reason is not visible. Treat the difference as a diagnostic prompt: decide whether the gap points to output assumptions, daylight conditions, dirt, ageing, aiming, controls or simple measurement inconsistency.
Daylight is a moving input
Daylight or electric-light condition changes with weather, sun angle, opening state, blinds, shading and the outdoor reference basis. Same-time indoor and outdoor readings are more useful than a daylight value copied from a different condition.
Daylight contribution and daylight-depth numbers should be read as planning evidence, not as a certified daylight design. Keep the opening condition, approximate room depth and whether electric light was on or off beside the result. That makes the page useful without pretending the sky is stable.
Targets are comparison notes
Several C4 calculators ask for a planning target. That target is a user-entered comparison line, not a compliance result. It helps show whether a reading sits above or below the chosen note and how large the gap is.
If the target comes from a project brief, internal standard or maintained-lighting table, write that source in the project file. The calculator keeps the arithmetic clear; the user remains responsible for choosing an appropriate basis for the task and space.
Averages hide variation
A single average can look acceptable while one side of a surface remains dark. Variation, spread, lowest reading and highest reading help reveal whether the average is hiding uneven lighting. Read those diagnostic outputs before treating the average as a summary.
For vertical faces, display walls and task surfaces, the lowest point can matter as much as the average. Keep the point labels and orientation clear so the next check can decide whether the issue is aiming, obstruction, surface reflectance or local fixture placement.
Australian measurement limits
sensor state lux comparison pages on AuLumens are measurement and daylight planning calculators for repeatable planning notes. They stay outside workplace compliance, emergency lighting, public roads, healthcare tasks, school spaces, sports lighting and specialist design outcomes.
It is a control-state comparison, not a compliance result. Keep formal assessment, public-space decisions, specialist task requirements and project approvals in the appropriate project review process. The page is valuable because it records a repeatable arithmetic note before those wider decisions begin.
Keep a comparison trail
A measurement page is most useful when the result can be checked against a later visit. Record the date, approximate point labels, fitting state, blinds or shade position, meter orientation and whether the reading was made before or after cleaning, lamp replacement or control changes.
That trail turns a small lux set into practical evidence. A later reviewer can decide whether the movement came from daylight, maintenance, ageing, furniture, aiming or a changed target instead of guessing from a single final number.
A concise measurement note
A readable note includes the assessed plane, approximate point layout, meter condition, daylight or control state, target line if used, and the calculator result. For a comparison, keep both cases and the difference visible.
Keep lux-before-after and occupancy-sensor-savings nearby when the same room also needs a control-saving note. That context lets another person repeat the reading, revise the estimate or link the result back to the room, daylight, control or energy calculator that owns the next decision.