Illuminance Sensor Commissioning: PLC Acceptance Test Procedure

Quick Answer: Illuminance sensor commissioning must prove three things separately: the sensor responds to light, the PLC converts its signal correctly, and the controller behaves correctly during changing light or a fault. Test the analog or Modbus input before enabling automatic outputs. Record the sensing plane and light source, then verify switching delays, manual override and recovery with the actuator isolated where necessary.

Separate a light measurement test from a controller test

A lamp switching when the sensor is covered is a useful functional observation, but it does not establish optical accuracy or correct scaling across the operating range. Equally, a plausible lux display does not prove that the controller applies its delay, hysteresis and fault rules correctly.

Use separate acceptance stages. First verify model and input configuration. Next check the electrical conversion. Then compare light measurements using an appropriate reference. Finally test the control sequence. Isolate or simulate outputs when an unexpected command could operate a shading mechanism or other equipment during testing.

This procedure concerns a lux-based installation. For the distinction between illuminance, irradiance and photon flux, use the separate illuminance sensor principle and application guide. Do not begin commissioning by renaming a lux channel as solar radiation or PAR.

A weather-station installation may contain several independent instruments. Identify the actual illuminance channel rather than assuming that one of the assemblies in a station photograph supplies light data.

Freeze the input configuration before applying a test signal

For a NiuBoL NBL-W-LUX installation, check the following items against the delivered unit and the receiving module. Supply and output choices are ordering versions, not interchangeable settings on every device.

Save the PLC channel configuration before changing it. Record whether an analog input expects current, voltage or an internally converted value. For serial input, record the device identity as well as its address. A replacement sensor can have the same physical housing while requiring a different conversion or supply.

Run an electrical scale test without claiming optical calibration

Disconnect the field signal only under an approved safe test arrangement. A suitable current or voltage simulator checks the receiving chain independently of the optical sensor. For an illustrative zero-based 0-200000 lux configuration, the expected values are:

Apply only the signal appropriate to the configured input. Those values are calculated from the stated endpoints, not measured product results. If the installed span differs, recalculate the table. A constant factor error suggests a span or unit mismatch; an offset affecting all points suggests a zero or input-configuration issue.

Also test around the actual decision region. On that wide span, 100 lux corresponds to 4.008 mA or 0.0025 V. This calculation shows why a successful mid-scale test does not establish a useful dusk threshold. Check the combined input resolution, noise and transmitter performance near the chosen control levels before accepting a low-light application.

A compact multi-parameter instrument such as the one below needs a different input schedule if it supplies several quantities together. Do not reuse the stand-alone transmitter's scale for an integrated sensor without checking its actual channel representation.

For RS485, prove identity and conversion at the host

The NBL-W-LUX serial arrangement uses 9600 bps, 8 data bits and no parity, with at least 1000 ms between communications. Confirm the stop-bit setting, register representation and scaling for the delivered firmware. Use the actual protocol definition rather than copying a rain or temperature register just because it is also Modbus RTU.

Test one sensor before connecting a shared bus. Change its light exposure and confirm that the intended PLC tag changes. On a multi-device bus, repeat this identity check for each physical instrument; successful polling does not rule out a swapped address-to-location assignment.

Compare the decoded reading at two or more relevant light levels and include the upper operating region where practical. Retain raw replies with the expected engineering values during commissioning. If a value wraps or changes by a factor at higher light, investigate the data representation before adjusting an optical offset.

Compare illuminance under reproducible field conditions

Use a suitable reference lux meter close to the sensing face, with matching orientation and no mutual shadow. Compare simultaneous readings while the source is reasonably stable. Record the source, geometry and surface condition; a reference held at a different angle is testing a different light field.

The quoted +/-7% does not define a complete site-comparison tolerance by itself. Agree the percentage basis, reference uncertainty and source conditions before using a numeric pass/fail limit. Keep observed disagreement separate from a guaranteed transmitter error, especially under rapidly changing daylight.

For a combined station, verify that the tag really is illuminance in lux. The multi-parameter assembly below illustrates why a channel name, unit and documented configuration are needed: a count of weather parameters does not identify the light quantity.

Test the switching sequence with an event timeline

Use a documented test profile in the PLC or a controlled signal arrangement. For illustration, assume switching on below 100 lux and off above 150 lux, with a continuous 60-second qualification delay for each command. These are test settings, not lighting standards, sensor defaults or a recommendation for every site.

Record the input time, timer state, command time and output feedback where available. Decide whether a threshold equality counts as above or below, and whether interruption resets the timer. These details should come from the control specification, not from assumptions made during a demonstration.

If a separate wind condition restricts a moving shade, test the combined permissions with motion safely inhibited as needed. A wind instrument such as the one below supplies an independent input. It does not make the lux transmitter an actuator or establish a safety-rated control function.

Test faults, overrides and restart before leaving automatic mode enabled

Interrupt communication or the signal through the agreed safe method. Verify that the PLC detects invalid or stale data, shows a distinct diagnostic and applies the specified fallback. Do not assume that every analog fault is zero or that every serial failure immediately removes the last value.

Check manual override separately. Record whether it has a timeout, who can apply it and how automatic control resumes. Test a controller restart while the light value is between the two thresholds; the required initial output may depend on retained state or a defined startup rule.

Finally disconnect the remote uplink while keeping local acquisition operating. A local lighting rule should behave according to its specification, and the platform should show the communication gap rather than a false sensor reading. Restore the link and check that historical records retain observation times.

Keep other environmental channels separate during these tests. A louvered air-temperature, humidity and pressure assembly is not a reference lux meter, and a shared data logger must not copy its status into the light channel.

Project Decision FAQ

Q1. Does covering an illuminance sensor prove it is calibrated?

No. It demonstrates a response to reduced light. Optical comparison needs a suitable reference and controlled geometry; electrical scaling and controller sequence tests are additional independent checks.

Q2. Why can mid-scale pass while a low-light threshold is unreliable?

A small lux change occupies a very small signal interval on a wide analog span. Receiver resolution, noise and sensor uncertainty may be significant in that interval. Verify performance near the operating threshold or select a more suitable configuration.

Q3. Should the installer correct a factor-of-ten error with an offset?

No. Check span, units, register scaling and data type first. An offset cannot correct a proportional conversion error across the range and can hide the cause at only one test point.

Q4. What should happen if the sensor fails?

Use the agreed control response, such as a local schedule, bounded fallback or operator intervention. Invalid input must be identified separately from a genuine low-light reading. Test recovery as well as failure detection.

Q5. What evidence should the acceptance record contain?

Keep the model and configuration, sensing plane, electrical test points, reference comparison conditions, control-event timeline and fault results. Distinguish measured observations from simulated inputs so later maintenance can reproduce the relevant check.

Q6. What should be requested with a commissioning quotation?

Provide the transmitter version, PLC input module, required light levels and control sequence. State whether the work covers wiring, software conversion, optical comparison, actuator testing and operator training; these are separate tasks rather than an implied sensor-only service.

Summary

Accept the measurement channel and the control sequence separately. A usable illuminance sensor installation has verified scaling near its operating region, reproducible optical exposure and tested behavior during faults and restart. Give NiuBoL the output version, receiver details and decision levels to assess whether the selected configuration suits the intended installation.