Danfoss VFD Alarm 60: A Troubleshooting Story About System Context

I got the draft in an email at 3:42 on a Tuesday. I remember the time because I had a quality review at 4:00, and the subject line said Final - Danfoss VFD Alarm 60 troubleshooting.

I sit on the quality side of a motion-control company. I don't repair drives on the plant floor every day, but I review the guides and knowledge base pages that tell customers what to do. Last year I reviewed about 180 documents. I rejected 12% of first drafts, usually for the same reason: not because the facts were wrong, but because the instructions were too clean.

A tidy draft and a nagging doubt

The draft started promisingly. Alarm 60, it said, is the Danfoss current-limit alarm in the drive series we were writing for. The drive detects output current above its configured limit and shuts down to protect the motor and itself. Correct so far. Then it gave three steps: check motor leads, check mechanical load, reset the drive and monitor.

I have a theory: a Danfoss VFD troubleshooting guide should not tell a customer to reset and hope. Alarm 60 is not an I am broken message. It is an I protected myself message. If the guide did not explain why the current limit was reached, a customer would reset it, watch it trip, and call back.

I flagged it and asked for the notes from our applications engineer. That is a step I have learned to take even when the writer swore it was final. The engineer came back with a support log and one story that changed my mind.

Alarm 60 is a symptom, not a verdict

We pulled 47 Alarm 60 tickets from the previous 12 months. Not a scientific sample, and every site is different, but the patterns were hard to ignore. Several cases were mechanical overloads. A couple were wrong current limit settings. One was a conveyor with a motor that definitely did not belong behind a Danfoss VFD.

The conveyor sat in a small packaging plant. The motor was an old single-phase induction motor, the capacitor-start kind rated for fixed mains frequency. Someone needed adjustable line speed, and a spare Danfoss VFD was in the maintenance cabinet. It looked like a clever way to avoid changing sprockets.

The drive kept hitting current limit. They checked fuses, terminals, and wiring, and all of it was fine. The problem was not a loose connection. It was a motor-drive mismatch. A standard VFD power stage creates a three-phase output that is normally paired with a three-phase AC motor. A single-phase induction motor like that one has auxiliary windings and in many cases phase-shifting capacitors sized for a fixed mains frequency. It is not a three-phase motor wearing a different label. Feeding it from a VFD can confuse it, overheat it, and push the drive into Alarm 60.

I still kick myself for nearly approving a document that would have told that customer to reset and keep watching. A reset is harmless once, but that support loop can go on until the motor fails. The right answer was to check the motor nameplate before touching the parameter list.

Servo, stepper, and the word motor was not enough

The rewrite forced a bigger conversation. One of our content requests was for a quick answer to what stepper motor fits the application. Another draft described a stepper as a low-cost servo. That is the kind of simplification that works in marketing and fails on a machine.

So what is a stepper motor? In basic terms, it is a brushless motor that moves in fixed increments. A typical hybrid stepper moves 1.8 degrees per step, so 200 full steps per revolution. It can run open loop, meaning no encoder is required for many positioning tasks. If the load stays within the motor torque curve, it is a simple and reliable positioning tool. If the load exceeds torque, it can lose steps and the controller might not know.

A robot servo motor is different. The word servo signals closed-loop control: commanded position or velocity is compared continuously with feedback from an encoder, resolver, or similar sensor. A robot arm lifting a load that changes is a classic case. The motor and drive need to correct in real time, not just spin at a set frequency.

Neither of those motors belongs on the same spec sheet as a Danfoss VFD unless the system was designed as a package. A VFD is a variable-speed drive for AC motors, not a universal motor controller. It is not an inferior servo drive. It is a different tool. Trying to force a robot servo motor or a small stepper into a VFD conversation usually means someone skipped the requirement definition.

What the published guide looked like

The version that went live was less pretty than the first draft. It still said to check motor connections and mechanical load. But it added questions at the top instead of conclusions.

• What type of motor is connected? Three-phase induction, single-phase induction, servo, or stepper?
• Is the motor nameplate compatible with the drive output?
• Has any component been added to the system since it last ran correctly?
• Is the mechanical load free to rotate across the full range of motion?

That four-item list looks obvious after the fact. It stopped the symptom-circling because it put the motor-drive system first. Alarm 60 is still the alarm, but the answer depends on the machine around it.

We also added a note about authority. According to the Danfoss documentation for the drive series in question, Alarm 60 is tied to current limit. I don't need to make it more dramatic. The part I needed to get right was what to do next. We started linking to the relevant Danfoss manual instead of paraphrasing it in a way that looked final.

This is a somewhat small view. My experience comes from support tickets, retrofits, and document reviews for a technical distributor. If you are an OEM designing a drive package from scratch, your process can be cleaner. If you are maintaining older equipment, expect more mismatches like the single-phase induction motor on a VFD. The old fixed-speed technology is not bad, but it is not automatically compatible with newer variable-speed technology.

What was best practice five years ago may not apply in 2025. The fundamentals have not changed: know the motor type, know the load, and treat an alarm as a clue instead of a nuisance. That is what I want our documents to teach.