Random DI Card Faults on Allen Bradley

-

Fault Log · Field Report

Random DI Card Faults on Allen Bradley — Traced to Motor-Start Transients

Plant: Cement, kiln/mill area  |  System: Allen Bradley PLC, discrete input cards  |  Downtime: Zero

Symptom

Intermittent, unexplained faults were showing up on discrete input (DI) cards — no fixed pattern, no fixed card, no fixed input. Sometimes a channel would flag a fault and clear itself within seconds. No process upset that lined up with it. The kind of fault that's easy to write off as "noise" until it starts eating into your team's trust in the system.

Investigation

First move was to stop treating it as random. I started logging the exact time of every fault occurrence against the plant event log — motor starts, breaker operations, VFD activity, everything electrical happening plant-wide at that moment.

The pattern showed up fast: every fault correlated with a large motor starting nearby — not necessarily on the same card, not necessarily on the same circuit. That pointed away from a wiring or card defect and toward electrical transients riding into the DI cards during motor inrush.

Root Cause

Large motor starts generate voltage transients and induced noise on nearby cabling. Where DI wiring ran in proximity to power cabling or shared trays with motor feeders, that noise was enough to momentarily trip the input threshold on the AB card — read as a genuine state change even though nothing on the field device had actually changed.

Fix

  • Input filter time adjustment — increased the on/off delay on the affected DI channels so momentary transients shorter than the filter window are ignored, without affecting genuine fast state changes.
  • Ferrite cores — clamped on the DI signal cabling near the transient-prone runs to suppress induced high-frequency noise before it reached the card terminals.

Both changes were done live, channel by channel, with zero process downtime.

Lesson

Don't chase "random" faults as a card or wiring defect until you've checked what else was happening electrically at the exact fault timestamp. Nine times out of ten, intermittent DI faults with no repeatable pattern are a noise/transient problem, not a hardware failure. A quick correlation check against the plant event log will tell you in minutes what could otherwise take days of card-swapping to rule out.

Have you run into similar transient-related DI faults? Drop a comment — always good to compare notes across plants.

🎥 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

Post a Comment

Popular posts from this blog

Belt weigh feeder Zero and Span Drift

-
Image
Fault Log · Field Report Schenck Weigh Feeder — Zero and Span Drift, Two Different Root Causes Plant: Cement  |  System: Schenck weigh feeder, belt scale, hopper load cells  |  Downtime: None Symptom A Schenck weigh feeder started showing both zero drift and span drift at the same time. Two separate accuracy problems showing up together made this a two-part investigation from the start — zero and span errors don't always share the same root cause, even when they appear together. Investigation — Zero Drift Started with the load cell loop and mechanical side of the belt scale: Load cell loop — checked the full loop, cleaned the load cell area. Idlers/rollers — checked the rollers for wear or misalignment. Belt tracking — with the belt empty, noticed it was drifting to one side. Zero was being tared in that empty, drifted position. Once material loaded onto the belt, the belt tracked back closer to center — meaning the zero reference had been tak...
Read more

Zirconia Oxygen Analyzer Reading Maximum O2

-
Image
Fault Log · Field Report Zirconia Oxygen Analyzer Reading Maximum O2 — Not the Cell, a Rusted Outlet Plant: Cement  |  System: Zirconia oxygen analyzer, sample extraction system  |  Downtime: None Symptom The zirconia oxygen analyzer started reading maximum oxygen — pegged at the top of the range rather than tracking the actual process value. A reading stuck at maximum on a zirconia cell usually means the cell is seeing something close to ambient air instead of process gas, which points straight at a sample delivery problem before you even think about the analyzer itself. Investigation Started at the sample path, from the process side inward: Probe, extractor filter, sampling line, pump — checked the full sample path from the probe through the extraction filter and sampling line, including the sample pump. Performed a leakage test across this section. All found ok. Panel-side tubing and membrane filter — checked all tubing inside the panel along...
Read more

Control Valve Positioner Calibration

-
Image
Practical Procedure · Calibration Control Valve Positioner Calibration — Full Stroke, Limits, and Auto vs. Manual Applies to: Pneumatic control valves with smart/digital positioners (e.g. HART-based) or conventional analog positioners  |  Equipment needed: HART communicator (for smart positioners), air supply/regulator, mA source or 4–20 mA loop calibrator Control Valve: Throttling the Flow ACTUATOR As the PLC output signal changes, the actuator rotates the internal disc — from fully open (parallel to flow) toward fully closed (perpendicular to flow). This is exactly why a control valve isn't just "on/off" like a block valve: it throttles anywhere between 0% and 100% to hold a process variable at setpoint. Before You Start Confirm the valve is safe to stroke — coordinate with operations, since a full 0–100% stroke will move the valve through its complete range on a live process line. Chec...
Read more