PLC Troubleshooting Guide

Step 1: Confirm the PLC is actually running

Before chasing sensors, HMIs, or outputs, verify that the controller is healthy. If the PLC is faulted, powered down, or offline, nothing else matters yet.

• Check that the controller is in RUN mode.
• Look for major faults or module faults.
• Confirm the rack or remote I/O has power.
• Check whether communication LEDs look normal.
• Compare current status to a known-good condition if one exists.

Step 2: Check communication problems first

If the HMI is offline, remote I/O is faulted, or devices are dropping from the network, decide whether the problem affects one node or multiple nodes. That tells you whether to suspect device-level issues or a larger network problem.

• Check IP addresses, subnet, and gateway if used.
• Look for duplicate IP conflicts.
• Verify Ethernet cables, M12 connectors, and switch ports.
• Check whether the PLC communication module is healthy.
• Determine whether only one path is down or the whole segment is affected.

Step 3: Verify inputs before blaming logic

If the PLC is not seeing a sensor, prox, switch, or field signal, measure the signal where the PLC receives it. Do not stop at the sensor end and assume the PLC is getting the same thing.

• Measure input voltage at the PLC terminal or I/O node.
• Check whether the device output is actually switching.
• Verify sourcing and sinking match the hardware design.
• Watch the input LED on the card if available.
• If the LED changes but logic does not, suspect mapping, aliasing, or program usage.

Step 4: Check outputs and field power

If the machine is not actuating, verify whether the PLC output is actually turning on and whether the load is receiving usable power under real conditions.

• Check whether the PLC output point is active.
• Measure voltage at the output terminal.
• Check relay, contactor, valve, or drive control wiring.
• Verify field power and common return path.
• Do not confuse a commanded output with a powered load.

Step 5: Separate analog signal issues from scaling issues

A bad displayed value is not always a bad signal. First decide whether the raw electrical signal is wrong, or whether the conversion into engineering units is wrong.

• Measure the real 4-20mA or 0-10V signal at the PLC input.
• Check the configured analog range.
• Make sure signed vs unsigned values are handled correctly.
• Verify the HMI is not scaling a value that is already scaled in logic.
• Confirm the device and card are using the same signal type.

Step 6: Check scan time and missed signals

If short pulses, fast sensors, or quick events are being missed, the issue may be timing rather than wiring. Normal cyclic scan logic does not catch every fast event.

• Compare pulse duration to PLC scan time and module update time.
• Check input filter or debounce settings.
• Watch whether the physical input LED changes faster than the logic can respond.
• Consider immediate input, hardware latch, or high-speed input hardware where needed.

Step 7: Treat intermittent issues differently

Intermittent faults usually mean unstable power, cable damage, loose terminals, vibration, grounding noise, or device electronics that are beginning to fail. These are often harder to catch because the machine works sometimes.

• Trend when the issue happens: motion, load change, heat, or random timing.
• Check for cable flex points and strained connectors.
• Look for voltage dip under load.
• Check whether multiple nodes drop together or only one device does.
• Suspect noise, grounding, or poor shield termination on unstable analog signals.

Step 8: Use the right next tool

Once you know the problem area, move into the right calculator or tool. This saves time and makes your site more useful than a generic checklist page.