Use this step-by-step guide to troubleshoot PLC input problems in real automation systems. Check input LEDs, voltage at the PLC terminal, sourcing vs sinking, wiring faults, sensor output, and scan-time issues before blaming the logic.
This page fits best when the field device is physically doing something, but the PLC or HMI is not showing the input the way it should.
Use the path that matches the real symptom instead of jumping into the wrong troubleshooting page.
Start here when the prox, switch, or sensor appears to be working physically but the PLC never reflects the state correctly.
Use these when the problem may actually be voltage, conductor size, common wiring, or electrical stability instead of PLC logic.
Go here when the input type, sensor output type, or common wiring may be mismatched.
Use this when the signal is short, fast, or inconsistent and scan timing may be the real issue.
If the input is okay but the real machine still is not responding, jump to the output/device side next.
Use the hub when you want the connected structure around inputs, outputs, communication, scaling, voltage, and reference pages.
These flows help users move through the section logically instead of bouncing between unrelated pages.
Use this when the field device appears to work physically but the PLC is not seeing it correctly.
Use this when field power, wire size, voltage loss, or common wiring may be the real problem.
Use this when the input issue is only one part of a larger machine problem.
Use this when the machine is not responding and you need to verify whether the real issue moves downstream after the input.
If a prox, switch, photoeye, pressure switch, or other field input is not showing up in the PLC, do not jump straight into software changes. Start at the physical input path first and verify the signal at each point. :contentReference[oaicite:2]{index=2}
If you are troubleshooting a real PLC issue, start with the full step-by-step guide or use the interactive troubleshooter to narrow the issue down by symptom.
Start with PLC Troubleshooting Guide Use PLC TroubleshooterThis is one of the fastest ways to separate field problems from logic problems. If the physical input LED on the PLC card or remote I/O point never turns on, the PLC logic usually is not the first issue.
Simple rule: no physical input LED usually means no real signal at the PLC input.
Do not stop at the sensor. Measure where the PLC actually receives the signal. A sensor can appear to work while the PLC input still never sees a valid voltage.
A lot of input problems come from the hardware being wired one way while everyone assumes it is wired the other way. If sourcing and sinking do not match the card and sensor type, the input may never behave correctly.
Common mistake: the sensor may switch correctly, but the PLC input still never turns on because the common path is wrong.
If the PLC input is dead, verify whether the field device is actually changing state. Powered is not the same thing as switching.
A good device does not help if the signal never reaches the PLC. Trace the whole path and verify terminals, splice points, quick disconnects, and remote I/O nodes.
This is where timing starts to matter. Fast signals can be real and visible physically, but still get missed by normal scan logic.
If the input works sometimes, suspect vibration, cable flex, loose terminals, weak field power, or a failing sensor rather than a static logic problem.
Intermittent inputs are usually easier to solve when you trend when they fail, not just whether they fail.
Once you know whether the problem is power, wiring, timing, or a broader PLC issue, move into the right calculator or troubleshooting page instead of guessing.
Once you work through the physical input path, move into the next tool that matches the symptom. That is the fastest way to isolate the root cause instead of guessing.
These pages work well with input troubleshooting when you are moving between field devices, wiring, timing, downstream outputs, and electrical support tools.
Start here if the issue is broader than one input point and you want a symptom-first path.
Open troubleshooter →Use the full workflow when the input issue is only part of a larger machine problem.
Open guide →Move here when the input is good but the real device still does not actuate or respond properly.
Open guide →Use this when input type, sensor output type, or common wiring may be mismatched.
Open page →Use this when the signal is real but too fast, too short, or inconsistent for normal PLC scan logic.
Open page →Go here when weak field voltage, long runs, or bad delivered voltage may be the real cause.
Open calculator →Use this when conductor size and run length may be part of the input or field-power problem.
Open calculator →Use this as a quick reference when you need a faster wire check instead of a full sizing path.
Open chart →Jump back to the larger connected system when you want the full PLC / electrical structure around this page.
Open hub →This page is not just a checklist. It helps separate real PLC input failures from field-device, common, wiring, timing, and electrical delivery problems. The current version already had the right system intent; this update mainly brings it into the cleaner page style. :contentReference[oaicite:3]{index=3}
It starts with the real symptom instead of assuming the PLC logic is the first place to look.
It connects input troubleshooting to sourcing/sinking, pulse capture, voltage drop, downstream outputs, and the larger PLC system.
Built for real sensors, proxes, switches, commons, cable flex, intermittent faults, and weak field signals.
It now matches the cleaner white-hero system pages instead of looking like a separate page family.
Input guides help narrow likely causes, but some situations still need live review of the machine, field device, wiring path, PLC input hardware, and electrical conditions. If the issue is active on a real system, use the help page and describe what the machine is doing.