PLC troubleshooting: electrical first, programming second.
Many PLC issues blamed on programming are actually field wiring or I/O hardware. Electrical diagnosis first; engage PLC programmer if electrical checks out.
By Steven Lockhart · Reviewed by Alex Towery, C-10 #989290
Updated 2026-06-16
PLC electrical troubleshooting covers: power supplies (PLC processor, I/O modules, field power), I/O module diagnosis (input not seeing field signal, output not driving field device), field wiring integrity (sensor wiring, output device wiring, grounds), control voltage stability (24V DC typical for modern systems), and I/O scaling correctness for analog signals. Electrical scope ends at the PLC processor terminals; PLC programming and program logic is separate domain (typically handled by controls engineer or system integrator).
01Electrical vs programming split for PLC systems.
PLC-based control systems have a clean split between electrical and programming work. Electrical scope: power infrastructure to PLC (24V DC supplies, transformer-rectifier sources), field wiring from PLC I/O to field devices (sensors, actuators, relays, contactors), grounds, control circuits between PLC and motor starters, terminations, panel layout and wire management, conduit and pathway to field devices. Programming scope: PLC ladder logic or structured text, HMI screens, communication protocols, alarms, data logging.
Many operational issues blamed on PLC programming are actually electrical: failed input sensor (PLC reads no signal because there is no signal), broken output wire (PLC drives output but no field connection), corroded terminal (intermittent connection), incorrect grounding (creates noise affecting analog signals). Electrical diagnosis first: verify field signals at PLC terminals match field device states. If signals match field reality, then programming logic is the issue.
02Three common electrical issue patterns.
Input not seeing field signal
PLC input shows no signal change when field device state changes. Diagnosis: measure voltage at PLC input terminal while operating field device, verify input module LED indication, check input module wiring and configuration. Common causes: broken sensor wire, failed sensor, wrong voltage range, defective input module.
Output not driving field device
PLC programs output ON but field device doesn't operate. Diagnosis: verify output module LED indication shows commanded state, measure voltage at output terminal during commanded ON, check field wiring continuity, verify field device functions on direct power. Common causes: broken wire, failed output relay/transistor on PLC, blown fuse on output circuit, failed field device.
Analog signal noise or drift
Analog inputs (4-20mA, 0-10V) show unstable or drifting values. Diagnosis: check signal isolation, verify shield and grounding, measure noise on signal lines, isolate from VFD output cables or other noise sources. Common causes: improper grounding, signal cable run parallel to power cables, failed sensor, poor connection.
03Coordination with programming and integrators.
Electrical troubleshooting typically coordinates with PLC programmer or system integrator on programmed control systems. Common pattern: client reports operational issue, we perform electrical diagnosis, document field signal states at PLC terminals, hand off to programmer if electrical is healthy. Integrator handles programming changes; we handle any electrical changes recommended. Clean documentation of electrical scope (single-line diagrams, I/O termination drawings, field device locations) enables clean coordination.
For Marin industrial clients: typical engagement is electrical troubleshooting under PM contract or as-needed service, with system integrator providing programming and PLC system design. Some clients have in-house controls engineer who handles programming; others rely on outside integrator (Rockwell partners, regional system houses). Our scope is electrical infrastructure for PLC systems — we don't program PLCs but coordinate cleanly with those who do.
Common questions.
Do you program PLCs?
No — PLC programming is specialty work requiring deep platform expertise (Allen-Bradley, Siemens, Mitsubishi, Schneider all have different programming environments and approaches). We handle electrical scope for PLC systems including field wiring, I/O hardware troubleshooting, power supplies. For programming work, we coordinate with system integrator or client's in-house controls engineer. Clean handoff between electrical and programming scope is standard practice.
Can you replace PLC I/O modules?
Yes — replacement of standard I/O modules (input modules, output modules, analog modules) is electrical scope. We verify module compatibility with installed PLC chassis, coordinate any configuration with programmer if needed, perform replacement during scheduled downtime. Module costs vary $200-$1,200+ depending on type and manufacturer. Coordinate with PLC system source for module procurement when in stock with us is impractical.
What about HMI or SCADA hardware?
HMI display hardware: electrical scope (power, communication wiring, mounting). HMI software/programming: separate scope (integrator). SCADA infrastructure varies — server hardware electrical scope, SCADA software and configuration separate. We coordinate on combined projects with integrator handling software scope.
How do you document electrical scope for PLC systems?
Standard documentation: single-line diagrams showing power to PLC and major components, I/O termination drawings showing field wiring to PLC inputs and outputs (often delivered as 1-line per PLC slot with field device identification), panel layout drawings, conduit routing as applicable. Documentation typically generated during project; updates with any modifications. Critical for future troubleshooting and PM.
How do you handle pricing — flat fee or hourly?
Both, depending on scope. Routine service calls and predictable scope (panel replacement, EV charger install, transfer switch install, fixture replacement) are flat-fee quoted up front. Diagnostic visits and emergency scope are hourly because we don't know what we'll find. Either way, you get a written quote before work starts on anything significant, and we don't proceed beyond the quote without your sign-off.
How quickly can you schedule?
Depends on scope and season. Emergency dispatch: same-day across Marin County (1-3 hours business hours, 1-4 hours after-hours). Same-day standard service: 3-6 hours from call when capacity allows; otherwise next business day. Scheduled service work: 1-3 weeks typical. Larger projects requiring permits and PG&E coordination: 4-12 weeks depending on scope. We're upfront about timeline at the quote stage.
What warranty do you offer on work?
Our standard residential warranty: 2 years on labor, manufacturer warranty on parts (varies by product — typically 1-10 years). Major installs (panels, generators, EV chargers) often have longer manufacturer warranties (5-10 years). If there's an issue with our work in the warranty period, we come back and fix it at no cost. We also stand behind work past warranty — repeat customers and referrals matter more than a transactional fix.
Are you licensed and insured?
Yes. California State License Board C-10 Electrical Contractor #989290, in good standing. Carry general liability insurance and workers' compensation insurance as required by California law. Bondable on projects requiring it. Happy to provide proof of insurance to clients or property managers on request. License lookup: cslb.ca.gov.
Talk to a licensed electrician in Marin.
Family-run, C-10 #989290, 20+ years in the trade. Honest scoping, fair pricing, work that lasts.