Use this section to troubleshoot PLC-side problems, work through communication and input issues, evaluate scan-time-related misses, scale analog values, and check common electrical design questions like voltage drop and wire sizing.
This is built for practical controls work — machine troubleshooting, field checks, startup, and design support.
Use the path that matches the real symptom instead of guessing which PLC or electrical tool fits.
Start here if you want the full troubleshooting workflow before jumping into individual calculators or symptom pages.
Start here when the prox, photoeye, switch, or input condition does not match what the PLC or HMI is showing.
Go here when the problem is communication-related — remote I/O offline, module faulted, network issue, IP mismatch, or no connection.
Use this when the PLC seems to miss a pulse, a short signal, or a fast event that is physically happening.
Use this when the displayed value, engineering units, or raw signal interpretation does not look right.
Use these when the question is more electrical than PLC logic — wire sizing, voltage drop, ampacity, or reference charts.
These paths help people move through the section logically instead of bouncing around randomly.
Use this when you want the full problem-first path before drilling into specific symptoms.
Use this when a sensor or input state is not matching what the machine is doing.
Use this when the PLC, HMI, remote I/O, or Ethernet path is offline or unstable.
Use this when the issue is signal interpretation, wire runs, voltage, or reference sizing.
Most PLC issues are not random. They usually fall into a handful of repeatable failure patterns: field signal mismatch, missing power, bad commons, fast signals, failed communication, scaling errors, safety interlocks, or logic conditions that are not satisfied.
This is one of the most common troubleshooting problems. The sensor or switch appears to be working in the field, but the PLC input bit does not change. Common causes include wiring faults, incorrect sourcing or sinking configuration, missing common, incorrect input address, failed input point, loose terminals, or field power problems.
If the PLC output bit is on but the solenoid, relay, contactor, valve, or light does not respond, the problem is often outside the PLC logic. Check output card status, field power, blown fuses, load-side wiring, relay contacts, output type, and whether the device has the correct return path.
Intermittent signals are often caused by loose wiring, vibration, electrical noise, poor grounding, damaged cables, marginal sensors, or a pulse that is too short for the PLC scan to catch reliably. Do not assume a flickering signal is always logic related.
Communication faults usually come from IP conflicts, wrong subnet, incorrect gateway, bad Ethernet cable, unmanaged switch issues, duplicate addresses, wrong driver path, disabled adapter, failed module, or a controller that is not reachable from the current network.
Analog issues are often scaling problems, not sensor failures. Check the raw value, card range, signal type, engineering unit range, sensor configuration, broken loop wiring, shield grounding, and whether the HMI is using the same scaled value as the PLC.
When inputs and outputs look normal but the machine will not cycle, the issue is usually a missing permissive, sequence step, safety condition, mode condition, reset requirement, HMI command, robot ready signal, drive ready bit, or interlock that has not been satisfied.
Many PLC issues get misdiagnosed because the visible symptom is not the root cause. A PLC may show the symptom, but the actual problem may be wiring, field power, addressing, safety, communication, or mechanical movement.
A lot of problems blamed on the PLC are actually outside the controller. Before changing code, verify the physical signal, field voltage, common, device state, and input or output module indication. Changing logic too early can hide the real fault and create a second problem.
Inputs and outputs need the correct electrical reference. A missing common, incorrect common, floating reference, or mixed wiring style can make a good sensor appear dead. Always measure between the correct points, not just to a nearby ground that may not be part of the circuit.
A signal can happen physically and still be missed by the PLC. Short pulses, prox triggers, encoder-related events, and fast reject signals may need input filtering review, high-speed input hardware, latch logic, interrupt handling, or a different sensing strategy.
Sourcing and sinking mismatches are a common reason inputs and outputs do not behave as expected. The device may be good, the card may be good, and the wire may be connected — but the current path may still be wrong.
HMI values can be delayed, mapped wrong, stale, or pointed at the wrong tag. When troubleshooting a real issue, confirm the PLC tag, module status, and field device before assuming the HMI display is telling the whole story.
Swapping sensors, cards, power supplies, relays, or cables can work, but it can also waste time if the root cause is configuration, wiring, or logic. Prove whether the fault follows the device, the wire, the input point, the output point, or the program condition.
The PLC is often where the problem becomes visible, but it is not always where the problem starts. These outside issues can look like controller faults if you only look at the logic.
Sensors, switches, valves, relays, contactors, drives, and actuators can fail while the PLC is working normally. Check device LEDs, output voltage, actual actuation, connector damage, and whether the device changes state under real machine conditions.
Weak 24 VDC power, overloaded supplies, blown fuses, shared commons, voltage drop, bad terminals, and loose conductors can all cause PLC-side symptoms. Measure voltage while the load is active, not only when the circuit is idle.
Ethernet switches, unmanaged loops, IP conflicts, damaged cables, wrong subnets, bad gateways, or overloaded networks can make a PLC, HMI, robot, drive, or remote I/O rack appear faulty when the infrastructure is the real issue.
Binding cylinders, jammed slides, misaligned tooling, worn bearings, part-present errors, and physical obstructions can make the logic look wrong. Always compare commanded state, output state, and actual machine motion.
Guard doors, light curtains, E-stops, safety relays, safety PLC zones, robot safety, and drive safe-off conditions can block motion while standard PLC logic appears ready. Confirm safety status before chasing normal outputs.
Incorrect HMI tags, stale values, bad aliases, wrong PLC shortcuts, or mismatched arrays can make a system look broken even when the actual PLC state is correct. Compare HMI value, PLC tag, and physical machine state.
Use these quick decision checks when you are standing at the machine and need to decide which direction to troubleshoot first.
Focus on wiring, input card, common, addressing, terminal assignment, and sourcing or sinking configuration. Do not start by rewriting logic.
Focus on output card indication, load power, fuse, relay, solenoid, contactor, return path, and whether another safety or permissive circuit is blocking the device.
Focus on IP address, subnet, gateway, Ethernet cable, switch, driver path, module configuration, and whether the device is reachable from the same network.
Focus on raw value, input range, engineering scaling, sensor range, broken loop wiring, voltage drop, and whether the HMI is reading the correct scaled tag.
These are the current PLC and electrical pages in the section. Together, they cover troubleshooting, communication, signal behavior, scaling, voltage checks, and reference support.
Start here if you want the full step-by-step troubleshooting workflow before drilling into a specific symptom page or calculator.
Open guide →Start here for field-device mismatch problems, sensor state issues, PLC-side logic checks, addressing questions, and HMI/PLC status disagreement.
Open troubleshooter →Use this when the PLC, HMI, remote I/O, or Ethernet path is offline and you need a step-by-step communication troubleshooting guide.
Open guide →Work through network, module, addressing, and path issues when the problem is really communication-related.
Open troubleshooter →Use this when the input issue is tied to field wiring, device condition, addressing, power, or how the input is actually getting into the PLC.
Open guide →Troubleshoot when PLC outputs are on but the real device does not actuate. Covers field power, relays, contactors, and load-side issues.
Open guide →Evaluate whether short pulses or fast signals are getting missed because the PLC scan is not catching them consistently.
Open page →Convert raw analog values into engineering units and get a clearer handle on 4–20 mA, 0–10 V, or PLC-side scaling logic.
Open calculator →Estimate field voltage loss over cable length and check whether wire size or run length is affecting device behavior.
Open calculator →Quick reference for wire gauge and ampacity comparisons when you need a practical field-side check.
Open chart →Use this as a cleaner wire gauge reference when you need a quick chart instead of a calculator flow.
Open chart →Use this to support basic safety distance checks and related electrical / controls support work around safeguarding questions.
Open page →Browse electrical and general support charts from one place when you need fast lookups instead of a full troubleshooting flow.
Open reference hub →Use the problem solver when the symptom is clear but you do not yet know which PLC or electrical page fits best.
Open problem solver →Use the help page when the problem is live, machine-specific, or bigger than a calculator or single guide can cover cleanly.
Request help →This section is built to help people solve real PLC and electrical problems faster — not just calculate numbers in isolation.
Users usually know the symptom, not the perfect tool name. This section helps route from the real issue first.
It separates PLC state mismatch, communication faults, fast pulse issues, and electrical signal questions more cleanly.
Not every problem needs a calculator. Sometimes a wire chart, voltage check, or safety reference is the right move.
Built for real startup, field troubleshooting, and controls support instead of abstract textbook examples.
PLC and electrical tools help you move faster, but some situations need live review of the machine, field devices, network path, or wiring conditions. If you need help on a real system, use the help page and describe what the machine is doing.