A cobble doesn't start at the exit of a hot strip mill, that's just where it becomes visible. By the time strip is piling up and the line is stopping, the actual cause, usually a servo valve responding a fraction slower than it should, has been building for days. One mill traced that chain back to its source and cut cobble events by more than two-thirds. Here's the chain, and where they broke it. Sign up to see where a similar chain might be building on your mill.
68% Fewer
Reduction in cobble events after servo valve monitoring went live
Caught Upstream
Servo valve drift flagged before it ever reached the strip
~45 Min Saved
Typical line downtime and cleanup avoided per prevented cobble
6 Months
Time to a stable new cobble rate after the program started
The Problem
Every cobble meant the same routine: an emergency stop, a strip pileup to clear, and hours of lost rolling time on top of the damaged coil itself. The mill's maintenance team kept fixing servo valves after a cobble happened, but never had visibility into which valve was drifting before it caused one.
Anatomy Of A Cobble
1
Servo Valve Response Drifts
A hydraulic servo valve's response time slows gradually, often for weeks before it's noticeable in normal operation
2
Roll Gap Control Lags
Automatic gauge control starts correcting roll position a fraction later than the process calls for
3
Strip Tension Becomes Uneven
Inconsistent gap control creates uneven tension across the strip width, especially at higher speeds
4
Strip Buckles And Cobbles
Accumulated tension imbalance causes the strip to buckle and pile up, usually at the exit side of the stand
Catch Servo Valve Drift Before It Reaches The Strip
Oxmaint tracks servo valve response and roll gap control against each stand's own history, flagging drift long before it affects tension. Sign up for a free trial to see it against your own mill data, or book a demo to walk through your cobble risk points.
Where Monitoring Interrupted The Chain
| Chain Stage |
Before |
After |
| Servo valve response |
Only checked after a fault was already suspected |
Response time trended continuously per valve |
| Roll gap control lag |
Relied on an operator noticing gauge drift |
Control lag flagged automatically against baseline |
| Strip tension variance |
Reviewed only after a cobble to find the cause |
Tracked in real time across the strip width |
| Cobble events |
Frequent, unplanned line stops |
Rare, most drift caught well upstream |
The Results
The mill didn't need new hardware to make this work, the servo valves were already producing response data every cycle. The change was capturing that data against each valve's own history and acting on the drift instead of waiting for it to show up as a cobble downstream.
Frequently Asked Questions
Q
What is a cobble in a hot strip mill?
A cobble is when strip loses its stable path through the mill and buckles or piles up, usually forcing an emergency stop to clear the tangled strip before rolling can resume.
Q
Why do servo valves affect cobble risk?
Servo valves control roll gap positioning, so a valve that responds even slightly slower than spec introduces a lag in gauge control that can build into uneven strip tension and eventually a cobble.
Q
Can predictive maintenance prevent cobbles without slowing production?
Yes, since it works from data the servo valves and control system are already generating, the monitoring runs alongside normal rolling without requiring any change to line speed or schedule.
Stop A Cobble Before The Strip Ever Buckles
Oxmaint tracks servo valve response and roll gap control against each stand's own history so drift is caught long before it reaches the strip. Sign up for a free trial to see it against your own mill data, or book a demo to walk through your cobble risk points.
