Prox Sensor Not Detecting

Walt — Simple Man Takeaway

A prox does not care where you think the target is. It only cares whether the target enters its real detection field.

Plain-English Summary

Use this flow when a proximity sensor fails to detect its target, detects late, detects inconsistently, or drops out during machine motion. Prox sensors depend on target material, distance, alignment, mounting stability, wiring, and electrical compatibility.

R.E.A.L. firstProve process truthCapture before changingCompare field state to logic stateHumans remain authoritative

Sensor / Instrument First-Check Flow

1. Identify sensor type

Confirm inductive, capacitive, magnetic, ultrasonic, shielded, unshielded, or specialty sensor.

2. Confirm target material and size

Verify the target is large enough and made of material the sensor can detect.

3. Confirm target distance and path

Watch the actual motion path and make sure the target enters the sensing field.

4. Compare device and PLC states

Check sensor indicator, PLC input, HMI status, and the logic using the signal.

5. Check electrical health

Verify supply voltage, signal common, connector, cable, and input card state.

6. Check mounting and vibration

Look for loose brackets, target looseness, impact, vibration, or mechanical overtravel.

7. Check replacement specs

Confirm sensing range, output type, and wiring match the original application.

8. Test at speed

Compare slow jog behavior against real production speed.

Field Checks

Sensor type and output style
Target material, size, distance, and path
Sensor indicator vs. PLC input vs. HMI state
Supply voltage, signal common, connector, cable, and input card
Bracket tightness, target looseness, overtravel, and vibration
Replacement sensor sensing range and output type
Metal correction factors for inductive sensors
Contamination, chips, coolant, oil, dust, shielding effects
Signal timing at actual machine speed

Watch Out For

Target never actually entering the real sensing field
Wrong replacement sensor range or output type
Signal works in jog but fails at production speed
Loose target or loose bracket
Prox detecting too late for the sequence timing
Blaming the sensor when the mechanism stopped bringing the target home

Reverse-Trace / Ghost Busting™ Decision

Use Reverse-Trace Logic Solving™
if the prox signal is stable but a permissive, interlock, or sequence step using it is blocked.

Use Ghost Busting™
if the prox flickers, drops for one scan, arrives late, or disappears before a technician sees it.

Recipe / Health Log

Record the good, the bad, and the in-between: real-world condition, sensor state, PLC input state, HMI display, logic use, product/material, method, atmosphere, utility condition, timing, symptom, corrective action, and result.

A.I.R.O.N. reminder: the manual Recipe / Health Log teaches the user what A.I.R.O.N. captures automatically — conditions, context, timing, material, method, atmosphere, signal behavior, and outcome — so learning does not disappear.

Related Calculators / S.W.A.T. Screens

Sensory King™ Prox / Photoeye Signal Sanity Check Sensory King™ Sensor False-Trigger Clue Screen Volta™ 24VDC Power Supply Load Check

Related Handbook / Flows

PLC Input Not Responding Sequence Step Not Advancing Reverse-Trace Logic Solving™

Walt says STOP! - Safety First

Make these checks prior to proceeding.

Stop and follow site procedures when machine motion can restart, hands must enter a pinch/crush/clamp/slide/transfer zone, sensor adjustment could allow an unexpected cycle, bypassing prox feedback could defeat protection, or lockout/tagout is required. Do not place hands in moving mechanisms to prove a prox.

Key Terms in This Section