Troubleshooting guide
Is It the Sensor or the Machine? Diagnosing a PLC Input Fault
When a sensor reports a fault, you've got two suspects: a real problem on the machine, or a problem in the sensor circuit itself. Chase the wrong one and you either replace a good sensor or miss a real fault.
Last updated: August 2026 · written and reviewed by a working maintenance professional
A PLC input goes bad and the fault light comes on. The question that decides everything: is the machine actually in the state the sensor is reporting, or is the sensor circuit feeding the PLC bad information? These lead to opposite actions, and getting it wrong is expensive both ways — you either swap a perfectly good sensor, or you chase a machine fault that was never there.
The good news: telling them apart is fast, and fast matters when a fault has stopped the line.
Trust nothing — verify the real-world condition first
Before you touch the sensor, confirm what's actually true on the machine. If a proximity sensor says “no part present,” go look — is the part there? If a level switch says “low,” is the tank actually low? This thirty-second reality check splits your problem in half. If the machine really is in the reported state, the sensor is doing its job and your fault is mechanical or process-side. If the machine is fine but the sensor disagrees, the sensor circuit is your suspect.
When the sensor is lying: work the signal chain
If the real-world condition doesn't match what the PLC sees, walk the signal from the field back to the processor. Check the obvious physical things first because they're fastest: sensor gap and alignment (a proximity sensor mounted too far from its target, or aimed at the wrong material, simply won't detect reliably), wiring and connections (a wire pulled from a terminal is more common than a failed sensor), and the sensor's power and output with a meter.
The trap: the program looks right but nothing moves
One case worth knowing because it fools people: the PLC output bit is set in the program, everything looks correct on screen, but the device doesn't act. The program is not the machine. A blown output fuse or a broken wire downstream means the bit turns on and nothing happens. When the logic says go and the world says no, measure the actual voltage at the output terminal — don't trust the screen.
Reading about it is one thing. Doing it is another.
faultline101 drops you into scenarios like this one where the readings respond to your choices — chase the wrong theory and you'll watch it cost you, exactly like a real callout. You practice the sequence until it's instinct, on equipment you can't actually break.
Module 1 is free, no card required — see how it works.
Works with no signal. Install it on your phone and the whole course — 35 modules, 210 faults — comes with you into the plant.
Try the trainer freeSensor faults reward a calm order
Verify the real condition, then walk the signal chain from field to processor, checking the fast physical things before assuming a component failed. Most “bad sensor” calls turn out to be a gap, a wire, or a genuine machine condition the sensor correctly caught — and each of those is faster to find than a sensor is to replace.
The instinct to swap the sensor first is exactly backwards. The sensor is usually the honest one in the story. Your job is to find out whether it's telling the truth — and that's a skill you build by doing it, not reading it.