Topic
Communications
53 guides across the knowledge base.
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
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
Modicon M340
Field notes on the Schneider Electric Modicon M340, a rack-based mid-range controller common in water plants: rack and CPU layout, X80 I/O, memory card behavior, Ethernet and serial communications, programming in Control Expert, and what to check on site.
8 min readUpdated Sep 5, 2026
Siemens
Field notes on Siemens controllers in water and wastewater: the S7-1200 and S7-1500 with TIA Portal, the older S7-300 and S7-400, PROFINET and PROFIBUS, the block model and memory cards, protection levels, and why it arrives inside packaged equipment.
8 min readUpdated Sep 5, 2026
AutomationDirect
Field notes on AutomationDirect controllers in water and wastewater: the Productivity, Do-more and BRX, and CLICK families with free software, the legacy DirectLOGIC line, Modbus and EtherNet/IP support, what they suit, and what to check on site.
8 min readUpdated Sep 5, 2026
EtherNet/IP
How EtherNet/IP moves control data: CIP over standard Ethernet, implicit I/O connections on a requested packet interval, explicit messaging, producer and consumer tags, and what the network has to provide.
9 min readUpdated Sep 5, 2026
DNP3
The protocol built for utility telemetry: master and outstation, static and event data classes, unsolicited reporting, time-stamped events, and why it suits slow links that Modbus does not.
8 min readUpdated Sep 5, 2026
OPC UA
What OPC UA is for, how its information model, security, and transports differ from OPC Classic, where it belongs in a plant, and what to check before relying on it.
8 min readUpdated Sep 5, 2026
Serial Communications
RS-232, RS-422, and RS-485 in practice: which is which, cable and distance, termination, biasing, the common reference wire everyone leaves off, and the settings that have to match at both ends.
9 min readUpdated Sep 5, 2026
Protocol Gateways
Protocol converters between a controller and devices that do not speak its language: what a gateway does, the common pairings in water and wastewater, the mapping table that is the whole configuration, the failure modes a gateway adds, and when to use a native interface instead.
9 min readUpdated Sep 5, 2026
Remote I/O
Extending controller I/O to another panel or another site over a network: the adapter and the rack, the update rate and what it costs, what the outputs do when the link fails, the difference between remote I/O and a remote controller, and the wiring, addressing, and diagnostics that make it dependable.
9 min readUpdated Sep 5, 2026
SCADA Communications
How SCADA servers talk to controllers and the field: polling and report by exception, the protocols and what each is for, media from plant Ethernet to radio and cellular, poll rate arithmetic, timeouts and quality, time sync, store and forward, and security.
11 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
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
Schneider SCADA
Field notes on Schneider Electric SCADA for water: EcoStruxure Geo SCADA Expert, formerly ClearSCADA, the telemetry platform built around DNP3 events, an object database, and hot standby servers, with SCADAPack RTUs, and how it relates to the AVEVA products.
8 min readUpdated Sep 5, 2026
HART
Digital data riding on the 4-20 mA loop: how HART signaling works, what a handheld or a HART-enabled input can read, multidrop and burst modes, and the wiring conditions that make HART fail while the current loop keeps working.
10 min readUpdated Sep 5, 2026
How to Configure a Modbus Connection
Set up a Modbus RTU or TCP link between a controller and a device: get the register map, match the physical and protocol settings, build the reads and writes, handle data types and the addressing offset, and verify with a protocol tool before trusting a value.
10 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 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 Test Fiber
Test a fiber link at acceptance and at fault: inspect and clean every connector, measure end-to-end loss with a light source and power meter in both directions and at the operating wavelengths, and record everything with the fiber schedule.
8 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
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
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
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
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
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
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
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
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
Modbus TCP
Modbus over Ethernet: what the MBAP header changes, why the CRC disappears, how the unit identifier works, and what does not get easier just because it is on Ethernet.
8 min readUpdated Jul 28, 2026
Modbus RTU
Serial Modbus over RS-485: function codes, register addressing, the off-by-one that catches everyone, and the physical layer details that decide whether a bus is stable.
10 min readUpdated Jul 21, 2026
Other topics
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.