Gardner Denver Compressor Fault Codes: The $6,200 Mistake That Taught Me What the PDF Doesn’t Say

The fault code that started this mess

Last month, I was leaning against a 2010363 Gardner Denver Electra-Screw compressor that had faulted four times in two days. The display kept flashing "High Discharge Temp" at me, and I was running out of obvious moves.

I'd already replaced the cooling fan. Replaced the temperature sensor. I even had a third-party tech come out for an emergency call—$820 for a few hours of looking and a "might be the controller, might be wiring" verdict.

Then I did what everyone does. I searched "gardner denver compressor fault codes pdf" and downloaded the first result. The PDF listed five possible causes for high discharge temperature. I went through each one. Again. Everything checked out.

Same code. Same checklist. Same result.

That's when I started keeping track of my own mistakes, because this wasn't the first time I'd chased a phantom fault code. It was just the most expensive.

What a fault code actually tells you

Here's what took me way too long to understand: a fault code is a symptom, not a diagnosis. The controller is saying "I detected something outside the normal range." It's not saying why that thing is outside the normal range.

The PDF gives you a menu. High discharge temp could mean a bad cooling fan, high ambient temperature, low oil level, or a blocked cooler. All real possibilities. But the PDF treats them as equals. It doesn't tell you which one is most likely for a 2010363 unit with 12,000 hours on it in a plant that runs two shifts.

It's tempting to think a fault code PDF gives you a straight answer. It doesn't. It gives you options, and you're left guessing which one applies.

I've seen crews fix the symptom in clever ways. One team set up a Milwaukee fan to blow hot air out of the mechanical room, hoping to lower ambient temperature enough that the fault would stop appearing. It worked for about an hour. Then the real issue—a failing oil filter creating pressure drop—caught up and the fault came back.

The fault log: where the real answers hide

What most people don't realize is that the code on the screen is the last event, not the first. The controller keeps a fault log. The sequence matters.

In my first year doing compressed air service, I walked into a plant where a Gardner Denver unit had been tripping on "motor overload" for a week. The previous tech had already replaced the contactor and megger-tested the motor. Both fine. I was about to recommend replacing the starter assembly when I decided to scroll into the fault log.

The first event in the sequence was a low voltage condition that lasted 1.2 seconds. About ninety seconds later, the motor overload fault appeared. The plant's electrician found a loose connection inside the incoming breaker—leftover from a repair six months earlier.

Motor overload code. But the motor wasn't overloaded. The voltage sagged, and the controller did exactly what it was supposed to do.

That was my wake-up call. I stopped staring at the last fault code and started reading the sequence. It changed how I've troubleshot every compressor since. And that $820 emergency call? The tech never opened the fault log. He checked the same checklist I'd already gone through, shrugged, and handed me the bill.

The industry moved on. Most PDFs didn't.

What was best practice in 2018 may not apply in 2025. That's true across compressed air, and it's especially true for Gardner Denver Electra-Screw controllers. They've evolved significantly across the product line—the fault code sets expanded, the logic got more sophisticated, the sensors improved.

And the PDF floating around on some third-party site? It's still describing the logic from an older generation of controllers.

The fundamentals haven't changed. Heat, pressure, lubrication, moisture—those still rule everything. A machine that runs hot is still running hot. But the fault code you get on a current-production Electra-Screw is processed through different logic than a 2006 unit. Treat them the same way and you'll burn through parts while the same error appears on the screen the next morning.

Moisture: the silent troublemaker

Here's something that doesn't get enough attention when people are chasing fault codes: moisture.

I get asked about dehumidifier vs humidifier a lot in compressor rooms. People see condensation on the compressor and wonder if a room dehumidifier would help. It won't. A dehumidifier changes the humidity of the room. It does nothing about the moisture inside your compressed air lines.

That moisture can cause control air failures, icing in cold conditions, and corrosion that eventually shows up as a sensor misread. Misreads are one of the sneakiest causes of phantom faults. I've seen a low oil pressure alarm triggered by corrosion on a sensor connector, not by actual low oil pressure.

If your fault log shows inconsistent codes that never quite repeat, moisture is worth investigating. The fix is a properly sized compressed air dryer, not a dehumidifier in the corner.

You might also see online advice about using a Milwaukee leaf blower to clear debris from cooler cores. It actually works—I've done it. But it won't fix a plugged oil filter or a faulty unloader valve. It just buys you time.

What guessing really costs

Let me total up my 2010363 adventure for you:

• Cooling fan replacement: $340 for the part, $200 in labor
• Temperature sensor: $90, plus an afternoon of work
• Emergency service call: $820
• Production downtime over two weeks: roughly $4,800 in lost output
• A box of donuts for the maintenance crew who kept putting up with my repeated teardowns

Total: about $6,200.

The actual problem turned out to be an oil filter that was about 400 hours past its change interval. It was restricting oil flow enough that the compressor ran hot at full load—just enough to trip the controller fault, not enough to trip any mechanical protection.

The fix cost about $75.

That pricing was accurate as of early 2025. Parts costs move around, so treat those figures as directionally true rather than a current quote.

The point isn't the exact number. It's the gap between troubleshooting a symptom and understanding a system.

The boring fix that works

If you're standing in front of a Gardner Denver compressor that won't stay running, here's what I'd do, in this order:

Get the right documentation for your exact unit. Know your serial number, not just the model. Ask your Gardner Denver distributor for the service manual for that specific controller version. If the document they send doesn't match your controller, ask again.

Read the fault log, not just the current code. Look at the sequence of events. Ask what happened before the fault, not just what caused the final trip. This one habit will save you more money than anything else on this list.

Measure, don't guess. Take actual temperature readings, actual oil pressure readings, actual voltage at the controller. "Looks fine" is not a diagnostic step.

If the same fault comes back twice, stop. Change your approach. Whatever you tried the first two times probably won't work on the third.

This approach works for my situation—a mid-size plant with predictable running hours. If you're supporting critical process equipment with no backup compressor, your calculus might be different. You may need a faster escalation path or a service contract with guaranteed response times.

I keep a running journal of every fault code I've chased, what the PDF claimed, and what the real root cause turned out to be. I started it because I was tired of spending thousands on lessons I should've learned once. If you're staring at a Gardner Denver fault code right now, start with the fault log. Get the right manual. And if you're in a hurry, call a distributor who can pull current documentation.

The PDF on page one of Google might be a starting point. But it's almost never the whole story.