ApprenticeLow risk

Proximity sensor permanently on (always made)

A proximity sensor reads 'detected' all the time — its output stays on even with no target present, so the controller always sees the input made.

Safety first

A stuck-on sensor can make a machine think it's in a position it isn't. Confirm actual position before moving anything based on the input.

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.

Full detail — causes, the why, and common mistakes.

Likely causes

Ranked from most to least likely.

  1. 1

    Target/metal too close or fixed metal in range

    Most likely

    Fixed metal within the sensing range, or the gap set too small, keeps an inductive prox permanently triggered.

  2. 2

    Sensor output short / failed on

    #2

    The sensor's output transistor has failed in the conducting state, holding the signal on.

  3. 3

    Wiring short to the active line

    #3

    A cable short or pinched wire holds the input line at the active level regardless of the sensor.

  4. 4

    Wrong sensor type for the application

    Least likely

    A normally-closed (NC) sensor used where NO logic is expected reads as always-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.

Test 1 of 3
1

Remove all targets and check the sensor's indicator LED and output state.

Expected reading

Output turns off with no target in range.

If it passes

Sensor releases — your 'always on' was a present target; check positioning.

If it fails

Stays on with nothing present — check for fixed metal, then the sensor/wiring.

View all expected readings at once
1. Remove all targets and check the sensor's indicator LED and output state.
Output turns off with no target in range.
2. Check for fixed metal within range and confirm the sensing gap is set correctly.
No fixed metal in range; correct gap.
3. Disconnect the sensor output and check whether the input clears; confirm NO/NC type.
Input clears when the sensor is disconnected (if it's the sensor).

Fault-finding flowchart

The same logic as a decision tree.

  1. 1
    start

    Prox always on

    → step 2
  2. 2
    decision

    Does the output turn off with no target present?

    Yes→ step 3No→ step 4
  3. 3
    result

    It was a present target — check positioning/gap.

  4. 4
    decision

    Is there fixed metal in range or the gap too small?

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

    Reposition / adjust the gap.

  6. 6
    decision

    Does the input clear when the sensor is disconnected?

    Yes→ step 7No→ step 8
  7. 7
    result

    Sensor failed on — replace (confirm NO/NC).

  8. 8
    result

    Wiring short to the active line — find and repair.

Common mistakes apprentices make

  • Not realising fixed nearby metal keeps an inductive prox triggered.
  • Confusing an NC sensor's 'always on at rest' behaviour with a fault.
  • Blaming the sensor when a pinched cable shorts the line.
  • Setting the sensing gap too small.

When to stop & escalate

If a stuck input affects a safety or positioning interlock, treat position confirmation as critical before any movement. Replace a failed sensor rather than working around it.

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.

Related faults

Learn the theory

How the gear and circuits behind this fault actually work.