If you're searching for "Danfoss VFD not working in auto mode," I can tell you right now: there's no single fix. I've been through this four times now, and each one turned out to be a different problem. The answer depends on the scenario — and honestly, it also depends on who you are in the process.
I'm the office administrator for a 180-person manufacturing operation. I run procurement for facilities equipment — roughly $400K annually across a dozen or so vendors. I'm not the person who programs drives or reads parameter lists for fun. But when a drive goes down, I'm the one who has to figure out whether to call the electrician, the panel builder, or Danfoss tech support. That's a $500 decision if you get it wrong, and I've gotten it wrong.
The drive does have good documentation — the FC 102 programming guide alone runs 200+ pages, and Danfoss publishes the full parameter list on their site if you know the model. But documentation doesn't tell you which scenario you're in. That's the part you have to figure out yourself.
The Four Scenarios
Over the past 14 months, our facility has dealt with four distinct "won't go into auto" situations on three Danfoss drives (two FC 102s and one older VLT). Here's what I've learned about each.
Scenario 1: The Drive Is New and Has Never Run in Auto
This one's usually a commissioning issue, not a fault. The drive powers up, shows correct readings in hand-on mode, but won't switch to auto. The problem is almost always in the parameter setup — specifically, whether the drive is receiving a valid auto-mode command from the BMS or PLC.
What surprised me: the drive has an auto-mode "source" parameter, and if it's set to fieldbus but the fieldbus isn't communicating, the drive just quietly stays in whatever mode it was last in. It doesn't throw an alarm. It doesn't flash a warning. It just...doesn't respond to the switch command.
The fix in our case was to verify the auto-start signal at terminal 18 (a digital input) with a multimeter, then confirm the digital input parameter group (5-1x) matched whatever the panel builder specified. If you're not the one with the wiring diagram, this is where you get stuck.
Scenario 2: It Worked Fine Yesterday and Now Won't Go Auto
Our second case was intermittent — the drive would quit going to auto, then start working again if we cycled power. We spent a week chasing this before figuring out that one of the safety interlocks was dropping out on a loose connection. Not a drive fault at all — the drive was correctly doing what it was supposed to do.
That's the thing nobody tells you: "VFD not working in auto mode" often means "something upstream of the VFD isn't letting it start." The drive is the messenger, not the problem.
We traced it back to a $4 terminal block connection in the safety circuit that had vibrated loose. Total fix cost: $4 for a ferrule and a screwdriver. The week of downtime and service calls? Considerably more.
Scenario 3: External Interlock A60 Is Active
This is the one that sends a lot of people to Google. "Danfoss VFD external interlock A60" doesn't have a simple answer because A60 (as it appears on the LCP or in a fault log) can mean a few different things depending on drive model and firmware version. In our case, it meant the drive was reading an open circuit on its external interlock input.
The question everyone asks is "how do I clear the fault?" The better question is "what is the interlock telling me?"
The external interlock is usually a safety-related input — a door switch, an over-temp sensor, a pressure switch, or a customer-installed E-stop circuit. The drive isn't broken. It's doing exactly what it was told: don't run until the interlock closes.
Our first step now is always to check the interlock chain with the door open and a multimeter, before doing anything else. That alone has saved us at least two unnecessary service calls.
Scenario 4: You're Not the One With the Laptop
This is my default scenario, and honestly the one I suspect most buyers are in. You're not holding a laptop connected to the drive — you're coordinating between people who are. The purchase order is yours, the documentation is yours, and the vendor relationship is yours, but the technical fix is not.
If you're in this scenario, the single most useful thing you can do is know the model number, the fault code, and the exact moment the failure happened. "Danfoss FC 102, external interlock A60, first occurrence at 6:14 AM when the second-shift line restarted" gets you a tech response in minutes. "The drive isn't working" gets you a scheduled visit next Thursday.
I learned to keep a simple log: date, time, what changed (shift change, weather, production start), what the LCP displayed. This isn't a technician's job — it's a coordinator's job. And it makes a real difference.
How to Figure Out Which Scenario You're In
Here's the flow I use now. It's not foolproof, but it works more often than not.
Step 1: Check the timeline. Has this drive ever successfully run in auto? If no, you're in Scenario 1 (commissioning). If yes, you're in Scenario 2 or 3.
Step 2: Check the fault log. If you see A60 or "external interlock," you're in Scenario 3. Everything else goes to Scenario 2.
Step 3: Check who you are. If you're hands-on with the wiring diagram, work through the technical steps. If you're coordinating, work through the documentation and communication steps. Both matter. Neither is optional.
One more note on finding information, because this trips up a lot of people: documentation doesn't work the same way on every device. Figuring out the oil filter location on a GMC Acadia, learning how the control panel on a Maytag Quiet Series 200 actually navigates, figuring out how to open the control panel in Windows 11, or locating parameter group 5-1x in a Danfoss manual — these all feel like the same task in theory, but they're not. VFD documentation assumes you already know what a terminal is. Appliance documentation assumes you don't. Windows 11 documentation assumes you're already sitting at the right screen. Match your expectations to the document, or you'll waste a lot of time.
The Honest Truth About Getting It Right
Even after three years of managing these drives, I still second-guess myself on every failure. When I approved our last service call, I kept wondering if I was missing an obvious parameter issue — the service call cost us $850 for a diagnosis that took the tech about 20 minutes. But here's what I've come around to: getting the right answer on the first try is a quality issue. It affects downtime, it affects cost, and honestly, it affects how the plant manager sees my department.
We now keep a two-page "drive readiness" checklist in the shared drive — model numbers, firmware versions, parameter backups, a spare terminal block, and the on-call electrician's number. It's not glamorous, but it's the difference between a 20-minute fix and a 20-hour one. And in my experience, that difference is what people remember.
If you're in one of these four scenarios right now, my advice is simple: figure out which one you're in first, then work the answer that belongs to that scenario. Don't skip to the fix. The drive will still be there when you've figured out what it's actually telling you.
Rebecca Sloan
Rebecca Sloan is a power distribution and protection analyst specializing in circuit breakers, switchgear, contactors, fuses, surge protective devices, and coordination. She applies IEC 60947-2 breaker requirements, IEC 60269 fuse characteristics, and IEC 61643-11 tests while examining rated voltage, breaking capacity, time-current curves, selectivity, and prospective short-circuit current. She helps engineers and buyers compare protective devices against documented fault levels, installation conditions, maintenance access, and continuity priorities.