The 2 AM Danfoss VFD Checklist: 5 Things to Check Before You Replace Anything

Every VFD failure story sounds the same until it's your line down at 2 AM. An alarm code is blinking on the keypad, the production manager is standing behind you, and the machine won't run. The easiest thing to do in that moment is reach for the Danfoss VFD manual, search for the alarm code, and start ordering parts.

Don't. At least not yet.

I've been doing emergency callouts on industrial drives for about 10 years — Danfoss FC series most of the time, plus plenty of servo systems and direct drive setups. I've logged well over 100 after-hours trips in that time. This article is the troubleshooting sequence I use at the cabinet — in the order that saves time and money.

When This Checklist Applies

Use this when the drive still powers up and shows an alarm but won't run. If the display is completely dark — or you smell that unmistakable burnt-electronics smell — skip ahead to checking input fuses and the main disconnect. This list isn't for dead drives.

The list has five checks, in order. I arranged it that way because the cheapest and most likely fixes come first. If you skip around, you'll waste time.

Step 1: Ask What Changed — Before You Ask What the Code Means

The biggest mistake I see is reading an alarm code, looking it up in the manual, and immediately chasing the listed cause. But half the "mystery" faults I get called out for were caused by something that changed the day before — not by a spontaneous drive failure.

So, first questions, in this order:

• Was anyone in this cabinet recently? New wiring, new motor, new connection, changed parameters?
• Did the line have power problems today? A loose neutral on the supply side creates some weird alarm combinations.
• Did the fault happen on a cold start, or after running for hours? That single detail splits the troubleshooting path in half.

Why does this matter? Because if I fix the effect and leave, the same alarm will be back at 3 AM next week — unless the change is found.

I learned that one the hard way. I assumed a sudden ground-fault alarm on an FC 302 meant the motor windings were degrading. Didn't verify what had changed on the line that morning. Turned out someone had routed a new sensor cable too close to the motor output cable, and the insulation was already nicked. I was about to quote a motor replacement. The motor was perfectly fine. Ask "what changed" first.

Step 2: Check the Danfoss VFD Cooling Fan — It's Often the Fan

Okay, "it's always the fan" would be wrong. But the cooling fan is the most common physical failure I see in drives over three years old. It's a wear item — a spinning part with a finite life. In most industrial environments, I expect fan trouble somewhere in the 30,000 to 50,000 hour range.

Here's what catches people out: the trip often happens on a cold morning, in a cold cabinet, at part load. The heat sink alarm — Alarm 29 on the FC 102/202/302 series — is triggered by heat buildup over time, not by one hot day. So you're standing there thinking "overheating? It's freezing in here," and you get distracted.

The fan check takes 30 seconds:

1. Lock out and tag out the drive. Wait for the DC bus to discharge if you're going near the terminals.
2. Look at the fan. Is it spinning freely? Or humming while stopped? A stopped fan while the drive still runs slowly cooks the heat sink.
3. Check for dust. A thick layer on the heat sink is the same as a dead fan — it insulates and blocks airflow. Blow it out, but only with the drive safely off.

Replacing a Danfoss VFD cooling fan takes about 15-20 minutes, and the fan is one of the cheaper parts you'll ever buy for a drive. Replacing the entire drive because the fan died and took the power stage with it runs into real money. The 5-minute inspection beats the 5-day repair. I've watched it happen both ways more times than I can count.

Step 3: Read the Danfoss VFD Manual — But Read the Right Part

The Danfoss VFD manual has an alarm code table that lists possible causes in order of probability. Use it. But don't just read the code name and stop. Read the conditions for each cause, and compare them against what's actually in front of you. The manual's engineers listed those conditions in a deliberate order — respect that.

What most people don't realize is that many different alarm codes share the same root cause: grounding. A bad ground on the motor cable produces intermittent faults that look completely unrelated — voltage warnings, phase loss, current imbalance.

If your codes keep changing and nothing you replace fixes it, check the grounding before anything else.

One practical tip: keep a copy of the alarm table on your phone, and check the firmware revision on the drive's nameplate before you trust the PDF. Danfoss has changed alarm behavior across firmware generations, and a downloaded manual from three years ago may not match the drive in front of you.

Step 4: Isolate the Motor — Servo Motors Included — Before You Blame the Drive

This is the step that saves people the most money and gets skipped the most. A VFD trip often gets reported as "the drive broke my motor" or "my drive is fried." But when I disconnect the motor and check it properly, a large percentage of the time the motor — or the cable to the motor — is the actual problem.

If you can safely decouple the motor, measure the winding resistance phase-to-phase and phase-to-ground. Significantly unbalanced readings tell you more than any alarm code. Then open the terminal box and look for moisture, corrosion, or loose connections. I've seen a burnt terminal connection cause a year of intermittent trips.

For servo motors specifically, the winding is rarely the culprit — the feedback cable is. A damaged encoder cable produces the same symptoms as a dead encoder: position errors, torque fluctuations, random "illegal" faults. Before you send a servo motor off for repair, check cable continuity and connector pins. I can't count the number of servo motor repair quotes that got cancelled after someone wiggled the cable and the fault cleared.

And for direct drive servo motors, there's an extra wrinkle: since the motor is coupled straight to the load, the load's mechanical condition reflects directly back into the motor. A worn bearing in the machine creates current fluctuations that look like an electrical fault. Which brings us to the last step.

Step 5: What's a Ball Bearing — and Why It Makes a VFD Look Broken

Most techs — including me, early on — skip this because it's not in the electrical section of the manual.

So what's a ball bearing? It's the simple mechanical component that lets a motor shaft spin with low friction: a set of steel balls running between an inner race and an outer race, sealed and greased. Cheap to buy. Huge importance to your plant, because a failing bearing is one of the best ways to create a phantom VFD fault.

Here's how it works. A bearing with damaged balls or races makes the shaft vibrate and creates tiny variations in torque demand. The VFD's current sensing interprets these as load disturbances. You get repeated current limit alarms, torque limit alarms, even motor phase loss codes that make no sense electrically. Replace the drive, and the new drive will trip too. Replace the motor, and the new motor will fail prematurely. The bearing was the root cause all along — the VFD was just the messenger.

Quick field check: run the motor uncoupled, if possible, and listen. A healthy bearing is nearly silent. A failing one usually grinds or rumbles. Put a screwdriver to your ear (the old mechanic's stethoscope) and place the tip on the motor end bell. If it sounds like gravel, that's your answer. Replacing a bearing is dramatically cheaper than replacing the motor or the drive.

The Mistakes I See Repeatedly

From over a decade of callouts, the same patterns show up:

1. Replacing the drive first. I've seen perfectly good drives sent back as "defective" when the fan or the motor was the problem.
2. Deferring a fan replacement. The drive warned you months earlier — a noisier fan, a slightly hotter heat sink — and nobody acted until shutdown.
3. Ignoring the mechanical connection. Couplings, pulleys, and belts cause load oscillations that look like drive faults.
4. Using the wrong manual revision. Verify the firmware version before trusting a downloaded PDF.

The pattern in one sentence: most emergency VFD work is not about the VFD. It's about a fan, a bearing, a cable, or a ground — all things you could have inspected for far less than the cost of a repair call.

A 5-Minute Prevention Routine

You won't eliminate every breakdown. But you can stop most of them from becoming 2 AM events:

• Quarterly: feel the heat sink, blow out the cabinet, confirm the fan spins freely.
• Annually: meg the motor and inspect the terminal box.
• When a new drive is installed: save the alarm table on the phone of the person who responds to alarms.

It took me about three years and fifty-plus callouts to understand that the expensive fix is rarely the correct fix. The correct fix is almost always something small, mechanical, or environmental — preventable with five minutes of attention. The VFD is the messenger. Listen to the message, but inspect the whole system before you shoot the messenger.