PLC Input Not Responding

Walt — Simple Man Takeaway

Before you blame the program, prove the signal made it through the wire.

Plain-English Summary

Use this flow when a prox, photoeye, limit switch, pressure switch, pushbutton, safety device, or other input appears to be changing in the field but the PLC input status does not follow the real condition.

R.E.A.L. firstRead-only firstCapture before changingReverse-trace failed conditionsTrap intermittent ghosts

First-Check Flow

1. Confirm the real field condition

Look at the device and the machine condition first. Prove what should be true before judging the PLC.

2. Check device power and local indicator

Verify sensor power, supply/common, device LED, alignment, target, and physical actuation.

3. Check the input card side

Measure or observe the signal at the terminal, input card indicator, and PLC input status online.

4. Compare device state, card state, and logic state

Separate field device failure from wiring, terminal, card/channel, alias/tag, or logic-use problems.

5. Reverse-trace the failed input use

If this input blocks a failed rung, use Find All and trace to the logic that creates or consumes the condition.

6. Trap intermittent drops

If the input flickers, drops, bounces, or only fails during motion, arm Ghost Busting™ on the input and affected sequence step.

Field Checks

Field device actually actuated or de-actuated
Correct supply voltage and common present
Sensor target, alignment, range, contamination, or environment checked
Terminal voltage measured at input card
PLC online input status compared to real field state
Alias/tag/reference confirmed
Input card/channel health checked

Watch Out For

Dirty photoeyes or reflective false targets
Loose terminals or broken conductors near moving cable track
Shared commons, blown fuses, or missing 24VDC
Wrong sinking/sourcing wiring assumptions
Intermittent vibration-induced signal loss
Logic using the wrong bit, alias, or inverted condition

Reverse-Trace or Ghost Busting™?

Use Reverse-Trace Logic Solving™
when the failure is stable and visible live. Open the PLC program, monitor in RUN mode, chase only failed conditions, find the driving OTE, and repeat failure-to-failure.

Use Ghost Busting™
when the failure is intermittent, self-clearing, timing-based, or disappears before maintenance sees it. Select the suspect routine from the HMI and let the comparator trap expected-vs-actual mismatch every scan.

Find the failed result. Identify the blocking condition. Reverse-trace only what is failing. If the truth disappears, trap the ghost.

Related Calculators / SWAT Screens

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

Walt says STOP! - Safety First

Make these checks prior to proceeding.

Do not bypass safety, force outputs, defeat guards, or work live beyond your qualification and site procedure. If motion, stored energy, live electrical exposure, lockout/tagout requirements, or personnel inside guarded areas are involved, stop and follow the required safety process.