Safety laser scanners: zones, distance and setup in India

A safety laser scanner protects an area. A light curtain protects a line. Using one where the other belongs is how cells end up with a protected-looking gap.

This guide covers how scanners work, how to set the warning and protective zones, the separation distance, mounting height and resolution, the environment problems in Indian plants, and what scanners cost.

When a scanner is the right device

A light curtain is better for a regular opening that people walk through. A scanner is better where the protected shape is irregular, where the hazard moves, or where the same space must be shared with a vehicle. The scanner’s advantage is a configurable zone; the disadvantage is that the zone is invisible and easy to get wrong.

How the scanner sees

The scanner rotates a laser beam through a fan, usually 270 degrees, and measures the distance to anything that reflects light. It compares each measurement against the zones you configured and switches its safety output when a measurement falls inside the protective zone.

• Range: the maximum distance it can detect a target reliably; it shrinks for dark or low-reflectivity surfaces.
• Resolution: the smallest object it detects at a given distance, often quoted at a specific range.
• Response time: the time from detection to output change, including the configured multiple-scan setting.
• Angular resolution: how finely the fan is divided; coarser angles leave gaps at long range.
• Protective field set: the configuration file, which must be validated and recorded.

Two zones, not one

A working installation has a warning zone and a protective zone. The warning zone slows or alerts; the protective zone stops. Setting only one zone means either nuisance stops or no warning at all.

The restart condition matters more than the zone shape. If the operator can stand inside the cell and reach a reset button, the scanner is protecting the boundary and nothing else.

Mounting height and the scan plane

Most scanners detect legs, not torsos, so the scan plane sits low, typically around 300 mm above the floor. That choice has consequences: the plane must be clear of floor clutter, and the separation distance must account for a person stepping over or crawling under it.

• Keep the scan plane level; a tilted scanner changes the geometry you validated.
• Check the floor for ramps, drains and expansion joints that can create false detections.
• Make sure nothing can be stacked inside the warning or protective field.
• Protect the scanner from impact with a guard that does not block the fan.
• Use the manufacturer’s mounting brackets; a bracket that bends invalidates the setup.

Separation distance

ISO 13855 gives the general form S = K × T + C, where K is the approach speed, T is the total response and stopping time, and C is an additional distance that depends on the detection capability and, for scanners, the mounting height and resolution. The scanner manufacturer’s manual gives the exact formula for that model, and it should be used instead of a generic number.

S = K * T + C

K = 2000 mm/s for a walk-in approach
T = scanner response + safety controller + machine stopping time
C = depends on resolution, mounting height and the standard's tables

A scanner set to a coarse resolution at a low mounting height
needs a larger C, and therefore a larger protective field.

Measure the stopping time. A scanner configured for a 0.1 s response feeding a robot that takes 0.8 s to stop has a very different field from one feeding a robot that stops in 0.3 s. Copying a field file from another cell is the most common cause of a protective field that is too small.

Muting, zone switching and AGVs

Zone switching lets the scanner use different fields depending on the robot’s position or direction. It is powerful and easy to get wrong: the switch must be driven by a safe signal, not a standard PLC output, and the inactive field must never leave the hazard unprotected.

On an AGV, the scanner is usually the primary protective device, with the field shape changing with speed and steering direction. That design needs a proper risk assessment and a documented test of every field combination, not just the forward one.

The Indian plant environment

Dust, coolant mist, welding fume and monsoon humidity all reduce optical performance. A scanner that works in a clean lab can produce nuisance stops on a foundry floor within a week, and nuisance stops lead to bypassing.

• Choose an IP rating that matches washdown and dust exposure, and check the window cleaning interval.
• Fit the optional hood or air purge where dust settles on the window.
• Keep the scanner out of direct weld spatter and grinding dust.
• Plan a weekly window clean in the maintenance checklist.
• Log nuisance stops; a rising count is a maintenance signal, not an operator problem.

Wiring and output

The safety output is usually a pair of OSSD signals. They must go to a safety relay or safety-rated input with cross-monitoring, not to a standard PLC input. The configuration port also needs protection: if anyone can connect a laptop and change the field, the validation means nothing.

• Dual-channel wiring with short-circuit and cross-fault detection.
• Password or key protection on the configuration.
• A record of the configuration file, its checksum and the date.
• Labels at the scanner and in the panel showing the protected zone.
• A test point for verifying the output without dismantling the cell.

Response time: the setting people forget

Scanners are configured to react only after an object appears in a set number of consecutive scans. More scans means fewer nuisance stops from dust, rain or a passing insect, and more delay before the output changes. That delay goes straight into the separation distance.

A scanner in a clean indoor cell can run with a low scan count. The same scanner at a loading bay with wind-blown dust needs a higher count, which means a larger protective field for the same machine. Change the setting and the validated distance changes with it, so it belongs in the configuration record.

• Record the configured scan count with the field file.
• Re-run the distance calculation if the count changes.
• Do not raise the count to hide an environmental problem that cleaning would fix.
• Measure the total response time from a test piece, not from the datasheet alone.

Cost in India

Planning ranges, not quotes. Range, resolution, field sets and interface options move the price significantly, and the safety controller is often a separate line.

Selection and validation checklist

• Confirm the required performance level from the risk assessment.
• Check range at the actual target reflectivity, not the best case.
• Check resolution at the distance you need, not at the datasheet’s reference range.
• Confirm response time including multiple scans.
• Confirm IP rating and cleaning routine for the environment.
• Confirm the configuration is password protected.
• Validate every zone and every switching combination with a test piece.
• Record the configuration file, checksum, date and tester.

Mistakes that leave a gap

Related: safety light curtains, robot safety standards in India, AGV vs AMR, robot cell layout, integration checklist.

Scanner outputs land on the same safety inputs, and our safety relay wiring guide covers the EDM feedback loop.

Scanners and their junction boxes belong in a properly sealed panel; see how IP ratings work in Indian workshops.

Scanners suit open layouts where mesh would block the workflow; the guarding cost guide covers the combined approach.

Zone switching adds logic, which is where a safety PLC starts to earn its price over a relay.

Sources and further reading

• ISO 13855 — positioning of safeguards with respect to approach speeds.
• ISO 13849 — safety-related control system performance levels.
• SICK — safety laser scanner configuration and mounting guides.
• OMRON — safety sensor and controller documentation.