Troubleshooting Articles
Longer-form technical writing, published as it is finished and revised as field experience corrects it. Every entry carries its published and updated dates.
121 entries
The Watchdog Timer
What the scan watchdog protects against, why it faults the controller instead of pausing it, what makes a scan run long, and why raising the limit is the wrong first response.
6 min readUpdated Sep 5, 2026
PLC Will Not Run
A controller that stays in program mode, faults on every attempt to run, or will not power up: the mode switch, the major fault log, the power supply, the memory and battery, the firmware and program mismatch, and the I/O configuration errors that stop a processor, in the order that finds them.
9 min readUpdated Sep 5, 2026
I/O Not Updating
Inputs that do not change and outputs that do not respond while the controller runs: the module and rack status, the inhibited and faulted connections, the input filter and the scan, the remote adapter link, the forced points, and the program that stopped writing the tag.
9 min readUpdated Sep 5, 2026
Analog Signal Problems
The controller side of a bad analog value: raw counts against the module range, channel diagnostics, scaling that does not match the transmitter, wiring by device type, noise and filtering, resolution, and a symptom table that points at the check.
8 min readUpdated Sep 5, 2026
Communication Failures
What to read when a controller stops talking to a device, another controller, or SCADA: port and connection status, message error codes, timeouts and retries, addressing, limits, and the order of checks that separates controller, cable, device, and network.
8 min readUpdated Sep 5, 2026
Network Problems
The controller as a network device: addressing, duplicate addresses, link speed and duplex, connection limits, packet rate and storms, multicast for remote I/O, ring protocols, and time synchronization, with the diagnostics that show which is wrong.
8 min readUpdated Sep 5, 2026
Program Faults
Faults the program causes: an index out of range, division by zero, an invalid indirect address, a missing routine, a type mismatch, or task overlap. Reading the fault record, what a fault handler should do, clearing safely, and logic that does not fault.
8 min readUpdated Sep 5, 2026
Watchdog Faults
A task that did not finish in time: what the watchdog protects, why the scan grew, and how to fix it. Measuring task times, finding the loop or instruction that took the time, communications load, and when raising the watchdog is legitimate.
7 min readUpdated Sep 5, 2026
Trending
Using historian trends to understand a process and diagnose a problem: pens that belong together, scaling and time ranges, raw versus averaged data and what compression hides, overlays and cursors, event markers, and the patterns that point at each cause.
9 min readUpdated Sep 5, 2026
Frozen Values
Why a SCADA value stops changing while looking normal: the five layers where it can freeze, from a transmitter holding its output to a client that lost its server, how to find the layer by comparing each, and the heartbeat that makes a freeze announce itself.
9 min readUpdated Sep 5, 2026
Lost Communications
What should happen when SCADA loses a device, a site, or everything, how the pattern tells which, the diagnostic order from the server outward through network, firewall, medium, and site, and the design that makes a lost link an alarm rather than an incident.
9 min readUpdated Sep 5, 2026
Bad Quality
What a quality flag means and where it comes from: good, uncertain, and bad with substatus codes, how quality propagates from device through driver, tag, display, alarm, and historian, the causes by layer, and the rule that a bad value is never a number.
9 min readUpdated Sep 5, 2026
Server Failure
How SCADA servers fail and what to do when one does: failure modes from a full disk to a dead hypervisor host, what the plant experiences with and without redundancy, the recovery sequence from restore to alarm verification, and the monitoring that warns.
9 min readUpdated Sep 5, 2026
Client Problems
Diagnosing the operator station rather than the system: a client that will not connect, shows nothing, runs slowly, freezes, or stays silent on an alarm, with the causes, the order of checks, and the standard build and spare that make the fix a swap.
8 min readUpdated Sep 5, 2026
Historian Problems
How a historian goes wrong and how to find each fault: gaps, wrong values, detail never stored, disks that fill, slow queries, backfill that never arrives, and unreadable archives, with the collector, queue, configuration, and storage checks that locate it.
9 min readUpdated Sep 5, 2026
Alarm Problems
How an alarm system fails: alarms that never raise, raise unheard, stick, chatter, or flood, acknowledgments that do not propagate, and notifications that never arrive, with the causes by layer and the end-to-end test that proves the whole chain.
9 min readUpdated Sep 5, 2026
Time Synchronization
Why every clock in a control system must agree and what happens when they do not: out-of-order events, historian gaps at daylight saving, authentication failures, wrong totals. The time source and hierarchy, how each device is synchronized, and the checks.
9 min readUpdated Sep 5, 2026
Flow Troubleshooting
A method for a flow reading that is wrong, noisy, zero, or disputed: establish the truth with an independent check, separate installation from configuration from signal chain, then the specific checks for magnetic, ultrasonic, and DP meters.
10 min readUpdated Sep 5, 2026
Level Troubleshooting
A method for a level reading that is wrong, frozen, jumping, or lost: establish the true level, check the signal chain and configuration, then the checks for ultrasonic, radar, hydrostatic, DP, and float instruments, and the failure behavior to design in.
10 min readUpdated Sep 5, 2026
Calibration Troubleshooting
When an instrument will not calibrate or stay calibrated: wrong or expired standards, slope and offset out of range, compensation errors, procedure mistakes, loop scaling that disagrees with the instrument, and deciding when to adjust, replace.
8 min readUpdated Sep 5, 2026
Noise Problems
Electrical noise as a panel problem: the four ways it couples, the design features that keep it out, the sources people forget such as unsuppressed coils and unbonded doors, and the sequence for finding where noise gets into a panel that should be clean.
10 min readUpdated Sep 5, 2026
Ground Faults
Ground faults in and around control panels: what happens on grounded 120 VAC circuits, on grounded and ungrounded 24 VDC systems, and on drive outputs; where they hide, from chafed wire to flooded boxes; and the divide-and-conquer method that finds them.
10 min readUpdated Sep 5, 2026
No Control Power
The control power path from the disconnect to the last relay, and how to work along it when the panel is dead: transformer and fuses, control breaker, emergency stop and safety relay, DC supply and distribution, what trips them, and design that makes it easy.
10 min readUpdated Sep 5, 2026
Blown Fuses
Working a blown fuse in a control panel: reading the circuit before replacing anything, fault against overload, finding a short by sectioning, the transformer and power supply cases, fuse types that must match, indicating holders, and replacement rules.
8 min readUpdated Sep 5, 2026
Failed Power Supplies
Diagnosing the 24 volt supply in a control panel: dead, low, noisy, or cycling, a failed supply against an overloaded one, loads that grew, heat and capacitor aging, redundant supplies, sag on the input, and what to specify so the next failure is an alarm.
8 min readUpdated Sep 5, 2026
Panel PLC Faults
Working a controller fault from the panel side: reading the indicators before opening the software, faults caused by the panel rather than the program, power and grounding, I/O module and wiring faults, heat, loose connections, and the order of checks.
8 min readUpdated Sep 5, 2026
Relay Problems
Diagnosing control relays in a panel: contacts that do not make or that weld, coils that fail or chatter, drop-out on sag, interposing relays on controller outputs, loads that burn contacts, suppression, sockets, and replacing against fixing the cause.
7 min readUpdated Sep 5, 2026
How to Diagnose a Ground Loop
Prove that a noisy or offset analog signal is a ground loop, find the second ground, and fix it the right way: remove the extra ground, isolate the signal, or correct the shield termination. With the measurements that make the diagnosis certain.
9 min readUpdated Sep 5, 2026
How to Diagnose a Bad Quality Tag
Trace a bad quality indication from the SCADA screen back to its source: the tag configuration, the driver and device connection, the controller tag, and the field signal, using the diagnostics each layer provides, and separate a stale value from a bad one.
8 min readUpdated Sep 5, 2026
How to Troubleshoot an Ethernet Connection
Work an Ethernet problem one layer at a time: link light and cable, then speed, duplex, and VLAN on the switch port, then address, mask, and gateway, then the application port through the firewall. Each layer has a one-minute test that rules it in or out.
10 min readUpdated Sep 5, 2026
How to Diagnose Packet Loss
Find where and why frames are dropped: measure loss with a continuous ping, localize it hop by hop from both directions, read the port counters on the path, and match the pattern to its cause: a cable, a duplex mismatch, congestion, a loop, or a radio link.
10 min readUpdated Sep 5, 2026
How to Diagnose Read and Write Communications
Diagnose a controller that cannot read from or write to a device: capture the exact request and response, classify the failure as no link, no answer, or a rejected exchange, read the error or exception code, compare with a test tool, and fix the port.
8 min readUpdated Sep 5, 2026
How to Troubleshoot a Flowmeter
Work a flowmeter that reads wrong, reads zero, or reads with the pipe still: confirm the pipe is full and the flow is real, check the installation against the meter requirements, and compare against an independent measurement before adjusting anything.
9 min readUpdated Sep 5, 2026
Processor Faulted
A PLC with its fault light on and no logic running. How to read what it is telling you, the causes in order of likelihood, and how to restart it without repeating the fault.
8 min readUpdated Sep 5, 2026
Outputs Not Energizing
The program says the output is on and the equipment is not running. Where the signal gets lost between the output image and the field device, and how to find the point in a few measurements.
8 min readUpdated Sep 5, 2026
Inputs Not Reading
A switch closes in the field and the program never sees it. How the wetting voltage, the common, sinking and sourcing, and the wiring each lose the signal, and how to find which one did.
8 min readUpdated Sep 5, 2026
Program Will Not Download
The software refuses to download, or the download starts and fails. The version, path, mode, memory, and protection problems behind it, and the order to check them in.
7 min readUpdated Sep 5, 2026
Logic Not Executing As Expected
The rung looks right and the plant does something else. The scan-order, duplicate-output, unscheduled-routine, and data-type traps behind it, and how to find which one you are in.
8 min readUpdated Sep 5, 2026
Retentive Data Lost
The plant came back from a power cycle with zero setpoints, zero totals, and the wrong pump as lead. Which backup failed, which restore overwrote what, and how to get the data back and keep it.
7 min readUpdated Sep 5, 2026
Values Frozen On Screen
The HMI shows numbers that are not changing while the plant runs. Whether the controller, the communication driver, the tag server, or the display stopped, and the order to check them in.
7 min readUpdated Sep 5, 2026
Tag Shows Bad Quality
A tag flagged bad or uncertain by the driver. What the quality codes mean, the difference between a device that is not answering and an address that does not exist, and how to clear each.
7 min readUpdated Sep 5, 2026
Pump Will Not Start
A pump that is called and does nothing. The order to check: permissives and mode, control power, the starter or drive, the motor circuit, and the pump itself, with the measurements that settle each one in minutes.
10 min readUpdated Sep 5, 2026
Pump Runs But No Flow
The motor turns and nothing moves. How to tell a clogged impeller from an air-bound pump, a closed valve, a stuck check, a broken coupling, or reverse rotation, using motor current and discharge pressure before pulling anything.
10 min readUpdated Sep 5, 2026
Pump Short Cycles
A pump that starts and stops far more often than it should: the control band, the level signal, a leaking check valve, a waterlogged pressure tank, a lag pump doing the lead job, and the starts-per-hour limit that makes short cycling a motor killer.
9 min readUpdated Sep 5, 2026
Drive Will Not Start in AUTO
The drive runs from the keypad or in HAND but not from the controller. The command source, the enable and safe torque off inputs, the speed reference, and the network control word, checked in the order that finds the problem fastest.
9 min readUpdated Sep 5, 2026
Transmitter Reads Wrong Value
The reading is steady, plausible, and wrong. How to prove it against a reference, then separate a scaling mismatch, a range change, a zero shift, an installation effect, and a genuine transmitter fault, with the order of checks that finds it fastest.
9 min readUpdated Sep 5, 2026
Level Reading Jumps
A level that steps, spikes, or flips to a fixed value while the water moves smoothly: the false echoes, foam, turbulence, condensation, cable faults, and controller-side causes behind each pattern, and how to tell them apart from the trend before opening a hatch.
9 min readUpdated Sep 5, 2026
Device Times Out
A polled device that answers late or not at all: how to read the driver counters, tell a dead device from a slow one, and find the timeout setting, the bus loading, the radio latency, the duplicate address, or the device that is simply too busy to answer.
9 min readUpdated Sep 5, 2026
Alarms Not Annunciating
The condition is real and nothing happened on the screen or the phone: where an alarm can be lost between the controller and the operator, from the alarm bit and the tag quality to the alarm server, the display filter, the shelved and suppressed lists, the audible, and the notifier.
9 min readUpdated Sep 5, 2026
Drive Faults on Overcurrent
An overcurrent trip on a variable frequency drive: what the drive measured and when, the difference between a trip at start, during acceleration, at steady speed, and at deceleration, the motor and cable faults behind each, the parameter settings that cause nuisance trips, and the tests that separate them.
9 min readUpdated Sep 5, 2026
Drive Faults on Overvoltage
A DC bus overvoltage trip on a drive: where the bus voltage comes from, why deceleration and a driving load raise it, the utility-side causes from a high supply and capacitor switching, the deceleration ramp and overvoltage controller settings, braking resistors, and how to tell a regeneration trip from a supply transient.
9 min readUpdated Sep 5, 2026
Motor Will Not Reach Speed
A drive that runs but never gets the motor to the commanded speed: the reference and its scaling, the maximum frequency and speed limits, current limit holding the ramp, a load beyond the motor, a wrong motor parameter set, and a low supply, with the drive readouts that separate them.
9 min readUpdated Sep 5, 2026
Drive Trips on Ground Fault
A ground fault trip on a variable frequency drive: how the drive detects it, the motor and cable insulation faults behind most trips, the submersible cable problem, the capacitive leakage on long cables and filters that produces nuisance trips, wiring errors, and the insulation test that decides it.
9 min readUpdated Sep 5, 2026
Ground Loop Symptoms
How a ground loop shows itself: hum on analog signals, offsets that change when large loads switch, serial links that error, and readings that differ by location. The mechanism, the measurements that prove it, and fixes that never lift a safety ground.
9 min readUpdated Sep 5, 2026
Floating Reference Between Panels
Signals between two panels that misbehave because the panels do not share a DC reference: inputs that never turn on or half turn on, strange voltages to ground, and noise that comes and goes. How DC commons should be bonded and how to cross a panel boundary.
9 min readUpdated Sep 5, 2026
Shield Grounded at Both Ends
A shield connected to ground at the panel and again in the field becomes a conductor between two grounds, and its current becomes noise on the pair inside. How to find the second connection, what to measure before lifting it, and when both ends are correct.
8 min readUpdated Sep 5, 2026
Missing Equipment Ground
An enclosure, motor, or device with no effective equipment ground: how it shows up as a tingle, a fault that does not trip, surge protection that does nothing, or instrument noise; how to test the path safely; and why a ground rod is no substitute.
9 min readUpdated Sep 5, 2026
High Neutral-to-Ground Voltage
What a neutral-to-ground voltage reading means, the values that are normal, and the causes of a high one: a long or heavily loaded neutral, harmonic current, a loose or open neutral, a missing service bond, or an extra bond downstream, and telling them apart.
9 min readUpdated Sep 5, 2026
Cable Routing Problems
Noise that comes from where a cable runs: signal cables sharing a conduit, tray, or wireway with power or drive cables, long parallel runs, and shallow crossings. How coupling works, the separations that prevent it, and how to find the shared path.
9 min readUpdated Sep 5, 2026
Common-Mode Noise
Noise that rides on both conductors of a signal pair together, relative to ground: where it comes from, why a differential input rejects it only up to a limit, how to tell it from normal-mode noise with a scope, and the fixes that work.
9 min readUpdated Sep 5, 2026
Radio Frequency Interference
Readings that jump when a handheld radio is keyed, inputs that flicker near a telemetry antenna, transmitters that drift beside a modem: how radio energy gets into control circuits, how to prove it with the radio itself, and the fixes.
9 min readUpdated Sep 5, 2026
Unshielded Cable in a Noisy Run
The signal was run in plain conductors through a route full of power and drive cables, and now it is noisy. What unshielded cable cannot do, how to prove the cable is the problem before pulling a new one, and the options when replacing it is not possible.
9 min readUpdated Sep 5, 2026
VFD Noise on Analog Signals
Analog readings that jump or wander when a drive runs, and speed references that make a drive hunt: how the drive output couples into signal wiring, why the input turns kilohertz noise into a slow wander, the tests that pin it on the drive, and the fixes.
10 min readUpdated Sep 5, 2026
Drive Causes Instrument Noise
When many instruments became noisy after a drive was installed, the drive installation is the place to look: the checklist for motor cable, shielding, grounding, filters, and carrier frequency that decides how much noise a drive puts into the plant.
10 min readUpdated Sep 5, 2026
No Control Power in Panel
The panel is dead: no pilot lights, no controller, no HMI. The order of checks from the disconnect through the control transformer and its fuses, the control breaker, the emergency stop chain, and the DC supply, with the readings that locate the break.
8 min readUpdated Sep 5, 2026
Fuse Blows Repeatedly
A control fuse that opens again after replacement has a cause the replacement did not touch: a shorted coil, a ground fault in a wet field device, an overloaded circuit, the wrong fuse type for inrush, or an intermittent short. How the timing identifies it.
8 min readUpdated Sep 5, 2026
Relay Chatter
A relay or contactor that buzzes, cycles, or will not stay pulled in: low coil voltage from an overloaded supply or a sag, an AC coil with a dirty armature or broken shading ring, a solid-state output leaking, or an input bouncing at its threshold.
8 min readUpdated Sep 5, 2026
Ground Fault Present
The ground fault indicator is on, the monitor alarms, or a fuse opens when a field circuit is energized: how to find which conductor touches ground and where, by dividing the circuit with the monitor or an insulation tester, and where faults hide.
8 min readUpdated Sep 5, 2026
Panel Overheating
A panel that runs hot: drives tripping on temperature in the afternoon, controllers faulting in summer, components discolored, a fan that never stops. The causes from an undersized enclosure to a clogged filter, measuring the rise, and the fixes.
8 min readUpdated Sep 5, 2026
Nuisance Breaker Trips
A breaker that trips without a fault anyone can find: inrush against an instantaneous trip, a circuit loaded beyond its rating by additions, the wrong trip curve, a breaker weakened by heat, a loose terminal, or harmonics. Reading the curve.
8 min readUpdated Sep 5, 2026
Loss of Control Voltage
Control voltage that drops out for a moment and comes back, resetting controllers and dropping contactors: utility sags when a large load starts, a transfer switch operation, a loose neutral, or an overloaded control transformer. Catching it with a recorder.
8 min readUpdated Sep 5, 2026
Power Supply Failure
A 24 volt DC supply whose output is gone, low, cycling, or noisy: an overload that has put it into current limit, a supply killed by heat and age, input voltage out of range, or surge damage. One test tells an overloaded supply from a dead one.
8 min readUpdated Sep 5, 2026
UPS Not Carrying Load
The power failed and the controls went down anyway: a battery aged out or never connected, a UPS sitting in bypass since a fault, an overload, loads on the wrong receptacles, or a failed self-test nobody read. Finding out which, and testing properly.
8 min readUpdated Sep 5, 2026
Voltage Sag on Motor Start
Lights dim, contactors drop, and controllers reset every time the big pump starts: the starting current of an across-the-line motor pulling down a weak source. Measuring the sag, checking the source, and fixing it with a soft starter or ride-through.
8 min readUpdated Sep 5, 2026
Generator Transfer Problems
The generator started and something still went wrong: no transfer, controls reset during the gap, drives faulted, pumps ran backward, or the retransfer caused a second outage. The sequence and its timers, neutral and rotation, and the monthly test.
9 min readUpdated Sep 5, 2026
Pump Loses Prime
A suction-lift pump that runs without pumping, or pumps for a while and then stops: air leaking into the suction line, a foot valve that lets the line drain, a lift too high, a vortex or an aerated inflow, or a self-priming casing that lost its charge.
8 min readUpdated Sep 5, 2026
Seal Failure Alarm
The moisture probe in a submersible pump has tripped its relay: a seal that is leaking, or moisture in the cable, the junction box, or the probe circuit, a relay that does not match the pump, or a failed relay. What the alarm should do and what to check.
8 min readUpdated Sep 5, 2026
Both Pumps Running Constantly
A duplex station where lead and lag run together and never catch up: inflow beyond one pump, pumps that lost capacity to wear or rags, a force main partly blocked, a pump that runs but does not pump, a level stuck high, or bad setpoints. The drawdown test.
8 min readUpdated Sep 5, 2026
Valve Will Not Reach Position
A valve commanded to a position that stops short: an obstruction or a seat the actuator cannot push through, travel limits or a positioner span set wrong, a stem binding, an actuator undersized or out of air, or a command signal that does not span.
8 min readUpdated Sep 5, 2026
Valve Hunting
A modulating valve that never settles: a loop tuned too hard, a positioner gain too high, stiction producing a limit cycle, a noisy command or feedback, an oversized valve working near its seat, or two loops fighting. The manual test that separates them.
8 min readUpdated Sep 5, 2026
Valve Slow to Respond
A valve that takes far longer to move than it should: a pneumatic supply restricted or leaking; a positioner tuned slow; an electric actuator whose speed is fixed; a stem binding in cold or packing; or a rate-limited output. Measuring the stroke time.
8 min readUpdated Sep 5, 2026
Position Feedback Wrong
The HMI says one position and the valve is at another: a feedback potentiometer worn or miscalibrated, a linkage that slipped, scaling that does not match, a reversed signal, limits set wrong, or noise. Comparing indicator, feedback, and process.
8 min readUpdated Sep 5, 2026
Actuator Torque Fault
An electric actuator that trips on torque: at the seat because the seating mode or setting is wrong, in mid-travel because something is in the way or the stem binds, or under flow because the differential exceeds the sizing. The checks before a reset.
8 min readUpdated Sep 5, 2026
Remote Site Stops Communicating
One radio site silent while its neighbors answer: site power, the radio, antenna and coax after a storm, a reset configuration, the controller behind it, or a changed path. What the master diagnostics say before anyone drives, and the order of checks on site.
8 min readUpdated Sep 5, 2026
Intermittent Radio Path
A site that drops and returns by the hour, season, or weather: thin fade margin, foliage, a new obstruction, a loosened antenna, coax taking water, a corroding connector, interference, or a marginal supply. How to trend signal against time and weather.
8 min readUpdated Sep 5, 2026
High Retry Count
Polls that succeed on the second or third try: a weak or noisy path, interference, collisions from a second master, a timeout shorter than the radio turnaround, a data rate the path cannot carry, or a slow controller. Reading retry statistics per site.
8 min readUpdated Sep 5, 2026
Poor Signal Margin
A path with too little signal above receiver threshold to survive rain, leaves, and inversions: the link budget from transmitter to receiver, the Fresnel zone, and why the margin is smaller than the study said. How to compute, measure, and add to it.
9 min readUpdated Sep 5, 2026
Interference on Channel
Data lost on a strong-signal path: another system on the frequency, a nearby transmitter overloading the receiver, intermodulation on a shared tower, drive noise, or a stuck transmitter. How to measure the noise floor, find the source, and cure it.
8 min readUpdated Sep 5, 2026
Cellular Modem Will Not Register
A modem that never attaches to the network: a module not activated, provisioned, or suspended; unsupported bands or a network shutdown; no antenna or coverage; a wrong access point name; or a reset modem. Reading the registration state and asking the carrier.
8 min readUpdated Sep 5, 2026
Frequent Reconnects
A cellular site that connects, drops, and reconnects: a weak signal at the cell edge, tower handoffs, idle session teardown, a NAT timeout that needs a keepalive, a firmware fault, a sagging supply, or an antenna problem. Settings that keep sessions up.
8 min readUpdated Sep 5, 2026
Data Plan or APN Problems
A modem that registers but has no data, or runs out mid-month: a wrong or changed APN, a capped or throttled plan, a module on the wrong plan or network, a missing static address, or polling that uses more data than planned. Sizing a plan, cutting traffic.
8 min readUpdated Sep 5, 2026
VPN Tunnel Drops
The modem is up and the tunnel keeps dropping: a changing cellular address, keepalive longer than the carrier timeout, mismatched rekey lifetimes, an oversized MTU, a modem reconnecting under the tunnel, a full concentrator, or a clock or certificate fault.
9 min readUpdated Sep 5, 2026
Weak Cellular Signal
A modem at the edge of coverage: the signal readings that matter, an antenna inside a metal enclosure or vault, the wrong band, a damaged antenna or lossy coax, a tower or carrier change, and fixes from a mast antenna to a directional one or a new medium.
8 min readUpdated Sep 5, 2026
Fiber Link Down
A fiber link with no light: a cut or crushed cable, a failed or unseated transceiver, a reversed patch cord, a dirty connector, a disabled port, a mismatched module pair, or a dead media converter. Reading port state and optical power to find the break.
8 min readUpdated Sep 5, 2026
High Optical Loss
A link that is up but running near the receiver floor: the loss budget from transmitter to receiver and what ate it. Dirty connectors, bad splices, tight bends, a run too long for the module, or a wrong fiber type. Measuring the loss and getting margin back.
9 min readUpdated Sep 5, 2026
Intermittent Fiber Link
A fiber link that flaps: down for seconds and back, worse at night, in the cold, in wind, or when a door opens. No margin, a nearly seated connector, a failing or hot transceiver, a moving bend, water freezing in a splice case, or a port flapping on its own.
8 min readUpdated Sep 5, 2026
Wrong Fiber Type or Wavelength
A link that will not come up, or runs with high loss, because parts do not match: single-mode modules on multimode fiber, a multimode cord in a single-mode run, mixed grades, different wavelengths, or a same-wavelength bidirectional pair. Reading the markings.
8 min readUpdated Sep 5, 2026
Dirty or Damaged Connector
The most common fiber fault: a connector end face with dust, oil, or a scratch that takes decibels from the link and damages its mate. How to inspect with a scope, what contamination and damage look like, how to clean properly, and when to replace it.
8 min readUpdated Sep 5, 2026
Intermittent Packet Loss
Polls that occasionally fail, tags that flicker bad, a ping that drops one in fifty: a bad cable or port, a duplex mismatch, a saturated link, a buffer overrun, a marginal radio or fiber hop, a slow device, or a loop. Finding which hop loses packets and why.
9 min readUpdated Sep 5, 2026
Cannot Ping Across VLANs
Two devices that work on their own networks but cannot reach each other across a VLAN boundary: no route, a wrong or missing gateway, a mask that puts the target on the wrong side, a trunk missing the VLAN, or a firewall rule. Testing each in order.
8 min readUpdated Sep 5, 2026
Duplicate IP Address
Two devices claiming one address: a controller that answers sometimes, a workstation that reports a conflict, a ping returning from two hardware addresses. Where duplicates come from, finding both in the switch address table, and the discipline that stops it.
7 min readUpdated Sep 5, 2026
Switch Port Errors Incrementing
What each counter on a managed switch port means and which fault makes it grow: check errors from a damaged cable or noise, late collisions from a duplex mismatch, runts from a bad transceiver, discards from congestion, link flaps from a marginal connection.
9 min readUpdated Sep 5, 2026
Broadcast Storm
A network suddenly slow or dead everywhere, every link light solid: a loop between switches without protection, a failed ring protocol, or a device flooding broadcasts. Recognising a storm, breaking it with a cable pull, finding the loop, and preventing it.
8 min readUpdated Sep 5, 2026
Trend Gaps
Holes in a trend where data should be: a communication loss, a historian that stopped or fell behind, a buffer that filled or never forwarded, compression set too coarse, a renamed tag, or a clock that jumped. Reading the cause from the shape of the gap.
8 min readUpdated Sep 5, 2026
Client Cannot Connect
A workstation, web, or mobile client that cannot reach the SCADA server: the service down, a firewall path closed, a license or session limit, a certificate or name failure, a version mismatch after an update, or expired credentials. Testing each layer.
8 min readUpdated Sep 5, 2026
Duplicate or Missing History
A historian with two records for one moment, or none: a redundant pair both collecting, a buffer that forwarded twice, a tag under two names, a daylight saving shift, or a source that resends on reconnect. Cleaning the record without inventing data.
8 min readUpdated Sep 5, 2026
Signal Pegged High or Low
A 4-20 mA signal stuck at a rail or a fault current: a transmitter in fault, a process truly out of range, an open or shorted loop, a wrong range, a wiring error, an input channel fault, or a scaling clamp. How the current itself tells you which.
8 min readUpdated Sep 5, 2026
Analog Does Not Match Field Indicator
The gauge on the pipe says one thing and the screen says another: a scaling or range mismatch, a drifted transmitter, a drifted gauge, a different elevation or datum, different units, or damping that lags. Deciding which is right and where the error lives.
8 min readUpdated Sep 5, 2026
Loop Powers Up but Reads Zero
The transmitter is lit and the controller shows zero, so loop current is not reaching the input: a loop wired for power but not signal, an active and passive mismatch, a missing jumper, an unconfigured channel, a blown fuse, or a transmitter sending nothing.
7 min readUpdated Sep 5, 2026
Read Works but Write Fails
Polling a device returns good data and writing a setpoint does nothing or returns an exception: a write-protected device, a read-only register, the wrong function code, a wrong address or type, logic that overwrites the value, a security rule, or a local mode.
8 min readUpdated Sep 5, 2026
Wrong Register Data
The poll succeeds and the numbers are nonsense: an offset by one, the wrong table, swapped words in a 32-bit value, a float read as an integer, signed read as unsigned, a scale factor not applied, a stale gateway value, or the wrong unit answering.
8 min readUpdated Sep 5, 2026
Protocol Gateway Stops Passing Data
The gateway is powered and pingable and the data behind it is frozen or gone: the device side failed while the master side answers, a stalled gateway, configuration lost on a power cycle, a stale mapping, or a master polling too fast. Testing each side.
8 min readUpdated Sep 5, 2026
Troubleshooting Checklist
A general checklist for any control system problem, usable at 2 a.m.: define the problem, ask what changed, make the process safe, gather the evidence before touching anything, divide the chain, change one thing at a time, restore, and record.
8 min readUpdated Sep 5, 2026
The Panel You Can Troubleshoot at Two in the Morning
Panels are designed for the day they are built and used for the nights they fail. The design choices that decide whether a technician with a flashlight and a meter can find the fault: labels and wire numbers, and the fuse that tells you it blew.
8 min readUpdated Sep 5, 2026
Measure Before You Replace
Parts-swapping is the most expensive way to troubleshoot and the most common. A method for controls faults that starts with a measurement, splits the problem in half at every step, and ends with a cause instead of a coincidence.
8 min readUpdated Sep 5, 2026
When the Transmitter and the Gauge Disagree
The SCADA screen says 62 psi and the gauge on the pipe says 58, and someone has to decide which one to believe. Why two readings of the same pressure differ, and a procedure for settling the argument with a reference instead of an opinion.
9 min readUpdated Sep 5, 2026
The Intermittent Fault Is a Data Problem
A fault that happens once a week at random cannot be found with a meter, because it is never happening while the meter is connected. How to turn an intermittent problem into a recorded one, and how the patterns in the record point at the cause.
9 min readUpdated Sep 5, 2026
4-20 mA Signal Is Unstable
An analog reading that will not settle. How to separate a genuine process swing from induced noise, a ground loop, or a loop running out of voltage.
8 min readUpdated Aug 23, 2026
Modbus Device Intermittently Offline
A device that answers most of the time. Termination, bias, timing, and the physical layer details that produce a bus which almost works.
9 min readUpdated Aug 21, 2026
Ethernet Device Drops Offline
An industrial Ethernet device that disappears and comes back. Duplex mismatch, cabling, spanning tree, and the switch counters that identify it in minutes.
9 min readUpdated Aug 16, 2026
How to Test a 4-20 mA Loop
Prove a current loop end to end with a meter and a calibrator, without interrupting a process you were not authorized to interrupt.
8 min readUpdated Aug 6, 2026
Direct contact
Have a controls question?
Reach Eric Sullivan directly about anything on this site, a controls or automation topic, or one of his personal projects.
Content on CurryControls.com is general technical reference information provided for educational and reference purposes only. It is not engineering advice for a specific installation. All information must be independently verified against current codes, standards, manufacturer documentation, project requirements, and qualified professional judgment before it is relied upon or applied.