If you're like I was a few years ago, you've got the Danfoss VFD fault codes PDF bookmarked, maybe even printed out and tucked into your service bag. And if you're like I was, you probably treat it like a phone book—flip to the code, read the description, and try the suggested fix. Sometimes it works. Sometimes it doesn't.
Here's the thing I learned the expensive way: the same fault code means very different things depending on your setup. The PDF isn't wrong. But it's written for a general audience. Your specific drive, application, and wiring can turn a simple alarm into a three-hour headache if you're following the wrong branch of the troubleshooting tree.
So in this guide, I'm not going to just list fault codes (you've got the PDF). I'm going to walk you through the three most common scenarios I've run into—personally, after making some boneheaded mistakes—and what to actually do when you see each one.
Scenario A: The Repeat Offender (Same Fault, Different Day)
This is the code that keeps coming back. You reset it, the drive runs fine for a few hours, and then it trips again. If you're chasing the same code like a groundhog, you're probably looking at a system-level issue, not a drive-level one.
Classic example: Danfoss VFD current limit W59.
I once spent an entire afternoon swapping drives on a HVAC fan application because I kept hitting W59. In the PDF, it says "Current limit. Reduce load or check motor." So I checked the motor, it tested fine. I swapped the drive, still tripped. I was about to call tech support when my lead—who'd been doing HVAC controls since before I was born—walked over and asked, "You checked the duct dampers, right?"
No. No I had not.
A manually closed damper (left from a building shutdown) was creating backpressure that made the fan pull more current than the drive's limit setting. Fixed the damper, code cleared, drive ran for years. The W59 was doing its job—it wasn't the drive that was wrong.
If you see W59 or any "overcurrent" fault repeatedly, stop looking at the drive and start looking at what the drive is driving. Check for:
- Mechanical binding or obstructions (dampers, valves, blocked vents)
- Motor cable issues (shorts to ground between phases—a megohm meter can find these)
- Incorrect motor nameplate data entered during setup (I've seen people type in kW instead of hp, or the wrong full-load amps)
Here's a rule I now follow: if the same code resets and comes back within 24 hours, it's not a glitch. It's a symptom.
Scenario B: The New Installation That Won't Play Nice
This one hurts. You've just finished wiring a brand-new FC 102 for a chiller or an HVAC system. You power up, run the automatic motor adaption (AMA), and get a fault. Or worse, it passes AMA but faults the second you try to run it.
This is where the "Prevention Over Cure" mindset pays off. I've wasted more time debugging new installations than I care to admit. Specifically, I'm thinking of one job where an Allen-Bradley panel builder had wired the VFD control terminals wrong—treating the Danfoss digital inputs like a PLC output. (That particular mistake is its own story, but let's just say checking the control wiring against the manual before power-up would have saved us $350 in callbacks and a very unhappy customer.)
For new installations, the most common confusing fault is an unexpected "alarm" or "trip" that occurs immediately after the first run command.
What the PDF might say: "Check control wiring, check 24V supply." Which is fine advice. But here's what I've found actually causes it 9 times out of 10:
- The drive is in Hand mode, not Auto. The LCP (local control panel) has a hand/off/auto button. If someone left it in Hand, your remote start signal goes nowhere. The PDF doesn't always emphasize this because it assumes you're in the right mode.
- Missing enable signal. Many Danfoss drives require a "coast inverse" or "start enable" signal on a specific terminal before they'll run. If you're wiring from a standard PLC or thermostat, you might miss that. It's not a fault you see on screen—it just sits there saying "Ready" and does nothing.
- The 24V supply is loaded down. If you've wired multiple sensors or an external display off the drive's 24V supply, you can drag the voltage low enough that the control logic behaves erratically. I saw this on a job where someone wired in a Samsung oven touch control panel (seriously) into the same 24V loop for some reason. The drive couldn't keep the logic stable. (And honestly, mixing an oven panel with a VFD control circuit is asking for trouble—but that's what I walked into.)
My advice for new installs: run through a pre-power checklist before you even open the main breaker. Walk the control wires, verify terminal by terminal against the manual's installation diagram. I know it sounds tedious. It is. But I promise you, 20 minutes of boredom upfront beats a day of troubleshooting.
Scenario C: The "Will a Bad Fuel Pump Throw a Code?" Type Question
Okay, the title is a little click-baity, but this scenario is real. Sometimes people call me about faults on industrial equipment that isn't a VFD at all. Lately, I've been getting questions like "Will a bad fuel pump throw a code on my engine controller?" which usually leads to a conversation about whether a VFD is involved or if someone confused a motor controller with a fuel injection system.
Here's my honest answer to that kind of cross-system question: A fuel pump failure is a mechanical problem that may or may not trigger an engine controller code. But on a VFD-driven pump system (like a fuel transfer pump using a Danfoss VLT drive), a bad pump—meaning seized bearings, worn impeller, or a failing motor—will absolutely show up as a fault code like W59 or a High Current alarm.
This is where a lot of technicians get confused. They expect a code that spells out "PUMP FAILURE" in plain text. The drive doesn't do that. It reports what it sees: abnormal current. You have to connect the dots.
A practical tip from someone who's connected those dots wrong before:
If you're troubleshooting a VFD-driven pump and you see current limit or overcurrent faults, don't immediately label the code as "bad drive." Take a step back. What's the pump doing? Does it sound different? Have you checked the pump's free rotation with the power off? A simple hand-turn test of the pump shaft (with all safety precautions) can tell you more than staring at a fault log for an hour.
I once wasted a day on a fuel transfer pump on a generator system because I was too focused on the drive fault log. Turned out the pump coupling was sheared. The fault was real, but the cause wasn't the VFD or even the motor—it was a $15 mechanical part.
How to Figure Out Which Scenario You're In
The hardest part of troubleshooting isn't the fix. It's knowing what category your problem falls into. Here's a quick gut check I use:
- Has this fault happened before? If yes, you're in Scenario A (system-level problem).
If no, move to the next question. - Is this a brand new install or a recent modification? If yes, you're in Scenario B (wiring or setup issue).
If no, move to the next question. - Is your equipment completely different from a VFD (like an engine controller)? You might be in Scenario C, and you need to trace back to what's failing mechanically before blaming the electronics.
I can't tell you which scenario fits your situation without seeing your equipment. But I can tell you this: if you've glanced at the Danfoss VFD fault codes PDF, tried the first suggestion, and it didn't work, you're probably not looking at the whole picture. Step back, check the mechanical side, verify the wiring with the power off, and be honest about whether this is a new problem or a recurring one.
A final note: I'm not a Danfoss engineer or a certified VFD trainer. I'm a field technician who's made his share of mistakes, and I'm just sharing what worked for me. For specific drive parameters or factory-level settings, I always recommend consulting the official Danfoss documentation or their technical support team. They have tools I can't speak to—like their configurator software—which may catch things you'd miss on a handheld keypad.
That checklist I mentioned earlier? The one I created after my third (okay, fourth) major mistake? It's saved me an estimated $4,000 in potential rework over the last 18 months. The irony is, the one thing it doesn't have on it is a list of fault codes. Because the code itself is never the full story.
