Topic
Ethernet
33 guides across the knowledge base.
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 M580
Field notes on the Schneider Electric Modicon M580, the Ethernet-backplane controller at the top of the range: remote I/O drops on a ring, hot standby CPUs, built-in security features, the networks it defines, Quantum migration, and what to check on site.
9 min readUpdated Sep 5, 2026
ControlLogix
Field notes on the Rockwell Automation ControlLogix, the chassis-based controller of larger water plants: chassis and modules, tag-based memory and tasks, EtherNet/IP and older networks, controller redundancy, version matching, and what to check on site.
9 min readUpdated Sep 5, 2026
CompactLogix
Field notes on the Rockwell Automation CompactLogix, the smaller Logix controller behind most lift stations and small plants: families and I/O, the two Ethernet ports, what it shares with ControlLogix and what it lacks, 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
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
Network Switches
Selecting and installing the Ethernet switch in a control panel: managed against unmanaged, industrial ratings and DIN rail mounting, ports and media including fiber, ring protocols, power and grounding, and the configuration documented with the panel.
8 min readUpdated Sep 5, 2026
Panel Networking
The network inside a controller panel: which networks exist and how they are kept apart, where the switch sits, copper patching and fiber entry, the radio or cellular router as a panel component, cable management, shield grounding, and labeling.
7 min readUpdated Sep 5, 2026
Passive Discovery
Finding out what is on a control network by listening rather than probing: why active scans are risky around older controllers, how a mirror port feeds a sensor, what the traffic reveals, the blind spots, and how the sensor becomes continuous monitoring.
8 min readUpdated Sep 5, 2026
VLAN Segmentation
Using VLANs to build the zones of a control network on shared switches: what a VLAN separates and what it does not, the zone-to-VLAN mapping, trunks and the native VLAN, routing only through a firewall, and where separate hardware begins.
9 min readUpdated Sep 5, 2026
How to Assign IP Addresses on a Control Network
Build an addressing plan before the first device is configured: one subnet per zone and site, a fixed block layout so an address says what the device is, static addresses on everything that controls a process, and a schedule that is kept current.
9 min readUpdated Sep 5, 2026
How to Configure VLANs on a Control Network
Turn a zone plan into switch configuration: a VLAN per zone with its own subnet, access ports for devices, tagged trunks between switches, a native VLAN that carries nothing, a separate management VLAN, and routing between VLANs only through the firewall.
10 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 Configure Remote I/O
Add a remote I/O rack to a controller over Ethernet: plan the network and addresses, set the adapter, and prove every point and the failure behavior before the rack goes into service.
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
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
Fiber Schedules
The record of every fiber strand between every pair of patch panels: cable identifiers, strand numbers and the standard color sequence, fiber type, connectors, what each strand carries, splices, lengths, and test results, with the labeling that matches it.
8 min readUpdated Sep 5, 2026
Network Schedules
The tables behind the network drawings: the address schedule of every device, the switch port schedule of every port, the VLAN table, and the conduit list of what the firewalls permit. How they are built, kept as the single source of truth, and protected.
8 min readUpdated Sep 5, 2026
Fiber Between Buildings, Every Time
The copper Ethernet cable between two buildings works on the day it is pulled and costs the plant a controller, a switch, and how to specify it so it stays simple.
7 min readUpdated Sep 5, 2026
One Flat Network Is One Big Fault Domain
A looped patch cable in an office closet took down every PLC at the plant, because the office and the plant were one network. Why a flat network makes every fault a plant-wide fault, and how to get there one switch at a time.
9 min readUpdated Sep 5, 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
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
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.