Plc fault tracing

Fault Log · Field Report

Loesche Mill PLC — Communication & I/O Fault Traced by Replacing 34 Cards One by One

Plant: Cement, Loesche vertical roller mill  |  System: PLC panel, Profibus, digital output rack (60+ card rack)  |  Downtime: Extended — raw meal level critical, heavy pressure to restore


Symptom

The Loesche mill PLC panel started showing a red blinking fault indicator flagging both a communication fault and an I/O fault together. Two fault types lighting up at once meant the starting point wasn't obvious — could be the network side, could be the I/O side, could be both pointing at the same root cause.

Investigation

Started by tracing both sides of the fault in parallel rather than guessing which one was primary:

  • Communication side — checked the Profibus communication cable end to end. Found acceptable, no damage or continuity issues.
  • Connectors — replaced the Profibus connectors on the suspicion of a degraded connection. Fault persisted after replacement — ruled out.

With the communication path cleared, the fault was isolated down to a specific rack — a digital output rack carrying more than 60 cards. That narrowed the problem to somewhere inside that rack, but with that many cards, "somewhere in the rack" isn't a diagnosis on its own.

It was rainy season, and humidity brings its own problems on panels like this — rust and dust buildup on card edge connectors can cause exactly this kind of intermittent communication/I/O fault without any single card being visibly damaged. Cleaned all cards in the rack with contact cleaner as a first pass. Fault still didn't clear.

Root Cause

With the cable, connectors, and rust/dust cleaning all ruled out, the fault had to be a single faulty card somewhere in a rack of 60+ cards — but with no diagnostic software support on this system to isolate it directly, there was no shortcut to identify which one.

Raw meal level was running low at the time, putting the maintenance team under heavy pressure to get the mill back up fast. That ruled out a slow, methodical narrow-down approach in favor of a direct one: replace cards one by one until the fault cleared.

Fix

Replaced the cards in the rack one at a time, checking panel status after each swap. Thirty-three cards were replaced with no change. On the 34th card, the fault cleared — confirming that card as the faulty one all along.

Lesson

Not every fault gets solved by clean, textbook diagnostics. When the system doesn't have the software support to pinpoint a faulty card directly, and operational pressure doesn't allow for a slow methodical isolation process, sometimes the fastest real-world path is the brute-force one — replace one by one until the fault clears. It's not elegant, but on an older PLC system without proper diagnostic tooling, it's often the only method that actually works within the time you're given. Don't be afraid to fall back on the old-school approach when the modern one isn't available to you.


Ever had to brute-force a card fault under production pressure? Drop a comment — worth comparing how others handle it when diagnostic tools fall short.


🎥 Watch It Explained on PLC Key Channel

Prefer video? I break down topics like this with animations on my YouTube channel.

▶ Watch the full playlist on PLC Key Channel →

🛠️ Tools I Actually Use in the Field

A few affiliate links to tools that come up constantly in instrumentation work — I only list things I'd recommend to my own team:

As an Amazon Associate I earn from qualifying purchases. It doesn't cost you anything extra.

Got a specific instrumentation problem you're stuck on? Drop it in the comments — I answer based on real plant troubleshooting, not textbook theory.

Comments

Popular posts from this blog

Belt weigh feeder Zero and Span Drift

Zirconia Oxygen Analyzer Reading Maximum O2

Control Valve Positioner Calibration