AdvancedLow risk

PLC input stays on after the sensor has switched off

A digital input LED (and the PLC bit) stays on even after the sensor/switch has clearly released. The logic thinks the input is still made, so the sequence stalls or behaves wrongly.

Safety first

A stuck input can make a machine behave unexpectedly. Treat the machine as able to move, keep clear of moving parts, and isolate/secure it before working on field wiring.

Isolate, lock out / tag out, and prove dead before working unless a live test is specifically required, authorised, and carried out under proper supervision. Always follow local regulations, your site procedures, and the equipment manufacturer's documentation.

Apprentice mode

Full walk-through — the why, what readings mean, mistakes & safety.

Likely causes

Ranked from most to least likely.

  1. 1

    Leakage current holding the input on

    Most likely

    Three-wire sensors and long cable runs leak a small current. With a high-impedance input it can stay above the off-threshold, so the input never drops out. A bleed resistor or different input type may be needed.

  2. 2

    Welded/stuck field contact

    #2

    A relay or switch contact feeding the input that's welded closed keeps the input made regardless of the actual condition.

  3. 3

    Wiring short to the supply rail

    #3

    A conductor chafed to the +24V (or 0V on sinking) keeps the input energised independent of the sensor.

  4. 4

    Forced bit or logic latch in the program

    Least likely

    An input forced in the software, or a latch/seal in the logic, can make a healthy input appear stuck on.

Reports are saved on this device to reflect what you actually find.

Testing sequence

Work through one test at a time. Expected reading and what each result means.

On the tools? Job Mode shows one test at a time with thumb-sized buttons — your place and readings carry straight over.

Enter Job Mode
Test 1 of 3
1

Measure the voltage at the input terminal with the sensor released and compare to the input's off-threshold.

Expected reading

Input voltage well below the off-threshold when the sensor is off.

If it passes

Field signal is genuinely off but the bit is on — suspect a forced bit or logic latch.

If it fails

Voltage still present at the terminal with the sensor off — it's leakage or a wiring/contact fault keeping it energised.

Mark this test
View all expected readings at once
1. Measure the voltage at the input terminal with the sensor released and compare to the input's off-threshold.
Input voltage well below the off-threshold when the sensor is off.
2. Disconnect the field wire at the input; check whether the input drops out.
Input turns off the moment the field wire is removed.
3. Check the program for forces and any latch/seal logic on that bit; for a three-wire sensor on a long run, consider leakage and the input/sensor type.
No forces, no unintended latch; sensor/input suited to the run.

Fault-finding flowchart

The same logic as a decision tree.

  1. 1
    start

    PLC input stuck on after sensor off

    → step 2
  2. 2
    decision

    Is voltage at the input below the off-threshold with the sensor off?

    Yes→ step 3No→ step 4
  3. 3
    decision

    Does the input drop out when the field wire is removed?

    Yes→ step 5No→ step 6
  4. 4
    result

    Field signal still present — leakage / short / stuck contact in the field wiring.

  5. 5
    result

    Fault is in field wiring/sensor — but check program forces too.

  6. 6
    result

    Module fault or forced/latched bit — clear forces/logic or replace the module.

Common mistakes apprentices make

  • Blaming the PLC module when leakage from a three-wire sensor is holding the input on.
  • Forgetting to check for forced bits in the program.
  • Not disconnecting the field wire to split field vs module faults.
  • Adding a 'fix' in software to mask a stuck field contact.

When to stop & escalate

If a welded field contact is feeding a safety-related function, treat it as a safety issue and escalate. Leakage problems on long sensor runs may need an input-type/design change — flag rather than bodge.

If you're past your competence, authorisation, or the safe limits of the job — stop and hand it on. There's no fault worth getting hurt over.

Was this guide helpful?

Related faults