Light-ON vs Dark-ON Photoelectric Sensors: Which Output Mode Do You Need?

What is the difference between Light-ON and Dark-ON?

Light-ON activates the switching output in the light-received state; Dark-ON activates it in the light-interrupted state. Manuals may call them Light Operate / Dark Operate, L-ON / D-ON, or LO / DO. They describe when the output switches, not whether the object is light-colored or dark-colored.

For an ordinary intensity-based sensor, “dark” means the received signal is below its switching level, not necessarily that no light reaches the lens. Hysteresis separates switching and reset boundaries, so a marginal signal is not a clean test state. Create a definite light and dark condition when checking operation.

The term refers to the sensor's sensing light, not simply the brightness of the room. Changing L-ON to D-ON reverses the output assignment. It does not change the optical path, make the sensor see farther, or improve a weak target return.

Which mode makes the output turn ON when an object is present?

For a reliably detected opaque object, choose Dark-ON for beam interruption and Light-ON for ordinary diffuse reflection. The difference comes from what the object does to the sensing light. If your event is a clear path or an absent object, the required mode reverses.

Through-beam and retroreflective: the object removes light

A through-beam receiver looks toward a separate emitter. A retroreflective sensor receives light returned by its reflector. In both arrangements, an opaque object that sufficiently interrupts the intended path creates the dark condition. Dark-ON therefore gives an active output for the blocked path; Light-ON gives an active output for the clear path.

Diffuse reflection: the object supplies the return

A diffuse sensor has its emitter and receiver in one housing. The object reflects light back, so a valid target usually creates the light-received state. Light-ON makes that detection active. This assumes the target produces a distinguishable return and the background does not produce the same detection state.

A conventional optical fork sensor also uses beam interruption. Background-suppression sensors, by contrast, evaluate whether the return comes from an accepted distance region. Where a BGS model uses L-ON/D-ON labels, read its object-position operation chart; total light level alone does not describe its decision.

Is Light-ON the same as NO, PNP or a TRUE PLC input?

No. These labels answer different questions. Light-ON/Dark-ON chooses the optical condition that activates the output; the other labels describe its switching convention, electrical interface or interpretation in the controller.

NO/NC needs a defined reference condition

If “normally open” means inactive with no object present, ordinary diffuse detection maps that behavior to Light-ON. Beam-interruption detection maps it to Dark-ON. Thus Light-ON = NO is not a universal equivalence. Request the target-present/target-absent operation chart when a listing says only NO or NC.

A transistor output is not a mechanical contact, and the contact-like symbol in a PLC program is another convention again. For a relay-output sensor, also distinguish the selected terminal from whether the internal relay is energized.

PNP/NPN determines the current path, not the optical mode

For ordinary three-wire DC outputs, PNP supplies current to a compatible sinking input; NPN sinks current from a compatible sourcing input. Either output type can operate in Light-ON or Dark-ON when the specific model supports that mode.

An active NPN output can sit near 0 V relative to the sensor's negative supply while the compatible PLC input reports ON: current is flowing through the input circuit. Therefore, low signal voltage is not automatically a FALSE input bit. The input module's wiring and state convention are decisive.

Read the chain in this order: physical target → accepted optical state → sensor output → PLC input → application meaning. Changing an optical mode cannot repair an incompatible output circuit or a missing connection.

Can the PLC simply invert the input?

For a healthy, steady two-state signal, software can often express the opposite meaning. But inversion does not repair missing optical contrast, change electrical compatibility, or guarantee fault detection. It can also change which target edge a counting instruction sees.

For example, a Dark-ON through-beam output becomes active when a carton enters the beam and inactive when it leaves. Reversing the mode swaps those transitions. Whether the signal voltage rises or falls also depends on the output circuit. Review edge-triggered logic, timers and startup behavior before changing a working machine's signal convention.

How do you change the mode without changing sensitivity?

Find the output-mode control in the exact sensor instructions. It may be a selector, menu parameter, specified control-wire connection or fixed model variant. Do not reverse the supply wires to change Light-ON/Dark-ON. Isolate equipment before connection changes and prevent unintended movement during configuration tests.

Separate the mode control from the detection adjustment

A sensitivity or teach adjustment changes how the sensor distinguishes the optical states. The mode control chooses which state activates the output. Changing both together makes a reversed signal harder to diagnose.

The Banner Q85 manual, page 3, illustrates why the full variant matters: Q85VR3 detectors select light/dark operation through the hookup, while Q85BW13 and Q85BB62 detectors use a switch. Sensitivity has its own adjustment. This is a documented example, not a wiring instruction for another sensor.

Read the correct indicator

A power light, signal/stability indicator and output indicator need not show the same state. Colors are model-specific. The output indicator helps check the selected logic; the stability indication helps assess optical margin. Neither proves that the PLC receives the intended signal.

After selecting the mode, test both target states and record the output result. If the sensor uses stored parameters or IO-Link configuration, confirm the intended values also remain effective after the applicable restart or replacement procedure.

Why does detection still look wrong after selecting the mode?

A clean reversal in both target states points toward logic. Failure to distinguish those states points toward sensing or signal transmission. Compare the sensor's documented output indication with the physical PLC channel before changing anything else.

• The sensor switches consistently, but in the wrong target state: confirm the light path and mode. On a multi-output model, also confirm you are observing the intended output rather than a complementary or diagnostic channel.
• The sensor indication is correct, but the PLC channel does not follow: inspect output/input compatibility, the specified common, conductor and terminal assignments. Use the sensor and input-module diagrams; do not try to fix this by repeatedly toggling L-ON/D-ON.
• The PLC input follows correctly, but the action is reversed: compare the raw input with the named application variable, inversion and edge instructions. The problem may be in interpretation rather than sensing.
• It works slowly but fails at speed: check the actual ON and OFF intervals, sensor timing functions, input filters and controller capture. A mode change swaps active intervals; it does not remove the need to capture the event.

If the sensor itself cannot distinguish the two target states, investigate the optical cause. A clear object may only slightly reduce reflector return; a shiny object may return unwanted light; a dark diffuse target may provide too little return. Polarized retroreflection can help reject mirror-like reflections, but it is not a blanket guarantee for transparent materials.

For a missing-part check, define when a part should be present. The gap between correctly spaced products is also an absence. An absence-active output alone cannot tell a missing part from a normal gap without the machine's cycle or position context.

Does Dark-ON make a photoelectric sensor fail-safe?

No. Dark-ON is an output mode, not a safety rating. A powered beam receiver may produce the same dark state for a carton, dirt or misalignment. If the receiver loses power, its ordinary transistor output cannot be relied on to energize an alarm. An internal failure may leave an output either active or inactive.

Likewise, using Light-ON to monitor a clear beam can support a process alarm when the signal disappears, but it does not prove every dangerous fault is detected. Ordinary object-detection photoeyes must not be treated as personnel-protection devices. Safeguarding requires suitable safety-rated equipment and validation of the complete safety function.

What should you verify before using the selected mode?

Verify the required physical event, the output state and the receiving input together. The useful result is a documented two-state check, not simply a photograph of the selector.

1. State the event: “output active while the carton blocks the beam” is clearer than “use NO.” Name the sensing arrangement and the output being used.
2. Create both real conditions: record target present and absent, the relevant sensor indication, the PLC channel and the application meaning. Do not use a hand as the only substitute for the production object.
3. Check the limits that matter: repeat with the actual target/background variations and operating speed. Observe both entry and exit; a single successful transition is incomplete evidence.
4. Retain the configuration: record the exact part number, mode, teach or distance settings, output type and PLC channel. Check the required restart behavior using the equipment's controlled commissioning procedure.

The selection rule remains simple: identify whether your required event removes the sensing light or creates the accepted return, choose the corresponding mode, then verify the complete signal path. Keep optical detection, electrical conduction and machine meaning separate.