Danfoss VFD Alarm 16: The Fault Code That Cost Us $38,000 Before We Learned to Read It

When I look at our cost tracking system, one line item keeps telling me a story I was too busy to read at first. Same fault code, eleven times in one year, on the same packaging line. Total: roughly $38,000 in replacement drives, freight, and emergency labor.

Search “danfoss vfd alarm 16” and you get the textbook answer: short circuit. Dig into the forums and you'll find the same advice repeated — the module is gone, replace the drive. We followed that advice. It's exactly why the bill got as high as it did.

The first time the line stopped, the red LED on the Danfoss VLT keypad said it all: alarm 16. The operator followed the checklist. The maintenance tech verified the code in the manual. The supply room grabbed a replacement drive. It worked for two weeks. Then the new drive tripped with the exact same code.

A brand-new drive shouldn't short-circuit. So we replaced the motor leads. Then the motor. Then the drive again. Sound familiar?

What Alarm 16 on a Danfoss VFD Actually Means

I'm not an electrical engineer. I'm the person who signs the purchase orders, so I've had to learn this the hard way.

According to the Danfoss VLT operating guide for the current series, alarm 16 signals a short circuit condition. The exact alarm table varies by VLT series and firmware version, so check the manual for your specific drive before assuming anything.

Here's the part nobody puts in the alarm table: a short circuit alarm means the drive detected current flowing somewhere it shouldn't. Sometimes that means the drive failed. More often, the drive is doing its job and catching a problem that belongs to the wiring, the motor, or the machine configuration.

When I finally sat down with our senior controls tech and reviewed all eleven events, the pattern was almost embarrassing. Four were chafed motor leads on the linear actuator axis — the cables flexed with every movement, wore through the jacket, and the VFD caught the resulting fault. Three were an aging motor with failing winding insulation. Two were actual drive failures. And the last two were loose terminations from our own rush job during a previous “emergency” replacement.

Nine out of eleven cases, the drive wasn't the problem. It was the smoke alarm, not the fire.

That kind of analysis is hard to do when the line is down. I get it. When a $100,000 line stops at 11:30 PM, you're not thinking about total cost of ownership. You're thinking about the customer order due in the morning. That pressure is real. But that same pressure is exactly why we spent $38,000 instead of $6,400.

The Motion Control Mismatch Behind the Fault Code

This is where alarm 16 hides a deeper problem. The searches that land people on pages like this one — “danfoss vfd alarm 16,” “danfoss vlt vfd,” “how fast can a linear actuator move,” “servo motor diagram” — usually come from engineers pushing a machine past its intended limits and hoping a fault code will explain the pain.

Let me translate that into budget terms. A Danfoss VLT VFD is designed to control the speed of an induction motor. That's what it's brilliant at. It is not designed to do precise positioning, and it won't survive being treated like a servo system.

We saw this after production asked us to speed up a linear actuator assembly. The answer to “how fast can a linear actuator move” depends on lead screw pitch, motor torque, duty cycle, and cable management — not just on the drive. We raised the speed, the actuator moved faster, and within two weeks the VFD started logging alarm 16. The faster cycle was stressing the cable and the motor beyond what the system was built to handle. The drive was protecting itself. We kept reading the code as “buy a new drive,” when it was really saying “this machine design is at its limit.”

If you're looking at a servo motor diagram because you think your application needs positioning, you may be right. A servo system handles dynamic load changes and holds torque at standstill in ways a VFD can't. A stepper motor solves simple point-to-point motion at a lower cost, but it has its own limits. All of these are valid tools. The mistake is forcing one to do another one's job, because the fault codes will eventually teach you the difference — at emergency pricing.

The Real Cost of a Repeated Alarm Code

Here are the numbers I actually track. One alarm 16 event on Line 3 cost us, on average:

• $4,200 to $5,800 for a replacement VLT drive, depending on model and how fast we needed it.
• $680 to $1,100 in expedited freight and after-hours labor.
• $2,800 per hour of line downtime. A 14-hour stoppage, from first alarm to post-swap test, disappears that budget quickly.

That's $38,000 in a single year for a fault that — nine times out of eleven — never required a new drive.

There was also a hidden cost. After the third replacement, the maintenance team started doubting the equipment. The operator slowed the line down “to be safe.” Nobody invoiced us for that, but it showed up in output numbers.

The last alarm 16 forced a real decision. I had to choose between a $900 diagnostic visit and a $4,800 replacement drive. Production wanted the drive. The spreadsheet wanted the diagnosis. We spent the $900 — it was a loose termination in a junction box left open during the previous “quick fix.” The $4,800 drive would have told us nothing.

Honestly, I'm still not sure why one of the rewound motors failed after fourteen months when the invoice said it should last three years. My best guess is the rewind shop cut a corner on the varnish. But that's a different story. The main lesson stands: alarm codes are data, not verdicts.

When I audited our VFD-related spending for 2023, I found that 61% of it was reactive — emergency purchases, rush freight, double labor rates. After we fixed the root causes, VFD spend dropped by about $31,000 the following year. The corrective work, including a cable carrier upgrade and two motor rewinds, cost $6,400.

A $38,000 problem had a $6,400 solution. The reason it took so long to find it is that we kept buying the failure instead of understanding it.

What We Changed (and What You Can Steal)

None of this required a complex reliability program. It started with one rule:

No new drive gets ordered until the old one gets diagnosed.

That rule has saved more money than any vendor discount I've negotiated in six years of tracking every automation invoice. Here's what the triage looks like now:

1. Check the obvious first. Inspect the motor leads along their full path, especially on moving axes. A chafed cable is the #1 cause of alarm 16 in our facility.
2. Test the motor, not just the drive. A megohmmeter test on winding insulation takes ten minutes and costs almost nothing compared to a drive swap.
3. Confirm the code against the manual for your exact Danfoss VLT series and firmware. Alarm tables change across generations. What you learned on an older VLT may not apply to a brand-new one.
4. Log every trip. Spreadsheet, notebook, whatever. Track the code, the action taken, and the outcome. Patterns become visible fast when you stop relying on memory.

And one more thing: be honest about what the machine is asking the drive to do. If it needs positioning, it needs a servo system, not a VFD with a clever trick. If you're drawing a servo motor diagram to understand the difference, you're already ahead of where we were. Selecting the right motion component upfront is cheaper than any fault code cleanup.

The fundamentals haven't changed since I started in this role: read the alarm, understand the system, fix the cause. But the execution has evolved. Diagnostics are sharper, documentation is more accessible, and the industry has stopped treating every drive trip as a hardware failure.

Line 3 hasn't logged alarm 16 in nine months. I know because I still track it. And when a distributor calls offering a deal on replacement drives, I politely decline. That's my favorite line item in the budget — the one we no longer need.