When the drive alarms, everyone assumes I know exactly what's wrong
From the outside, it looks like the admin who orders the Danfoss VFD must also know how to fix it when an FC 102 throws an alarm 14 or a VLT drive won't connect to the PLC. The reality is that my job isn't diagnosing the drive—it's making sure the right manual, the right part, and the right technician get to the right place before production stops. I manage the ordering, the paperwork, and the vendor relationships. I'm not the one with the multimeter.
But you know what? After five years of buying Danfoss VFDs and handling the fallout when they trip, I've learned exactly which resources matter. The Danfoss VFD troubleshooting manual PDF is a masterpiece of technical writing—if you know where to look. The problem is that most people don't, and they end up calling me for a part that doesn't exist or demanding a tech support call that costs more than the repair.
So here's the decision tree: the approach to troubleshooting depends on your situation. I'll lay out three common scenarios, and you can find yourself in one of them.
Scenario A: The drive is new, but you're getting an alarm code you can't decode
This is ironically the most stressful scenario. You just unboxed a spanking new Danfoss VLT drive, wired it up, and now it's flashing alarm 14 (which, if you don't have the manual handy, is a ground fault). Or maybe it's alarm 38—phase loss. The drive isn't even broken yet; it's just confused by the installation.
What most people don't realize is that the Danfoss VFD troubleshooting manual PDF is available for free on their website. I know, I know—everyone wants to pretend that's obvious. But I can't tell you how many times I've fielded a call from a shop floor manager asking me to 'find the Danfoss tech support phone number' when the answer was on page 47 of the manual that came in the box.
Here's my advice: if you're staring at a brand new drive and you haven't downloaded the manual for that specific model, stop. Go to the Danfoss VFD VLT support page. Enter your model number (FC 102? VLT Micro Drive?). Download the manual. Search for the alarm code. 80% of the time, the fix is a parameter change.
If you're dealing with a VFD that's supposed to be talking to a PLC program and it isn't, check your wiring first. The manual has a diagram. Seriously. I can't count how many 'dead drives' I've seen that were actually just miswired. People assume the PLC is wrong. The reality is that the VFD is just a dumb box that does exactly what it's told—if you told it wrong, it's not going to argue.
When to call tech support anyway
If the alarm code isn't in the manual (rare, but happens with older models) or if the fix requires a parameter change that you don't have access to because the previous guy set a password, then call Danfoss support. But don't expect a five-minute fix. Bring the model number, serial number, and the alarm code. If you call and say 'my VFD is broken,' they'll politely ask you to read the manual. I learned that the hard way when I called in 2022 without the manual in front of me.
Scenario B: The drive is old, and you're trying to decide if it's worth fixing
This is where the admin buyer in me wakes up. I process maybe 60-80 orders a year for electrical components across 8 vendors, and the VFDs are the most painful to replace because they require downtime. So here's the decision: do I buy a new Danfoss VFD, or do I try to fix the old one?
If the drive is more than 10 years old and the cost of a replacement is under $1,000, I tell people to just replace it. That seems wasteful to the guy on the shop floor who wants a quick fix, but I've seen the math: a repair callout costs $400 minimum, plus the part, plus your lost production. A new VLT drive is $800-1,200. If the old one has any other issues (bad capacitors, worn-out fans), you're just deferring the inevitable.
But—and this is where I sound like the admin who actually reads the spreadsheets—if the drive is still supported by Danfoss and the repair is simple (like a bad fan module or a fried control card), it's often cheaper to fix it. The error codes that indicate a bad power card (like alarm 4 or alarm 8) are pretty clear in the Danfoss VFD troubleshooting manual PDF. If you can find the part number on the VFD's nameplate, you can order it yourself and have your in-house electrician swap it in an hour.
What I tell my internal team: 'If the VFD alarm code is for a 'minor' fault (like a communication error or a parameter conflict), try the manual first. If it's for a 'major' fault (like a power card failure or a blown IGBT), just tell me to order a new drive. Don't waste my time on a diagnosis that's going to cost the same as a replacement.'
The one thing everyone overlooks: the motor starter vs contactor debate
I know the search terms—people are looking for motor starter vs contactor comparisons when their VFD isn't working. Here's the thing: a VFD is an advanced motor starter. If you're seeing weird behavior on your drive, check if your motor starter (or contactor) is actually the one causing the issue. A bad contactor can chatter, which creates voltage spikes that a VFD doesn't like. It's not the VFD's fault—it's the hardware around it.
Scenario C: You're the admin responsible for the whole electrical ecosystem
This is me. I don't just order VFDs; I order everything from 36-volt battery chargers near me to PLC programs for custom automation. When a Danfoss VFD fails, I have to coordinate across three layers: the drive itself, the PLC it talks to, and the motor it drives.
Don't forget the battery charger
Random, I know. But I once had an issue where a VFD kept losing its parameter settings because the backup battery on the control card was dead. You'd think that's an alarm code. It's not. The drive just forgets everything when the power cycles. I had to order a 36-volt battery charger to test the battery, only to find out the battery itself wasn't replaceable on that model (FC 300 series, I think). Cost me $45 and an hour of frustration. The manual didn't mention it. I only figured it out by calling Danfoss tech support, where the guy said 'oh yeah, that's the internal capacitor not holding charge anymore. Just replace the drive.'
So my advice to other admins: if you're inheriting a system of used VFDs (and trust me, used VFDs are a whole different headache), order a backup battery for the control card. They're cheap, and they save you from re-parameterizing every time the power flickers.
PLC programs: the unknown variable
When your PLC program loses communication with the VFD, everyone blames the VFD. I've sent back two drives for 'not working' before I realized the issue was the RS485 wiring in the panel. The manual said to use a twisted pair. The panel builder used regular wire. The VFD was fine; the PLC was fine. The wiring was not.
If you're troubleshooting a VFD that won't talk to the PLC, don't swap the drive. Swap the cable. Check the termination. Double-check the baud rate in the PLC program and the VFD parameters. I guarantee you 9 times out of 10, it's a mismatch.
How to know which scenario you're in
Here's a quick checklist I use when someone calls me with a Danfoss VFD problem:
- Is the drive new? (Under 2 years old) → You're probably in Scenario A. Check the manual. Call support if the alarm code isn't obvious.
- Is the drive old? (Over 5 years old) → Scenario B. Estimate the repair cost. If it's over 50% of a new drive, replace it.
- Is the problem intermittent or related to communication? → Scenario C. Check wiring. Check PLC parameters. Check the battery/charge on the control card.
- Are you the one who has to process the order? → You're me. Download the manual, call Danfoss support with the model number ready, and always have a replacement on standby if the fix takes more than an hour.
Honestly, admin buyers don't get enough credit. We're the ones who know that the Danfoss VFD troubleshooting manual PDF is gold, but only if you actually read it before the drive breaks. I keep a printed copy of the FC 102 manual in my filing cabinet. It's not fancy. But when the line goes down at 2 PM and everyone's looking at me, I've got the answer.
