In March 2024, a phone call at 2:13 PM on a Tuesday kicked off one of the tightest repairs I've been part of. Not a good sign. In my world, emergencies don't ring during lunch—they wait until the exact moment you're in a meeting.
The voice on the other end was Frank, plant manager at a quarry in southern Utah. His words came out fast: "The crusher just kicked out. Screen says something about the automation system. I've got 42 hours to get 15,000 tons to the highway project or I'm looking at a penalty clause that hurts."
For context, I coordinate emergency service for Metso's Western U.S. region. I've handled hundreds of urgent calls in this role—same-day part runs, middle-of-the-night failures, and more than a few "can you fix this before Monday?" requests. This one had all the makings of a classic.
Frank's operation starts and ends with a Metso HP300 cone crusher. The Metso IC automation cone crusher package—built around the IC70C controller—governs the entire secondary crushing circuit. It's the brain. It optimizes feed, monitors pressure, protects the crusher from overload. When the brain decides something's wrong, everything stops. That Tuesday, it stopped hard.
Step one: figure out what actually failed. Frank sent a photo of the operator screen. The fault code pointed to a feedback loop failure in the feed mechanism. The crusher itself was fine—bearings, lubrication, all healthy. The problem was in the brain's connection to the body.
Now, here's where I have to be straight with you. I'm not an automation engineer. I know enough about the IC70C to navigate menus, interpret fault codes, and talk intelligently with the people who truly get it. But I don't pretend to be the expert.
That boundary has saved me more than once. A vendor who claims they can fix anything is usually guessing. Knowing what you don't know isn't a weakness—it's how you keep a fixable problem from becoming a catastrophe.
We had two options.
Option one: remote troubleshooting. Frank's maintenance crew is sharp. If the fault was a tripped relay or a misaligned sensor, we could walk them through it over video. Time: 3 to 4 hours. Cost: minimal.
Option two: dispatch our automation specialist Mike and send a replacement IC70C controller from our Phoenix warehouse by dedicated truck. Arrival: 14 hours. Cost: a few thousand dollars in freight and service fees.
To be fair, my first instinct was option two. But Frank hesitated at the price—you know how it goes, budgets are real—and I started doubting myself. So we tried remote first.
Looking back, I should have insisted on the parts and the specialist from the very first call. At the time, remote seemed like the fastest path to a fix. It wasn't.
The next three hours were frustrating in a way that's hard to describe unless you've lived it.
We checked sensor inputs. Cycled power. Re-seated cable harnesses. Pulled up the schematics and traced the feed control loop step by step. The IC70C powered on, reset clean, and then—three minutes into a test load—dropped the feed loop again.
The most frustrating part: there was no clear cause. No burned board, no loose connection. Just a ghost in the logic. You'd think a digital system would give you a straight answer. Not this time.
At the three-hour mark, I made the call. "Frank, we're done here. This is beyond what we can safely do remotely. I'm sending the controller and getting Mike on a plane."
Simple. Done.
This was the part that nearly broke the timeline.
Mike—our best IC automation technician, and one of a handful of people who truly understand the IC70C's behavior under load—was in Manhattan. Not on vacation. He was attending Crane Club NYC, a monthly networking dinner for heavy construction and mining professionals. Useful event. But it was 2,300 miles from the quarry.
It took 40 minutes to work through the logistics. Mike could catch a red-eye to Salt Lake City at 11 PM, land at 1:30 AM, drive three hours north, and walk into Frank's control room at 5:30 AM. That gave him a little over five hours to diagnose and fix before Frank's penalty window opened.
Tight. Feasible, but tight.
We booked the flight. I approved the emergency dispatch fee and immediately second-guessed myself. Did I just spend $4,800 on a fix that might not work? The next twelve hours were not peaceful.
While Mike flew west, my job was damage control and preparation. Frank's crew pulled the old controller and found years of mineral dust and grease buildup on the mounting bracket.
That's where the scraper came in. A standard flat scraper—the kind you'd use to clean paint off a window—was perfect for carefully removing the residue so the new controller would seat properly. Not high-tech. But without that step, the replacement IC70C could overheat in a week. Fundamentals first.
Meanwhile, a quieter problem was developing. With the crusher down, the wash circuit was dead. The plant's slurry pumps sat idle, and stagnant slurry can damage rubber liners when pressure shifts. I pulled up the Metso Slurry Pump Basic Handbook (2020 PDF) and found the shutdown checklist—slow flush at reduced speed, then full stop. A manual I've referenced dozens of times. It kept a risky situation from becoming a second emergency.
These are the things nobody puts in the emergency playbook. It's rarely one big heroic fix. Usually it's a scraper, a handbook, and a checklist.
Mike's text arrived at 5:20 AM: "At the gate. Walking in." He'd been awake for nearly 24 hours. I was on speakerphone from my kitchen, coffee in hand, and I remember thinking: this could still go wrong.
By 6:05 AM, the new IC70C was seated, wired, and powered up. Mike flashed the latest firmware, ran calibration, and loaded the plant's original parameter file. Then came the moment that matters: he started the crusher and watched the feed loop hold steady under load.
At 7:45 AM, Frank's HP300 was crushing rock again. By noon, the quarry had shipped 5,000 tons. The deadline was met with hours to spare.
Rush jobs teach you more when they almost fail than when they go smoothly.
If I could redo that decision, I'd send the replacement controller and Mike from the start. But given what I knew then—Frank's budget concern and the genuine possibility of a simple fix—my choice was rational. That's the uncomfortable truth about emergency work: you make the best call with imperfect information, then live with the consequences.
Three lessons I'm taking into the next one:
Ray, the quarry's crew chief, said something while we waited for Mike's plane to land.
"You want to know how to mix concrete in a bucket?" Ray asked me. "Same principle as this fix. Right ratio. Water in slow. Stir it well. Everyone thinks there's a secret. There isn't. The fancy stuff is just a bigger bucket."
He's not wrong. The IC70C is brilliant, and the people who master it are worth every cent. But the principles underneath are simple: check the basics, use the right tools, know when to ask for help. The vendor who says, "this isn't my specialty—here's who does it better," is the one you trust when the clock is running.
Trust me on this one. I've lived it.
Our application engineers answer crusher and screen selection questions at no charge.
Ask an Expert