PLC Output Not Switching? 7 Causes & How to Diagnose Them The single fastest diagnostic step is one most people skip: check whether the PLC's own status LED for that output is actually lit when the program commands it on. If the LED is lit but the field device doesn't respond, the fault is downstream of the PLC — wiring, the field device, or its power supply. If the LED itself never lights, the fault is in the program logic, the I/O configuration, or the module itself. That one check splits almost every "PLC output not working" call-out into the right half of the system before you touch a multimeter. This guide covers the seven most common reasons a PLC output fails to switch a field device, split cleanly between what's actually inside the PLC and what's outside it. Talk to Our Expert Team Inside the PLC or Outside It? One Check Tells You Every PLC output module has a status LED per point that reflects the internal logic state — it lights when the program has commanded that output on, completely independent of whether the field device actually receives power or responds. That makes it the cleanest possible split point in the whole fault path: it separates "is the program and module doing what it should" from "is everything downstream of the terminal working." Fault-finding flowchart for a PLC output not switching, split by whether the output status LED is lit If the output LED is lit but the field device does not respond, the fault is downstream in wiring, the field device, or its power supply. If the LED never lights, the fault is in the program logic, forcing, I/O configuration, or the module itself. PLC output not switching field device Is the output's status LED lit when commanded on? No Inside the PLC Program logic, forcing, I/O mapping, or a failed output channel Yes Outside the PLC Field wiring, device power supply, or a failed field device 7 Causes of a PLC Output Failing to Switch 1 Output Forced or Overridden in the Programming Software A very common and easily overlooked cause — an output left forced on or off from a previous commissioning or testing session will ignore the program logic entirely until the force is cleared. Check the programming software's force table before assuming a hardware fault; most platforms display forced I/O clearly, but it's easy to miss if you're not specifically looking. 2 Program Logic Not Actually Reaching That Rung/Output An interlock, a permissive condition, or a fault latch elsewhere in the program can be silently preventing the output rung from ever energising, even though the operator's intent (and the HMI, if the fault isn't surfaced there) suggests it should be on. Cross-reference the actual live logic state in the programming software rather than assuming the program does what the documentation says it should. 3 Incorrect I/O Address Mapping Especially after a module has been replaced, added, or moved to a different slot, the program's I/O mapping can point at the wrong physical address — the program logic and the intended output LED both look correct, but the actual point commanded is a different, possibly unused, output entirely. Confirm the I/O configuration in the project against the physical module layout after any hardware change. 4 Failed Output Channel or Blown Internal Fuse A single output channel can fail — from age, an overcurrent event, or a wiring short that's since been corrected but damaged the driver — while every other channel on the same module keeps working normally. Many modules have per-channel or per-group fusing; check the module's datasheet for fuse or channel-fault indication before condemning the whole module. 5 No Field-Side Supply Voltage Reaching the Module Many I/O modules separate their logic-side power (from the PLC backplane) from the field-side supply that actually powers the switched output — a healthy status LED can still be lit while the field-side 24V supply feeding that output group has failed or been isolated. Confirm field-side supply voltage is actually present at the module's power terminals. 6 Field Wiring Fault Between the Module and the Device A loose terminal, a broken conductor, or a connector that's backed out over time between the output terminal and the field device will produce exactly the symptom of "LED lit, device doesn't respond." Measure voltage directly at the field device's terminals while the output is commanded on, working back toward the module if it's absent. 7 Failed Field Device Itself Once voltage is confirmed present and correct at the device's own terminals and it still doesn't respond, the fault has moved to the device — a burnt-out solenoid coil, a failed contactor coil, or a dead indicator lamp are all common examples. This is confirmed, not assumed, by measuring the device's own coil/load resistance or substituting a known-good unit. Quick Reference: Symptom, Likely Cause & What to Check Symptom Most Likely Cause Quick Check Output LED never lights, program should command it onForced I…