Home/Field resources/When the Plant Network Drops
Diagnostic field guide · free PDF

When the Plant Network Drops

Comms faults on the floor — EtherNet/IP, Modbus, PROFINET, DeviceNet. Physical layer, VFD noise and grounding, switch and duplex faults, and reading the port counters and module fault bits before you swap hardware.

Get the library by email →   Browse the full library

One email, the whole 24-guide library. No drip campaign, no spam.

From the guide

How it reads

Excerpt

The line trips, the HMI (Human-Machine Interface, the operator screen) throws a red comms banner, and the controller shows a module fault. Everybody's first instinct is to swap a switch or re-pull a cable. Nine times out of ten that's the wrong first move, because the network already wrote down what happened and nobody read it. This is my field method for chasing comms dropouts across the mix of protocols you actually find on a floor — EtherNet/IP, Modbus TCP, PROFINET, PROFIBUS, DeviceNet — starting with the checks that cost nothing and keep you out of an energized panel until you have a reason to open one.

I'm writing this vendor-neutral. I run into these faults most on jobs where the network was built by one integrator, the drives by another, and the field devices got added over five years by three different hands. That handoff is where the ghosts live. A quick note on what "the network" means here so we're speaking the same language. EtherNet/IP (Ethernet Industrial Protocol) is the CIP-over-Ethernet protocol used by Allen-Bradley/Rockwell and many others — it is not the same thing as generic office Ethernet, even though it rides the same copper and fiber. Where I use a term the first time I'll spell it out, because at 2am definitions matter more than jargon.

Read the evidence before you touch anything The single habit that separates a 20-minute fix from a two-shift outage: read the controller's comms/module fault bits and the managed switch's port statistics and timestamps before you swap any hardware. The network keeps counters. Those counters are your black box recorder. On the controller side, pull: - Module fault codes / connection status bits for each I/O and device connection. On a Rockwell ControlLogix/CompactLogix that's the module properties Connection tab and the controller fault log; on a Siemens S7 it's the diagnostic buffer (the timestamped fault log inside the CPU). Get the timestamp of the fault, not just that it faulted. - Connection timeout / connection loss counts. A connection that dropped and re-established leaves a count and usually a time.

Inside the guide

What it covers

  • Read the evidence before you touch anything
  • Safety before hands-on work
  • Check-order: physical layer first
  • Electrical noise and grounding

Dealing with this on your plant right now?

Network still dropping out? Send me the port-error counts and we’ll trace it.

Get in touch Call (707) 690-7054