Here's an opinion that might surprise you: most emergency service calls for Kaeser compressors don't actually need to be emergencies. I coordinate compressed air service in the greater Fredericksburg VA area, and after dispatching on 200+ emergency calls over 8 years, the pattern is unmistakable. A fault code appears. Someone resets it. The machine runs for a while. The code comes back. Lather, rinse, repeat—until the compressor finally quits entirely, and then we get the frantic call.
I'm not going to soften this: if you're resetting fault codes on your Kaeser without investigating what caused them, you're gambling, and the house always wins. The code isn't the problem. It's a symptom. Reset the code but not the cause, and the issue's going to keep coming back—usually at the worst possible time.
Fault Codes Are a Starting Point, Not a Verdict
Every code your Kaeser controller throws is a red flag, not a diagnosis. The machine isn't saying, "this component is broken; replace it." It's saying, "one of my measured values went outside acceptable limits, and you need to figure out why."
Take a high-temperature shutdown. On paper, it means discharge temperature exceeded the threshold. But the root cause could be a dirty oil cooler, low oil level, high ambient temperature in the compressor room, a faulty temperature sensor, or—worst case—actual mechanical wear in the airend. Five completely different scenarios, same code. If your troubleshooting ends at "reset and see what happens," you're rolling dice with a piece of equipment that costs more than a small car.
In my first year doing this, I made the classic rookie mistake: I treated the fault code documentation as gospel. A client near Richmond had a recurring low-pressure fault. I showed up with the printed manual pages, confident the answer was a failing inlet valve before I'd even touched the machine. We ordered the replacement part—$800—and it didn't fix anything. The actual issue was a maladjusted pilot valve controlling the inlet regulator. That was my $800 lesson in why a code is the start of the conversation, not the end of it.
The Same Code Means Different Things in Different Contexts
Here's something that gets lost in a lot of troubleshooting: the same code can mean completely different things depending on what the system was doing when it tripped. And honestly, that context is tough to capture in a fault code PDF.
A low-pressure alarm in July during peak production, when every line is running at maximum flow? That's a demand-versus-capacity issue. You're asking the compressor for more air than it can produce. No reset in the world changes that.
The same low-pressure code in November on a quiet weekend shift? That's suspicious. Could be a leak, a failing inlet valve, or a sensor drifting out of calibration. Totally different troubleshooting path.
The most frustrating part of this job is watching operators treat those two situations as identical. You can clear the code all day and never touch the root cause, because the answer was in the context, not in the code itself.
In March 2024, a Kaeser SM10 at a workshop in Spotsylvania kept tripping on motor overload. The operator told me he'd reset it five times in about three weeks. When I pulled the event history, the pattern jumped out: the faults always occurred in the afternoon, right after the workshop's new exhaust fan kicked on. They'd added the fan to the same breaker circuit. Under start-up load, the compressor was seeing a voltage dip severe enough to trip the overload relay.
The compressor wasn't failing—or rather, it wasn't the compressor at all. The electrical supply was choking it. The fix? A dedicated circuit, about $900 in electrical work. If they'd called after the second reset instead of the fifth, we could've diagnosed it as a planned visit and avoided three afternoon production stops.
It's Also a Language Barrier
Sometimes the problem isn't the machine. It's the conversation around it.
I told a client once, "I need you to verify the oil separator isn't restricted." What he heard was, "the oil separator probably needs replacing." By the time I arrived, he'd already ordered a replacement—an $850 part that wasn't needed. The separator was fine. The actual issue was a drain valve stuck open, causing the separator to fill with oil and carry over.
It's not that he was careless. We were using the same words but meaning different things. He heard a suggestion as a verdict. These conversations happen in every shop I walk into, and they're a big reason why emergency calls get more expensive than they should.
Not Everything Needs a Technician
I'll be straight with you, because my credibility depends on it: there's a lot a good maintenance team can handle on its own.
Simple fault codes with a clear, verifiable cause—low line voltage you can confirm with a multimeter, a high ambient temperature alarm when the compressor room gets brutal in summer, or a sensor fault confirmed with a quick resistance check—these are well within an in-house maintenance person's capability. I regularly tell clients, "You don't need us for that. Here's what to check, and here's how to verify it."
But I also tell every client the same thing on the flip side: if you've cleared the same code two or three times in a month and the cause hasn't revealed itself, that's your signal to bring in someone with better diagnostic tools. A recurring code is your machine asking for help. If you don't listen, it eventually makes the decision for you—by stopping completely, or worse, by breaking something catastrophic like the airend.
And I'd rather get paid for a $300 diagnostic visit than a $15,000 airend replacement. Everyone comes out ahead in the first scenario.
"But I Can't Shut Down the Line"
I hear that a lot. And I get it. Production pressure is real. In this industry, downtime gets measured in dollars per minute, and no maintenance manager wants to be the one who stops the line for a "maybe."
But here's what I've learned from watching it play out dozens of times: a 15-minute shutdown to investigate a code will never cost as much as a catastrophic failure that stops the plant for three days. I've lived through both versions enough times to lose count.
I've handled plenty of rush calls where a client's deadline hung in the balance—same-day turnarounds, expedited freight, parts driven across the state. In 8 years, I've never once seen the "just reset it" strategy prevent a second failure. Not once. Every single emergency call I've responded to had a root cause that had to be found and fixed. The only variable was whether it got caught early or late.
Call Early, Not Often
Look, I'm not going to sit here and tell you every Kaeser owner needs a service contract. That would be self-serving and untrue. These are well-built machines. Kaeser's reliability record is earned, and their documentation is better than most manufacturers. If you can read the manual for your model and have basic electrical troubleshooting skills, you can handle the easy stuff.
But if you've got a fault code that keeps coming back, an event history full of repeated shutdowns, or new problems appearing after changes to your system—new equipment, shifted loads, modified piping—that's when you should call someone. Not because you're incapable. Because the cost of guessing wrong is too high.
And when you do call, have the basics ready: model number, run hours, the fault code, and any event history you can export. I want to say the Sigma Control 2 logs hundreds of events, though don't quote me on the exact number. What I'm sure about: that data saves time, and time is money on a service call. This is how a $300 diagnostic visit stays at $300 instead of turning into $700.
Use your Kaeser's fault codes for what they are: a communication system. The machine measures itself constantly and tells you when something's off. The smart operators listen. The ones who don't end up in my dispatch queue.
Your compressor is trying to tell you something. Maybe give it a chance to finish the sentence.
