An ESP doesn't lose collection efficiency because the electrodes fail. It loses efficiency because a rapper in field three stopped firing on schedule three shifts ago, dust cake built up past the point rapping can dislodge it, and nobody heard the missing impact over the noise of everything else running. Sequential rapping is standard for a reason — sign up to verify every rapper in that sequence fires correctly, every shift, before a silent field turns into an opacity spike.
Why It Matters
Under-rapping lets dust cake build up until it re-entrains at high gas velocity; over-rapping strips the cake before it can drop into the hopper. Both failure modes cut collection efficiency and raise stack opacity — and both are invisible on a control room screen unless someone verifies the actual sequence, not just the setpoint.
The Verification In Three Stops
Sequence Confirmation
Confirm rapping intensity and frequency settings match the optimized schedule, with no manual overrides left active from the previous shift.
Rapper Deck Walk
Listen for a distinct impact from each rapper as it cycles, and check rapper motor current for any group reading zero or unusually high.
Ash & Log
Check hopper levels and heater temperatures, then log any drift or missed impact for the next shift and route it to a work order.
The Daily Sequence Verification Checklist
Verify rapping intensity and frequency against the optimized schedule: confirm no manual override is still active from a previous shift, since a forgotten override is one of the most common causes of a slow, undetected efficiency drift
Confirm each field rap is sequential, never simultaneous: rapping inlet and outlet fields at the same time maximizes re-entrainment losses — this should never happen on a correctly configured sequence
Check rapper motor current for every group: elevated or zero current signals a jammed rapper or a seized mechanism that visual inspection alone would miss
Investigate any hopper at high-level alarm immediately: a plugged hopper shorts the electric field in that section within hours, so this is one finding that should never wait for the next scheduled round
Log visible ash buildup on plates or wires: visible buildup during a walkdown is one of the clearest signs that rapping energy isn't transferring effectively, even if the sequence looks correct on the control screen
Every Rapper Verified, Every Missed Cycle Flagged
Oxmaint logs rapper sequence, motor current, and hopper status against the optimized schedule for every field, and raises a work order the moment a rapper drifts out of pattern. Sign up for a free trial to run it on your own ESP, or book a demo to see it configured for your fields.
Why Rapper Drift Hides From The Control Room
A rapper controller can report that a rapping cycle completed without confirming that dust actually left the plate. A shaft coupling worn just enough to run free, an impact cap flattened enough to cut transmitted energy without failing outright, or a rapper timing that has quietly drifted from the optimized schedule — none of these trip an alarm on their own. What they produce instead is a slow rise in stack opacity and a slow fall in collection efficiency that looks, on a trend graph, exactly like normal day-to-day variation. That's why the verification has to be physical: standing at the rapper deck and confirming a distinct impact sound from each unit in sequence catches what the control room display cannot.
What A Drifting Sign Usually Means
| Check Point |
Early Warning Sign |
Likely Cause |
| Rapper motor current |
Reading at zero or unusually high for the group |
Jammed rapper or seized mechanism |
| Impact sound |
Missing or dulled impact during walk-down mode |
Worn shaft coupling or flattened impact cap |
| Hopper level |
Trending toward high-level alarm |
Slow discharge valve or plugging risk |
| Visible plate buildup |
Dust cake visible during internal walkdown |
Weak or inconsistent rapping energy transfer |
Frequently Asked Questions
Q
Why does simultaneous rapping across fields cause problems?
Rapping multiple fields at once, especially inlet and outlet together, maximizes the amount of dislodged dust that gets carried back into the gas stream instead of falling into the hopper. Sequential rapping is the standard configuration specifically to avoid this.
Q
Should rapping be increased whenever opacity rises slightly?
Increasing rapping frequency is a reasonable first response, but any increase in intensity generally shouldn't exceed about 50% above normal, since over-rapping strips the dust cake early and can damage electrodes over time. Confirm the cause before pushing intensity further.
Q
Does a UK coal station need a digital record of this daily check?
A digital, technician-attributed record gives a much stronger audit trail for emissions compliance than a paper log, and it's what actually connects a missed rapper or a rising hopper level to a work order instead of leaving it noted but unactioned.
Verify Every Rapper Before A Field Goes Silent
Oxmaint tracks rapper sequence, motor current, and hopper condition against your optimized schedule for every ESP field, and turns a missed impact into a work order before it becomes an opacity spike. Sign up for a free trial to build your own rapper verification checklist, or book a demo to see it set up for your ESP.
.png)
.png)