PLCs are excellent diagnostic tools when you use them to observe the sequence instead of using them as a place to guess.
SURVIVAL RULE: Separate field state, I/O state, logic state, and output state.
The PLC is not a magic box
A PLC reads inputs, executes logic, and updates outputs according to a program. When troubleshooting, separate four layers: what the field device is doing, what the input module sees, what the program believes, and what the output module commands. Confusing these layers creates false conclusions.
A guard switch may be physically closed, but its safety input may remain off. A normal input LED may be on, but the program may require a second permissive. An output bit may be true, but field voltage may be missing.
Field habit: Move through the layers in order and name the state at each one.
Common trap: Do not say ‘the PLC sees it’ unless you know whether you mean module LED, input tag, or logic condition.
Online monitoring is observation first
Going online with a controller should initially be an observation activity. Find the relevant input, output, permissive, sequence step, timer, or fault bit. Watch how those states change when the machine moves. Good monitoring can reveal the first missing condition without any program change.
If a cylinder does not extend, you may see that the command bit never turns on because a ‘part present’ permissive is false. That prevents an unnecessary valve replacement.
Field habit: Follow your plant’s access and change-control rules, and make sure you have the correct project and controller.
Common trap: Never force a bit or edit logic simply because the machine is stopped. Forcing can bypass the very conditions that protect the machine.
Quick check
What should be true at this point in the sequence?
What evidence can prove or eliminate this section of the system?
What changed recently or only under the failing condition?
Output LED on does not mean load on
Many output modules indicate internal command state, but the field circuit may still be open. The output group may lack field supply, a fuse may be open, a terminal may be loose, or an interposing relay may have failed.
When an output LED is on and the solenoid is off, measure at the output terminal and then at the load. This distinguishes module/field supply problems from cable or device problems.
Field habit: Use the diagram to identify whether the output is sourcing, sinking, relay-based, or driving an interposing device.
Common trap: Do not replace a PLC output module until you have proven the module is the missing link.
Logic explains why, not always what failed
The PLC program is excellent for answering ‘why is the command not being issued?’ It is less reliable as a direct statement of component health. A timer timeout may say ‘cylinder failed to extend,’ but the actual cause could be no air, a stuck valve, bent mechanics, broken sensor, or lost output power.
Treat alarms and logic as maps to the expected sequence. Then prove the physical failure using field evidence.
Field habit: When you find a recurring logic condition, note the tag description and physical device it represents.
Common trap: Do not rename the fault after the alarm message and assume diagnosis is complete.
Quick check
What should be true at this point in the sequence?
What evidence can prove or eliminate this section of the system?
What changed recently or only under the failing condition?
Field Exercise
Monitor one PLC-controlled actuator from input permissives through output and feedback, without making any program change.