Leuze LSIS 400i Smart Camera — No Read

Leuze · intermediate · 25 min

A Leuze LSIS 400i smart camera that won't read a 1D/2D code is usually a focus, lighting, or code-type-configuration problem, not a broken camera. Learn to set it up over the browser (webConfig), dial in the motorized focus, and work through a no-read.

ℹ️ The LSIS 400i is configured entirely through a web browser over Ethernet — no extra software or connection unit. A no-read is almost always focus, lighting, or the enabled code type, and the camera even has an OLED display and motor-driven focus to help you set it.

Set it up in the browser (webConfig)

The Leuze LSIS 400i is a smart camera for industrial image processing — omnidirectional 1D and 2D code reading, code qualification, type detection, object detection and position. A big practical advantage: it's configured directly via a web browser through its configuration interface over Ethernet — no additional connection unit or separately installed software is required. So access is just a browser pointed at the camera's IP. It also has an OLED display for basic configuration and messages, motor-driven focus, internal lighting and an 8 mm lens.

Work a no-read in order

A code that won't read is a chain — image, then decode. Check them in order:

1. Focus. The 400i has motor-driven focus — set the focus for your actual working distance in webConfig. A soft image is the number-one no-read cause. Use the live image to sharpen the code edges.
2. Lighting / exposure. Use the internal lighting effectively; adjust exposure/gain so the code has good contrast and isn't blown out or too dark. Watch for glare on shiny/curved surfaces — angle the part or lighting.
3. Code type enabled. Confirm the symbology you're actually reading (e.g. Code 128, DataMatrix, QR) is enabled and configured in the job. The camera reads many types, but only the ones you turn on.
4. Code quality / size. Verify the printed/marked code quality and that it's large enough (enough pixels per module) at your field of view and distance.
5. Trigger / timing. Make sure the read is triggered at the moment the code is in view and steady (not motion-blurred).

Check the interfaces

The 400i offers 8 × I/O, 1 × RS232 and 1 × Ethernet (M12, IP65). If the read result isn't reaching the PLC, confirm the output/interface that carries the result and its wiring — a good read that isn't wired out looks like a failure downstream.

Step-by-step

1. Browse to the camera (webConfig over Ethernet); use the OLED/live image.
2. Set the motorized focus for the real working distance until the code is sharp.
3. Fix lighting/exposure for clean contrast, kill glare.
4. Enable the exact code type you're reading in the job.
5. Confirm trigger timing and the output wiring to the PLC, then verify on real parts.

Never do this

Don't crank gain/exposure and loosen decode tolerances just to force an occasional read of a poor code — you'll get unreliable reads and false results in production. Fix the image (focus, lighting) and the code quality so reads are solid and repeatable.