QualifiedMedium risk

PLC output flickering / device chattering

A PLC output rapidly switches on and off, making the connected device (contactor, valve, lamp) chatter or flicker instead of staying in a steady state.

Safety first

A chattering output makes a contactor arc and a valve hammer. Don't leave it running like that. Confirm what the output controls before forcing.

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

    Program logic toggling the output

    Most likely

    The logic is genuinely switching it rapidly — an unstable condition, race, or a sensor input bouncing.

  2. 2

    Bouncing input driving the logic

    #2

    A noisy/intermittent input the logic depends on makes the output follow it.

  3. 3

    Marginal output load / supply

    #3

    A marginal field supply or a load near the output's limit can't hold steadily.

  4. 4

    Failing output point

    Least likely

    The output point itself is failing and switching erratically.

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

Watch the output bit/logic: is the program itself toggling the output?

Expected reading

A stable commanded state from the logic.

If it passes

Logic stable but output chatters — check field supply/load and the output point.

If it fails

Logic is toggling — trace the input/condition causing it (often a bouncing input).

View all expected readings at once
1. Watch the output bit/logic: is the program itself toggling the output?
A stable commanded state from the logic.
2. If logic toggles, find the input/condition driving it; check that input for bounce/noise.
A stable input/condition once corrected.
3. If the logic is stable, check the field supply/load and try a known-good output point.
Steady supply/load; stable on a good output.

Fault-finding flowchart

The same logic as a decision tree.

  1. 1
    start

    PLC output flickering

    → step 2
  2. 2
    decision

    Is the program itself toggling the output?

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

    Is a bouncing/noisy input driving it?

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

    Is it stable on a known-good output with good supply/load?

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

    Fix the bouncing input or debounce in logic.

  6. 6
    result

    Unstable logic condition — correct the logic (change-control).

  7. 7
    result

    Original output point failing — repair/replace.

  8. 8
    result

    Marginal field supply/load — strengthen it.

Common mistakes apprentices make

  • Forcing the output to mask a bouncing input.
  • Not checking whether the logic itself is toggling.
  • Overlooking a marginal field supply.
  • Leaving a contactor chattering on a flickering output.

When to stop & escalate

Logic/debounce changes follow site change-control with backups. A failing output point is a module repair per procedure.

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