If you've ever stood in front of a Danfoss VFD with a red alarm light on the keypad while the rest of the plant waits, you know the feeling. The display says alarm 60, the motor has stopped, and someone is already asking how long this will take.
In that moment, you have two options. Option A: reset it and run. Clear the trip, restart the drive, and assume it was a one-time event. Option B: diagnose it first. Read the fault log, inspect the load, and remove the cause before pressing start again.
This article compares those two approaches head-to-head. Same drive, same alarm, same situation — only the response changes. Let's call it reset-and-run versus diagnose-first.
A quick note on where I sit. I'm the person at our company who reviews Danfoss VFD returns and RMA requests before a replacement drive is approved. Roughly 200+ cases a year, for four years now. When I started, I expected failed drives to come back with obvious faults. Most come back with an alarm history and a story.
What alarm 60 is really telling you
On the Danfoss VLT drives we support, alarm 60 is the current-limit trip. The drive asked for more output current than the configured limit allows. After holding that limit for as long as the protection logic permits, it stopped the motor. Depending on the software version, you may see a warning first, then the alarm if the condition doesn't clear.
Here's the part that surprises most operators: alarm 60 is rarely a drive failure. The drive did exactly what it was designed to do — protect itself, the cable, and the motor from a condition that exists somewhere else.
From the outside, a VFD that trips on alarm 60 looks like a failed drive. The reality is that the drive may be the only healthy component in the whole chain.
Dimension 1: Time to restart
On pure restart speed, reset-and-run wins. Three keystrokes, and the motor is turning again. A machine that runs is worth more than a machine that is being examined. That's production math, not opinion.
But measure time over a week, not over a minute. If the cause is a loose motor connection or a supply voltage sag, the drive will trip again. And the second trip always costs more than the first. In my first year reviewing cases, I made the classic beginner mistake: reset a customer's drive, saw it run for about an hour, and then watched it trip on the same alarm. The five minutes I saved cost them a full shift.
Where this lands: reset-and-run is faster today. Diagnose-first is faster when the trip repeats. If you reset, treat that reset as the start of a diagnosis, not the end of one.
Dimension 2: What it actually costs
When alarm 60 keeps coming back, replacing the drive looks like the fast answer. But add up the real numbers: the replacement drive, the freight, the hours spent reprogramming parameters, and the cost of the original unit sitting on a shelf. Then add the possibility that the drive was never faulty in the first place. The same alarm follows the new drive, because the real cause was never addressed.
We didn't have a formal pre-approval checklist for returned drives until a batch of units came back from testing with no fault found. That was an expensive lesson in how often a “failed” drive is actually fine. Since 2022, every return request has to include the trip log and the field measurements. It's not bureaucracy. It's a $40 clamp meter and 15 minutes of a technician's time.
A proper field diagnosis costs an hour. An unnecessary drive replacement costs the drive itself, the freight, the reprogramming time, and the downtime. In most cases, the comparison isn't even close.
Where this lands: diagnose-first wins on cost in almost every scenario except a confirmed internal failure.
Dimension 3: What the fault log says
This is the dimension most people skip, and it's the one that changes minds. The VLT drive records trip history, alarm counters, and run time. The fault log tells you what the drive experienced. It does not tell you why.
We see units where alarm 60 appears again and again in the log, and someone already ordered a replacement before checking the first entry. Or worse, a parameter was changed without recording the original value, and the new setting became the cause of the next trip. If you know how to open Control Panel in Windows 11 and change a setting, do not treat a drive keypad the same way. A PC tolerates a casual click-around. A drive does not. In our shop the rule is simple: write down the original value before you change anything.
Where this lands: reset-and-run doesn't read the log. Diagnose-first builds its decision on it. The counterintuitive finding from our bench: the drive usually survives alarm 60; the process that ignores the log is what fails.
When the right move is to call a rep
Let me be clear: diagnose-first doesn't mean never calling for help. There are situations where a distributor or service rep should be involved right away:
- There's a burning smell, visible damage, or evidence of an internal short.
- The drive trips on alarm 60 even with the motor disconnected and a fresh start.
- The fault log shows internal faults alongside the current-limit trips.
- The drive is under warranty, and removing it yourself could void the coverage.
If you need a local service organization, use the Danfoss VFD rep locator to find the authorized rep for your area. And before you call, gather the facts: the alarm code, the fault log, the motor nameplate data, and the measured current in all three phases. A rep with data is far more useful than a rep who has to start from zero.
Same plot, different hardware
The pattern is not limited to industrial VFDs.
Take an off-grid power setup: a solar inverter and charge controller shut down at the same time, and the owner assumes both are dead. Usually, neither is. If the battery bus has a loose connection, voltage collapses under load and both units trip. Replacing the inverter would not have fixed the terminal.
The same story shows up in RV and marine cooling. A fault code on a Dometic control panel looks like a failed compressor controller. The real cause is often a voltage drop at the board when the compressor starts. Different hardware, same plot.
So which approach should you choose?
No single answer fits every site. Here's a practical way to decide:
- Reset-and-run is reasonable if this is the first trip in weeks, the fault log shows no cluster of similar trips, and you can monitor the current while the drive runs.
- Diagnose-first is the better call when the same alarm has appeared before, when the drive runs near its rated current, or when the process can't afford a surprise stop.
- Call a rep when your checks don't find a clear cause, or when the drive shows signs of internal damage.
The mindset that saves the most money is prevention over cure. Five minutes of checking beats five days of explaining why a drive failed — especially when the drive didn't.
Alarm 60 is not the enemy. It's information. Based on the hundreds of cases I've reviewed, technicians who treat it as a clue are the ones who don't see the same fault twice.
