Fog, rain and dark or wet targets all shorten a laser rangefinder’s range: the air scatters part of the pulse on the way out and back, and a dark or wet surface returns less of what arrives. Catalog range figures are measured on a stated target and visibility (for example, a large target of known reflectivity in clear air), so treat them as an upper bound and keep margin for bad weather and low-reflectivity surfaces.
A wet target can change a 905 nm rangefinder’s return without changing the module itself. Treat the problem as a target-and-optical-path acceptance test, not as evidence that a catalogue range has become a guaranteed rain rating. Compare a dry baseline, a wet target and a wet protective window separately, while recording valid readings and the conditions of every run.
Separate three different wet-weather problems
Water on the object, water on the viewing window and water in the air are different test conditions. A smooth wet surface may send less useful light back toward the receiver at one angle and a different return at another. A droplet on a window changes the path before the beam reaches the object. Rain in the measurement path adds another variable. A single observation labelled “rain failure” cannot identify which part of the installation needs attention.
Start with a stationary object and unchanged mounting. Keep the module, supply, requested measurement mode, host parser and logging configuration the same. Change only one wet condition at a time. Otherwise an apparent optical problem can actually be a supply interruption, an overwritten receive buffer or a changed host timeout. The purpose is to locate the failure mechanism before choosing a different module.
What the model records establish, and what they do not
The SPD1200N2 model page identifies a 905 nm module with UART-TTL communication. Its source table lists a measurement range of 0.2–1,200 m. The LR1000E2 model page also documents a 905 nm UART-TTL module, with a source-table range of 4–1,000 m. These are model-specific published rows, not promises that the upper distance is available on every material, angle or wet surface.
Both records describe the protection rating as IP67 “inside lens cavity.” Keep that qualification attached to the statement. It does not establish that an added enclosure, connector, cable entry or external optical window has the same protection. More importantly, ingress protection does not specify the usable optical return from a water-covered object. Ask separately about the supplied module’s environmental boundary and the assembled system’s measurement requirement.
Use the 905 nm UART module selection page to identify candidate hardware and documentation. Do not use a family overview to fill in a missing rain-performance figure. If a delivered configuration has no stated wet-target acceptance condition, the missing value remains a test requirement rather than a product specification.
Build a small condition matrix
| Run | Object | Window | Question answered |
|---|---|---|---|
| Baseline | Dry | Clean and dry | Does the installation work before adding water? |
| Object comparison | Wet | Clean and dry | Does the changed surface alter valid returns? |
| Window comparison | Dry | Controlled wet condition | Does water on the enclosure path dominate? |
| Combined condition | Wet | Controlled wet condition | Does the assembled system meet its requirement? |
Repeat the matrix at the actual minimum working distance, the normal operating distance and the farthest distance the application needs. These are installation requirements that the integrator supplies; they are not extra range claims for the module. Record the object material, dimensions, orientation, illumination, window material and mounting geometry with each run. Photographs help reproduce the arrangement, but they do not replace the measurement log.
Count useful readings instead of averaging away failures
A mean distance alone can look excellent when many frames were invalid or missing. Keep separate counters for complete received frames, valid distance readings, invalid outputs, checksum failures and host timeouts. Calculate a valid-reading fraction using valid readings divided by attempted measurement opportunities, with the denominator clearly defined. If the module runs adaptively, also log the actual received timestamps rather than assuming that every interval has the same duration.
For example, an evaluation plan might request a fixed observation window and count all complete frames received during it. That is a test-design choice, not a claim about how many frames either module will produce. Report the sample count and observation duration together. A run with fewer readings may have a different usable update interval even when its valid-reading fraction is similar to the dry baseline.
Check the invalid-value definition in the delivered unit’s protocol before calculating error statistics. An invalid marker is not a very distant object, and a missing frame is not a zero-distance measurement. Keep both out of the distance-error average while preserving their counts. This prevents the host software from hiding an optical loss or inventing a dangerous-looking distance jump.
Set acceptance criteria before running the comparison
- Define the real object, distance interval, angle range and illumination conditions.
- Confirm the exact module configuration and the protocol’s invalid-output handling.
- Establish an independently checked distance reference and state how it is positioned.
- Specify the minimum useful reading fraction and maximum acceptable reporting delay for the application.
- Run dry, object-wet, window-wet and combined conditions without changing unrelated settings.
- Repeat the dry baseline afterward to check whether contamination or alignment changed during testing.
- Keep raw frames, timestamps, conditions and photographs with the decision record.
Do not borrow an acceptance percentage from an unrelated data-sheet row. A detection probability, false-alarm figure and the fraction of application-usable readings may use different targets, windows and definitions. The useful criterion is the one that answers the installation’s stated decision and can be reproduced with the delivered configuration.
Decide what to change from the evidence
If only the window-wet run deteriorates, investigate the enclosure path, cleaning and water management before changing wavelength. If the object-wet run deteriorates while the clean-window baseline remains stable, review the object’s material, angle and required working distance. If dry and wet runs both show checksum failures, investigate wiring and parsing first. These are diagnostic branches, not guarantees that a particular adjustment will solve every installation.
A move to another wavelength should follow a comparison under the same relevant conditions. A label such as 1535 nm does not by itself prove rain performance, an acceptable optical window or compatibility with the existing host. Send the condition matrix, required distance and raw failure categories through the ERDILRF contact form so the module documentation and the proposed evaluation can be checked together.
FAQ
Does IP67 guarantee a reading through rain?
No. Ingress protection and optical measurement performance are different requirements. The cited records qualify their IP67 statement as applying inside the lens cavity; the assembled enclosure and wet-target performance need their own checks.
Should I change from 905 nm immediately?
Not from one failed wet reading. Separate wet object, wet window and host communication effects first. Compare any replacement under the same target, geometry and reporting requirements.
What should be included in a wet-target test report?
Include the exact configuration, target material and angle, distance reference, illumination, window condition, timestamps, complete-frame count, invalid outputs, checksum failures and useful-reading criteria. Preserve the dry baseline and raw data.
Frequently asked questions
Does fog mess up range finders?
Yes. Fog scatters the laser pulse in both directions, so less light returns and the receiver may also see an early echo from the fog itself. Expect shorter range and occasional false short readings; filter readings in software.
Can a laser go through fog?
Partly. In light haze a strong pulse still reaches the target; in dense fog the usable range can drop below the visibility distance. 1535 nm modules allow more pulse energy within eye-safety limits, which helps in haze.
What is the maximum range of a laser rangefinder?
In the ERDILRF catalog, up to 18 km for the largest 1.54 µm module under its stated conditions; see long range laser sensors.
Category pages: Laser rangefinder module
Models mentioned in this article
- SPD1200N2905 nm · up to 1.2 km · UART · TTL · ≤5 gFrom $70 · shipping includedSee price & buy
- LR1000E2905 nm · up to 1 km · UART · TTL · ≤10 gFrom $60 · shipping includedSee price & buy