— Blogs —
—Products—
Consumer hotline +8618073152920 WhatsApp:+8615367865107
Address:Room 102, District D, Houhu Industrial Park, Yuelu District, Changsha City, Hunan Province, China
Product knowledge
Time:2026-02-01 09:55:45 Popularity:657
PV soiling alarm settings must start with the meaning and direction of the reported value. A cleanliness channel becomes less clean as its percentage falls; a calculated loss channel usually moves in the opposite direction. Confusing those two definitions can send crews to clean an acceptable block while missing a deteriorating one. For an integrator, the alarm should identify a valid local condition that needs review, not automatically declare a whole-plant energy loss.

The NiuBoL NBL-W-PSS provides optical cleanliness observations from its sensing glass through RS485 Modbus communication. The example protocol identifies Cleanliness 1 and Cleanliness 2. They should not be renamed as plant energy loss or airborne dust concentration merely because a dashboard has a generic pollution tag.
Keep the two channels identifiable until their intended use is established. Do not silently average them, label one as a clean reference module or treat their difference as a direct electrical loss. Their physical roles and reporting convention belong to the selected instrument configuration.
For an explicitly defined derived quantity, a cleanliness value of 96.5% has a numerical complement of 3.5 percentage points to 100%. That arithmetic does not demonstrate that the plant has lost 3.5% of its energy. Use names that distinguish the optical observation from any independently validated electrical-loss estimate.
The PSS optical ratio range and accuracy bands describe its measurement configuration. They do not establish a universal cleaning threshold. Near a decision point, small changes need to be considered alongside repeatability, sensing-glass condition and the measurement's relationship to the monitored modules.

| NBL-W-PSS item | Specification | Consequence for alarm design |
|---|---|---|
| Optical ratio range | 50-100% | Keep the reported convention and channel identity |
| Specified accuracy | +/-1% over 90-100%; +/-3% over 80-90%; +/-5% over 50-80% | Do not assume identical measurement confidence across the whole range |
| Supply and average load | 12 V DC; approximately 1 W | A supply problem must be distinguishable from a contamination event |
| Communication | RS485 Modbus; 9600 bps | Remote notification and event storage require the selected controller or platform |
An optional temperature channel has its own definition. Its -50 to +100 degree C measurement span and +/-0.5 degree C accuracy at 25 degrees C do not establish the operating-temperature rating of the entire soiling instrument or prove automatic compensation of every optical effect.
The PSS example response contains 0x03C5 for Cleanliness 1 and 0x03C8 for Cleanliness 2. These are decimal 965 and 968, interpreted as 96.5% and 96.8%. Verify the same numbers at the logger, database and displayed alarm input before evaluating a threshold.

A decimal fraction of 0.965 and a percentage value of 96.5 express the same proportion, but they cannot use the same numeric threshold without conversion. Check whether a gateway already applies scaling so the platform does not divide a second time.
For a cleanliness-based warning, a downward crossing is the relevant direction after the channel convention is confirmed. If the software intentionally creates a different loss-related quantity, define and test its direction separately. Avoid a dashboard in which a high cleanliness percentage is labeled high pollution.
A missing response is not a cleanliness value of zero, and a held last value is not a new observation. Store the time of the last valid measurement and display an unavailable or stale state when its permitted age is exceeded. The allowed age should follow the acquisition schedule and operating requirement.

Use device quality information where it is available and documented. Do not invent an invalid-value code or assume that a code used by another NiuBoL sensor family applies here. Test the selected PSS version's behavior during supply interruption and communication loss.
Also establish any operating conditions needed for a valid assessment. Do not assume that all night values are invalid or that one generic irradiance cutoff suits every optical configuration. Agree the acceptable conditions with the selected instrument and verification procedure before using a software validity gate.
A practical alarm has an activation condition, a persistence requirement and a clearing condition. These should reduce repeated notifications without concealing an important change. A threshold alone does not describe how an operator will experience the event.
| Illustrative state | Example logic | Important qualification |
|---|---|---|
| Candidate warning | A selected valid cleanliness channel falls below 94% | 94% is a logic example, not a recommended cleaning threshold |
| Active warning | The condition persists for the agreed elapsed time | Missing observations must not be counted as valid persistence |
| Recovery | Valid observations recover above 96% for the agreed clearing period | The separate clearing threshold illustrates hysteresis, not an instrument setting |
| Unavailable | No acceptable current observation is available | Do not silently convert the event to normal or generate a false contamination value |
Counting ten samples is not necessarily the same as waiting ten minutes if the sampling times change or records are missing. Specify whether the persistence rule uses elapsed time, consecutive valid samples or another explicit convention. Test it with irregular intervals as well as evenly spaced records.
Distinguish a historical event from a current one during data recovery. Backfilled low-cleanliness records should retain their measurement times; they should not automatically summon a crew as though the condition has just started. Agree whether the platform reconstructs a past event, raises a separate data-recovery notice or requires a current valid observation before issuing an operational warning.
A PSS observation describes its sensing location. Include that location and its associated array or cleaning group in the event message. An operator should be able to identify the instrument and inspect the relevant modules without interpreting a site-wide alarm label.

If neighboring points disagree, check exposure and cleaning history before treating one as faulty. Local deposits and different cleaning times can produce meaningful differences. Conversely, a point that no longer follows its assigned array's orientation or cleaning practice may no longer represent that area.
For choosing monitoring coverage, use a separate soiling sensor deployment assessment. Alarm settings cannot compensate for an important area that has no representative observation.
An operator can acknowledge that a warning was received without having cleaned or inspected anything. Keep acknowledgement, assigned action and event recovery distinguishable. Otherwise, a notification can disappear from view while the local condition remains unchanged.

Record instrument cleaning, array cleaning and calibration separately. A jump after an instrument-only intervention does not prove that the array recovered. Avoid recalibrating a dirty baseline simply to clear an alert; preserve the preceding observations and the reason for the intervention.
Whether to clean requires a further decision about the modules, recoverable production, work cost and access. That assessment is covered by the PV cleaning schedule, not established by an alarm threshold alone.
Test the controller with an agreed set of example records before enabling operational notifications. This isolates software logic from the physical sensor check. Do not assume that a single successful notification demonstrates correct clearing, outage or recovery behavior.
Then verify the installed sensor's supply, protocol, location and observed response. The PSS communication procedure requires more than 1000 ms between communications; a fast SCADA screen does not justify millisecond polling. Confirm which system owns notification routing, storage and configuration support in the NiuBoL project inquiry.

Not on a channel defined as cleanliness. Verify its meaning and scale first. A high cleanliness percentage should not be interpreted as a high contamination percentage, and a threshold must not be copied between oppositely defined channels.
Do not assume identical values or assign them unverified physical roles. Check the configuration, exposure and inspection observations. A small difference alone does not identify a faulty channel or establish a plant energy-loss difference.
Only after the method and intended meaning are agreed. Preserve the original channels alongside any derived value. Averaging is a processing choice, not proof that the result represents the whole array.
It should not silently establish a normal condition. Retain the event history and show data availability according to the agreed logic. A recovery or clearing decision needs the required valid observations or an explicitly recorded operator procedure.
The basic interface provides local data. Confirm the controller, gateway and platform that generate notifications and retain events. RS485 Modbus communication alone does not include email, mobile alerts or maintenance workflow software.
Provide the PSS version, current data format, controller or platform, monitoring locations and required event behavior. Include persistence, missing-data handling, notification recipients and support scope. Do not request a universal cleaning alarm without defining its operational purpose.
NBL-W-PSS Soiling Sensor Photovoltaic Dust Monitoring Instrument Data Sheet.pdf
PV soiling alarm settings should preserve channel meaning, measurement validity and a clear local response. Verify the PSS scaling, test the direction and clearing logic, and keep data outages separate from contamination. An understandable warning helps the operator investigate; it does not independently diagnose lost plant energy or authorize an automatic cleaning decision.
Prev:Photovoltaic Weather Station Integration Guide
Next:Tipping Bucket Rain Gauge Resolution: 0.2 mm vs Accuracy
Related recommendations
Sensors & Weather Stations Catalog
Agriculture Sensors and Weather Stations Catalog-NiuBoL.pdf
Weather Stations Catalog-NiuBoL.pdf
Agriculture Sensors Catalog-NiuBoL.pdf
Water Quality Sensor Catalog-NiuBoL.pdf
Related products
Combined air temperature and relative humidity sensor
TDR Soil Moisture & Temperature Sensor for irrigation| RS485 |4-20mA| NBL-S-THR
Soil pH sensor RS485 soil Testing instrument soil ph meter for agriculture |NBL-S-PH
Wind Speed sensor Output Modbus/RS485/Analog/0-5V/4-20mA
Tipping bucket rain gauge for weather monitoring auto rainfall sensor RS485/Outdoor/stainless steel
Pyranometer Solar Radiation Sensor 4-20mA/RS485
Screenshot, WhatsApp to identify the QR code
WhatsApp number:+8615367865107
(Click on WhatsApp to copy and add friends)